Inaccesible boot device

B

Borja

New Member
Nov 7, 2023
7
0
1
I have migrated a computer with Windows 2022 Standard from VMWare ESXI to Proxmox and when I try to boot it I get the error 'inaccessible boot device'. Before doing the migration I had uninstalled the VMWare Tools from the server. I have tried changing the disk from SATA to IDE and still the same thing happens. I have been reading dozens of pages that talk about this problem and I have consulted with some AI but no matter how hard I try I can't get it to boot, can anyone help me?

The funny thing is that the other day I imported another server with similar characteristics and it booted without problems.
 
I have done the migration with the wizard that incorporates Proxmox connecting before directly to VMWare ESXI. I have tried several times to do it, in some occasions I have tried uninstalling previously the VMWare Tools, installing before the migration the VirtIO drivers. In all cases the result has been the same.

I put screen with the details of the last migration.
 

Attachments

  • Import.PNG
    Import.PNG
    21.8 KB · Views: 7
Borja said:
uninstalling previously the VMWare Tools, installing before the migration the VirtIO drivers
Click to expand...
it's not mandatory.
VirtIO SCSI driver cannot be "pre-installed", it's installed only within Windows running on PVE when a SCSI drive is present / attached.
That's why the recommended way is boot once with sata, to post install VirtIO SCSI driver with a dummy temporary SCSI drive attached.

You can try the alternative "offline" VirtIO SCSI driver injecting / adding :
G

[SOLVED] Post in thread 'Migrating a VMware Windows 2019 to Proxmox using Veeam'

Jaques said:
>drvload vioscsi.inf
Click to expand...
Yes AFAIK that only loads the driver - but doesn't install it to your Windows install.

I believe you need to use the dism command to actually install the drivers. See an example here through Windows Recovery.
 
Last edited:
Hi, I have followed the steps in the link, the problem I see is that the hard disk volumes do not have letters assigned (I put the image), I have booted the main disk as SATA and I have added a 1Gb SCSI dummy disk. When I load the driver with drvload I can see that it has loaded the SCSI disk but I can't run DISM because I have no letter assigned.
 

Attachments

  • diskpart.PNG
    diskpart.PNG
    8.8 KB · Views: 4
I assigned the letter C: to the drive where the Windows folder is (first image), I executed the DISM command to install the vioscsi driver and I got the error of image 2. I tried to remove the Hidden and Read-Only attributes of Volume 1 and then it installed the driver. When I reboot the machine again I get Windows Boot Manager saying that the device is not connected or cannot access (third image).
 

Attachments

  • 1.PNG
    1.PNG
    9.2 KB · Views: 11
  • 2.PNG
    2.PNG
    8.2 KB · Views: 11
  • 3.PNG
    3.PNG
    23.2 KB · Views: 11
Hello, I have followed the steps you have told me, I attach screenshots of the results. Thank you very much.
 

Attachments

  • 5.PNG
    5.PNG
    122.9 KB · Views: 7
  • 4.PNG
    4.PNG
    116.7 KB · Views: 5
  • 3.PNG
    3.PNG
    102.2 KB · Views: 6
  • 2.PNG
    2.PNG
    12.1 KB · Views: 6
  • 1.PNG
    1.PNG
    28.5 KB · Views: 7
  • 6.PNG
    6.PNG
    66.7 KB · Views: 7
If you can see the disk below, then there seems to be a problem with the bcd.

dism /image:c: /add-driver /driver:d:¥amd64

I guess I need to fix it with bcdboot or bootrec or something.

I don't think it's a driver thing as it also occurs with sata and ide.
 
Last edited:
uzumo said:
I don't think it's a driver thing as it also occurs with sata and ide.
Click to expand...
indeed. it's something else.
I don't think it's boot manager as we can see Windows Boot Manager in #9

Weird thing is VirtIO SCSI Driver offline installation was successful in #11 (so screenshots of Log are pointless) where in #9 not.
Try now detach/attach boot disk as scsi.

By the way, it's not a PVE scope, it's job for a Windows guy and not over a forum as there is endless of combinations.
 
_gabriel said:
By the way, it's not a PVE scope, it's job for a Windows guy and not over a forum as there is endless of combinations.
Click to expand...
I agree. It is no longer something to be discussed here.
_gabriel said:
indeed. it's something else.
I don't think it's boot manager as we can see Windows Boot Manager in #9
Click to expand...
I believe it is a setting in Windows Boot Manager, so it is necessary to rewrite it with bootrec or bcdboot to the correct content.
 
You must log in or register to reply here.
Top Bottom