[SOLVED] Kernel panic - not syncing: VFS: unable to mount root fs on uknown-block(253,0)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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.
Markus
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.
Last edited by Richard Cranium; 01-26-2014 at 10:46 AM.
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 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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.