Help me with RAID 1 mirroring issue

I got an issue with using a new drive in an existing RAID 1 configuration. I am trying to mirror drive E onto the new drive D in Windows 10 via Disk Management. I am getting the All disks holding extents for a given volume must have the same sector size, and the sector size must be valid error. Both are 5TB WD blue drives. It's very odd. Drive E has 4648.88GB while Drive D has 4657.37GB. I read up on physical sector size, but don't know how to fix/get RAID 1 to work. Any ideas how to fix?

Code:

C:\Windows\system32>fsutil fsinfo ntfsinfo e:
NTFS Volume Serial Number :        xxxxxxxxxxxxxx
NTFS Version   :                   3.1
LFS Version    :                   2.0
Number Sectors :                   0x0000000048a37efa
Total Clusters :                   0x0000000048a37efa
Free Clusters  :                   0x0000000014276237
Total Reserved :                   0x0000000000000000
Bytes Per Sector  :                4096
Bytes Per Physical Sector :        4096
Bytes Per Cluster :                4096
Bytes Per FileRecord Segment    :  4096
Clusters Per FileRecord Segment :  1
Mft Valid Data Length :            0x0000000031400000
Mft Start Lcn  :                   0x00000000000c0000
Mft2 Start Lcn :                   0x0000000000000002
Mft Zone Start :                   0x000000001d69b460
Mft Zone End   :                   0x000000001d69c0c0
Max Device Trim Extent Count :     4294967295
Max Device Trim Byte Count :       0xffffffff
Max Volume Trim Extent Count :     62
Max Volume Trim Byte Count :       0xffffffff
Resource Manager Identifier :     4A072CC7-9BF1-11E5-9BDD-001FBC11AD24

C:\Windows\system32>fsutil fsinfo ntfsinfo d:
NTFS Volume Serial Number :        xxxxxxxxxxxxxx
NTFS Version   :                   3.1
LFS Version    :                   2.0
Number Sectors :                   0x00000002462bcfff
Total Clusters :                   0x0000000048c579ff
Free Clusters  :                   0x0000000048c438ba
Total Reserved :                   0x0000000000000000
Bytes Per Sector  :                512
Bytes Per Physical Sector :        512
Bytes Per Cluster :                4096
Bytes Per FileRecord Segment    :  1024
Clusters Per FileRecord Segment :  0
Mft Valid Data Length :            0x0000000000040000
Mft Start Lcn  :                   0x00000000000c0000
Mft2 Start Lcn :                   0x0000000000000002
Mft Zone Start :                   0x00000000000c0000
Mft Zone End   :                   0x00000000000cc820
Max Device Trim Extent Count :     0
Max Device Trim Byte Count :       0x0
Max Volume Trim Extent Count :     62
Max Volume Trim Byte Count :       0x40000000
Resource Manager Identifier :     56A623DA-B8D3-11E5-9BE6-001FBC11AD24

 

All disks holding extents for a given volume must have the same sector size, and the sector size must be valid error. Both are 5TB WD blue drives

Thats what I'm seeing too, looks like the new drive was formatted differently than the old drive that expired and the drive its to be copied from.
Go into format for the new drive and reformat to the same specifications of the drive thats going to disk copy to it. NTFS formatting has several variants, match each one to the same format.

Cheers
3Fees

 

I thought that was not possible? Physical sector sizes are hardware related, so they cannot be changed. At least what others are saying though.

 

C:\Windows\system32>fsutil fsinfo ntfsinfo e:
Bytes Per Sector : 4096
Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 4096
Clusters Per FileRecord Segment : 1

C:\Windows\system32>fsutil fsinfo ntfsinfo d:

Bytes Per Sector : 512
Bytes Per Physical Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0

512KB sectors is pre 2011, modern is 4K, I like both at 4K or both at 512

Different sector size discussion on 512/4K drives:

http://superuser.com/questions/3673...a-software-raid-1-with-different-sector-sizes



look here on making a dynamic disk ect.

http://answers.microsoft.com/en-us/...1/08f79d67-c05f-4fca-96ea-766e81d13a56?auth=1

See if those work.

It does seem your raid controller is having a problem, from icewolf

"4k sectors are typically only an issue if you clone the drives. Cloning from a 512-byte sector drive to a 4k makes things a little funky, and you will experience speed issues. The alignment of drives is really only needed when you do cloning of different sector sized drives. and even then, its arguable thats its really necessary.

I'm unaware of how any controllers handle the different sector sizes. I always thought sectors were more handled by the drive itself and any sectors the OS or likewise would see are technically virtual. Not sure where the controller falls in that.

Assuming you build the RAID array on 4k drives, all installations are done using 4k drives, and any images are also built on 4k drives. there is no worries to be had to my knowledge. If you tried to replace a 512 drive with a 4k drive in a RAID it might act funny, if you try to image a 512 server and install it onto the new 4k array you may have issues as well. RAID controllers may be able to compensate, idk, never had any experience with this.

Worst case scenario, there are some alignment tools available, usually from the drive manufacturer, that will align the drive. It's a pretty similar process to a defragmentation. Drive basically gets rewritten to properly populate the sectors.

I figure the issue arises where you'd have each 4k sector only populated with 512 bytes, where it'd be more efficient to have the 4k sectors properly filled. Drive has to read the entire sector so might as well have it read 4k bytes of data and not 512 bytes of data and the rest blank data then move on to the next sector. you'd have to read 8 sectors instead of 1 to get the same data. (all speculation based on what I guess the alignment issue to be)"


To be on the safe side get drives that match in every respect.