LinuxQuestions.org
Visit Jeremy's Blog.
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
 
Search this Thread
Old 06-05-2010, 12:41 PM   #1
abrahammer
Member
 
Registered: Dec 2006
Posts: 41

Rep: Reputation: 15
kernel panic while booting


hello, im a rookie at configuring linux and i have problem booting slackware 13.1 just installed. i get a message similar to this
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(8,4)
i got this one from another user who has a similar problem, they say i should fix lilo.conf and it actually was pointing to a wrong partition so i fixed it. i also fixed /etc/fstab to make it point to the right partition /dev/sda3.

but after fixing the files, it still wants to load something in /dev/sda4, i dont know why so what should i do next, please explain with commands and not just words. thanks!

edit this is my lilo.conf

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda3

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Windows bootable partition config begins
other = /dev/sda1
label = Windows
table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda3
label = Linux
read-only
# Linux bootable partition config ends

i can boot windows fine by the way

Last edited by abrahammer; 06-05-2010 at 12:43 PM. Reason: lilo.conf
 
Old 06-05-2010, 12:49 PM   #2
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,428

Rep: Reputation: 407Reputation: 407Reputation: 407Reputation: 407Reputation: 407
What partitions did you create on your hard drives?

What file system type is your root partition? Did you create an initrd? Did you tell mkinitrd the file system type of your root partition? Did you add the module(s) required to support your root partition file system type in your initrd?

If this was an initial install, mkinitrd will run and not find all the required kernel modules unless you had run the command "chroot /mnt" prior to running mkinitrd.
 
Old 06-05-2010, 12:52 PM   #3
linus72
Guru
 
Registered: Jan 2009
Location: Gordonsville-AKA Mayberry-Virginia
Distribution: PocketWriter/MinimalX
Posts: 5,057

Rep: Reputation: 328Reputation: 328Reputation: 328Reputation: 328
You gotta do

/sbin/lilo

in terminal as root
afetr updating /etc/lilo.conf
 
Old 06-05-2010, 01:51 PM   #4
abrahammer
Member
 
Registered: Dec 2006
Posts: 41

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by Richard Cranium View Post
What partitions did you create on your hard drives?

What file system type is your root partition? Did you create an initrd? Did you tell mkinitrd the file system type of your root partition? Did you add the module(s) required to support your root partition file system type in your initrd?

If this was an initial install, mkinitrd will run and not find all the required kernel modules unless you had run the command "chroot /mnt" prior to running mkinitrd.
1./dev/sda1 and /dev/sda2 for other os's, /dev/sda3 for this one (also installed lilo here and made this one the active partition), /dev/sda5 for swap /dev/sda6 and sda7 for files.
2. ext4
3. no i didn't, or i don't know i just installed slackware with the default configuration (pressed enter all the time).
4 and 5. how can i do this if i can't start the os?
 
Old 06-05-2010, 02:15 PM   #5
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.1, 14.1, 64-14.1, -current, FreeBSD-10
Posts: 1,658

Rep: Reputation: 570Reputation: 570Reputation: 570Reputation: 570Reputation: 570Reputation: 570
You must run lilo after edits

After editing your lilo.conf you must run lilo as root to install the changes to the boot reecord.
 
Old 06-05-2010, 02:24 PM   #6
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-14.1 on a Lenovo T61 6457-4XG
Posts: 4,015

Rep: Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962
If you have the Slackware DVD at hand, try what follows.

1. Boot with the DVD as if you would like to install Slackware again
2. Do not run setup but login as root then run following commands:
Code:
mkdir /prov
mount -t reiserfs /dev/sda3 /prov
chroot /prov
lilo -t -v #then if all goes well :
lilo
3. Reboot

Last edited by Didier Spaier; 06-05-2010 at 03:31 PM.
 
Old 06-05-2010, 02:51 PM   #7
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Rep: Reputation: 227Reputation: 227Reputation: 227
Quote:
4 and 5. how can i do this if i can't start the os?
There are instructions on screen when booting the Slackware setup disk which show how to boot to an installed Slackware partition using the setup disk. Just look at this and follow instructions.
 
