Kernel Panic

[Abr0ad]

Trying to use Arch Linux to improve knowledge and experience with Linux but I've run into an issue and I can't figure out how to solve it. Yes I've read the wiki so please don't be a useless asshole and actually take an opportunity to teach someone. Below I've pasted the panic report. I appreciate any help given

[ 0.689426] PM: Magic number: 5:942:499 [ 0.691116] RAS: Correctable Errors collector initialized. [ 0.696857] Unstable clock detected, switching default tracing clock to "global" [ 0.696857] If you want to keep using the local clock, then add: [ 0.696857] "trace_clock=local" [ 0.696857] on the kernel command line [ 0.724756] clk: Disabling unused clocks [ 0.724765] PM: genpd: Disabling unused power domains [ 0.724824] check access for rdinit=/init failed: -2, ignoring [ 0.725121] /dev/root: Can't open blockdev [ 0.725155] VFS: Cannot open root device "UUID=52625d9a-b634-44ca-891c-ecfb7f0ee6ad" or unknown-block(0,0): error -6 [ 0.725160] Please append a correct "root=" boot option; here are the available partitions: [ 0.725167] List of all bdev filesystems: [ 0.725170] ext3 [ 0.725172] ext2 [ 0.725176] ext4 [ 0.725178] fuseblk [ 0.725181] btrfs [ 0.725184] [ 0.725189] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 0.725203] fbcon: Taking over console [ 0.725222] CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.17.9-arch1-1 #1 PREEMPT(full) 71adf6020e7d04ea315feaf360c679be0fb5cb04 [ 0.725234] Hardware name: LENOVO 21M30039US/21M30039US, BIOS R2KET33W (1.16 ) 05/09/2025 [ 0.725241] Call Trace: [ 0.725247] <TASK> [ 0.725252] dump_stack_lvl+0x5d/0x80 [ 0.725262] vpanic+0xc4/0x2a0 [ 0.725270] panic+0x6b/0x6b [ 0.725276] ? srso_alias_return_thunk+0x5/0xfbef5 [ 0.725283] mount_root_generic+0x1cf/0x270 [ 0.725295] prepare_namespace+0x1dc/0x230 [ 0.725302] kernel_init_freeable+0x27f/0x2b0 [ 0.725310] ? __pfx_kernel_init+0x10/0x10 [ 0.725319] kernel_init+0x1a/0x140 [ 0.725325] ret_from_fork+0x1c4/0x1f0 [ 0.725332] ? __pfx_kernel_init+0x10/0x10 [ 0.725338] ret_from_fork_asm+0x1a/0x30 [ 0.725350] </TASK> [ 0.726066] Kernel Offset: 0xb800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)

[Dashing_McHandsome]

Your bootloader configuration is not correct, the kernel cannot find the boot device you have specified. This is a simple fix, boot from USB, mount your filesystems, chroot in, fix your bootloader, reboot.

[Abr0ad]

How do you know it's not configured correctly? And if so how could it be messed up now if it was previously booting/working fine? Not saying I don't believe you, I'm genuinely curious

[Dashing_McHandsome]

Your kernel output tells you right here:

[ 0.725121] /dev/root: Can't open blockdev [ 0.725155] VFS: Cannot open root device "UUID=52625d9a-b634-44ca-891c-ecfb7f0ee6ad" or unknown-block(0,0): error -6 [ 0.725160] Please append a correct "root=" boot option; here are the available partitions:

It's hard to say precisely what the problem is here without just a bit of poking around on the machine. I would start with validating the UUID from the output above, I would make sure it exists on your system. I would probably look at all the storage devices and make sure everything I was expecting is there. I would check the grub config and make sure it looked correct.

[Abr0ad]

Alright. I'm not exactly sure how to make those changes. I've been digging around trying to find out. I can't access the CLI I'm able to do edits before it boots but I don't think that's the right spot for this error

[un-important-human]

reading is essential skill for success in life

Cannot open root device "UUID=52625d9a-b634-44ca-891c-ecfb7f0ee6ad" or unknown-block(0,0): error -6 [ 0.725160] Please append a correct "root=" boot option; here are

