Kernel Panic?

Hey @seanosb! I saw the kernel panic on your Linode's console. It seems like it just booted, but now you're in emergency mode:

You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):

How did you resolve the kernel panic?

It now looks like your system is expecting to find a volume, and it can't:

[DEPEND] Dependency failed for /mnt/nextcloud-lv.^M
[DEPEND] Dependency failed for Local File Systems.^M
[DEPEND] Dependency failed for File…eck on /dev/mapper/vg00-lvol0.^M

Are you mounting this volume via /etc/fstab? If so, you might be able to get your system to boot by commenting out the relevant lines in fstab. I think you'll need to boot into Rescue Mode and mount your root disk to make that change:

https://www.linode.com/docs/troubleshooting/rescue-and-rebuild/#mounting-disks

Then chroot:

https://www.linode.com/docs/troubleshooting/rescue-and-rebuild/#change-root

Once that's done, you should be able to make changes to /etc/fstab.

Post here if you need additional help from the Community!

And now this…

/shutdown: error while loading shared libraries: libacl.so.1: cannot open sharey
[ 1062.199357] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00
[ 1062.200963] CPU: 0 PID: 1 Comm: shutdown Not tainted 5.0.0-38-generic #41-Ubu
[ 1062.202682] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14
[ 1062.205272] Call Trace:
[ 1062.205895] dump_stack+0x6d/0x9a
[ 1062.206709] panic+0x101/0x2a7
[ 1062.207718] do_exit.cold.24+0x26/0x75
[ 1062.208623] do_group_exit+0x43/0xb0
[ 1062.209528] __x64_sys_exit_group+0x18/0x20
[ 1062.210544] do_syscall_64+0x5a/0x110
[ 1062.211333] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 1062.212481] RIP: 0033:0x7f0896cdbe16
[ 1062.213214] Code: Bad RIP value.
[ 1062.213877] RSP: 002b:00007fffb8e3c0c8 EFLAGS: 00000202 ORIG_RAX: 00000000007
[ 1062.218189] RAX: ffffffffffffffda RBX: 00007f0896ce5420 RCX: 00007f0896cdbe16
[ 1062.222128] RDX: 000000000000007f RSI: 000000000000003c RDI: 000000000000007f
[ 1062.225324] RBP: 00007f0896cbe950 R08: 00000000000000e7 R09: 00000000ffffffff
[ 1062.227385] R10: 00007fffb8e3c45a R11: 0000000000000202 R12: 0000000000000007
[ 1062.229488] R13: 00007f0896cbe9c0 R14: 00007f0896cbe980 R15: 0000000000000000
[ 1062.231239] Kernel Offset: 0x2fe00000 from 0xffffffff81000000 (relocation ra)
[ 1062.234409] ---[ end Kernel panic - not syncing: Attempted to kill init! exi-

Ah, I see that this kernel panic is happening on shutdown, sorry for missing that before:

/shutdown: error while loading shared libraries: libacl.so.1: cannot open sharey

Did you recently install updates on this system? Some internet sleuthing seems to suggest other users (mostly on Arch systems) have experienced this issue as a result of an incomplete package installation:

https://bbs.archlinux.org/viewtopic.php?id=237195
https://github.com/AnarchyLinux/installer/issues/559
https://bbs.archlinux.org/viewtopic.php?id=232734
https://www.google.com/search?client=firefox-b-1-d&q=error+while+loading+shared+libraries%3A+libcryptsetup.so

If this is the result of a broken or incomplete package installation, you might be able to fix it – the steps are gonna be similar to my last answer:

1. Boot into Rescue Mode
2. Mount disks
3. Change root
4. Try to configure packages and fix broken ones:

dpkg –configure -a
apt-get install -f

This might fix the issue – just note that this kernel panic issue seems like it's separate from whatever is preventing that volume from mounting, so you might want to try to address these issues separately.

Best of luck!

I was able to comment it out and boot without issue but I can't seem to get that disk mounted now.

root@localhost:/# mount /dev/mapper/vg00-lvol0
mount: /mnt/nextcloud-lv: special device /dev/mapper/vg00-lvol0 does not exist.

I can't say for sure but it sounds like the device you're trying to mount is either no longer available or now has a different name. Since it's in /dev/mapper it sounds like it's a logical volume. If you're using LVM to manage it, try using lvscan to list all the logical volumes on your Linode.

There's a LVM guide on ArchWiki that might help. For example, if the logical volume you're looking for doesn't show up with lvscan it suggests running the following commands:

vgscan
vgchange -ay

If it's a disk volume, I'd recommend running lsblk to check which disks are available under which name.

In addition, check out your Linode's configuration profile to make sure that all disks and Volumes that you need are in the locations you'd like them in.