Old 06-05-2010, 04:08 PM   #8
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.1, 14.1, 64-14.1, -current, FreeBSD-10
Posts: 1,658

Rep: Reputation: 570Reputation: 570Reputation: 570Reputation: 570Reputation: 570Reputation: 570
Quote:
Originally Posted by abrahammer View Post
4 and 5. how can i do this if i can't start the os?
Follow bgeddy's instructions, or you can...

1. Boot to the install CD/DVD, login as root
2. Create a mount point for slackware partition, like
Code:
mkdir /mnt/slack
3. Mount the slackware partition, like
Code:
mount /dev/sda3 /mnt/slack
4. Chroot to the mounted partition, like
Code:
chroot /mnt/slack
5. Run
Code:
lilo -t -v
to see if all is OK, then...
6. Run
Code:
lilo
Then reboot and you should get to your slackware installation.

If anything fails along the way please post exactly what happens here and we will try to take it from there.

Good luck!
 
Old 06-05-2010, 04:54 PM   #9
abrahammer
Member
 
Registered: Dec 2006
Posts: 41

Original Poster
Rep: Reputation: 15
hello, what i needed to know was that i could chroot a partition to update lilo. Now the os boots fine, i'll make sure to read the documentation before posting if i have another problem, but sometimes there are little things like this that one doesn't manage to solve without asking, so thanks for answering, really apreciate.
 
Old 06-05-2010, 05:08 PM   #10
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware: 12.1, 13.1, 14.1, 64-14.1, -current, FreeBSD-10
Posts: 1,658

Rep: Reputation: 570Reputation: 570Reputation: 570Reputation: 570Reputation: 570Reputation: 570
Quote:
Originally Posted by abrahammer View Post
hello, what i needed to know was that i could chroot a partition to update lilo. Now the os boots fine, i'll make sure to read the documentation before posting if i have another problem, but sometimes there are little things like this that one doesn't manage to solve without asking, so thanks for answering, really apreciate.
I certainly know how important it is to be able to ask for those missing bits of knowledge!

Glad you got it working - glad to help!
 
Old 06-05-2010, 06:36 PM   #11
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,428

Rep: Reputation: 407Reputation: 407Reputation: 407Reputation: 407Reputation: 407
Quote:
Originally Posted by abrahammer View Post
hello, what i needed to know was that i could chroot a partition to update lilo. Now the os boots fine, i'll make sure to read the documentation before posting if i have another problem, but sometimes there are little things like this that one doesn't manage to solve without asking, so thanks for answering, really apreciate.
The interesting bit is that for an initial install of Slackware (in other words, from scratch), you almost certainly must run "chroot /mnt" prior to running mkinitrd. I have found that the installer kernel does not have all of the modules available that the generic kernel uses. (I guess if you choose to run the huge kernel yourself, this wouldn't be a problem.)

I used to solve the problem by symlinking everything that I needed into the /mnt area; needless to say, that was time consuming, irritating, and error prone beyond belief. Alien Bob mentioned in an e-mail that "chroot /mnt" would allow mkinitrd to work without any such administrative contortions. (It's actually mentioned in the README_LVM.TXT file on the installer.)

He was right.
 
Old 06-06-2010, 01:55 AM   #12
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-14.1 on a Lenovo T61 6457-4XG
Posts: 4,015

Rep: Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962
To avoid all that I always install lilo at first with the kernel-huge image
 
  


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


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel Panic while booting with a newly compiled kernel coolkrish Linux - Newbie 1 06-04-2008 06:22 AM
kernel panic while booting custom compiled 2.6.24 kernel on RHEL 4 AS samkraju Red Hat 4 02-10-2008 12:55 AM
kernel panic while booting gangaraju Fedora 7 06-19-2007 10:06 AM
Problem booting up new kernel. Kernel panic error... RHLinuxGUY Red Hat 2 04-11-2004 04:59 AM
kernel panic when booting 2.4.22 doncrawley Linux - Newbie 1 09-28-2003 11:55 PM


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

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