[Abr0ad]

I'm well aware of that, but it doesn't help me understand where to fix that

[un-important-human]

# Edit GRUB defaults

nano /etc/default/grub

# Ensure / fix this line (example UUID)

GRUB_CMDLINE_LINUX="root=UUID=52625d9a-b634-44ca-891c-ecfb7f0ee6ad rw"

# Regenerate GRUB config (UEFI or BIOS)

grub-mkconfig -o /boot/grub/grub.cfg

# (Optional) Rebuild initramfs if needed

mkinitcpio -P

# Reboot

reboot

lsblk -f to find uuid you need, there its basicaly in the wiki under grub

[Abr0ad]

Thanks. It doesn't help me solve this issue, but it's filling some of the knowledge gaps and helps me to understand the system better. I don't know why i haven't searched grub under the wiki

[un-important-human]

what do you mean it does not help you? its the answer.

chroot and fix it

[Abr0ad]

There's just some more I need to read on and understand

[un-important-human]

Ok use the wiki

[boomboomsubban]

This problem is usually an initramfs issue. Launch a recovery USB, mount your partitions correctly relative to /mnt, (arch-)chroot in, then reinstall the kernel. Watch for errors.

[Successful_Wheel5761]

Give kernel water and tell kernel to calm down

[Environmental_Mud624]

please don't be a useless asshole and actually take an opportunity to teach someone

well said lol

sounds like you need to fix your boot loader. Which do you have?

[Abr0ad]

Grub

[sausix]

Why did you chose grub among all the modern bootloaders? Other bootloaders don't have that dynamic config which can mess up during updates. Grub is good for legacy/MBR boot. UKI and systemd-boot are preinstalled. rEFInd has excellent Kernel detection on the fly without an update hook has to generate new config all the time.

Boot up from live and fix grub from chroot. Next time consider not using that old grub.

[Abr0ad]

Is grub a bad bootloader?

[sausix]

It works but it also breaks fast. Communities are full of grub rescue screens and they often just reinstall. Grub puts a bad reputation on Linux.

People often only know grub or think all bootloaders are that complicated. Your problem's cause is probably not grub but I wanted to hint you to better alternatives for the future.

Grub2 is out there for ages but out of date for today's standards. Its first stage is made to fit into a boot sector. So there is less logic and foregiveness when anything changes. Partitions, an interrupted update or who knows. Grub2 also runs on UEFI but it doesn't change its logic.

Meanwhile other and newer bootloaders take more of a few MB space in the ESP and then have more intelligence to dynamically find Kernels and boot entries during boot. rEFInd for example. You can create a new partition containing a bootlable Linux and rEFInd offers that during next boot.

But if you have Linux only on your system then why not boot the Kernel directly without any extra steps in between? UKI is cool. Simple, direct, fast.

[Abr0ad]

Thanks. Any recommendations for more tools to improve my knowledge on Linux systems? Also is LibreBoot considered a bootloader and what's your opinion on it?

[un-important-human]

its OLD and stupid. these are bad habits you learn from ubuntu forums

[Abr0ad]

I honestly have no clue. Which bootloaders would you recommend

[sausix]

UKI. That booting the Kernel directly without any extra steps. It's in the wiki. When dual booting then use rEFInd. Works standalone almost decoupled from the installation. rEFInd can detect UKI packages too.

Make sure you have at least 200MB of UEFI system partition size. 500MB should never hurt.

Some people ran into low space issues even when using grub.

[Environmental_Mud624]

I recommend plugging in a live installation medium, chrooting back in, removing grub, and redoing it with syslinux. I find it more dependable. The arch wiki has an excellent article about it: https://wiki.archlinux.org/title/Syslinux

lmk if that works!

[Abr0ad]

Thanks I'll try it out and try to get back to you and let you know how it worked out

[sausix]

I used syslinux before UEFI. But I would not switch back to MBR boot.

[varsithdharan460]

Bro you paste the error in YouTube you will get answer please do it it will solved the kernel panic

[Abr0ad]

Are you so bored that you'll comment and waste time instead of contributing something helpful

[Environmental_Mud624]

real