Can not boot! Failed to start AppArmor initialization

[gusto]

I use The last Proxmox.
I wanted to add in LXC a HDD /dev/sdd
I followed the instructions https://forum.proxmox.com/threads/container-with-physical-disk.42280/
And after the reboot system does not work.

[FAILED] Failed to start apparmor initialization
See systemctl status apparmor.service

I can sign up for the terminal

systemctl status apparmor.service

https://imgur.com/a/6DhRuuq
Web ip_adress:8006 don't work
Would anyone know to help?

 

[tom]

I use The last Proxmox.

Please always specify the version number, best by providing the output of:

> pveversion -v

 

[gusto]

only jpg

 

[gusto]

I apologize for the name of the thread
Can not boot!
Proxmox boots, but does not work web interface https://ip_address:8006

 

[Stoiko Ivanov]

Most commonly this is caused by a wrong/missing entry in `/etc/hosts`.
* check the status of pve-cluster.service and corosync.service (corosync.service should only run if you have a cluster)
* verify that the output of uname -n resolves to the ip which you want to access the GUI at.

If this doesn't work, please post the anonymized output of:
* `uname -n`
* `hostname -f`
* `hostname`
* `cat /etc/hosts`

 

[gusto]

I forgot to write yet.
I attached next SSD for backups (/dev/sdc)

fdisk /dev/sdc

I creatd new partition and formated it (ext4)
Then I make mount in /backup/images

mount /dev/sdc1 /backup/images

also /etc/fstab

nano /etc/fstab

UUID=337874af-321c-436c-ac41-ae47a7ce67f6       /backup/images  ext4    rw/auto 0       2

reboot
Then it stopped working.
Now I've deleted the line in /etc/fstab and everything works
hmm

 

[Stoiko Ivanov]

That's "normal/expected" behavior - If a disk/partition which should be mounted is not present during boot the system leaves you in a rescue shell (at least with systemd) - there you can hit 'Ctrl-D' to continue the boot (but you don't have network at that time - so you need to access the console)

 

[gusto]

I do not know why this is not working

UUID=337874af-321c-436c-ac41-ae47a7ce67f6       /backup/images  ext4    rw/auto 0       2

this also does not work

/dev/sdc1       /backup/images  ext4    rw/auto 0       2

but this works

/dev/sdc1    /backup/images    ext4    rw    0    0

 

[aghadjip]

one data point that was weird for me, I hotplugged and configured a local HDD as well as an ISCSI volume. hdd was listed as sdc, upon reboot I had the same problem, upon reboot my drive changed to sdb. After changing this in fstab, booted fine. dmesg showed my samsung ssd now had the sdb instead of sdc. Just a datapoint.

 

[Stoiko Ivanov]

@gusto the '/' in '/auto' is wrong - see `man fstab`

 

[Stoiko Ivanov]

@aghadjip - the /dev/sdb, /dev/sda, ... are not stable - use the links under /dev/disk/by-id/ for stable mountpoints

 

[gusto]

OK thx