LinuxQuestions.org - [SOLVED] Kernel panic - not syncing: VFS: unable to mount root fs on uknown-block(253,0)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Kernel panic - not syncing: VFS: unable to mount root fs on uknown-block(253,0) (https://www.linuxquestions.org/questions/slackware-14/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-uknown-block-253-0-a-4175492093/)

Markus why you dont put your Root lvm path on LILO root option

mine: root = dev/lvfelix/root

yours: root: dev/sda5

:s

Well, I don't use lvm ;)

That's the reason why I can't help with lvm, I don't have any experience.

I posted the part of my lilo.conf to show you how I use the huge kernel in a case of kernel-panic with the generic kernel.

Markus

What is the output of

Code:

/usr/share/mkinitrd/mkinitrd_command_generator.sh

Code:

mkinitrd -c -k 3.2.29-smp -f ext4 -r /dev/lvfelix/root -m mbcache:jbd2:ext4 -L -u -o /boot/initrd.gz

Quote:

Originally Posted by fjur94 (Post 5105109)

Markus why you dont put your Root lvm path on LILO root option

mine: root = dev/lvfelix/root

Correct. Mine working lilo.conf for LVM

Code:

image = /boot/vmlinuz

root = /dev/cryptvg/root

initrd = /boot/initrd.gz

label = Slackware

read-only

Quote:

Originally Posted by fjur94 (Post 5105293)

Code:

mkinitrd -c -k 3.2.29-smp -f ext4 -r /dev/lvfelix/root -m mbcache:jbd2:ext4 -L -u -o /boot/initrd.gz

As far as I can see, mkinitrd command looks correct. Although question is, when did you execute this command. After installation? After reboot with install CD? Or within actual chroot?

If you execute this after installation, it will write initrd.gz to /boot of Slackware install CD (it will disappear after reboot). You want to execute it within your newly installed linux, so Lilo can pick it up.

I assume that you did full install or have at least on kernel in /boot. Just to make sure, could you mount your boot partition and see if kernel is actually there?

Look what is mounted right now (just to get clear picture what's going on).

Code:

$ mount

If real boot partition isn't already mounted, do it.

Code:

$ mount /dev/sda1 /mnt/boot

$ ls -l /mnt/boot

And if it doesn't list any files, then you have to install kernel package again. If there are files, then you can move to chrooting your system and re-run lilo.

I'll stop now and wait for output of commands above, then we can move further.

i execute the mkinitrd command after installation without rebooting.

(/mnt/boot) didnt exist, so i created it.

Pictures shows (mount) and (ls -l /mnt/boot)

Note: i have not rebooted after i did the installation.

Quote:

Originally Posted by fjur94 (Post 5105518)

Well, thanks to yenn for asking ;)

Your approach seems quite odd. I'd strongly recommend that you put the huge kernel into your lilo.conf and boot with it (don't forget to rerun lilo). Then, when Slackware with the huge kernel is running, you may create the initrd, rerun lilo again and reboot then with the generic kernel.

Thanks to Richard Cranium for pointing me to this. I found this manual from Alien Bob, hope this helps.

Markus

Quote:

Originally Posted by markush (Post 5105545)

Not recommended. You must have an initrd in order to have your root partition on a logical volume.

I'm running a 14.0 install on a virtual machine right now to see what state the installer should be in when it finishes.

Quote:

Originally Posted by markush (Post 5105545)

Thanks to Richard Cranium for pointing me to this. I found this manual from Alien Bob, hope this helps.

I did the same that the guide says and nothing.

I recommend that you skip installing lilo as part of running setup. Then do the following immediately after setup exits:

Code:

mount -R /proc /mnt/proc

mount -R /sys /mnt/sys

mount -R /dev /mnt/dev

chroot /mnt

$(/usr/share/mkinitrd/mkinitrd_command_generator.sh -r )

liloconfig

While in liloconfig, select the Simple menu choice.
Select standard for "CONFIGURE LILO TO USE FRAME BUFFER CONSOLE?"
No optional parameters.
Select "No" for "Use UTF-8 TEXT CONSOLE?"
Select MBR for "SELECT LILO TARGET LOCATION"

You'll get a message indicating that lilo didn't install. Press enter.

Then run...

Code:

/usr/share/mkinitrd/mkinitrd_command_generator.sh -l /boot/vmlinuz-generic-smp-3.2.29-smp >>/etc/lilo.conf

Then use your favorite editor to edit /etc/lilo.conf; vi, emacs, nano, or whatever you would use when logged into a console. Delete lines 62 to 67 inclusive. Save the file and exit.

Next, run...

Code:

lilo

...which will give a warning or two. Then run...

Code:

exit

to get out of the chroot followed by ctrl-alt-delete to reboot.

62 to 67, even the 'image' option ?

Don't know why ours are that different, but from the screen shot you provided, it's lines 59-64.

I made a video because this is unexplainable

see link below
http://www.youtube.com/watch?v=qPFkQA4lkSc

I don't know if there is difference between selecting <Cancel> or actually using the Exit menu option to leave setup. I used the exit menu option.

Other than that, I'd have to run the installer under VM player. My tests were run in a VM running under libvirt.