FS#21659 - [kernel26] unable to determine major/minor modes of root device

Attached to Project: Arch Linux
Opened by Amitav (amitavmohanty01) - Wednesday, 10 November 2010, 13:41 GMT
Last edited by Allan McRae (Allan) - Saturday, 16 April 2011, 09:20 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
I am using kernel26; but on bootup it gives me the message in the image. My hooks are:
HOOKS="base udev autodetect pata scsi sata filesystems usbinput"

Additional info:
* package version(s)
2.6.35.8-1
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 16 April 2011, 09:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  Appears fixed...
Comment by Thomas Dziedzic (tomd123) - Thursday, 11 November 2010, 08:11 GMT
I have a feeling that this is a misconfiguration rather then a bug.
Comment by Amitav (amitavmohanty01) - Thursday, 11 November 2010, 15:40 GMT
I would prefer it to be a misconfiguration. Guide me to provide you more details to trace the root of the problem.
Comment by Roman Kyrylych (Romashka) - Monday, 15 November 2010, 19:20 GMT
Are you sure your root partition has that UUID?
Comment by Amitav (amitavmohanty01) - Tuesday, 16 November 2010, 04:42 GMT
Yes, I cross checked the uuid of the root partition: it matches with the one in the image.
Comment by Jacek Wojtkowski (jacek2v) - Sunday, 28 November 2010, 23:56 GMT
Hi,

I have the same problem after today's pacman -Syu update - I think kernel was update.
I don't change configuration today. After reboot I saw error : Root device does not exist ...

My grub menu.lst:
<"menu.lst">
# (0) Arch Linux
title Arch Linux
root (hd1,0)
kernel /vmlinuz26 root=/dev/sdb5 ro
initrd /kernel26.img

# (1) Arch Linux
title Arch Linux Fallback
root (hd1,0)
kernel /vmlinuz26 root=/dev/sdb5 ro
initrd /kernel26-fallback.img

# (2) Windows
title Windows
rootnoverify (hd0,0)
makeactive
chainloader +1
</"menu.lst">

It can be a good clue: ls -l /boot/
<"ls -l /boot/">
drwxr-xr-x 2 root root 4096 2010-11-28 23:55 grub
-rw-r--r-- 1 root root 8691963 2010-11-07 09:02 kernel26-fallback.img
-rw-r--r-- 1 root root 2034018 2010-11-07 09:01 kernel26.img
drwx------ 2 root root 16384 2010-03-23 20:22 lost+found
-rw-r--r-- 1 root root 1456835 2010-11-23 23:42 System.map26
-rw-r--r-- 1 root root 2208320 2010-11-23 23:42 vmlinuz26
</"ls -l /boot/">
I can't start my linux machine at all :( - fallback not working.
Comment by Amitav (amitavmohanty01) - Monday, 29 November 2010, 05:02 GMT
Arch is providing 2.6.36 kernel now. Please specify your kernel version. I have reported the problem for 2.6.35. A temporary solution would be to chroot into your / from a live cd and compile an older version. I ran 2.6.34 when I was facing this issue.
Comment by Jacek Wojtkowski (jacek2v) - Monday, 29 November 2010, 20:09 GMT
My kernel is 2.6.36 and I found solution :)

In pacman.log was:
<pacman.log>
[2010-11-28 16:01] >>> Generating initial ramdisk, using mkinitcpio. Please wai
t...
[2010-11-28 16:01] ==> Building image "default"
[2010-11-28 16:01] ==> Running command: /sbin/mkinitcpio -k 2.6.36-ARCH -c /etc/
mkinitcpio.conf -g /boot/kernel26.img
[2010-11-28 16:01] :: Begin build
[2010-11-28 16:01] :: Parsing hook [base]
[2010-11-28 16:01] :: Parsing hook [udev]
[2010-11-28 16:01] :: Parsing hook [autodetect]
[2010-11-28 16:01] :: Parsing hook [pata]
[2010-11-28 16:01] :: Parsing hook [scsi]
[2010-11-28 16:01] :: Parsing hook [sata]
[2010-11-28 16:01] ==> FAIL
<\pacman.log>

And solution is :
1. starting ArchLinux LiveCD
2. mounting root partition
3. chroot to root-partition
4. and execute mkinitcpio -p kernel26

That's all.
This bug is closed for me. Thanks for ur patience - sometimes the solution is comming after verbalization :)
Comment by Amitav (amitavmohanty01) - Monday, 29 November 2010, 21:30 GMT
Well that is why I specified the kernel version. The error does not occur in 2.6.36 or in 2.6.34.
Comment by Jacek Wojtkowski (jacek2v) - Monday, 29 November 2010, 21:32 GMT
My problem is in kernel 2.6.36 :) - during pacman update.
Comment by Jelle van der Waa (jelly) - Thursday, 14 April 2011, 21:38 GMT
is this issue still around?
Comment by Jacek Wojtkowski (jacek2v) - Friday, 15 April 2011, 08:14 GMT
This bug is closed for me. Solution above.
Comment by Amitav (amitavmohanty01) - Friday, 15 April 2011, 19:59 GMT
I have upgraded to latest kernel and this issue is not there. If anyone is still using older kernel, he might be interested in it. The bug is closed for me.