No GUI after adding 5th drive

[chebrutto]

I have been using Proxmox VE for about 2 years (still a lot to learn and still feel like Noob) I have 2 SSDs and 2 HDDs installed. My OS is on 1 SSD and the others are passthroughs to VMs and LXCs. I have been trying to add another HDD but every time I do when I reboot the GUI stops working. I can access the server directly (don't have SSH setup). I have tried with 2 different HDDs with the same results. I wipe the HDD and then add the UUID to fstab like I have always done. I am not sure what I am missing or what to share to give the best information to get help here...Thanks in advance!
EDIT: Added pics of the error I am seeing when I connect physically to server

 

[BobhWasatch]

Did you check if the name of your NIC changed? Sometimes adding PCI devices causes that. Use "ip a" to check.

 

[chebrutto]

Hey @BobhWasatch,
Thanks for the quick reply! I didn't think to check the NIC. Here is the ip a before and a pic of it after and also the commented out fstab. I edited the original post to include pics of the error. I think the NIC is the same but, like I said, I've got alot to learn.
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether 30:5a:3a:54:94:70 brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 30:5a:3a:54:94:70 brd ff:ff:ff:ff:ff:ff
inet 192.168.86.99/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::325a:3aff:fe54:9470/64 scope link
valid_lft forever preferred_lft forever
8: tap102i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
link/ether 8e:70:e9:a5:aa:d0 brd ff:ff:ff:ff:ff:ff
9: veth100i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether fe:0a:a5:a4:9f:95 brd ff:ff:ff:ff:ff:ff link-netnsid 1
10: veth101i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether fe:99:fc:87:6b:80 brd ff:ff:ff:ff:ff:ff link-netnsid 2
11: veth103i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr103i0 state UP group default qlen 1000
link/ether fe:cd:31:c7:3a:82 brd ff:ff:ff:ff:ff:ff link-netnsid 3
12: fwbr103i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ae:71:05:29:84:d9 brd ff:ff:ff:ff:ff:ff
13: fwpr103p0@fwln103i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 16:dc:37:37:a7:b1 brd ff:ff:ff:ff:ff:ff
14: fwln103i0@fwpr103p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr103i0 state UP group default qlen 1000
link/ether ae:71:05:29:84:d9 brd ff:ff:ff:ff:ff:ff
19: veth104i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i0 state UP group default qlen 1000
link/ether fe:db:a5:d4:97:36 brd ff:ff:ff:ff:ff:ff link-netnsid 0
20: fwbr104i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 9a:93:c9:2e:40:7d brd ff:ff:ff:ff:ff:ff
21: fwpr104p0@fwln104i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether e2:75:d4:1e:95:a9 brd ff:ff:ff:ff:ff:ff
22: fwln104i0@fwpr104p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i0 state UP group default qlen 1000
link/ether 9a:93:c9:2e:40:7d brd ff:ff:ff:ff:ff:ff

and fstab with commented out lines to make GUI work...

# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
UUID=C3EB-6DE4 /boot/efi vfat defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
UUID=bfa61e35-83c3-4176-88f8-7a60353a751d /media/mount ext4 defaults 0 2
UUID=1b0faee8-f1f6-458b-832d-39d34b1c70d3 /media/nvr ext4 defaults 0 2
#UUID=712a4c45-e57f-4283-9053-e9920a9a123c /media/storage vfs defaults 0 2
#UUID=5fb428c9-bb20-4bad-964f-430d7bfc8f801c1175b-e0c6-4a05-87c9-de444c7b5bc82 /media/general ext4 defaults 0 2

 

[BobhWasatch]

Maybe use the code tags next time. That's pretty hard to read!

It looks like your network is up so that's not the problem. The error in your first post refers to /media/general. That UUID in fstab doesn't look right, are you sure it is correct? It is way longer than normal. Mabye two got concatenated together?

 

[esi_y]

I have been using Proxmox VE for about 2 years (still a lot to learn and still feel like Noob) I have 2 SSDs and 2 HDDs installed. My OS is on 1 SSD and the others are passthroughs to VMs and LXCs. I have been trying to add another HDD but every time I do when I reboot the GUI stops working.

You are simply booting to emergency node (from the screenshots that you added), so that's why it's not working.

After such boot, take away the drive, boot normally and please attach the result of:

journalctl -b -1 > attach.log

 

[chebrutto]

Agreed! maybe I'll setup SSH just so I don't have to use pics for this! You were correct, two UUIDs were concatenated together because i apparently can't copy and paste well. I used blkid to fix it using sdc3 as my UUID however still got nearly the same error just a different UUID listed.

/dev/mapper/pve-root: UUID="e3752e32-bf48-4aa5-899e-ce4ca054cec6" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--104--disk--0: UUID="4b1c8535-58ee-4fe4-a4db-7c367e7c3b15" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdd2: UUID="C3EB-6DE4" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="33bd9ecc-a047-4da6-9bb3-76274345c890"
/dev/sdd3: UUID="sy9e0c-eUjU-eLa6-bRoH-17AN-ob1E-RfGNtR" TYPE="LVM2_member" PARTUUID="ac08498e-e9a5-4175-adee-96cacb9c5973"
/dev/sdb1: UUID="1b0faee8-f1f6-458b-832d-39d34b1c70d3" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e774e0e3-a2ed-9c4d-9cb3-d84fda9c3931"
/dev/mapper/pve-vm--101--disk--0: UUID="1224411d-2600-4c4b-9bc2-a60a2fb519f8" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-swap: UUID="abbe0c12-41e2-4975-8ae2-88f975545621" TYPE="swap"
/dev/sde1: UUID="bfa61e35-83c3-4176-88f8-7a60353a751d" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="8b2af532-6ed7-41b2-9314-bded786fca9a"
/dev/mapper/pve-vm--100--disk--0: UUID="ea2d81a6-26df-4453-af3f-e6130e342a7b" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdc2: UUID="E8ED-D20E" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="7bd2c33a-e662-4802-adba-df16d17c43b8"
/dev/sdc3: UUID="01c1175b-e0c6-4a05-87c9-de444c7b5bc8" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="bad71188-2222-458a-91c5-8a9c30fb7c39"
/dev/sda1: LABEL="Nextcloud" UUID="12490171234494651608" UUID_SUB="11165015422472800226" BLOCK_SIZE="4096" TYPE="zfs_member" PARTLABEL="storage" PARTUUID="712a4c45-e57f-4283-9053-e9920a9a123c"
/dev/loop1: TYPE="squashfs"
/dev/sdd1: PARTUUID="4d64ba55-2908-4189-be68-75c084eadff3"
/dev/mapper/pve-vm--102--disk--1: PTUUID="fba6c32f-b85c-4d96-b81d-0818e5da585d" PTTYPE="gpt"
/dev/loop0: TYPE="squashfs"
/dev/sdc1: PARTUUID="261323f0-95b2-4a3b-bb71-ae33e218fdf4"

 

[chebrutto]

You are simply booting to emergency node (from the screenshots that you added), so that's why it's not working.

After such boot, take away the drive, boot normally and please attach the result of:

journalctl -b -1 > attach.log

I wasn't able to get journalctl -b -1 > attach.log to work but did get journalctl -b -1 to work...should I post that? It's crazy long....

 

[esi_y]

I wasn't able to get journalctl -b -1 > attach.log to work but did get journalctl -b -1 to work...should I post that? It's crazy long....

Well, I am sure it did work, it simply saved the output into a file called attach.log that you were supposed to attach here.

If your mail is set up correctly you could just mail it out to yourself:
mail -s "PVE bootlog" your@email.address < attach.log


EDIT: The attach file button here is bottom left (at least I always search for it).

What @BobhWasatch was saying you should select the pasted snippets and apply the "inline code" or "code block" to them with the toolbar:


Or you can use [ CODE ] [ /CODE ] tags. But that's only good for short outputs like the above was:

 

[esi_y]

/dev/mapper/pve-root: UUID="e3752e32-bf48-4aa5-899e-ce4ca054cec6" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--104--disk--0: UUID="4b1c8535-58ee-4fe4-a4db-7c367e7c3b15" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdd2: UUID="C3EB-6DE4" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="33bd9ecc-a047-4da6-9bb3-76274345c890"
/dev/sdd3: UUID="sy9e0c-eUjU-eLa6-bRoH-17AN-ob1E-RfGNtR" TYPE="LVM2_member" PARTUUID="ac08498e-e9a5-4175-adee-96cacb9c5973"
/dev/sdb1: UUID="1b0faee8-f1f6-458b-832d-39d34b1c70d3" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e774e0e3-a2ed-9c4d-9cb3-d84fda9c3931"
/dev/mapper/pve-vm--101--disk--0: UUID="1224411d-2600-4c4b-9bc2-a60a2fb519f8" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-swap: UUID="abbe0c12-41e2-4975-8ae2-88f975545621" TYPE="swap"
/dev/sde1: UUID="bfa61e35-83c3-4176-88f8-7a60353a751d" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="8b2af532-6ed7-41b2-9314-bded786fca9a"
/dev/mapper/pve-vm--100--disk--0: UUID="ea2d81a6-26df-4453-af3f-e6130e342a7b" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdc2: UUID="E8ED-D20E" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="7bd2c33a-e662-4802-adba-df16d17c43b8"
/dev/sdc3: UUID="01c1175b-e0c6-4a05-87c9-de444c7b5bc8" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="bad71188-2222-458a-91c5-8a9c30fb7c39"
/dev/sda1: LABEL="Nextcloud" UUID="12490171234494651608" UUID_SUB="11165015422472800226" BLOCK_SIZE="4096" TYPE="zfs_member" PARTLABEL="storage" PARTUUID="712a4c45-e57f-4283-9053-e9920a9a123c"
/dev/loop1: TYPE="squashfs"
/dev/sdd1: PARTUUID="4d64ba55-2908-4189-be68-75c084eadff3"
/dev/mapper/pve-vm--102--disk--1: PTUUID="fba6c32f-b85c-4d96-b81d-0818e5da585d" PTTYPE="gpt"
/dev/loop0: TYPE="squashfs"
/dev/sdc1: PARTUUID="261323f0-95b2-4a3b-bb71-ae33e218fdf4"

 

[chebrutto]

Well I have not been able to get my email setup to get the file but did figure out that my syntax while creating the file system on the new drives was wrong and so I was mounting drives without a file system (not sure how I was getting UUID without FS). Creating FS on new drives fixed the issue.