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) |
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. |
Quote:
|
check the /etc/fstab file, may need editing
|
Quote:
|
So, I created the initrd and lilo.conf is OK, but no effect :( Maybe I should try to downgrade, although I wont.
|
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.
|
After I created initrd it changed for sd* to hd* no effect :(
|
Did you run lilo?
|
Quote:
WARNING:LBA32 adressing assumed FATAL: raid_setup: stat ("/dev/hda") |
did you try booting with the huge-smp kernel, shouldn't need initrd with it.
|
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.
|
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?
|
Quote:
|
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. |