LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
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 02-13-2012, 08:34 AM   #1
Azevedo
LQ Newbie
 
Registered: Feb 2012
Posts: 22

Rep: Reputation: Disabled
Kernel panic: lilo.conf: root="UUID=..."


Hey everyone!

I'm using this custom setting on lilo.conf to boot Slackware 13.37 and it gives me the kernel panic related to it.

lilo.conf:
root="UUID=..."

I have to use root="UUID=..." instead of root=/dev/sdX1 because X can change on every boot.

Any help?

Thanks
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 02-13-2012, 09:48 AM   #2
andrewthomas
Senior Member
 
Registered: May 2010
Location: Chicago Metro
Distribution: Arch, Gentoo, Slackware
Posts: 1,690

Rep: Reputation: 307Reputation: 307Reputation: 307Reputation: 307
When using UUID's, one must also use an initrd.
 
1 members found this post helpful.
Old 02-13-2012, 10:25 AM   #3
Azevedo
LQ Newbie
 
Registered: Feb 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
Thank you Andrew!

Pardon my newbie ignorance, but how do I configure this initrd?
Is there any disavantages using it?
 
Old 02-13-2012, 11:14 AM   #4
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,282

Rep: Reputation: 588Reputation: 588Reputation: 588Reputation: 588Reputation: 588Reputation: 588
Quote:
Originally Posted by Azevedo View Post
Thank you Andrew!

Pardon my newbie ignorance, but how do I configure this initrd?
Is there any disavantages using it?
Here is an article that should answer some of your questions.

http://slackware.osuosl.org/slackwar.../README.initrd
 
2 members found this post helpful.
Old 02-13-2012, 11:58 AM   #5
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 492
Blog Entries: 1

Rep: Reputation: 55
If you don't like using UUID (which I don't, in my own head I can never seem to match a UUID to a particular disk), the same initrd will allow you to use:
Code:
ROOT=LABEL=whatever
If you are still using the huge kernel, this is also a good time to put your filesystem in the initrd, per the above referenced README.initrd, & move to the generic kernel.
Regards,
Bill
 
1 members found this post helpful.
Old 02-15-2012, 12:48 PM   #6
Azevedo
LQ Newbie
 
Registered: Feb 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by TSquaredF View Post
If you don't like using UUID (which I don't, in my own head I can never seem to match a UUID to a particular disk), the same initrd will allow you to use:
Code:
ROOT=LABEL=whatever
If you are still using the huge kernel, this is also a good time to put your filesystem in the initrd, per the above referenced README.initrd, & move to the generic kernel.
Regards,
Bill
And how do I get the disk labels?


blkid -o list -c /dev/null
I can find the UUID

Last edited by Azevedo; 02-15-2012 at 12:49 PM. Reason: mistyped
 
Old 02-15-2012, 03:13 PM   #7
hotchili
Member
 
Registered: Sep 2009
Location: Germany
Distribution: slackware64-current
Posts: 72

Rep: Reputation: 18
Good day,

you have to set the LABEL yourself:
http://tldp.org/HOWTO/html_single/Pa.../#volumelabels

I used it to boot from a usb stick, worked well.
 
Old 02-15-2012, 04:12 PM   #8
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 492
Blog Entries: 1

Rep: Reputation: 55
Yes, as hotchili said, you make your own labels, thus the label may mean something to you in several months, when you have to reacquaint yourself with them.The above link deals with ext2/3/4 filesystems. If you use something else, you will have to research how to label the partitions.
Regards,
Bill
 
Old 02-15-2012, 09:04 PM   #9
Azevedo
LQ Newbie
 
Registered: Feb 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
Thank you guys!

This LDP is the ultimate kickass!
 
Old 02-17-2012, 05:46 PM   #10
Azevedo
LQ Newbie
 
Registered: Feb 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
Ok, thanks everyone! Now it boots after initrd is set up.

But then the system hangs up with these messages:
ERROR: no /sbin/init found on rootdev
/bin/sh: can't access tty; job control turned off


I added the entries on lilo.conf boot = "UUID: ..." and initrd = /boot/inird.gz.
Something like that

Maybe I missed something on /etc/lilo.conf?

Thanks
 
Old 02-17-2012, 06:26 PM   #11
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 492
Blog Entries: 1

Rep: Reputation: 55
That error generally means that you have not selected the proper root partition in the "root=whatever" statement. I use grub-2, this is the way I'm set up:
Quote:
linux /boot/vmlinuz-generic-3.2.2 root=LABEL=current ro
initrd /boot/initrd.gz
LILO will be different, but I don't know LILO, so can't tell you how.
Regards.
Bill
 
Old 02-17-2012, 07:21 PM   #12
Azevedo
LQ Newbie
 
Registered: Feb 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
I followed the instructions here: http://slackware.osuosl.org/slackwar.../README.initrd

mkinitrd -c -k 2.8.6.* -m ext4 -f ext4 -r /dev/sdb1

The command builds the /boot/initrd.gz succefully.
I reboot and it can't find the root even setting lilo to use initrd + UUID.

Now I'm back to beggining of my problem:

On reboot, /dev/sdb1 is not the same drive/partition.
I have 4 eSata drivers which can be detected in different orders /dev/sd* on each boot up (because not always all 4 drives are turned on).

