Booting is stuck, no files in /etc/pve, how to mount it?

[michaeljackson]

When I’m booting my Proxmox server it is stuck at Loading internal ramdisk. Rescue boot also is stuck, so I booted live cd Debian.

It had happened after I made PCIE passthrough to one of my VMs.

For now I mounted PVE-root to Debian, but in /etc/pve there isn’t any files.
My idea is to revert adding PCIE device in VM config file. I have access to proxmox’s database, but I don’t know how to mount it. As far I know it is in the pve folder.

Please let me know, if there is a way to access the file and edit it or I need to install proxmox again.

 

[simonhoffmann]

The DB file is just an sqlite3 database. You can access it with any tool that supports SQLite, like the sqlite cli command

 

[leesteken]

My idea is to revert adding PCIE device in VM config file.

If you did not change anything else and the only problem is that the VM starts autmatically, then it might be easier to temporarily disable IOMMU/VT-d/AMD-Vi in the motherboard BIOS to prevent the VM from starting (and you can edit the VM configuration from the Proxmox host).
Or maybe press e in the boot loader menu and add amd_iommu=off intel_iommu=off to boot Proxmox once with IOMMU disable (to prevent the VM from starting).

 

[michaeljackson]

The DB file is just an sqlite3 database. You can access it with any tool that supports SQLite, like the sqlite cli

How to mount it, so I can edit VM config file? Or I need to edit db?

 

[michaeljackson]

If you did not change anything else and the only problem is that the VM starts autmatically, then it might be easier to temporarily disable IOMMU/VT-d/AMD-Vi in the motherboard BIOS to prevent the VM from starting (and you can edit the VM configuration from the Proxmox host).
Or maybe press e in the boot loader menu and add amd_iommu=off intel_iommu=off to boot Proxmox once with IOMMU disable (to prevent the VM from starting).

No success, last lines of recovery mode boot until it stucks:

 

[leesteken]

No success, last lines of recovery mode boot until it stucks:

If changing the BIOS setting did not help, then you must have changed more than just the VM config. What else did you change that could break Proxmox? Or maybe your system has other problems that prevent booting? I cannot read the last line(s) of the screen in your photo.

 

[michaeljackson]

If changing the BIOS setting did not help, then you must have changed more than just the VM config. What else did you change that could break Proxmox? Or maybe your system has other problems that prevent booting? I cannot read the last line(s) of the screen in your photo.

I didn’t change anything that could broke it. A few months ago I also tried to passthrough AMD IGPU, but the system didn’t boot. Then the simple command repaired it and I gave up. Now I’m trying to passthrough PCIe network interface.

The last lines are:

VFIO - User Level meta-driver version: 0.3
[6.867337] systemd-journald[357]: Received client request to flush runtime journal.
Starting ifupdown2-pre.service
- Helper to synchronize boot up for ifupdown...
[6.875685] systemd-journald(357]: File /var/log/journal/db9051697b14301a1b5c9blee545ec8/system. journal corrupted or uncleanly shut down, renaming and replacing.

 

[michaeljackson]

Rescue boot is similar; VFIO, sysusers, sys-kernel-config.mount, journald and freeze