You are not logged in.
Quite the odd error
It goes like this:
run linux with stable release
->switch to lts and it works
-> switch back to stable and it fails to mount /home and fails to activate swap
"dependency fail for swaps
dependency failed for local file system"
->run using stable again and it works magically without doing anything
I reinstalled grub, did mkinitcpio -P, reinstalled both kernels and it still occurs
I can't send the output of journalctl -xb because the console wouldn't work (root is locked down) ![]()
Last edited by Crook3835 (2024-10-21 07:11:46)
Offline
If you reboot by frentically pressing crtl+alt+del, a SHORT press on the power button or the https://wiki.archlinux.org/title/Keyboa … el_(SysRq), the journal should be preserved and you can access it from the next boot:
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.stPlease never use -x w/ journalctl, it's just spam. (Likewise -r is like top-posting)
Offline
If you reboot by frentically pressing crtl+alt+del, a SHORT press on the power button or the https://wiki.archlinux.org/title/Keyboa … el_(SysRq), the journal should be preserved and you can access it from the next boot:
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.stPlease never use -x w/ journalctl, it's just spam. (Likewise -r is like top-posting)
Thanks
Here is the log: http://0x0.st/XlJq.txt
Offline
Oct 21 00:30:47 archlinux mount[566]: mount: /home: wrong fs type, bad option, bad superblock on /dev/nvme1n1p4, missing codepage or helper program, or other errorthis looks like the kernel you try to boot doesn't match the kernel installed in the system
check from arch instal - arch-chroot into the system and make sure the kernel you want to boot matches the kernel installed in the system so it can load the FS-driver module
this often happens when /boot isn't properly mounted when the kernel is update - hints to some issues with your /etc/fstab
Last edited by cryptearth (2024-10-20 21:53:07)
Offline
No, you then get complaints from the kernel about "wtf is a vfat, dude?"
Oct 21 00:30:46 archlinux kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
Oct 21 00:30:46 archlinux kernel: nvme0n1: p1 p2 p3 p4
Oct 21 00:30:46 archlinux kernel: nvme nvme1: 12/0/0 default/read/poll queues
Oct 21 00:30:46 archlinux kernel: nvme1n1: p1 p2 p3 p4 p5 p6Oct 21 00:30:46 archlinux kernel: BTRFS: device fsid 6db308bc-9516-46d4-9986-7d5fda9b4619 devid 1 transid 1836 /dev/nvme0n1p3 (259:3) scanned by mount (316)
Oct 21 00:30:46 archlinux kernel: BTRFS info (device nvme0n1p3): first mount of filesystem 6db308bc-9516-46d4-9986-7d5fda9b4619
Oct 21 00:30:46 archlinux kernel: BTRFS info (device nvme0n1p3): using crc32c (crc32c-intel) checksum algorithm
Oct 21 00:30:46 archlinux kernel: BTRFS info (device nvme0n1p3): using free-space-tree
Oct 21 00:30:46 archlinux systemd[1]: Expecting device /dev/nvme1n1p1...
Oct 21 00:30:46 archlinux systemd[1]: Expecting device /dev/nvme1n1p2...
Oct 21 00:30:46 archlinux systemd[1]: Expecting device /dev/nvme1n1p4...
Oct 21 00:30:46 archlinux systemd[1]: Found device KBG40ZNS256G NVMe KIOXIA 256GB ESP.
Oct 21 00:30:46 archlinux systemd[1]: Found device KBG40ZNS256G NVMe KIOXIA 256GB Microsoft\x20reserved\x20partition.
Oct 21 00:30:46 archlinux systemd[1]: Activating swap /dev/nvme1n1p2...
Oct 21 00:30:46 archlinux systemd[1]: Found device KBG40ZNS256G NVMe KIOXIA 256GB WINRETOOLS.
Oct 21 00:30:46 archlinux swapon[492]: swapon: /dev/nvme1n1p2: read swap header failed
Oct 21 00:30:46 archlinux systemd[1]: dev-nvme1n1p2.swap: Swap process exited, code=exited, status=255/EXCEPTION
Oct 21 00:30:46 archlinux systemd[1]: dev-nvme1n1p2.swap: Failed with result 'exit-code'.
Oct 21 00:30:46 archlinux systemd[1]: Failed to activate swap /dev/nvme1n1p2.
Oct 21 00:30:47 archlinux mount[566]: mount: /home: wrong fs type, bad option, bad superblock on /dev/nvme1n1p4, missing codepage or helper program, or other error.Please post your fstab and don't address drives via the device node, the order isn't deterministic, so nvme0 and nvme1 can change places any time.
Offline
Please post your fstab and don't address drives via the device node, the order isn't deterministic, so nvme0 and nvme1 can change places any time.
# UUID=6db308bc-9516-46d4-9986-7d5fda9b4619
/dev/nvme1n1p3 / btrfs rw,relatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/ 0 0
# UUID=0384-58F6
/dev/nvme1n1p1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
# UUID=fb43de83-6891-4f22-8c06-1cf0e9649149
/dev/nvme1n1p4 /home btrfs rw,relatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/ 0 0
# UUID=94b8065f-038e-40d3-93dd-d9eb716cd955
/dev/nvme1n1p2 none swap defaults 0 0 So I should use the UUID instead of using /dev/nvmexnxpx ?
Last edited by Crook3835 (2024-10-21 07:03:13)
Offline
No, you *want* to use the UUID instead of /dev/nvmexnxpx
Offline
No, you *want* to use the UUID instead of /dev/nvmexnxpx
Works flawlessly now.
Makes sense since during installation I rebooted and realised that the nvmes change numbers but I forgot about that.
Thanks for the help ![]()
Offline