Arch Linux

Primoz

Member

From: Ljubljana-Slovena-EU

Registered: 2009-03-04

Posts: 697

[Solved] Kenel panic: unable to mount root

I've installed Arch on my laptop and am constantly getting kernel panic.
At first it gave me this message: link
Now I have no idea why while being chrooted into new install gave me UUID=0d746d9c-e528-4723-8f10-796b3d357beb
But hey the error at least gave me correct UUID. But even after I changed my UUID to the correct one I still got kernel panic, now with this message: link
My bootloader is systemd-boot, and I did change option root=UUID= to the correct UUID.
Another less important question: Why would chroot give me the wrong UUID for my root?

Thanks for any response.

Last edited by Primoz (2025-12-08 07:36:21)

---

Arch x86_64 ATI AMD APU KDE frameworks 5
---------------------------------
Whatever I do, I always end up with something horribly mis-configured.

gromit

Administrator

From: Germany

Registered: 2024-02-10

Posts: 1,501

Website

Re: [Solved] Kenel panic: unable to mount root

Could you please detail which exact UUID you did choose and post the outputs of "lsblk --fs", "cat /etc/fstab" and "cat /proc/cmdline"?

Primoz

Member

From: Ljubljana-Slovena-EU

Registered: 2009-03-04

Posts: 697

Re: [Solved] Kenel panic: unable to mount root

At time of writing the post, I used the UUID ending in 9520 (the second one).
But since then I decided to troubleshoot further on. I've edited boot loader configuration to add this:

initrd=\initramfs-linux.img root=UUID=87b7a830-6b2c-4e2e-ad2c-6625024c9520 rw

This moved beyond panic, but hanged waiting for disk.
So I've decided to try the previous UUID (the one that I got while chrooted)

initrd=\initramfs-linux.img root=UUID=0d746d9c-e528-4723-8f10-796b3d357beb rw

And this works. Running all commands like lsblk --fs, cat /etc/fstab and cat /proc/cmdline now show the correct UUDI 0d746d9c-e528-4723-8f10-796b3d357beb.
The only question I have is do I have to ke backslash in initrd option in systemd-boot, or should it be normal?
So

initrd=\initramfs-linux.img 0d746d9c-e528-4723-8f10-796b3d357beb rw

or

initrd=/initramfs-linux.img 0d746d9c-e528-4723-8f10-796b3d357beb rw

EDIT: It's this one

Last edited by Primoz (2025-12-08 09:19:08)

---

Arch x86_64 ATI AMD APU KDE frameworks 5
---------------------------------
Whatever I do, I always end up with something horribly mis-configured.

Primoz

Member

From: Ljubljana-Slovena-EU

Registered: 2009-03-04

Posts: 697

Re: [Solved] Kenel panic: unable to mount root

Oh boy. Turns out I made a spelling mistake while writing boot loader conf.
instead of writing initrd, I wrote intrd, which meant that boot loader didn't find the initramfs file.
I'm pretty sure that was the main issue, besides UUID etc.

---

Arch x86_64 ATI AMD APU KDE frameworks 5
---------------------------------
Whatever I do, I always end up with something horribly mis-configured.