Vicenarian
Active Member
- Reaction score
- 19
Ok, so I've got a custom-built (not by me) PC here that had:
- a SSD boot drive
- a Seagate 2 TB hard drive for data
- another identical Seagate 2 TB drive for data (mirror of the first 2 TB disk)
The mirror was created in Windows 8 disk management originally. Both original 2 TB disks were 4K sector-size disks. Anyway, the second 2 TB disk failed, customer bought an identical disk, exact same model #/storage capacity (which is supposed to be 4K sector-size), but when I go to add the new disk as a mirror of the original 2 TB, I get the error "All disks holding extents for a given volume must have the same sector size", which basically means mirroring won't work because the new disk doesn't have the same physical sector size.
When I run fsutil fsinfo ntfsinfo DRIVELETTER from the command prompt, the original 2 TB disk shows "Bytes per physical sector: 4096", but the replacement disk shows "Bytes per physical sector: 512"
So, what's going on? The store that sells the disk says the disk is definitely a 4K sector disk (Seagate ST2000DM001), and the Seagate website confirms this.
All drives are connected to the motherboard's built-in SATA headers.
I haven't had a chance to check the disk from an offline OS, but if both disks are identical hardware-wise, and are supposed to both have a 4K physical sector size, why is Windows detecting a physical sector size of 512 bytes for the new 2 TB disk?
- a SSD boot drive
- a Seagate 2 TB hard drive for data
- another identical Seagate 2 TB drive for data (mirror of the first 2 TB disk)
The mirror was created in Windows 8 disk management originally. Both original 2 TB disks were 4K sector-size disks. Anyway, the second 2 TB disk failed, customer bought an identical disk, exact same model #/storage capacity (which is supposed to be 4K sector-size), but when I go to add the new disk as a mirror of the original 2 TB, I get the error "All disks holding extents for a given volume must have the same sector size", which basically means mirroring won't work because the new disk doesn't have the same physical sector size.
When I run fsutil fsinfo ntfsinfo DRIVELETTER from the command prompt, the original 2 TB disk shows "Bytes per physical sector: 4096", but the replacement disk shows "Bytes per physical sector: 512"
So, what's going on? The store that sells the disk says the disk is definitely a 4K sector disk (Seagate ST2000DM001), and the Seagate website confirms this.
All drives are connected to the motherboard's built-in SATA headers.
I haven't had a chance to check the disk from an offline OS, but if both disks are identical hardware-wise, and are supposed to both have a 4K physical sector size, why is Windows detecting a physical sector size of 512 bytes for the new 2 TB disk?
