[SOLVED] stuck after unlocking luks device

[Pechvogel]

Hi guys,
I need some advice.
I installed proxmox on debian 12, following these instructions https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm because I need an encrypted device.
After apt install proxmox-ve postfix open-iscsi chrony I can access the webgui and do everything, so I guess everything is working fine.
The problem starts when I reboot the system. I get the prompt to enter my luks password and the message that it was successful.

I hope you have some ideas how I can solve that problem.

 

[fireon]

The problem starts when I reboot the system. I get the prompt to enter my luks password and the message that it was successful.

That sounds good, but what happens after?

 

[waltar]

When you need an encrypted device it sounds like having a filesystem onto and that's not automatically mounted after giving luks pw which is normal. If you made a fstab entry last time by setup just type "mount -a", "df" should show your encrypted filesystem mounted.

 

[fireon]

Basically a similar entry should exist in your FSTAB.

/dev/mapper/luks-XXXXXXXXX /          ext4    defaults   0 1

 

[waltar]

Aah, I thought about an option disk but maybe you mean the debian+pve installation on "/" itself like fireon mention ... (only) then host should mount / and boot ... but you don't wrote about your host state after giving the luks pw ...
PS: Maybe even luks on / has UUID= ... fstab entry.

 

[Pechvogel]

That sounds good, but what happens after?

Nothing happens. I tried up to 30 min.

So, I installed it again, so here is how my fstab looks like:

fstab didn't change after installed the proxmox-ve package, and I stuck again at the same time.

I now know for sure it the proxmox-ve package ist at fault, because I installed the other 3 before and was able to fully reboot and installed the package after.
I hope some have another hint for me.
Thanks in advance.

 

[waltar]

You maybe have any errors in ext4 depend on your nvme, then the system mounted as advised in fstab "/" just readonly, lots of services couldn't start as logging couldn't write and system cannot come up readily. So would change once fstab entry "errors=remount-ro" just change to keyword "defaults" (eg with a live-cd mounted that vol) and see what happen after.

 

[Pechvogel]

Thanks for the idea, it sadly doesn't work.
I already changed the hardware to a sata ssd, just to be sure that there is no hardware problem

 

[waltar]

Yes, good test, nice to see what happens after new install onto ...

 

[Pechvogel]

It is the same independent of hardware or fstab
Can someone try to reproduce this? I installed debian with automated partitioning luks and lvm and followed the wiki https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm
I have no other hardware to try to reproduce it.
Any help is appreciated


This message pops up if I press the powerbutton to turn of the machine.

 

[SamTzu]

I'm using Debian 12 KDE with LUKS encryption on Proxmox. Works fine. No problems
Have you tried simpler password without any special characters?

 

[SamTzu]

Also Nvidia drivers are know to mess with LUKS.

 

[SamTzu]

Did you choose correct Grub boot device on installation?

 

[Pechvogel]

I'm using Debian 12 KDE with LUKS encryption on Proxmox. Works fine. No problems
Have you tried simpler password without any special characters?

I changed for test purposes the password to 1234 to exclude this possibilty.

Also Nvidia drivers are know to mess with LUKS.

I have an amd w5100 installed. Unfortunately I have only a nvidia gtx 750ti as a replacement.
But I don't understand why it stops booting after installing the proxmox-ve package. Before that everything works fine.

Did you choose correct Grub boot device on installation?

There is only one boot device, so i guess yes

Thank you for your input

 

[fireon]

I have tested the instructions up to point Install the Proxmox VE packages. And everything was working fine. I assume that you have allocated enough disk space to the root LVM?

Please edit /etc/default/grub with an live system and chroot and change the GRUB_CMDLINE_LINUX_DEFAULT line:

GRUB_CMDLINE_LINUX_DEFAULT="verbose"

Update your grub configuration with "update-grub".

On the next reboot you see an verbose boot. Maybe you can see there why it is not booting completely.

 

[Pechvogel]

Thanks for your effort.
I gave the root lv 50GB to 100GB, so I guess this should be enough.
I will try your idea later and tell you my results.

 

[fireon]

I gave the root lv 50GB to 100GB, so I guess this should be enough.

Yes that is ok

I will try your idea later and tell you my results.

Perfect.

 

[Pechvogel]

I tried the idea and got this result:

Is it normal that apparmor="DENIED" is?
If it is, then there is problem with a driver for my network card?
I am curious and want to understand what is happening and not only exchange my network card and try again The network cards worked fine in the past in proxmox...
I hope someone can explain it to me and help me to get my machine running

 

[waltar]

Don't think it's a network card or driver for problem. You should set ip and pve-name in /etc/hosts to not request dhcp (in debian before "upgrading" to pve as then it seems too late) !! And comment 127.0.1.1 hostname to be not valid also !!

 

[Pechvogel]

I never commented 127.0.1.1, I will try it and report after that