This is more of a Windows Server 2022 problem and just hoping someone has some experience with this. Apologies if this is not in the right place or even welcome on this forum.
Okay so Bottom Line Up Front (BLUF)...43TB virtual disk (4x12 TB HDDs for media) offline and can't bring online because of "critical write failure" More deets down below.
Specs:
Proxmox VE 8.1.4 running
Windows server 22 VM with 12 cores, 48 GB Ram assigned to it.
MB: asrock x399 fatality
Processor: AMD Ryzen 2990wx (32 Cores, 64 threads. I got a screaming deal)
Processor Cooler: Noctua tower cooler
4TB M.2 SSD hosting OS's
RAM: 64 GB DDR4 3200
4x 12 TB HDDs passing through.
Back story as short as possible.
I disabled the Windows admin account which was running everything. Why? Because I ate a box of stupid that morning and wasn't paying attention when doing account clean up. So I reinstalled the VM (home lab so no biggy and I wasn't taking snapshots...yeah...dumb) and the virtual drive didn't show up. Figured out that I had to go into disk management and bring the disk back "online". After that, All was grand. Then the VM would crash and reboot once or twice every 24 hours. See screenshot attached server event details. I thought perhaps a bad virtual driver? I used the same Virtio files from the original install and downloaded the most recent updated virtio files to run driver updates. No joy. Now the virtual drive is offline and unable to bring online due to "critical write failure". Is it just coincidence that I perhaps have a bad drive at the same time I reinstalled my VM? Or does my VM have beef with my previous virtual disk from the previous install?
Thanks so much for the assistance!
Okay so Bottom Line Up Front (BLUF)...43TB virtual disk (4x12 TB HDDs for media) offline and can't bring online because of "critical write failure" More deets down below.
Specs:
Proxmox VE 8.1.4 running
Windows server 22 VM with 12 cores, 48 GB Ram assigned to it.
MB: asrock x399 fatality
Processor: AMD Ryzen 2990wx (32 Cores, 64 threads. I got a screaming deal)
Processor Cooler: Noctua tower cooler
4TB M.2 SSD hosting OS's
RAM: 64 GB DDR4 3200
4x 12 TB HDDs passing through.
Back story as short as possible.
I disabled the Windows admin account which was running everything. Why? Because I ate a box of stupid that morning and wasn't paying attention when doing account clean up. So I reinstalled the VM (home lab so no biggy and I wasn't taking snapshots...yeah...dumb) and the virtual drive didn't show up. Figured out that I had to go into disk management and bring the disk back "online". After that, All was grand. Then the VM would crash and reboot once or twice every 24 hours. See screenshot attached server event details. I thought perhaps a bad virtual driver? I used the same Virtio files from the original install and downloaded the most recent updated virtio files to run driver updates. No joy. Now the virtual drive is offline and unable to bring online due to "critical write failure". Is it just coincidence that I perhaps have a bad drive at the same time I reinstalled my VM? Or does my VM have beef with my previous virtual disk from the previous install?
Thanks so much for the assistance!
