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

Hi everyone,

i have been trying to install kernel-generic-2.6.17.13 and i get the kernel panic error from above. I have installed the header and the modules. And created a initrd for ext3. AND I STILL GET THAT ERROR OR KERNEL PANIC - ATTEMPING TO KILL INIT. i have ln system, vmlinuz and rc.modules and still don't get it to work. I tried it from bareacpi.i and huge26.s my hdd is a ata. If someone has the solution for this i would hight appreciate it. Or please let me know what i am doing wrong. by the way i also edited lilo. with the vmlinuz-generic-smp and added initrd = /boot/initrd.gz. i will be waiting for your replies thanks...


bijit

I don't think you need an initrd for ext3. And from the looks of it, your lilo is pointing to the wrong partition. Are you sure that root is on the second partition of the fourth disk?

Hi,

Did you run lilo as root from the console? Just editing the lilo.conf with the proper stanza without writing will get you nothing.

Did you follow the '/boot/README.initrd' procedures?

I only have two partitions hda1=/ and hda2=swap. On lilo i have root = /dev/hda1. Yes i ran lilo as root on the console. And also followed /boot/README.initrd. this is all that I did.

That is all that i did. On the /boot the initrd.gz is red. It shouldn't be in the same color as the vmlinuz? Please reply back since my comp is in standby until i can fix it...

Hi,

Your line is not correct;
should be;
Also post your lilo.conf. What is your boot device?

This is my boot device. The line i just missed the 3 but i had it the same as you did.

Hi,

That's why you should use the cut&paste instead of typing. Wastes everyones time!

BTW, would you post the /etc/lilo.conf file as requested?

Here you go. Apologize for the typo.

Hi,

lilo.conf looks OK. Try as root from console;

If you have any errors for the first command above then post them.
If no errors then try the second. This will write to the 'MBR' of /dev/hda. I would also suggest the use of the 'compact' option in the lilo.conf.

I would 'man lilo.conf' for understanding.

Hi !
I had the same problem like you many years in the past I found that this happened when i separated some directories of linux (honestly i don't remember what are the name of those directories, maybe one is the /boot) in different hard disks, and when you recompiled the kernel, copied and moved all the stuff and modified lilo to start the new kernel. The mount point of the new kernel was pointing to another part.

The point in here is check your configuration, and start playing what directories you can move with the hard disks without making this error happens (i found that you can have /home safely in another directory, maybe the /tmp is another afe one to move).

Good luck

This is just a shot in the dark...what if you replace any hda word with sda in your lilo.conf and in /etc/fstab . I know u use paralel ata,but just give it a try....
And then don't forget to run lilo again.
(boot and mount to your slackware partition via liveCD or slackware install CD,of course).
It may still not work,though

I have found the error. The error for the 2.6.# is that the vga doesn't work. In order to see the booting process I have to give vga=normal. But I still have problems When give command:

Its gives some error and says it doesn't support my screen depth. Any screen depth I put. And when I do:

it says rebooting . and it doesn't do anything after and it doesn't reboot. Do you think its the same problem with the vga?