Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, October 24, 2014 10:38 PM
Hello everyone
The current setup: I have two 1TB disks, both with 512 byte sectors (no AF, 512e, ...). Disk 1 contains two partitions (System Reserved and C:) and lots of free space, disk 0 was emptied completely (DISKPART CLEAN) and is now an empty, initialized, dynamic disk:
What works:
- Creating a new mirrored (or spanned, or striped) partition on disk 0 and 1, when using disk 0's context menu.
What doesn't work:
- Creating a new mirrored (or spanned, or striped) partition on disk 0 and 1, when using disk 1's context menu. The relevant context menu items are all grayed out.
- Adding a mirror on disk 0 for an existing partition on disk 1. The error message is "All disks holding extents for a given volume must have the same sector size, and the sector size must be valid."
There are reports of similar problems all over this and other forums. Usually the OP tries to mix 512 & 4k sector disks, which isn't the case here.
Cheers,
Simon
All replies (18)
Tuesday, October 28, 2014 8:26 AM
Hi Simon,
I have done a test on my Windows Server 2008 R2 and have a same issue with you. The issue is not occurred on Windows Server 2012.
Please refer to the thread below to troubleshoot the issue:
Error - All disks holding extents for a given volume must have the same sector size, and the sector size must be valid.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/dc113f43-61d9-4929-afe9-fe3536ea937d/error-all-disks-holding-extents-for-a-given-volume-must-have-the-same-sector-size-and-the-sector?forum=winserverfiles
Best Regards,
Mandy
Tuesday, October 28, 2014 1:03 PM
Hi Mandy
Thanks for your reply.
Can you reproduce the issue with the preview?
I'm not sure how the troubleshooting thread applies here:
- First, that thread also states that people think this behavior is a bug. So maybe it actually is something MSFT engineers should look into?
- The mirroring works in principle. I CAN CREATE MIRRORED PARTITIONS *if* I create a new one, starting from disk 0. So it CANNOT be an alignment/sector size issue. Right?
Cheers,
Simon
Wednesday, November 5, 2014 4:38 PM
I just reinstalled the preview, onto disk 0. Now I have the same problem, but in the opposite direction:
- Creating mirrored volumes, starting form disk 1, works.
- Adding mirrors to volumes on disk 0, or creating volumes, starting from disk 0, does not work.
This looks really buggy.
Simon
Thursday, November 6, 2014 6:21 AM
Hi Simon,
I have done a test on the preview and the issue doesn’t reproduce on the preview. Based on my research, I found that the issue could due to the "Bytes Per Physical Sector". On my Windows Server 2008 R2 the "Bytes Per Physical Sector" of drives display "Not Supported". Please run the command "fsutil fsinfo ntfsinfo drive_letter" to check if the "Bytes Per Physical Sector" mismatch.
You could try to use different disks to test if the issue is due to disk architecture. For a workaround, you could backup the data, format both disks and then try to create a mirror using empty disks.
For more detailed information, please refer to the thread below:
Error Adding Mirror to Boot Volume - Sector Size?
http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/error-adding-mirror-to-boot-volume-sector-size/f5729d4c-629b-4978-9de4-faae382060c4?page=3
Best Regards,
Mandy
Thursday, November 6, 2014 11:04 AM
Hi Mandy
It feels as if you didn't read the OP. As the title already states, both disks are 512b-sector disks. And as you can see clearly in the second screenshot, creating mirrored partitions *IS* possible. So that's not it.
Cheers,
Simon
Thursday, July 2, 2015 7:57 AM
Hi Simon,
I have the same problem, did you find a solution?
Ciao
Claudio
Thursday, July 2, 2015 8:56 AM | 1 vote
No, unfortunately not. It's support as usual on these forums... :(
Thursday, July 16, 2015 7:23 PM
Can you temp give these drives a letter and run the following?
fsutil fsinfo ntfsinfo DriveLetter
What is the Bytes per Sector setting? How were these drives initially partitioned? Was it some partitioning utility not Disk Management? The other option to consider is the use of drive utilities to check. For example, Seagate used to have a DriveDetect.exe utility that would tell you the physical sector sizes. You would have to get with the vendor of the drives to see if they have such utilities available.
Thanks, John Marlin Microsoft Server Beta Team
Monday, August 3, 2015 8:48 AM | 1 vote
Hi John
I'm surprised by your questions: It feels as if you didn't read any posts in this thread. Mandy already asked about the physical sector size and I already explained twice that the disks are 512b-physical-sector disks. As you can see clearly in the second screenshot, creating mirrored partitions *IS* possible. So that's not it.
I used Disk Management and diskpart (CLEAN) for my experiments.
Cheers,
Simon
Wednesday, September 9, 2015 8:52 PM
Hi all,
I have the same issues on Windows 10.
3 HDs
HD0: System
HD1 (1TB): 1 Volume mit 900 GB und Daten. 100 GB unallocated
HD2 (1TB - neue HD): 1TB unallocated
Creating a new mirrored volume with 8 GB on drives HD1 and HD2 works.
Adding a mirrored volume to the HD1 900 GB volume on HD2 does not work.Error message: "All disks holding extents for a given volume must have the same sector size, and the sector size must be valid."
Tried and searched extensively - help much apreciated
Cheers Unitedeurope
Friday, September 11, 2015 8:40 PM
Hi Simon,
I tried to repro this issue on my system that is running Windows Server build 10533 and could not repro the error message "All disks holding extents for a given volume must have the same sector size, and the sector size must be valid." when adding a mirror on Disk 0 for an existing partition on Disk 1.
What works:
1.Creating a new mirrored (or spanned, or striped) partition on disk 0 and 1, when using disk 0's context menu.
Answer: Yes, because the Disk 0 is unallocated
What doesn't work:
1.Creating a new mirrored (or spanned, or striped) partition on disk 0 and 1, when using disk 1's context menu. The relevant context menu items are all grayed out.
Answer: Yes, because part/all of Disk 1 is allocated
2.Adding a mirror on disk 0 for an existing partition on disk 1. The error message is "All disks holding extents for a given volume must have the same sector size, and the sector size must be valid."
Answer: Issue does not repro on build 10533.
The disk I used have the same sector size.
C:\WINDOWS\system32>fsutil fsinfo ntfsinfo c:
NTFS Volume Serial Number : 0x9c5836b458368d50
NTFS Version : 3.1
LFS Version : 2.0
Number Sectors : 0x000000000fc34fff
Total Clusters : 0x0000000001f869ff
Free Clusters : 0x0000000001820396
Total Reserved : 0x00000000000055b0
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 : 0x00000000107c0000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x00000000009ceb60
Mft Zone End : 0x00000000009d8060
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 : 1094E9B0-03DB-11E5-ADBF-EFB93E36E01D
C:\WINDOWS\system32>fsutil fsinfo ntfsinfo g:
NTFS Volume Serial Number : 0x364834f04834b10b
NTFS Version : 3.1
LFS Version : 2.0
Number Sectors : 0x00000000747057ff
Total Clusters : 0x000000000e8e0aff
Free Clusters : 0x000000000e8d3e29
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 : 94B39B1E-57F1-11E5-981E-BC305BADD269
Regards,
Steven Graves
Windows Beta Support Team
Saturday, September 12, 2015 8:41 AM
What doesn't work:
1.Creating a new mirrored (or spanned, or striped) partition on disk 0 and 1, when using disk 1's context menu. The relevant context menu items are all grayed out.
Answer: Yes, because part/all of Disk 1 is allocated
Are you serious? I obviously tested with fresh, clean, empty disks each time. It doesn't work with *unallocated* disks.
2.Adding a mirror on disk 0 for an existing partition on disk 1. The error message is "All disks holding extents for a given volume must have the same sector size, and the sector size must be valid."
Answer: Issue does not repro on build 10533.The disk I used have the same sector size.
Thanks Steven for testing this. It is the case that it sometimes works and sometimes doesn't. On some of my servers it works with some disks too. Maybe try some more combinations of disks? (Manufacturers, ...)
Simon
Wednesday, September 16, 2015 2:41 PM
You're welcome Simon.
Yes, it could be a combination of HDD's used in the servers. Please ensure the HDD firmware is up to date.
Here are a couple of screenshots I took when repro'ing the issue on my system.
In the first screenshot I selected Disk 0, which is Unallocated, and the options are available.
In the second screenshot, I selected Disk 2 which is Allocated and the options are greyed because all or some of the disk is Allocated.
Steven Graves
Windows Beta Support Team
Wednesday, September 16, 2015 2:51 PM
Great, it seems to work on your server - But it doesn't work on my server. We already knew that it's working on most servers.
Your reply is not very useful. I would've expected that you would want to collect some diagnostic info? Details you need to know? A tool I can run? Maybe it's a bug in Windows? Maybe you could improve the error message?
I'm sorry that I sound so negative, but it's frustrating to get non-answers a year after the initial post. I hope you can understand.
Cheers,
Simon
Monday, October 10, 2016 6:35 AM
Were you ever able to find a solution?
I'm having the same problem another year later. Win10 build 14942. With a little twist...
I set up a mirror using 2 similar drives. The geometry DID NOT MATCH as disk 2 is 512/sector and disk 3 is 4096/sector.
Cleaned both drives first.
The mirror was created and formatted NTFS. Copied test data to the mirror and allowed sync to complete.
I'm testing for catastrophic failure, so I took disk 2 out and cleaned it. Reinstalled disk 2 and booted, simulating a hot spare
The mirror no longer existed, but the data was still visible on disk 3 (which was left untouched in the PC).
I removed the mirror. This left me with a formatted partition on one drive (disk 2) and a fully unallocated disk 3.
Attempting to add a mirror to the volume brings up the error message "All disks holding..." Noting there's extra space between same and sector.
So... format disk 3 as NTFS w/ 4k sectors (default). Copy the data to disk 3. CLEAN DISK 2.
Attempt to add a mirror to the volume on disk 3... same error.
How can this happen when the mirror WAS WORKING 5 hours ago?
I can clean both drives... but how are we supposed to trust this stuff if a drive actually fails? It would be faster to recover to a new unmirrored drive from backup.
Hoping you found a better solution than starting fresh with two clean drives.
Monday, October 10, 2016 8:11 AM
Update: Breaking the Mirror and running fsutil fsinfo ntfsinfo <drive letter>: shows that both my drives are recognized as having Bytes Per Physical Sector = 512. (below)
Previous runs showed disk 3 as 4096.
Monday, October 10, 2016 12:56 PM
Nope, I did not find a solution.
Or: My solution was to stop using Disk Mirroring. Maybe try Storage Spaces, if it's not the system volume that you want to mirror?
Sunday, May 27, 2018 2:54 PM
i got similar issue on win10 1511. The error message is misleading. fsutil fsinfo shows both hard disk is 512.
Finally. I backup the data on Disk1, remove the existing dynamic volumns on Disk1, and create a single dynamic volume on Disk1 again. Then i successfully created a mirror with the context menu on the new volumn on disk1.