Unable to boot Windows OS from ssd passthrough (inacessible boot device)

Namahe

New Member
Oct 30, 2024
2
0
1
Hello,

I'm new to Proxmox (more of a VMware guy so far but that might change :D), so here's what I did :

I converted my own Windows PC to a proxmox server by adding a new SSD, installing PVE and got it running pretty easily.

Now I have a dual boot Windows / PVE

I'm able to create VMs and so on, everything works perfectly, so far so good !


I wanted to see if I could use my Windows boot drive and use it in a VM, because I'd like to be able to use that Windows while Proxmox is running and avoid the whole shutdown / reboot to BIOS / change boot order / boot into windows.

It's not a fresh install at all, I've been using that Windows 10 for a few years now.


I'm struggling with this, I created the VM without a disk, and followed the guide to add the entire disk using it's ID like this :
qm set XXX -scsi0 /dev/disk/by-id/***********************


I installed the virtIO drivers in my OS as well, and made sure the boot order was scsi0 and nothing else.


Windows loads,then I get a BSOD "Inacessible Boot Device", and it goes into the troubleshoot menu.



I've been looking in the forum to see if someone had the same issue, and found some interesting posts tried a few things (OVFM instead of Seabios) but nothing fixed my issue.


SeaBios :



1730285194069.png

OVFM :
1730285031341.png
 
Windows does not handle changing from UEFI (OVMF) to (Sea)BIOS very well. In case of UEFI, the boot order and target is saved in the EFI variables (in a chip on the motherboard, which are stored on the virtual EFI disk in Proxmox). You probably need to do a boot repair for the Windows on the SSD from within the VM. I have no experience with that. It might also cause you to lose the dual boot you have now (and maybe destroy your data?).

How about installing a fresh Windows in a VM on a virtual disk and then (temporarily) connect the SSD to that VM (as you have now) and copy all relevant data (once)?
 
  • Like
Reactions: Namahe
Windows does not handle changing from UEFI (OVMF) to (Sea)BIOS very well. In case of UEFI, the boot order and target is saved in the EFI variables (in a chip on the motherboard, which are stored on the virtual EFI disk in Proxmox). You probably need to do a boot repair for the Windows on the SSD from within the VM. I have no experience with that. It might also cause you to lose the dual boot you have now (and maybe destroy your data?).

How about installing a fresh Windows in a VM on a virtual disk and then (temporarily) connect the SSD to that VM (as you have now) and copy all relevant data (once)?
Hi Leesteken,

I appreciate the fast response !

That's a good idea, I will try that out, I was also thinking about creating a new VM with an empty physical drive passed-through and install a new Windows and see if I can still dual boot after install.

I also might backup all my data and try to repair from the VM as you suggested.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!