I’ve been running a new Unraid (lastest 7x) server solid for almost a year with zero issues. Recently I decided to set up a Bazzite gaming VM with GPU passthrough. That’s when everything went sideways.

Here’s the pattern:

• Unraid boots fine
• Array starts fine
• Docker is fine
• The moment I try to start the Bazzite VM (or even open the VM tab sometimes), Unraid throws “Your flash drive is corrupted or offline”
• The flash drive gets remounted read‑only
• VM won’t start, and the array can’t be stopped cleanly

At first I assumed the USB stick was dying. I replaced it with a brand‑new one, transferred the license, restored config, and… the exact same thing happened. So it’s not the USB.

I reset the BIOS to defaults. Same issue.

In my case, the crash only happened when the VM services loaded, which explains why the array and everything else looked normal until that moment.

Disabling VMs in Settings → VM Manager instantly stopped the issue. Array starts clean, no flash errors. Re‑enabling VMs brings the problem back. So I am gussing it's tied to passthrough, not the USB.

i've tried rebuilding the VM from scratch using the simplest possible config (Q35‑7.1, OVMF, SATA vdisk, GPU only, no USB controller passthrough, no TPM). but that starts and my entire unraid server becomes slow and unusable...

Posting this in case someone knows how to resolve this “flash corrupt” message only when starting a VM with GPU passthrough.

12600k
128gb Mem
2070Super
30tb Z2
3tb Arrary (mixed SSD, NvME)

Sounds like you're passing through the wrong device, and that yeets the USB away from Unraid.

If you did something like update the OS or BIOS inbetween that can change the PCI addresses so that what was your GPU is now the USB controller... Always should remove all binds before doing that then set them up again afterwards.

Some 2070S have USB-C ports, you didn't plug your Unraid boot device to that, right?

Edited April 19Apr 19 by Kilrah

First, I should be honest... I blindly followed an LLM becuase setting this up was out of my comfort zone and now I am in this mess... lol

I did indeed update my BIOS in doing this. It was recommended i turn off Resize Bar and a bunch of other settings to make the passthrough better for the VM. then i noticed my BIOS was 2 versions old, so updated it.

I never thought about removing the Binding, just to confirm that is all those check marks items in Tools > System Devices?

I did not plug my new boot drive into my 2070 :) It's happily sitting in the furthest spot from my exhust.

infering from your post... I should unbind the 2070super, reboot... rebind reboot and try again?

Unbind any bound system devices, make sure to disable autostart for the VMs if enabled.

Reboot, rebind, and also select the proper device in the VM template again as it might have changed.