View previous topic :: View next topic |
Author |
Message |
MMMMM Tux's lil' helper
Joined: 13 Jun 2011 Posts: 141 Location: Berlin
|
Posted: Sun May 22, 2022 1:12 pm Post subject: [solved] fresh system: unable to boot / kernel panic |
|
|
Hi,
after some years I try to use a newer system for gentoo.
This pc has 3 drives. sda is where Win10 is installed, sdb is for later use, I use /dev/nvme0n1 for linux.
I did install using the live system. It worked more or less ok up to the point of reboot.
Code: | Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) |
I did use the live system's kernel config as a starting point, only disabled some not useful modules. Ext4 support definitely enabled.
In https://wiki.gentoo.org/wiki/Knowledge_Base:Unable_to_mount_root_fs it recommends to boot the old kernel, but it's a fresh install so I don't have one.
I have a separate /boot partition but for testing I copied everything to the /boot folder of the / partition.
/etc/fstab:
Code: | #LABEL=boot /boot ext4 noatime 1 2
#/dev/sda2 /boot/efi vfat noatime,noauto 0 0
LABEL=root / ext4 noatime 0 1
LABEL=swap none swap sw 0 0
LABEL=home /mnt/home ext4 noatime 1 2
LABEL=portage /mnt/portage ext4 noatime 1 2
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0
|
I even installed debian to try to boot from this grub2. No luck.
I think the kernel is loaded but for some reason it does not know which partition it should mount. When using the debian grub2 I tried by "c" and added root=/dev/nvme0n1p4. Which did not help.
So how can this be fixed? So far booting is the most painfull thing when installing gentoo.
Last edited by MMMMM on Sun May 22, 2022 3:32 pm; edited 1 time in total |
|
Back to top |
|
|
mike155 Advocate
Joined: 17 Sep 2010 Posts: 4438 Location: Frankfurt, Germany
|
Posted: Sun May 22, 2022 2:12 pm Post subject: |
|
|
First of all: do you know SystemRescue? You could copy SystemRescue to an USB stick and boot from that stick. In the boot menu, there's an option "Boot installed OS". If you choose that option, your Linux system will be booted - with the SystemRescue kernel. That's an easy way to get access to your system - no chroot is required.
I agree that the message
Code: | Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) |
means that the Linux kernel has started, but that it fails to mount the root partition. That's good, because it means that EFI and the boot manager seem to work: they load and start the kernel. The problem seems to be your kernel. If I had to guess, I would say that the NVME driver is missing.
How do you want to boot your system? Do you use an initramfs? Or do you want to boot without an initramfs? If you use an initramfs: something is wrong with that. If you don't use an initramfs: make sure that CONFIG_BLK_DEV_NVME ist compiled directly into your kernel - not as a module.
Have you read the handbook?
Which of the installation alternatives did you choose? Which kernel do you use? Gentoo kernel / vanilla kernel? Which version? |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54300 Location: 56N 3W
|
Posted: Sun May 22, 2022 2:41 pm Post subject: |
|
|
MMMMM,
Welcome to Gentoo.
tells that the kernel cannot reach the hardware holding the root filesystem.
Its a message from the kernel, so the kernel loaded.
Tell us how you made your kernel and its matching initrd.
Put your kenel config file onto a pastebin.
This page may help you understand what is going wrong. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
MMMMM Tux's lil' helper
Joined: 13 Jun 2011 Posts: 141 Location: Berlin
|
Posted: Sun May 22, 2022 2:50 pm Post subject: |
|
|
There is something with NVME not correct, good point, Ill make a new kernel.
Code: | livecd /mnt/gentoo/usr/src/linux # grep NVME .config
# NVME Support
CONFIG_NVME_CORE=m
CONFIG_BLK_DEV_NVME=m
CONFIG_NVME_MULTIPATH=y
# CONFIG_NVME_HWMON is not set
CONFIG_NVME_FABRICS=m
CONFIG_NVME_FC=m
CONFIG_NVME_TCP=m
# CONFIG_NVME_TARGET is not set
# end of NVME Support
CONFIG_RTC_NVMEM=y
CONFIG_NVMEM=y
CONFIG_NVMEM_SYSFS=y
# CONFIG_NVMEM_RMEM is not set
|
|
|
Back to top |
|
|
MMMMM Tux's lil' helper
Joined: 13 Jun 2011 Posts: 141 Location: Berlin
|
Posted: Sun May 22, 2022 3:31 pm Post subject: |
|
|
Solved; missing NVME support was my fault.
Thank you very much! |
|
Back to top |
|
|
|