EMERGENCY Storage pools removed when updating to Server 2019

[Warwick_Tech]

Hi all,

 

Mini emergency; When doing an in-place update to server 2019 from 2012R2 my Virtual Host PC has lost its VM storage (D: drive)

 

I can login to the RAID manager (megaRAID Storage Manager) but cannot see the disk in disk management or storage.

 

My other VM machine that is configured identically (still on 2012R2) suggests no issues, but I'm reluctant to use powershell as I know the data is there, I just need to mount the drive -

 

Can anyone help? I've never seen this before, but assume it's because windows doesn't like drives more than several TB's (?)

 

Screenshots attached

 

[psydii]

If you have a production host down, I would get the school credit card and open a call with Microsoft. Its about £240 and they will get you up again, with the backup position that if they can't nobody could.

 

https://support.microsoft.com/en-us/supportforbusiness/productselection

[Warwick_Tech]

If you have a production host down, I would get the school credit card and open a call with Microsoft. Its about £240 and they will get you up again, with the backup position that if they can't nobody could.

 

https://support.microsoft.com/en-us/supportforbusiness/productselection

 

Sooo, apparantly they say it's because this was a locked drive (?) something to do with tier storage to prevent data theft?

 

TBh this is getting odd so I may now just restore the VHD's from backup - It's been one of those days!

[Warwick_Tech]

So Thursday Update;

 

Seems rebuilding the server was the only option, which is odd as all my other servers (10+) updated perfectly fine (Except SIMS, I'm not stupid enough to update that)

 

As it turns out I was able to restore the VHD's directly from Windows Server Backup after a full rebuild, so it was a good test of our emergency response systems.

 

I'll share some of the links and info that helped so others can find it if they encounter a simlar problem.

https://american-boffin.com/2019/01/17/virtual-machines-do-not-boot-after-moving-from-windows-server-2012-r2-to-windows-server-2019/

https://support.microsoft.com/en-gb/help/2502233/restored-hyper-v-virtual-machines-won-t-start

https://support.storagecraft.com/s/article/Hyper-V-Virtual-machines-won-t-boot-after-host-machine-restore?language=en_US

https://tunecomp.net/restore-hyperv-virtual-machine-from-vhdx-file-windows-10-windows-server/

https://www.tenforums.com/tutorials/56436-see-if-hyper-v-virtual-machine-generation-1-generation-2-a.html

 

All I can say too, is make sure your backups are up to date, running and recoverable!

 

Good luck out there.

 

P.S if anyone knows how to create a cachecaid raid I'm all ears as I don't have a monkeys and skipped that step; didn't even know my servers had SSD's....