VMs will not boot 'The sector size of the physical disk on which the virtual disk resides is not supported.'
-
Sunday, December 06, 2009 2:08 AM
Hello all,
I'm running Hyper-V on Windows Server 2008 R2 in a lab environment.
In order to increase disk performance I have added another spindle to the the data disk RAID0 where I house my VMs. The previous configuration included 2x1TB drives in a RAID0. Now, I have 3 disks in a RAID0.
After restoring the VMs including permissions, I can no longer boot them. I recieve the following errors:
[Window Title]
Hyper-V Manager[Main Instruction]
An error occurred while attempting to start the selected virtual machine(s).[Content]
'VSVR01' failed to start.Microsoft Emulated IDE Controller (Instance ID {83F8638B-8DCA-4152-9EDA-2CA8B33039B4}): Failed to Power on with Error 'The sector size of the physical disk on which the virtual disk resides is not supported.'
Failed to open attachment 'D:\Hyper-V\Virtual Machines\VSVR01\VSVR01 DISK0_8B702ACC-15A2-4F1C-BD89-D1EEC07B7DAE.avhd'. Error: 'The sector size of the physical disk on which the virtual disk resides is not supported.'
Failed to open attachment 'D:\Hyper-V\Virtual Machines\VSVR01\VSVR01 DISK0_8B702ACC-15A2-4F1C-BD89-D1EEC07B7DAE.avhd'. Error: 'The sector size of the physical disk on which the virtual disk resides is not supported.'
[Expanded Information]
'VSVR01' failed to start. (Virtual machine ID 569A6DF8-4217-42C6-A809-0E7B03BF2A2E)'VSVR01' Microsoft Emulated IDE Controller (Instance ID {83F8638B-8DCA-4152-9EDA-2CA8B33039B4}): Failed to Power on with Error 'The sector size of the physical disk on which the virtual disk resides is not supported.' (0xC03A001D). (Virtual machine ID 569A6DF8-4217-42C6-A809-0E7B03BF2A2E)
'VSVR01': Failed to open attachment 'D:\Hyper-V\Virtual Machines\VSVR01\VSVR01 DISK0_8B702ACC-15A2-4F1C-BD89-D1EEC07B7DAE.avhd'. Error: 'The sector size of the physical disk on which the virtual disk resides is not supported.' (0xC03A001D). (Virtual machine ID 569A6DF8-4217-42C6-A809-0E7B03BF2A2E)
'VSVR01': Failed to open attachment 'D:\Hyper-V\Virtual Machines\VSVR01\VSVR01 DISK0_8B702ACC-15A2-4F1C-BD89-D1EEC07B7DAE.avhd'. Error: 'The sector size of the physical disk on which the virtual disk resides is not supported.' (0xC03A001D). (Virtual machine ID 569A6DF8-4217-42C6-A809-0E7B03BF2A2E)
[^] Hide details [Close]
Note - this also occurrs on VMs that do not have linked snapshots/migration points.
Originally, I configured the 3TB RAID0 as a GPT Partition style volume so I could overcome the 2TB limitation of doing it MBR. I suspected that this may have been the rootcause, so I deleted the volume, configured it MBR, restored the VMs including permissions, and still get the same error.
Thanks
Jerry
jerryabouelnasr
Answers
-
Monday, December 07, 2009 9:47 AMModerator
Hi,
Base on my experience, if you want to use a partition larger than 2TB, you have to use dynamic MBR or dynamic GPT. By the way, I have seen some issue related to the block size of the partition. The solution is to ensure the LUNS are created with a block size of 512bytes - some people had been created with a block size of 4096 bytes - NTFS & clustering were working fine, but NO VHD operations would succeed.
Vincent Hu
- Marked As Answer by Vincent HuMicrosoft Contingent Staff, Moderator Tuesday, December 15, 2009 3:05 AM
All Replies
-
Sunday, December 06, 2009 6:48 PMIt turned out that configuring the 3TB array with a 2TB MBR Partition, with the remaining space left as unallocated, was not sufficient.
After reconfiguring the array with a 2TB space allocation, repartitioning MBR, restoring the VMs and permissions, the VMs were able to boot successfully.
So, 'The sector size of the physical disk on which the virtual disk resides is not supported' apparently means.......that 'The sector size of the physical disk on which the virtual disk resides is not supported.'
jerryabouelnasr -
Monday, December 07, 2009 9:47 AMModerator
Hi,
Base on my experience, if you want to use a partition larger than 2TB, you have to use dynamic MBR or dynamic GPT. By the way, I have seen some issue related to the block size of the partition. The solution is to ensure the LUNS are created with a block size of 512bytes - some people had been created with a block size of 4096 bytes - NTFS & clustering were working fine, but NO VHD operations would succeed.
Vincent Hu
- Marked As Answer by Vincent HuMicrosoft Contingent Staff, Moderator Tuesday, December 15, 2009 3:05 AM
-
Monday, December 14, 2009 7:10 AMModerator
· Hi,
Have you tried the suggestion? I want to see if the information provided was helpful. Your feedback is very useful for the further research. Please feel free to let me know if you have addition questions.
Best regards,
Vincent Hu
-
Tuesday, December 29, 2009 2:28 AM
> The solution is to ensure the LUNS are created with a block size of 512bytes <
Could you explain what you mean. The RAID array (AMD AHCI) has a physical block size of 1024 bytes. There is no option for me to configure this. NTFS will not permit a sector size less than 1024 on this device. Is there some way to configure the sector size of the LUNS in the VM to match the sector size of the physical device. This is going to be a serious problem with the current size of disks > 1.5 TB. -
Wednesday, December 22, 2010 7:50 AMThe sector size is physically set by the manufacturer - we can't just change it. I can't believe Hyper-V R2 doesn't support 4k advanced format drives??? When is this oversight going to be patched??
-
Thursday, April 28, 2011 4:58 PM
Here is a KB article about this issue in case anyone needs the details http://support.microsoft.com/kb/2515143
- Proposed As Answer by pesospesos Thursday, April 28, 2011 5:01 PM
-
Thursday, April 28, 2011 5:01 PMYa, unfortunately MS just wrote a big long article that can be summed up as "you can't use 4k sector disks for VHD files." Ridiculous.
-
Thursday, April 28, 2011 5:45 PMYep, it seems that way. The odd thing is it appears to be actually a physical disk issue it seems that even persists when being used with RAID controller that masks the true drive.
-
Thursday, April 28, 2011 5:51 PM
ya the actual physical sector size doesn't get masked I don't think.
for now I have set up my 3 TB USB3 drive as a raw physical disk that is passed through to the VM - at least the 2008r2 guest can use that. hope they get this sorted before too long.
-
Friday, April 29, 2011 6:59 AM
I don't have any of these disks, but I did see that Jose Barreto has a blog post about it with several links to other articles.
http://blogs.technet.com/b/josebda/
Bill -
Friday, April 29, 2011 12:08 PM
Link to exact article. The interesting thing is that he indicates that windows doesn't support 4K at all, but I don't think that is true. I think there are only certain scenarios that have difficulty.
-
Friday, February 10, 2012 8:50 PM
I met the same problem - RAID, constructed on the SB950 (AMD SouthBridge), sector size was 1024b, which is not compatible with the Hyper-V.
As a solution, I create 2 RAID5 arrays, on the same set of disks (look at the picture), the combined 2 RAID arrays into 2 disk in Windows.
Disk combined in Windows:
.png){kind=spacer}
