[SOLVED] Lilo not booting slackware correctly. Errors listed inside.
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.
Lilo not booting slackware correctly. Errors listed inside.
I'm fairly new to Linux so I'm going to need a step-by-step guide to get me out of this rut. The install of Linux was fine but when I booted up I got this error.
VFS: Cannot open root device "302" or unknown-block (3,2)
Please append a correct "root=" boot option;
here are the available partitions;
0800 78150744 sda driver:sd
0801 47428608 sda1 <-- this is my Windows partition
0802 30719552 sda2 <-- this is my Linux partition
0b00 1048575 sr0 driver:sr
0b01 1048575 sr1 driver:sr
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (3,2)
I guessed from reading this error Lilo isn't pointing to the right partition to boot from? How will I fix this? I read another thread about boot problems on these forums and a guy said to do this:
#mkdir /slacktemp
#mount /dev/device /slacktemp
#chroot /slacktemp
#cd /slacktemp/etc <-- for me it told me that doesn't exist
#vi lilo.conf <-- couldn't do nothing and was frozen
#lilo -v -t -b /dev/device
#lilo -v -b /dev/device
The above solution did not work for me. Can anyone shed a light on a Linux rookie?
Well... I guess those commands shouldn't work quite right. Can you try the following:
Code:
mkdir /slacktemp
mount /dev/hda2 /slacktemp
(/dev/hda2 is your Linux partition, isn't it?)
Code:
ls /slacktemp/etc
(this command must show you a list of files, not an error - if it does not, something gone wrong)
Code:
cd /slacktemp
mkdir -p dev proc sys
mount --bind /dev dev
mount --bind /proc proc
mount --bind /sys sys
chroot .
vi /etc/lilo.conf
Have you ever used Vi? It's not as simple, nor it is a rocket science. After you're entered this command, press 'i'. Now you're in the insert mode. You can insert, delete or change your text in this mode as usual.
Find the section which loads your kernel. Something like:
Here '/dev/hda1' (may look different) is the device the kernel tries to mount as a root file system. Delete it and replace it with /dev/hda2. Add a line with 'root=/dev/hda2' with a few leading spaces if it does not already exist.
Press Esc (it usually works) after you're done with editing. Type ':w' (yes, with a colon), then press Enter. Vi will tell you the file is saved. Then type ':q', Enter. Vi will exit after that.
Code:
lilo -v -t -b /dev/hda2
lilo -v -b /dev/hda2
The first of the above commands may check if anything goes wrong without actually modifying anything. If anything is allright you may issue the second one. It will make Lilo write a boot sector to Linux partition. You may also do something to make your Windows boot loader boot from Linux partition, but it's just another story
After all above actions are performed, a few commands are left:
Code:
exit
umount dev proc sys
cd ..
umount slacktemp
Last edited by Prehistorik; 03-01-2010 at 01:07 PM.
I'm fairly new to Linux so I'm going to need a step-by-step guide to get me out of this rut. The install of Linux was fine but when I booted up I got this error.
VFS: Cannot open root device "302" or unknown-block (3,2)
Please append a correct "root=" boot option;
here are the available partitions;
0800 78150744 sda driver:sd
0801 47428608 sda1 <-- this is my Windows partition
0802 30719552 sda2 <-- this is my Linux partition
0b00 1048575 sr0 driver:sr
0b01 1048575 sr1 driver:sr
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (3,2)
I guessed from reading this error Lilo isn't pointing to the right partition to boot from? How will I fix this? I read another thread about boot problems on these forums and a guy said to do this:
#mkdir /slacktemp
#mount /dev/device /slacktemp
#chroot /slacktemp
#cd /slacktemp/etc <-- for me it told me that doesn't exist
#vi lilo.conf <-- couldn't do nothing and was frozen
#lilo -v -t -b /dev/device
#lilo -v -b /dev/device
The above solution did not work for me. Can anyone shed a light on a Linux rookie?
You would use 'mount /dev/sda2 /slacktemp' in the above. If you used 'mount /dev/device /slacktemp' then the device would not be correct. The comment stated that you would need to change to your device.
Yes. I'm about to just quit on slack and lilo. Probably the worst bootloader I ever dealt with. I have installed Gentoo easier than I had with slack and Gentoo is a horrid distro that breaks with every update. Can I installed GRUB and make this work? Lilo seems to be the worse damn bootloader I have ever dealt with.
Lilo is wonderful, it is elegant and simple and works, but if you are happier with grub you can install it. I would however point out that grub is a 32-bit program and you will have to install 32-bit extensions if you are using Slackware64.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.