LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   kernel panic after update to -current (https://www.linuxquestions.org/questions/slackware-14/kernel-panic-after-update-to-current-785633/)

Intel_ 01-29-2010 11:27 AM

kernel panic after update to -current
 
Hi I updated my slackware 13 to current with the commands as writes in man slackpkg:

slackpkg update
slackpkg install-new
slackpkg upgrade-all

but now it's print kernel panic and I can't restore it.

after updatenow have kernel panic:

kernel panic: - not sync: VFS: Unable mount root fs on unknown-block (3,3)
PID:1,comm: swapper not tainted 2.6.32.5-smp #2

I tryed to boot with root=/dev/sda3 parametre, but not effect. Do you have ideas?

The partitions on my system are:
/dev/sda1 - /boot
/dev/sda2 - swap
/dev/sda3 - / (root)

XGizzmo 01-29-2010 11:45 AM

Well if you are using an initrd like is recommended you also need to rebuild your initrd and rerun lilo.

If not checked the /boot/vmlinuz symlink and /etc/lilo.conf and make sure it points to the correct kernel.

Intel_ 01-29-2010 11:48 AM

Quote:

Originally Posted by XGizzmo (Post 3845127)
Well if you are using an initrd like is recommended you also need to rebuild your initrd and rerun lilo.

If not checked the /boot/vmlinuz symlink and /etc/lilo.conf and make sure it points to the correct kernel.

Yes, but which command do this? Or to edit /etc/lilo.conf?

colorpurple21859 01-29-2010 11:49 AM

check the /etc/fstab file, may need editing

Intel_ 01-29-2010 11:51 AM

Quote:

Originally Posted by colorpurple21859 (Post 3845135)
check the /etc/fstab file, may need editing

Checked it. I don't think so. Maybe it's rebuilding initrd...but how to do that?

Intel_ 01-29-2010 12:25 PM

So, I created the initrd and lilo.conf is OK, but no effect :( Maybe I should try to downgrade, although I wont.

marrowsuck 01-29-2010 12:25 PM

According to http://rlworkman.net/howtos/libata-switchover changing the entries hd* to sd* in /etc/lilo.conf and /etc/fstab may resolve your problem.

Intel_ 01-29-2010 12:31 PM

After I created initrd it changed for sd* to hd* no effect :(

marrowsuck 01-29-2010 12:35 PM

Did you run lilo?

Intel_ 01-29-2010 12:37 PM

Quote:

Originally Posted by marrowsuck (Post 3845170)
Did you run lilo?

Yes, but it's print error:

WARNING:LBA32 adressing assumed
FATAL: raid_setup: stat ("/dev/hda")

colorpurple21859 01-29-2010 08:22 PM

did you try booting with the huge-smp kernel, shouldn't need initrd with it.

escaflown 01-29-2010 10:27 PM

Post your lilo.conf along with the result of "ls -l" in /boot.It will make things easier for us in terms of diagnosing where the problem is.

Intel_ 01-30-2010 12:02 PM

So, I made clean installation. It seems that current is not for me and for my machine at this moment. I saw some graphical updater, buw whether if I use it will be different?

escaflown 01-30-2010 02:03 PM

Quote:

Originally Posted by Intel_ (Post 3846273)
So, I made clean installation. It seems that current is not for me and for my machine at this moment. I saw some graphical updater, buw whether if I use it will be different?

I think the problem is in your lilo.conf and the symlinks you have in boot.

Motaro 05-02-2010 11:32 PM

I have the exact same problem,

FATAL: raid_setup: stat ("/dev/sda")

to my understanding the previous version of lilo still has that it needs to look for the raid entries on sda
which at the moment are the ide.


All times are GMT -5. The time now is 06:57 AM.