FS#13340 - [kernel26] Unable to create/detect root device

Attached to Project: Arch Linux
Opened by Maggie (Maggie34) - Tuesday, 17 February 2009, 15:14 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 03 October 2009, 19:51 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity High
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Since I've installed kernel 2.8.5-1 I can't boot my system. I still get an error:

Root device '/dev/sda1' doesn't exist, attempting to create it
ERROR: Failed to parse block device name for '/dev/disk/by-uuid/f53df57c-df2d-4926-9f42-6591bc014f60'
ERROR: Unable to create/detect root device '/dev/disk/by-uuid/f53df57c-df2d-4926-9f42-6591bc014f60'
Dropping to a recovery shell... type 'exit' to reboot
NOTE: klibc contains no 'ls' binary, use 'echo *' instead

Last working kernel is 2.6.25.6-1.

My hwd (only HDD):

HARDWARE DETECT ver 5.4.2 (simple mode)
Kernel : 2.6.25-ARCH
CPU & Cache: Processor 0: Intel(R) Pentium(R) 4 CPU 3.06GHz 3066MHz, 1024 KB Cache
Processor 1: Intel(R) Pentium(R) 4 CPU 3.06GHz 3066MHz, 1024 KB Cache

HDD : 182 SATA/RAID Controller module: sata_sis

My fstab:
UUID=239fae1c-b6e0-4f63-89eb-cdac1b8c9d6b /home ext3 defaults 0 1
UUID=81ed8ccc-3938-4d29-a115-507534d107e6 swap swap defaults 0 0
UUID=f53df57c-df2d-4926-9f42-6591bc014f60 / ext3 defaults 0 1

My menu.lst:

# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/f53df57c-df2d-4926-9f42-6591bc014f60 ro
initrd /boot/kernel26.img

# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/f53df57c-df2d-4926-9f42-6591bc014f60 ro
initrd /boot/kernel26-fallback.img

And mkinitcpio.conf:
MODULES="pata_acpi pata_sis ata_generic scsi_mod sata_sis"
HOOKS="base udev autodetect pata scsi sata usbinput keymap filesystems"

This task depends upon

Closed by  Roman Kyrylych (Romashka)
Saturday, 03 October 2009, 19:51 GMT
Reason for closing:  No response
Additional comments about closing:  no news here and in bugzilla.kernel.org
Comment by Maggie (Maggie34) - Tuesday, 17 February 2009, 15:15 GMT
And my mkinitcpio -v
Comment by Maggie (Maggie34) - Tuesday, 17 February 2009, 17:09 GMT
I'm sorry I mean kernel 2.6.28.5-1 :)
Comment by Alessandro Doro (adoroo) - Tuesday, 17 February 2009, 22:59 GMT
Other [non] working kernel between 2.6.25.6-1 (june 2008) and 2.6.28.5-1?
Can you boot with the fallback image?
See also  FS#12818 
Comment by Maggie (Maggie34) - Wednesday, 18 February 2009, 00:38 GMT
I've installed from 2008.06 CD on my PC (I've any backups from my notebook where was Arch installed and worked very fine). I found here http://schlunix.org/archlinux/ old kernels and tried some of them.
No, I can't boot whit the fallback image. I can't also install from 2009.02 CD -> my harddisk is not found! :(
Comment by Bob (Cotton) - Sunday, 22 February 2009, 22:16 GMT
I've also experienced the same "unable to boot" problem as described in the original fault report.
This was a new installation using the final RC of the 2009.02 USB image for i686 with an ftp installation on an ASUS EEE901 (the cd method didn't work as the /src/core/pkg didn't mount for some reason).
After being dumped to the recovery shell, I tried all the usual rootdelay=8, rootfstype=ext4, (+fall back image) solutions without success.
echo /dev/sd* showed that the USB SD card that arch had been installed to (sdc2) didn't exist, even when the UUID was changed to sdc2. (Though it would have been sdd2 at the time of install due to the installation media being sdc. sdd2 also didn't exist).
Chrooting to the installed system and running "pacman -S base" completed successfully and the standard & fallback images were created without error. But still not able to boot.
Howwever, chrooting and installing the AUR kernel26-eee901 package (http://aur.archlinux.org/packages.php?ID=22904) resulted in success;)
Re-installing the kernel26 package (2.6.28.6-1) still didn't result in a successful boot.

This anomaly has been reported elsewhere on the web for some months now (eg http://bbs.archlinux.org/viewtopic.php?id=48604) ut it is very rare, and I haven't seen a successful solution posted.

Note tht I used the same USB img to perform an identical ARCH installation to a desktop machine only a few days previously, without experiencing this problem. The only difference I can think of is that it was that the base install was from the source USB stick rather than via an ftp install.

TTFN. Sorry it was long winded.
Comment by Bob (Cotton) - Monday, 23 February 2009, 07:34 GMT
Having just installed the latest kernel (2.6.28.7) whilst running with kernel26-eee901, it appears to boot fine. In other words, the problem has just fixed itself!
Comment by Maggie (Maggie34) - Tuesday, 24 February 2009, 21:34 GMT
Not for me... I've installed 2.6.28.7 and have also this problem. With Debian( Stable, Testing), Ubuntu 8.10 and Sidux Ouranox... The last working kernel is 2.6.25.
Comment by Bob (Cotton) - Thursday, 26 February 2009, 07:41 GMT
Try the ASUS EEE901 kernel package that worked for me. Its based on 2.6.29rc6.

I've uploaded it to http://www.mediafire.com/?mkf2nmks24i
Comment by Bob (Cotton) - Thursday, 26 February 2009, 18:48 GMT
Having just installed the latest kernel (2.6.28.7) whilst running with kernel26-eee901, it appears to boot fine. In other words, the problem has just fixed itself!
Comment by Bob (Cotton) - Thursday, 26 February 2009, 18:54 GMT
Ignore that last (duplicate) post.
Comment by Maggie (Maggie34) - Thursday, 26 February 2009, 19:25 GMT
@ Bob (Cotton) - I have PC, Not Asus EEE.
Comment by Bob (Cotton) - Thursday, 26 February 2009, 20:35 GMT
I realize that, but you can still use that package to see if kernel 2.6.29 solves your problem.
Comment by Maggie (Maggie34) - Friday, 27 February 2009, 02:57 GMT Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 31 May 2009, 09:10 GMT
status of this?

Loading...