[Bug Report] Hyper-V Server 2019 Command Line Tools access to the Volume Manager API [Repeatable]

%3CLINGO-SUB%20id%3D%22lingo-sub-2560312%22%20slang%3D%22en-US%22%3E%5BBug%20Report%5D%20Hyper-V%20Server%202019%20Command%20Line%20Tools%20access%20to%20the%20Volume%20Manager%20API%20%5BRepeatable%5D%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2560312%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20found%20a%20bug%20in%20Hyper-V%20Server%202019.%20This%20may%20exist%20in%20Server%20Core%202019%2C%20but%20I've%20wasted%20my%20entire%20day%20on%20this%20already%20and%20do%20not%20care%20to%20try.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20Environment%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3EHyper-V%20Server%202019%20hosts%2C%20all%20identical%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3ESynology%20NAS%20running%20SMB%203%2C%20current%20DSM%206%20release%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EDynamically%20Expanding%20VHDX%20files%20on%20a%20Synology%20SMB%20share%20-%203TB%20each.%20One%20formatted%20to%20ReFS%2C%20the%20other%20to%20NTFS%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EA%20script%20is%20designed%20to%20mount%20the%20VHDX%20and%20Windows%20Server%20Backup%20operations%20occur%20on%20the%20VHDX%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EWent%20to%20run%20a%20one-off%20backup%20this%20morning%20to%20the%20ReFS%20disk%20and%20it%20wouldn't%20run.%20%22ERROR%20-%20The%20specified%20backup%20location%20could%20not%20be%20found%20or%20is%20not%20a%20supported%20backup%20storage%20location.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETried%20to%20create%20a%20NTFS%20formatted%20VHDX%20(assuming%20it%20was%20a%20ReFS%20issue)%20on%20the%20HV%20system%2C%20the%20hypervisors%20could%20create%20the%20VHDX%2C%20could%20online%20it%2C%20initialise%20it%20and%20create%20the%20partition%2C%20but%20could%20not%20format%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECreated%20the%20VHDX%20off-machine%2C%20moved%20it%20over%2C%20attempted%20the%20backup%20and%20it%20failed%20with%20the%20same%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFully%20patched%20the%20HV%20install%20to%202021-07%2C%20same%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERan%20diskpart%20list%20disk%20-%20OK%3CBR%20%2F%3ERan%20diskpart%20list%20partition%20-%20OK%3CBR%20%2F%3ERan%20diskpart%20list%20volume%20-%20drive%20mount%20point%20(B%3A)%20not%20shown%2C%20volume%20missing%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGo%20to%20cmd%2C%20can%20browse%20and%20search%20B%3A%5C%20fine%3CBR%20%2F%3EGo%20to%20PowerShell%20can%20browser%20and%20search%20B%3A%5C%20fine%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUse%20Get-Disk%2C%20Get-Partition%20and%20Get-Volume%20in%20PowerShell%20-%20All%20OK%2C%20B%20drive%20is%20displayed%20as%20expected%20in%20PowerShell's%20WMI%20calls%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERan%20wbadmin%20get%20disks%20which%20can%20see%20the%20disk%20but%20gives%3A%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3EVolumes%3A%20There%20are%20no%20volumes%20on%20the%20disk%20or%20Windows%20is%20unable%20to%20retrieve%20volume%20information.%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EArduously%20De-installed%20the%20following%20KB's%2C%20rebooting%20after%20each%3C%2FP%3E%3COL%3E%3CLI%3E%3CP%3E5003258%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E4494174%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E4601558%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E4589208%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E4580422%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E5003646%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E5003171%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E5001342%3C%2FP%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3EIt%20all%20worked%20again%20after%20the%20removal%20of%20%222021-04%20Cumulative%20Update%20for%20Windows%20Server%202019%20for%20x64-based%20Systems%20(KB5001342)%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInstalled%20%222021-03%20Cumulative%20Update%20for%20Windows%20Server%202019%20for%20x64-based%20Systems%20(KB5001638)%22%20-%20all%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInstalled%20%222021-04%20Cumulative%20Update%20Preview%20for%20Windows%20Server%202019%20for%20x64-based%20Systems%20(KB5001384)%22%20-%20broken%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERoll%20back%20to%202021-03%2C%20all%20fine%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20appears%20that%20something%20got%20into%20the%202021-04%20branch%20and%20made%20it%20into%20production%20which%20has%20broken%20the%20API%20for%20reading%20the%20disk%20information.%20It%20is%20doing%20this%20on%20all%20of%20my%20Hyper-V%20Server%202019%20installs.%20All%20of%20the%20installs%20work%20when%20rolled%20back%20to%202021-03.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20Windows%20Server%202019%20GUI%20instances%20that%20I%20have%20are%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3Enot%3C%2FEM%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eexhibiting%20this%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20full%20and%20more%20comprehensive%20write-up%20can%20be%20found%20at%3A%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fwww.c-amie.co.uk%2Ftechnical%2Fhyper-v-server-2019-cannot-backup-to-or-format-a-vhdx-drive%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fwww.c-amie.co.uk%2Ftechnical%2Fhyper-v-server-2019-cannot-backup-to-or-format-a-vhdx-drive%3C%2FA%3E%2F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20else%20seen%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2560312%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2560453%22%20slang%3D%22en-US%22%3ERe%3A%20%5BBug%20Report%5D%20Hyper-V%20Server%202019%20Command%20Line%20Tools%20access%20to%20the%20Volume%20Manager%20API%20%5BRepeatable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2560453%22%20slang%3D%22en-US%22%3E%3CP%3ESounds%20like%20you%20have%20some%20good%20documentation%20and%20steps%20there.%20Support%20for%20confirmed%20bugs%20is%20always%20free%20so%20for%20immediate%20help%20you%20can%20start%20a%20case%20here%20with%20product%20support.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.serviceshub.microsoft.com%2Fsupportforbusiness%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ESupport%20for%20business%20(microsoft.com)%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2561246%22%20slang%3D%22en-US%22%3ERe%3A%20%5BBug%20Report%5D%20Hyper-V%20Server%202019%20Command%20Line%20Tools%20access%20to%20the%20Volume%20Manager%20API%20%5BRepeatable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2561246%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51719%22%20target%3D%22_blank%22%3E%40Dave%20Patrick%3C%2FA%3Ethanks%20for%20your%20comments.%20I%20tried%20to%20be%20thorough.%3C%2FP%3E%3CP%3EActually%20getting%20a%20bug%20report%20to%20Microsoft%20these%20days%20is%20a%20bit%20of%20a%20nightmare.%20I%20will%20try%20what%20you%20suggest.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20also%20reported%20it%20to%20the%20Feedback%20Hub%20now%20at%3A%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FAAd8q27%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FAAd8q27%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I have found a bug in Hyper-V Server 2019. This may exist in Server Core 2019, but I've wasted my entire day on this already and do not care to try.

 