Last edited by Azevedo; 02-17-2012 at 07:22 PM. Reason: spell check
 
Old 02-17-2012, 09:28 PM   #13
Uzuki
LQ Newbie
 
Registered: Jun 2010
Location: Indonesia
Distribution: Slackware, RedHat
Posts: 27

Rep: Reputation: 4
Quote:
Originally Posted by Azevedo View Post
Hey everyone!

I'm using this custom setting on lilo.conf to boot Slackware 13.37 and it gives me the kernel panic related to it.

lilo.conf:
root="UUID=..."

I have to use root="UUID=..." instead of root=/dev/sdX1 because X can change on every boot.

Any help?

Thanks
you forgot append before root=UUID=...
It should be like
Code:
append = "root=UUID=your disk UUID"
 
Old 02-19-2012, 12:21 PM   #14
Azevedo
LQ Newbie
 
Registered: Feb 2012
Posts: 22

Original Poster
Rep: Reputation: Disabled
Hey everyone!

Thanks for the replies. It still won't boot. The boot error is basically, it can't mount/find the root drive.
I tried with HDD UUID and LABEL.

One time it booted but when the root login is prompted, usb keyboard, everything else is locked.

Please, check the output below:

mkinitrd -c -k 2.6.29.6 -m ext4 -f ext4 -r /dev/sdb1
Code:
OK: /lib/modules/2.6.29.6/kernel/lib/crc16.ko added.
OK: /lib/modules/2.6.29.6/kernel/fs/jbd2/jbd2.ko added.
OK: /lib/modules/2.6.29.6/kernel/fs/mbcache.ko added.
OK: /lib/modules/2.6.29.6/kernel/fs/ext4/ext4.ko added.
lilo.conf
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:

# append=" vt.default_utf8=0 root=UUID=56c85790-3356-43ee-9261-06d086552a59"
append=" vt.default_utf8=0 label=slackware"
boot = /dev/sdb
default = "Linux" 

# 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 @ 1024x768x64k
# vga = 791
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# 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/sdb1
#  root = "UUID=56c85790-3356-43ee-9261-06d086552a59"
  root = "LABEL=slackware"
  initrd = /boot/initrd.gz
  label = Linux
  read-only
# Linux bootable partition config ends
Thanks for any help!
 
Old 02-19-2012, 11:26 PM   #15
Uzuki
LQ Newbie
 
Registered: Jun 2010
Location: Indonesia
Distribution: Slackware, RedHat
Posts: 27

Rep: Reputation: 4
Quote:
Originally Posted by Azevedo View Post
Hey everyone!

Thanks for the replies. It still won't boot. The boot error is basically, it can't mount/find the root drive.
I tried with HDD UUID and LABEL.

One time it booted but when the root login is prompted, usb keyboard, everything else is locked.

Please, check the output below:

mkinitrd -c -k 2.6.29.6 -m ext4 -f ext4 -r /dev/sdb1
Code:
OK: /lib/modules/2.6.29.6/kernel/lib/crc16.ko added.
OK: /lib/modules/2.6.29.6/kernel/fs/jbd2/jbd2.ko added.
OK: /lib/modules/2.6.29.6/kernel/fs/mbcache.ko added.
OK: /lib/modules/2.6.29.6/kernel/fs/ext4/ext4.ko added.
lilo.conf
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:

# append=" vt.default_utf8=0 root=UUID=56c85790-3356-43ee-9261-06d086552a59"
append=" vt.default_utf8=0 label=slackware"
boot = /dev/sdb
default = "Linux" 

# 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 @ 1024x768x64k
# vga = 791
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# 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/sdb1
#  root = "UUID=56c85790-3356-43ee-9261-06d086552a59"
  root = "LABEL=slackware"
  initrd = /boot/initrd.gz
  label = Linux
  read-only
# Linux bootable partition config ends
Thanks for any help!

Here is my lilo.conf, i use UUID.
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=1 resume=/dev/cryptvg/swap"
compact
boot = /dev/sda

# 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
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# 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

image = /boot/vmlinuz-generic-3.2.1-smp-2
  initrd = /boot/initrd-3.2.1-smp-2.gz
  append = "root=UUID=e200fb08-aac0-463a-a52a-1dd577da7564"
  label = Linux
  read-only
 
1 members found this post helpful.
  


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
[SOLVED] "Kernel panic" :VFS: Unable to mount root fs on 08:05" rsol4747 Slackware 7 04-20-2011 06:34 AM
"Kernel panic: VFS: Unable to mount root fs" - Kernel fails to boot linux Freedom Seeker Linux - General 11 11-12-2006 08:48 PM
"root=" option for SATA drives to avoid kernel panic neelay1 Linux - Software 1 05-01-2006 02:18 PM
Kernel Panic:VFS: Cannot open root device "hda3" or 00:10 shivendnrab Linux - General 1 07-01-2004 04:08 AM
error:"kernel panic: VFS: Unable to mount root fs":-( shyguy Linux - Newbie 1 07-23-2001 05:03 PM


All times are GMT -5. The time now is 10:49 PM.

Main Menu
Advertisement
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