[SOLVED] clean install: kernel panic

quantumduck · 2020-04-05 00:47:51

Hello! I decided I wanted to become a competent user, and so began installing Arch! I followed the install wiki and supporting documentation to the best of my ability and after wrestling with UEFI firmware and the windows boot loader have successfully set up a dual boot system with systemd-boot. However booting Arch without the install media ends in this:

[          0.003713] do_IQR: 1.55 No iqr handler for vector
[          0.003713] do_IQR: 2.55 No iqr handler for vector
[          0.003713] do_IQR: 3.55 No iqr handler for vector
[          1.227882] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,6)
[          1.227920] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.5.13-arch2-1 #1
[          1.227944] Hardware name: Acer Aspire V5-552P/Dazzle_RL , BIOS V2.07 12/23/2013
[          1.227969] Call Trace:
[          1.227991]  dump_stack+0x66/0x90
[          1.228007]  panic+0x112/0x2e8
[          1.228022]  mount_block_root+0x31c/0x32b
[          1.228040]  prepare_namespace+0x136/0x165
[          1.228058]  ? rest_init+0xbf/0xbf
[          1.228072]  kernel_init+0xa/0x101
[          1.228087]  ret_from_fork+0x22/0x40
[          1.228170] Kernel Offset: 0x3200000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[          1.228209] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,6) ]---
_

Some searching came up with this. The "unknown-block(x,x)" portion is different but here is my arch.conf anyway (not sure how to tell if I made it wrong.)

title	 Arch Linux
efi      /vmlinuz-linux
initrd   /amd-ucode.imgx
initrd   /initramfs-linux.img
options  rootfs=ext4
options  root=/dev/sda6

Further googling ended here. I added a rootfs line to arch.conf to no avail. The root partition is ext4 and on sda6. also the "unknown-block(8,6)" is identical to mine so I'd like to change what ever config file they're talking about to attempt that fix that worked in the post, but I am using systemd-boot, not GRUB. Is there an equivalent for systemd-boot? Am I just foolish for thinking that the problem experienced on that system is the same as what I am experiencing?

Here's my fstab

# /dev/sda6
UUID=4165c96b-66fe-4878-afb2-35dd46ebbc30	/         	ext4      	rw,relatime	0 1

# /dev/sda2
UUID=F08C-8090      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro	0 2

I'm unsure what further information I should furnish, please let me know!
Thank you for taking the time to look at my post.

Edit: changed applicable [ quote ] to [ code ]

Last edited by quantumduck (2020-04-05 17:18:17)

V1del · 2020-04-05 00:52:19

Welcome to the boards

Please use [ code ] instead of [ quote ] tags for pasting outputs.

Don't use /dev/sda that's an unstable identifier, use the UUID in your loader.conf, like in your fstab: https://wiki.archlinux.org/index.php/Pe … ice_naming

quantumduck · 2020-04-05 02:00:20

Here is the new arch.conf

title	Arch Linux
efi	/vmlinuz-linux
initrd	/amd-ucode.imgx
initrd	/initramfs-linux.img
options rootfs=ext4
options	root=UUID=4165C96B-66FE-4878-AFB2-35DD46EBBC30

And the new panic changed to unknown-block(0,0)

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

quantumduck · 2020-04-05 06:20:01

There are quite a few unknown-block(0,0) posts. Unfortunately they have quite varied solutions. Several say to update initramfs, but I can't see how that would apply here. I was also led to fstab, and a post recommending changing "root=" untill something worked lol. I'm tempted to wipe widows and see if I can get a single os Arch to boot.

WorMzy · 2020-04-05 09:45:31

Is "amd-ucode.imgx" actually in the entry file? That looks like a typo to me (there's certainly no amd-ucode.imgx file in the repos).

I'm also curious why you're specifying the kernel as "efi", rather than "linux"?

quantumduck · 2020-04-05 17:15:47

WorMzy wrote:

Is "amd-ucode.imgx" actually in the entry file? That looks like a typo to me (there's certainly no amd-ucode.imgx file in the repos).

Fixed the typo. Boot still hangs.

WorMzy wrote:

I'm also curious why you're specifying the kernel as "efi", rather than "linux"?

I tried using "linux" and it WORKED!

Thank you both V1del and WorMzy for your help! Marking solved.

I am left a little confused though, https://wiki.archlinux.org/index.php/Sy … ng_loaders seems to say "efi /path" and "linux /path" are interchangeable?

V1del · 2020-04-05 17:45:59

I also had to do a double take but this sentence explains this

systemd-boot wiki wrote:

linux and initrd followed by the relative path of the corresponding files in the ESP; e.g. /vmlinuz-linux; this will be automatically translated into efi path and options initrd=path – this syntax is only supported for convenience and has no differences in function.

so if you do not use linux your options line should include a initrd= reference that gets syntatically sugared automatically otherwise

Arch Linux

#1 2020-04-05 00:47:51

[SOLVED] clean install: kernel panic

#2 2020-04-05 00:52:19

Re: [SOLVED] clean install: kernel panic

#3 2020-04-05 02:00:20

Re: [SOLVED] clean install: kernel panic

#4 2020-04-05 06:20:01

Re: [SOLVED] clean install: kernel panic

#5 2020-04-05 09:45:31

Re: [SOLVED] clean install: kernel panic

#6 2020-04-05 17:15:47

Re: [SOLVED] clean install: kernel panic

#7 2020-04-05 17:45:59

Re: [SOLVED] clean install: kernel panic

Board footer