My Environment

  • Hyper-V Server 2019 hosts, all identical

  • Synology NAS running SMB 3, current DSM 6 release

  • Dynamically Expanding VHDX files on a Synology SMB share - 3TB each. One formatted to ReFS, the other to NTFS

  • A script is designed to mount the VHDX and Windows Server Backup operations occur on the VHDX

Went to run a one-off backup this morning to the ReFS disk and it wouldn't run. "ERROR - The specified backup location could not be found or is not a supported backup storage location."

 

Tried to create a NTFS formatted VHDX (assuming it was a ReFS issue) on the HV system, the hypervisors could create the VHDX, could online it, initialise it and create the partition, but could not format it.

 

Created the VHDX off-machine, moved it over, attempted the backup and it failed with the same error.

 

Fully patched the HV install to 2021-07, same error.

 

Ran diskpart list disk - OK
Ran diskpart list partition - OK
Ran diskpart list volume - drive mount point (B:) not shown, volume missing

 

Go to cmd, can browse and search B:\ fine
Go to PowerShell can browser and search B:\ fine

 

Use Get-Disk, Get-Partition and Get-Volume in PowerShell - All OK, B drive is displayed as expected in PowerShell's WMI calls

 

Ran wbadmin get disks which can see the disk but gives:

Volumes: There are no volumes on the disk or Windows is unable to retrieve volume information.

Arduously De-installed the following KB's, rebooting after each

  1. 5003258

  2. 4494174

  3. 4601558

  4. 4589208

  5. 4580422

  6. 5003646

  7. 5003171

  8. 5001342

It all worked again after the removal of "2021-04 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5001342)".

 

Installed "2021-03 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5001638)" - all fine.

 

Installed "2021-04 Cumulative Update Preview for Windows Server 2019 for x64-based Systems (KB5001384)" - broken again.

 

Roll back to 2021-03, all fine again.

 

It appears that something got into the 2021-04 branch and made it into production which has broken the API for reading the disk information. It is doing this on all of my Hyper-V Server 2019 installs. All of the installs work when rolled back to 2021-03.

 

All Windows Server 2019 GUI instances that I have are not exhibiting this issue.

 

A full and more comprehensive write-up can be found at: https://www.c-amie.co.uk/technical/hyper-v-server-2019-cannot-backup-to-or-format-a-vhdx-drive/

 

Anyone else seen this?

4 Replies

Sounds like you have some good documentation and steps there. Support for confirmed bugs is always free so for immediate help you can start a case here with product support.

Support for business (microsoft.com)

 

 

 

@Dave Patrickthanks for your comments. I tried to be thorough.

Actually getting a bug report to Microsoft these days is a bit of a nightmare. I will try what you suggest.

 

I have also reported it to the Feedback Hub now at: https://aka.ms/AAd8q27

 

Thanks,

Yeah... it's still a nightmare. That link just gets stuck in a "you have now been signed out" Azure loop of death and is demanding a credit card to do anything. So what I have done will have to suffice.

Cheers,

Sounds correct, a credit card will be required to secure the support contract, but confirmed bugs are not charged.