Arch Linux

whot

Member

Registered: 2005-03-13

Posts: 18

[SOLVED] Can't boot after kernel upgrade to 2.6.25.10

Hi All,

Did pacman -Syu.  Update completed ok.  Including kernel26.

Modified rc.conf, added fuse to modules array for gnome.  I don't know if this is causing the problem.

After reboot I get the following during boot:

------SNIP---------
:: Loading root filesystem module...
Attempting to create root device '/dev/hdb3'
ERROR: Failed to parse block device name for '/dev/hdb3' unknown
ERROR: root fs cannot be detected.  Try using rootfstype= kernel parameter.
Waiting for devices to settle...done.

Root device '/dev/hdb3' doesn't exist, attempting to create it
ERROR: Failed to parse block device name for '/dev/hdb3'
ERROR: Unable to create/detect root device "/dev/hdb3'
Dropping to recovery shell...type 'exit' to reboot
NOTE: klibc contains no 'ls' binary, use 'echo *' instead

If the device '/dev/hdb3' gets created while you are here, try adding 'rootdelay=8' or higher to
the kernel command-line
ramfs$
------SNIP---------

This happens with the fallback kernel also.

Any and all help is greatly appreciated.

Last edited by whot (2008-07-07 13:57:26)

tigrmesh

IRC Op

From: Florida, US

Registered: 2007-12-11

Posts: 794

Re: [SOLVED] Can't boot after kernel upgrade to 2.6.25.10

Please post your rc.conf.

whot

Member

Registered: 2005-03-13

Posts: 18

Re: [SOLVED] Can't boot after kernel upgrade to 2.6.25.10

Used Knoppix Disk to remove fuse from modules array.  Rebooted and still same bad result.

Lots of messages after Loading udev  and before ::Running Hook [filesystems]

This is the first time I remember seeing these type of messages.

They look like sata configuration instead of pata. (sda,sdb instead of hdb etc.)

----SNIP----
.
.
ata2.01: configured for UDMA/33
.
.
scsi 1:0:1:0: Direct-Access   IOMEGA ....
Driver 'sd' needs updating - please use bus_type methods
sd 0:0:0:0:  [sda] ...
.
.
  sda: sda1
sd 0:0:0:0: [sdb] ...
.
.
sdb: sdb1 sdb2 sdb3 ...
sd 1;0:1:0: [sdc]
done.
:: Running Hook [filesystems]
:: Loading root filesystem module...
Attempting to create root device '/dev/hdb3'
ERROR: Failed to parse block device '/dev/hdb3' unknown
.
-------SNIP----------

Here is rc.conf

---------------
#
# /etc/rc.conf - Main Configuration for Arch Linux
#

#
# Localization
#
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/unimaps
# USECOLOR: use ANSI color sequences in startup messages
#
HARDWARECLOCK="localtime"
TIMEZONE=EST5EDT
KEYMAP=us
CONSOLEFONT=default8x16.psfu.gz
CONSOLEMAP=
USECOLOR="yes"

# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by hwdetect
MOD_BLACKLIST=()

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# Networking
#
HOSTNAME="V5fdzg77e"

#
# Module to load at boot-up (in this order)
#   (prefix a module with a ! to disable it)
#
#MODULES=(!usbserial !ide-scsi snd-emu10k1x snd-pcm-oss
#snd-seq-oss snd-mixer-oss)
#MODULES=(!usbserial !ide-scsi snd-emu10k1 snd-pcm-oss)
#MODULES=(!usbserial capability)
MODULES=(!usbserialy)

#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   (prefix an interface in INTERFACES with a ! to disable it)
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)

#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   (prefix a route in ROUTES with a ! to disable it)
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

#
# Daemons to start at boot-up (in this order)
#   (prefix a daemon with a ! to disable it)
#   (prefix a daemon with a @ to start it up in the background)
#
#DAEMONS=(syslog-ng hotplug !pcmcia network netfs crond)
DAEMONS=(syslog-ng !hotplug !pcmcia network firestarter netfs cups crond
dbus hal alsa nvidia)
#dbus hal alsa gensplash nvidia gdm)
#dbus hal alsa)
#archstatsrc)
#
# -----------------------------------------------------------------------
# GENSPLASH
# -----------------------------------------------------------------------
#
# VERBOSEONFAIL: drop to verbose splash on rc fail events.
# Please note - splash ALWAYS drops to verbose if fs check fails
#
#VERBOSEONFAIL="yes"

# End of file

Last edited by whot (2008-07-07 04:17:09)

m_kylli

Member

Registered: 2008-07-07

Posts: 8

Re: [SOLVED] Can't boot after kernel upgrade to 2.6.25.10

Kernel upgrades kan sometimes cause block-devices to change names.
Have you tried renaming '/dev/hdb3' to '/dev/sdb3' ?

whot

Member

Registered: 2005-03-13

Posts: 18

Re: [SOLVED] Can't boot after kernel upgrade to 2.6.25.10

Haven't tried renaming because fstab uses:

/dev/hdb2
/dev/hdb3
/dev/hda1

Is fstab used only after kernel is booted?  If it is I will try your suggestion.

Purch

Member

From: Finland

Registered: 2006-02-23

Posts: 229

Re: [SOLVED] Can't boot after kernel upgrade to 2.6.25.10

Change the kernel line in grub:  hdx -> sdx (choose the line in the grub menu and press 'e')

Last edited by Purch (2008-07-07 07:41:28)

m_kylli

Member

Registered: 2008-07-07

Posts: 8

Re: [SOLVED] Can't boot after kernel upgrade to 2.6.25.10

On the kernel line of menu.lst grub uses the 'root=/dev/hdb3' parameter to tell the kernel on which device contains the root filesystem.
The kernel can then find and read '/etc/fstab' to mount the devices it should. If the kernel upgrade has caused the devices to change names
you should try changing 'root=/dev/hdb3' in menu.lst to 'root=/dev/sdb3' and change the entries in fstab from '/dev/hdXX' to '/dev/sdXX'.

whot

Member

Registered: 2005-03-13

Posts: 18

Re: [SOLVED] Can't boot after kernel upgrade to 2.6.25.10

SOLVED

I changed the kernel line in grub: hdx -> sdx.  This allowed the kernel to boot.

It failed at  ::Checking Filesystem. 

I used Knoppix disk to:
Modify  /boot/grub/menu.lst  changed hdx -> sdx
Modify  /etc/fstab  changed all /dev/hdxx to /dev/sdxx (/dev/hdb3 -> /dev/sdb3, /dev/hda1 -> /dev/sda1, etc)

Rebooted and I have my system back and working.

Thank you everyone for your help.

Why did I need to change the names of the devices?  Did something in mkinitcpio (initrd?) change?

Thanks.

m_kylli

Member

Registered: 2008-07-07

Posts: 8

Re: [SOLVED] Can't boot after kernel upgrade to 2.6.25.10

I use persistant block device naming to avoid problems with devices
changing names. The wiki entry also seem to describe your problem in point two of 'Why persistent naming?'.

whot

Member

Registered: 2005-03-13

Posts: 18

Re: [SOLVED] Can't boot after kernel upgrade to 2.6.25.10

Thank you.  I'll check it out.