[SOLVED] Emergency mode after nvme u.2 port change halp please

rsvg

Member
Mar 23, 2021
20
0
6
43
So, I’m new to lvms and lvs and vgs and so on. I worked my way through a Debian buster install and then proxmox on top of it because my zfs had a feature that required it vs normal install.

But I believe I was able to replicate the normal disk setup. i have two partitions on my nvme, boot and the lvm. One volume group, “pve”, and then three logical volumes, root mapped to /, swap, and data mapped to /var/lib/vz.

Anyway, all was fine and great, as always love proxmox, but I decided to put a video card in it and the sff-8639 port I had my nvme plugged into cannot be occupied while the video card is installed.
I figured if I just swap it to the other sff-8639 port I can switch the boot drive in bios, and all will be fine.

well, a couple hours of emergency mode later, and I’m considering making a custom heat sink for the video card just to free up the initial port so I don’t hose my system.

I haven’t done anything yet except for check the /etc/fstab which shows that the boot efi is using a uuid, I’m assuming that’s why I’m still able to boot at all. Emergency mode says it can’t find the pve-data.

I don’t know how to point pve-data, pve-swap, and pve-root to nvme0n1 instead of nvme1n1 where it originally was. My reading tells me that you don’t use uuids in fstab. So I’m pretty confused.
 
I actually solved this by running fsck on the nvme after returning it to the previous port. I had a pcie riser cable laying around so I’m just gonna call this solved for now. Happy to hear the right way to do it though.