LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 01-29-2010, 11:27 AM   #1
Intel_
Member
 
Registered: Mar 2009
Location: Bulgaria
Distribution: Slackware
Posts: 103
Blog Entries: 5

Rep: Reputation: 20
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)

Last edited by Intel_; 01-29-2010 at 11:34 AM.
 
Old 01-29-2010, 11:45 AM   #2
XGizzmo
Member
 
Registered: Mar 2007
Distribution: Slackware
Posts: 264

Rep: Reputation: 68
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.

Last edited by XGizzmo; 01-29-2010 at 11:47 AM.
 
Old 01-29-2010, 11:48 AM   #3
Intel_
Member
 
Registered: Mar 2009
Location: Bulgaria
Distribution: Slackware
Posts: 103
Blog Entries: 5

Original Poster
Rep: Reputation: 20
Quote:
Originally Posted by XGizzmo View Post
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?
 
Old 01-29-2010, 11:49 AM   #4
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,299

Rep: Reputation: 180Reputation: 180
check the /etc/fstab file, may need editing
 
Old 01-29-2010, 11:51 AM   #5
Intel_
Member
 
Registered: Mar 2009
Location: Bulgaria
Distribution: Slackware
Posts: 103
Blog Entries: 5

Original Poster
Rep: Reputation: 20
Quote:
Originally Posted by colorpurple21859 View Post
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?
 
Old 01-29-2010, 12:25 PM   #6
Intel_
Member
 
Registered: Mar 2009
Location: Bulgaria
Distribution: Slackware
Posts: 103
Blog Entries: 5

Original Poster
Rep: Reputation: 20
So, I created the initrd and lilo.conf is OK, but no effect Maybe I should try to downgrade, although I wont.
 
Old 01-29-2010, 12:25 PM   #7
marrowsuck
Member
 
Registered: Sep 2006
Posts: 83

Rep: Reputation: 25
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.
 
Old 01-29-2010, 12:31 PM   #8
Intel_
Member
 
Registered: Mar 2009
Location: Bulgaria
Distribution: Slackware
Posts: 103
Blog Entries: 5

Original Poster
Rep: Reputation: 20
After I created initrd it changed for sd* to hd* no effect
 
Old 01-29-2010, 12:35 PM   #9
marrowsuck
Member
 
Registered: Sep 2006
Posts: 83

Rep: Reputation: 25
Did you run lilo?
 
Old 01-29-2010, 12:37 PM   #10
Intel_
Member
 
Registered: Mar 2009
Location: Bulgaria
Distribution: Slackware
Posts: 103
Blog Entries: 5

Original Poster
Rep: Reputation: 20
Quote:
Originally Posted by marrowsuck View Post
Did you run lilo?
Yes, but it's print error:

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

Last edited by Intel_; 01-29-2010 at 12:48 PM.
 
Old 01-29-2010, 08:22 PM   #11
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,299

Rep: Reputation: 180Reputation: 180
did you try booting with the huge-smp kernel, shouldn't need initrd with it.
 
Old 01-29-2010, 10:27 PM   #12
escaflown
Member
 
Registered: Apr 2009
Location: Canada
Distribution: Slackware
Posts: 235

Rep: Reputation: 30
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.
 
Old 01-30-2010, 12:02 PM   #13
Intel_
Member
 
Registered: Mar 2009
Location: Bulgaria
Distribution: Slackware
Posts: 103
Blog Entries: 5

Original Poster
Rep: Reputation: 20
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?
 
Old 01-30-2010, 02:03 PM   #14
escaflown
Member
 
Registered: Apr 2009
Location: Canada
Distribution: Slackware
Posts: 235

Rep: Reputation: 30
Quote:
Originally Posted by Intel_ View Post
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.
 
Old 05-02-2010, 11:32 PM   #15
Motaro
Member
 
Registered: Mar 2003
Location: USA, Florida
Distribution: slackware 12.1
Posts: 44

Rep: Reputation: 16
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel panic after upgrading slackware64-current to 2.6.32.x kernel Lenard Spencer Slackware 4 01-22-2010 10:54 AM
-current and 12.2 Kernel security update Interject Slackware 21 08-19-2009 10:48 PM
RHEL4 Strange kernel panic on boot. Kernel Update no solution RattleSn@ke Red Hat 3 02-07-2009 03:24 AM
Slackware-current 20080429: Kernel panic psynot Slackware 4 05-02-2008 03:57 AM
YaST Online Update + AMD kernel patch = kernel panic THX1138 Linux - General 3 10-26-2003 04:25 PM


All times are GMT -5. The time now is 01:59 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration