You are not logged in.
Have had my laptop kernel panic a couple times now while updating my system. I did the usual to fix it this time:
Live boot, mount everything, fix pac-man, fix broken packages, then run
pacman —sysroot /mnt linux making sure my boot partion is mounted to /mnt/boot.
Unfortunately, I ran into this when booting after fixing everything:
/init: line 16: can't open /proc/cmdline: no such file
:: running early hook [udev]
/proc/ is not mounted, but required for successful operation of systemd-impfiles. Please mount /proc/. Alternatively, consider using the root= or --image= switches.
Failed to parse kernel command line, ignoring: No such file or directory
Starting systemd-udevd version 255.5-4-arch :: running hook [udev]
:: Triggering uevents...
Running in chroot, ignoring request.
Running in chroot, ignoring request.
Running in chroot, ignoring request.
:: running hook [keymap]
:: Loading keymap… done.
ERROR ‘’ not found, Skipping fsck.
:: mounting ‘’ on real root
:: running cleanup hook [udev]
Running in chroot, ignoring request.
ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck.
sh: can't access tty; job control turned off
[rootfs ~]#I couldn’t find much about it but considering it is trying to mount an empty string I feel like something went wrong with my boot partition. Any help appreciated, thank you.
I did hand type that above so if it looks like something is off let me know.
SOLVED:
I am not sure what did it but:
Mounted my fs to /mnt, boot portion to, /mnt/boot, and sysfs and something else to their respective places in /mnt. Then just reinstalled every package that had the word Linux in it and systemd. Sorry if you have the same issue and this isn't to helpful.
I am not to sure what is causing these panics. Doesn't feel like its a hardware thing but I should prob just run memtest at some point. Here is my journal if anyone is curious: https://0x0.st/X8Wq.txt
Last edited by qualia (2024-05-10 02:23:14)
Offline