kernel 2.6.30 boot error

linopolus · 2009-06-24 17:10:44

Hi
I have a prob with kernel 2.6.30: I upgraded it from 2.6.29 without errors, appended .conf to any files in /etc/mkinitcpio.d/ and tried to reboot.
But: FAIL
The errors a bit shortened(don't have a camera:():

Parsing Hook: filesystems
loading module: ext3
waiting for devices to settle... done
root device /dev/sda5 not found, try to create it..
ERROR: failed to parse block device name /dev/sda5
ERROR: failed to create/detect root device /dev/sda5

I also tried it with the UUID, but the same in green:(
blkid says:

% sudo blkid
/dev/sda1: UUID="56586C99586C7A1F" TYPE="ntfs" 
/dev/sda2: UUID="e4743c5b-c23d-49e5-9ec2-97506d22d727" SEC_TYPE="ext2" TYPE="ext3" 
/dev/sda3: TYPE="swap" UUID="0ef0e63e-8721-4823-ad23-ca6b5032cf9f" 
/dev/sda5: UUID="e9e3ee1d-4ffa-44f5-8e4f-62391ec5057b" SEC_TYPE="ext2" TYPE="ext3" 
/dev/sda6: UUID="2142730A00DD9F6D" LABEL="Daten" TYPE="ntfs"

My fstab:

#<file system>                <dir>                                <type>            <options>                                                    <dump>    <pass>
none                                    /dev/pts                        devpts            defaults                                                    0                0
none                                    /dev/shm                        tmpfs                defaults                                                    0                0
/dev/sda1                            /mnt/windows                ntfs-3g            noauto,users,noatime,uid=1000            0                0
/dev/sda2                            /mnt/ubuntu                    ext3                noauto,users,noatime,uid=1000        0                0
/dev/sda6                            /mnt/daten                    ntfs-3g            auto,users,noatime,uid=1000                0                0
/dev/psp                            /mnt/psp                        vfat                noauto,users,rw,noatime,uid=1000    0                0
/dev/usb-stick_grau        /mnt/usb-stick_grau    vfat                noauto,users,rw,noatime,uid=1000    0                0
/dev/sdb1                            /mnt/test                        ext3                noauto,users,noatime,uid=1000            0                0
/dev/sr0                            /mnt/dvd0                        udf,iso9660    noauto,users,uid=1000,unhide,ro        0                0
/dev/sr1                            /mnt/dvd1                        udf,iso9660    noauto,users,uid=1000,unhide,ro        0                0

UUID=0ef0e63e-8721-4823-ad23-ca6b5032cf9f    swap    swap    defaults                    0    0
UUID=e9e3ee1d-4ffa-44f5-8e4f-62391ec5057b    /            ext3    defaults,noatime    0    1

With kernel 2.6.29 after a downgrade it runs:(
Plz help me!

Last edited by linopolus (2009-06-25 08:48:47)

n37 · 2009-06-24 17:27:28

Given the number of topics reporting bugs/problems with 2.6.30, I wouldn't advise anyone to upgrade. I upgraded this morning and now I'm back with 2.6.29.
As far as your sitution is concerned, I recently experienced exactly the same when I moved a disk with an arch install from one machine to another. The solution was to use the fallback option in grub. It allowed me to boot into arch and then I reinstalled the kernel. However, it was a 2.6.29 kernel, so I'm not sure whether that would be of help to you.

Last edited by n37 (2009-06-24 17:27:50)

linopolus · 2009-06-24 17:43:45

The fallback image didn't help. I must downgrade out of a chroot from ubuntu.

Pank · 2009-06-24 19:28:02

Sorry for not starting a new topic (due to lack of time) but I have a similar problem.
My problem is as follows.
I update to the new kernel. According to the pacman output everything is fine. However, when I reboot I am not able to start linux. The boot up does not even get past the initial kernel-stuff. The computer reboots after having shown the line "decompressing linux". The fallback image does not work either.

I booted a usb-linux (larch) and chrooted my linux disk and did pacman -S kernel26. When I do this I get errors from mkinitcpio since it is not able to access /dev/null. However, once I reboot I am able to boot into Arch again. . .

If I try pacman -S kernel26 it will fail again. . .

I have no idea what mkinitcpio and I did not understand the wiki.

My primary problem is that I do not know if my kernel is configured correctly and I do not have an cached version of the kernel. (I could of course get the older kernel image . . .)

--Rasmus

linopolus · 2009-06-25 07:15:18

Pank wrote:

Sorry for not starting a new topic (due to lack of time) but I have a similar problem.
My problem is as follows.
I update to the new kernel. According to the pacman output everything is fine. However, when I reboot I am not able to start linux. The boot up does not even get past the initial kernel-stuff. The computer reboots after having shown the line "decompressing linux". The fallback image does not work either.
I booted a usb-linux (larch) and chrooted my linux disk and did pacman -S kernel26. When I do this I get errors from mkinitcpio since it is not able to access /dev/null. However, once I reboot I am able to boot into Arch again. . .
If I try pacman -S kernel26 it will fail again. . .
I have no idea what mkinitcpio and I did not understand the wiki.
My primary problem is that I do not know if my kernel is configured correctly and I do not have an cached version of the kernel. (I could of course get the older kernel image . . .)
--Rasmus

You must mount not only the root dev but also do

mount -t proc none /mnt/YOURMOUNTEDROOTDEVICE/proc && mount -o bind /dev /mnt/YOURMOUNTEDROOTDEVICE/dev

. Then the errors won't appear.

Plz show us your /etc/mkinitcpio.conf!

Last edited by linopolus (2009-06-25 07:16:26)

Pank · 2009-06-25 07:48:11

Hi,
Thanks. As said, it worked although there were errors.

This is my (unmodified) mkinitcpio.conf:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES=""

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish.  This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway.  This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
#    FILES="/etc/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
#    This setup specifies all modules in the MODULES setting above.
#    No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
#    This setup will autodetect all modules for your system and should
#    work as a sane default
#    HOOKS="base udev autodetect pata scsi sata filesystems"
#
#    This is identical to the above, except the old ide subsystem is
#    used for IDE devices instead of the new pata subsystem.
#    HOOKS="base udev autodetect ide scsi sata filesystems"
#
#    This setup will generate a 'full' image which supports most systems.
#    No autodetection is done.
#    HOOKS="base udev pata scsi sata usb filesystems"
#
#    This setup assembles an pata raid array with an encrypted root FS.
#    Note: See 'mkinitcpio -H raid' for more information on raid devices.
#    HOOKS="base udev pata raid encrypt filesystems"
#
#    This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata filesystems"

# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"

Thanks,
Rasmus

PS: when I run pacman -Syu I get the following error:

aufs2 needs kernel26<2.6.30

. I don't know if that means anything.

linopolus · 2009-06-25 07:49:49

It means that aufs2 need the Kernel in a version below 2.6.30 eg 2.6.29.
plz open a new thread!

Pank · 2009-06-25 08:19:16

Sorry for hijacking your thread then And Thanks for the tips!
--Rasmus

szal · 2009-06-25 08:32:10

linopolus wrote:

I have a prob with kernel 2.6.30: I upgraded it from 2.6.29 without errors, appended .conf to any files in /etc/mkinitcpio.d/ and tried to reboot.
But: FAIL
[...]
ERROR: failed to parse block device name /dev/sda5
ERROR: failed to create/detect root device /dev/sda5

There you have your mistake (see underlined part in the quote). There's no need to alter any filenames in /etc/mkinitcpio.d/, neither before nor after upgrading the kernel. Leave the filenames as-is and you'll be set.

Rgds

Sven

linopolus · 2009-06-25 08:53:40

szal wrote:

linopolus wrote:
I have a prob with kernel 2.6.30: I upgraded it from 2.6.29 without errors, appended .conf to any files in /etc/mkinitcpio.d/ and tried to reboot.
But: FAIL
[...]
ERROR: failed to parse block device name /dev/sda5
ERROR: failed to create/detect root device /dev/sda5
There you have your mistake (see underlined part in the quote). There's no need to alter any filenames in /etc/mkinitcpio.d/, neither before nor after upgrading the kernel. Leave the filenames as-is and you'll be set.
Rgds
Sven

That didn't help:(

TjPhysicist · 2009-06-25 09:11:41

I have been told in irc that mkinitcpio now has a changed algorithm for HDD detection. Can anyone confirm this? all these problems may be related to mkinitcpio. (cuz the little people who do not use it on irc are fine, including me )

ETA: s/forum/irc

Last edited by TjPhysicist (2009-06-25 09:22:46)

combuster · 2009-06-25 10:54:51

For me both arch and my custom kernel are working fine... Don't know why a lot of people are having trouble...

Dave Cohen · 2009-06-25 16:43:42

I have this problem too. Could it be related to RAID arrays? I ask because I'm booting from a RAID array, and see this thread: http://bbs.archlinux.org/viewtopic.php?id=68536

All that said, I'm helpless in this recovery shell that I now boot into. Can someone walk me through how to downgrade my kernel?

Pank · 2009-06-25 17:04:35

I use JFS file system. I have posted my error description above.
--Rasmus

Trent · 2009-06-25 22:54:13

I had a similar problem to the OP's, and the problem was my mkinitcpio.conf. When merging the two during the upgrade I accidentally removed the space between 'usb' and 'filesystems' which led to obvious problems. I hope nobody else has this precise problem, but I thought I'd let you know that in my case it was an initrd problem -- you should try tweaking your mkinitcpio.conf.

ione · 2009-06-26 12:06:18

hi!

i had a similar problem as in the opening message, except i used 'hd?' names prior to updating to 2.6.30-5. though in mkinitcpio.conf i had 'pata' hook seems i not used libata pata driver afterall all that time. and in the modules section of the same file i had only one module 'amd74xx'.

the problem was that with 'pata' hook, my system needed proper kernel modules in the modules section of mkinitcpio.conf, that is 'pata_amd' in my case (order of modules is important: 'pata_amd' had to be the first one). to put driver in place i had to properly chroot and reinstall kernel26 (or you could just regenerate with mkinitcpio the ramdisk). after reboot i got a bunch of errors due to device naming problems (hd? -> sd?) because earlier i not used persistent names, but after another chroot and editing fstab/menu.lst it worked. i found out which module i need, by trying out with the help of the output of the mkinitcpio -M command (when in livecd).

after this, i switched to persistent block device naming. now i used new libata driver but i not liked it because of small irritating noises coming from hdds, and poor performance compared to earlier. so i changed back to legacy ide support by replacing 'pata' with 'ide' hook in mkinitcpio.conf, and removed 'pata_amd' too from modules. good thing that because of persistent naming, now i didn't have to chroot and edit fstab, etc. because i refer to devices by-label in relevant files.

linopolus · 2009-07-02 05:30:36

I don't use a array or exotic filesystems

thisllub · 2009-07-13 11:00:17

This problem is stopping me from getting xen to work.

On booting the xen kernel ide drives are found but not sata.
Maybe someone will see this and understand the problems above as well as mine.
I am just about out of ideas.

mkinitcpio -g /boot/kernel26xen.img -k 2.6.18.8-xen -p xen0
....

ERROR: module 'amd74xx' not found
ERROR: module 'ide[-_]pci[-_]generic' not found
ERROR: module 'scsi[-_]mod' not found
ERROR: module 'sata[-_]nv' not found
ERROR: module 'ext3' not found

I have checked for the presence of the modules (e.g. :/lib/modules/2.6.18.8-xen/kernel/drivers/scsi/sata_nv.ko) and they are all there.

Curiously
mkinitcpio -M -c /etc/mkinitcpio.d/xen0.conf

lists sata_nv but not the others.

xen0.conf is just a copy of the default xen0.preset is

source /etc/mkinitcpio.d/xen0.kver

PRESETS=('default' 'fallback')

default_config="/etc/mkinitcpio.d/xen0.conf"
default_image="/boot/xen0.img"

fallback_config="/etc/mkinitcpio.d/xen0-fallback.conf"
fallback_image="/boot/xen0-fallback.img"

Arch Linux

#1 2009-06-24 17:10:44

kernel 2.6.30 boot error

#2 2009-06-24 17:27:28

Re: kernel 2.6.30 boot error

#3 2009-06-24 17:43:45

Re: kernel 2.6.30 boot error

#4 2009-06-24 19:28:02

Re: kernel 2.6.30 boot error

#5 2009-06-25 07:15:18

Re: kernel 2.6.30 boot error

#6 2009-06-25 07:48:11

Re: kernel 2.6.30 boot error

#7 2009-06-25 07:49:49

Re: kernel 2.6.30 boot error

#8 2009-06-25 08:19:16

Re: kernel 2.6.30 boot error

#9 2009-06-25 08:32:10

Re: kernel 2.6.30 boot error

#10 2009-06-25 08:53:40

Re: kernel 2.6.30 boot error

#11 2009-06-25 09:11:41

Re: kernel 2.6.30 boot error

#12 2009-06-25 10:54:51

Re: kernel 2.6.30 boot error

#13 2009-06-25 16:43:42

Re: kernel 2.6.30 boot error

#14 2009-06-25 17:04:35

Re: kernel 2.6.30 boot error

#15 2009-06-25 22:54:13

Re: kernel 2.6.30 boot error

#16 2009-06-26 12:06:18

Re: kernel 2.6.30 boot error

#17 2009-07-02 05:30:36

Re: kernel 2.6.30 boot error

#18 2009-07-13 11:00:17

Re: kernel 2.6.30 boot error

Board footer