Proxmox VE doesn't boot after I installed a new SSD on the computer

[a22728033]

I have a desktop PC which had one SSD and one HDD. Arch Linux is installed on the SSD and Proxmox VE is installed on the HDD.I configured the Web UI of Proxmox VE and had one VM autostart with GPU passthrough to it.
Today I installed a new SSD on the computer, and UEFI can detect 2 SSDs and 1 HDD properly. There is no problem when booting into Arch Linux. When booting into Proxmox VE from UEFI, the bootloader starts without problems. But when I select the Proxmox VE and boot into the system, it turns out to be black screen.
I tried to access the Web UI, but to no avail. Proxmox can't even connect to the router. Please can someone help me with this issue?

 

[Dunuin]

Did you install a M.2 SSD? Because before adding/removing any PCIe devices you should disable any autostart of VMs with passthrough and be ready to have a display and keyboard attached to the PVE host. Because when adding/removing PCIe devices the adresses of the PCIe devices might change and then a wrong device might be passed into the VM crashing your system. And NIC names might change, so SSH and webUI won't be available.

 

[a22728033]

Yes, I installed a M.2 SSD. So the only way to solve it is to reinstall the new SSD? Because SSD slot is on the back of the motherboard, reinstalling it will cause much trouble, therefore I want to prevent it.

 

[leesteken]

Disable auito-start of VMs that use passthrough (or temporarily use amd_iommu=off or intel_iommu=off kernel parameters in the boot menu to prevent those VMs to start), install additional PCIe devices like NVMe SSDs and check the new PCI IDs with lspci and change the configuration files of the VMs or use the Proxmox web GUI to fix the PCI Devices before rebooting. Depending on which PCI ID the SSD got, some PCI(e) devices have the same ID and some are shifted one up (in hexadecimal).
EDIT: Don't forget to manually edit /etc/network/interfaces (on the Proxmox host console) because network devices get their name from their PCI ID. Use ip a to find the new names, which have a higher number (+1) in the middle of their name.

 

[a22728033]

Disable auito-start of VMs that use passthrough (or temporarily use amd_iommu=off or intel_iommu=off kernel parameters in the boot menu to prevent those VMs to start), install additional PCIe devices like NVMe SSDs and check the new PCI IDs with lspci and change the configuration files of the VMs or use the Proxmox web GUI to fix the PCI Devices before rebooting. Depending on which PCI ID the SSD got, some PCI(e) devices have the same ID and some are shifted one up (in hexadecimal).
EDIT: Don't forget to manually edit /etc/network/interfaces (on the Proxmox host console) because network devices get their name from their PCI ID. Use ip a to find the new names, which have a higher number (+1) in the middle of their name.

Using amd-iommu=off enables me to access the terminal on the monitor, but Proxmox VE doesn't detect the keyboard and still can't connect to the router (For some reason I temporarily use Wifi network instead of Ethernet). I passthrough USB devices to VMs via PCI passthrough, too. Is it relevant?

 

[leesteken]

and still can't connect to the router (For some reason I temporarily use Wifi network instead of Ethernet).

I added this to my previous post: manually edit /etc/network/interfaces (on the Proxmox host console) because network devices get their name from their PCI ID. Use ip a to find the new names, which also changed by one. But I guess you can't do that without a keyboard. ..

Using amd-iommu=off enables me to access the terminal on the monitor, but Proxmox VE doesn't detect the keyboard

I passthrough USB devices to VMs via PCI passthrough, too. Is it relevant?

Maybe it does not detect the keyboard because the USB controller is passed through. It is not actually passed through because of the amd_iommu=off and not starting the VM, but maybe you early bind it to vfio-pci in a file in the /etc/modprobe.d/ directory?

Either try other USB ports (maybe not all USB controllers are passed through?) or remove the new SSD device and disable the early binding of at least one USB controller. Without both network and keyboard, I don't see how you could resolve this. Did your keyboard come with a USB-PS/2 converter-plug and does your motherboard have a PS/2 port (might require a reboot)?

 

[komoe]

Hi Leesteken , I am Newbies Using Proxmox VE-7.4-3 . I am same Problem M2 SSD Issuse . If i insert M2-SSD, I cannot access to Proxmox Web UI.
Could you help me How to upgrade M2-SSD and to get access Proxmox Web UI.

 

[leesteken]

Hi Leesteken , I am Newbies Using Proxmox VE-7.4-3 . I am same Problem M2 SSD Issuse . If i insert M2-SSD, I cannot access to Proxmox Web UI.
Could you help me How to upgrade M2-SSD and to get access Proxmox Web UI.

Adding (or removing) PCI(e) devices, like NVMe SSDs, can change the PCI ID or other PCI(e) devices. Feel free to contact your motherboard/BIOS manufacturer to complain about this. The default network device name (of Proxmox and other Linux) is determined by the PCI ID. If that changes (check with ip a, you need to adjust the Proxmox network configuration accordingly. Lot's of threads about this on this forum.

 

[komoe]

Noted , I will try that. Thanks

 

[komoe]

Now okay to access for Web UI. I check and update in nano /etc/network/interfaces. Network Card Name Error. Thanks you for your Guide.

 

[komoe]

Hi , Leesteken ,Now I have Anoter Error in CT , I tested with Exteranal-HDD to use LVM to create One CT. and then I removed that External HDD to use Another Case.I forgot to destroy CT Creating with External HDD Storage. Now My Problem is that i can not detroy that CT ID 109. Could you show me how to destroy ?

 

[Dunuin]

Hi , Leesteken ,Now I have Anoter Error in CT , I tested with Exteranal-HDD to use LVM to create One CT. and then I removed that External HDD to use Another Case.I forgot to destroy CT Creating with External HDD Storage. Now My Problem is that i can not detroy that CT ID 109. Could you show me how to destroy ? View attachment 52666

best way: connect your external HDD and destroy it.
Not so great way: manually destroy those LV on the external HDD and then delete the "/etc/pve/lxc/109.conf" nd remove VMID 109 from your backup jobs etc.

 

[komoe]

Hi, Dunuin , Sorry for late reply. Thanks you for your Help. I chose to delete file 109.conf.

I have relative problem. whenever i make create CT using Proxmox Helper Script, it happen error because of vmbr 0 . i already remove vmbr 0. Because When I added New Storage SSD M2 at PCI Slot , Some Network Interface Name is change. I edit nano /etc/network/interfaces for vmbr 1 is Access for Web View to Proxmox. Can you give me suggestions to solve that Error. ? Thanks again for your time.