Bootup fails - Dmraid - probably new klibc

beomuex · 2008-10-09 18:07:09

Hi ,

i need your help!

My x86_64 machine does not reach any runlevel since yesterday.(upgraded on 7.8.2008)
There appears a strange error message when running this with "quiet" i cut some unnessary out....

:: Loading Initramfs
Buffer I/O error in device sdb3 locial block 389752828
*Same error 10 times with other blocks (all ~2828-2964)
ERROR: either the required RAID set not found or more options required
no raid sets and with names ">/dev/null"
ERROR: Failed to parse block device name for '/dev/mapper/nvidia_badbdbcap1'
ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter.
ERROR: Failed to parse block device name for '/dev/mapper/nvidia_badbdbcap1'
ERROR: Unable to create/detect root device '/dev/mapper/nvidia_badbdbcap1'
Dropping shell

This error comes right after the hwclock thing.

Here is my menu.lst mtab and the fstab: http://rafb.net/p/DEwGYu81.html
Perhaps this is important:

I also installed all the packages in the [testing] to get the newest klibc udev hal and dmraid.
After updating these, the identification of the devices changed from

nvidia_badbdbca*

to

nvidia_badbdbcap*

I changed this in the fstab mtab and in the menu.lst via the archlive rescue disk.
I also made a mkinitcpio - no effect on the booting process.

This has probably something to do with the initscripts, but i have no idea how to check that.

I hope somebody is into that...

thanks

Last edited by beomuex (2011-04-09 23:16:54)

lilsirecho · 2008-10-09 18:29:41

You may need to ...modprobe dm-mod...................

beomuex · 2008-10-09 20:02:25

Sorry but this doesn't help.
Still the same.

The system detects the partition, It mounts it actually (only readonly).
I'm also able to navigate in the filesystem after the check deploys a maintenance shell.
Reiserfs does his checks too:
ReiserFS: dm-1: found reiserfs format "3.6" with standart journal
etc...

Last edited by beomuex (2008-10-09 20:05:05)

ndlarsen · 2008-10-09 20:18:44

If you got udev-128-5 installed, try downgrading to 119-1. I had a unbootable system untill I did so.

# EDIT:

Nevermind, missed the part about updating from testing.

Last edited by ndlarsen (2008-10-09 20:23:34)

beomuex · 2008-10-09 20:29:23

ndlarsen, thank you so much.

Last edited by beomuex (2011-04-09 23:17:21)

uwolfer · 2008-10-11 09:43:09

I have had the same issue too now after updating kernel26 to 2.6.27. But I think the issue is in the new dmraid package. I first downgraded the kernel; it did not help. After I also downgraded dmraid and generated a new image. After that thing works well again.

Can you also confirm that dmraid package is broken?

hardfalcon · 2008-10-11 21:10:35

I figured out a way to get it to work again without downgrading any packages (at least on my 64 bit machine, where I have enabled the testing repo).

0.) You'll need a Linux boot CD with dmraid (Otherwise you obviously wont be able to access your soft-RAID and fix up the whole mess. An Archlinux setup CD is fine, if your's is too old and doesn't contain yet dmraid, you can boot from it, set up your internet connection with dhcpcd eth0, and then install it with pacman -Sy dmraid.)

1.) Create the /dev/mapper/ devices of your RAID with dmraid -ay and mount your Arch installation with mount -t ext3 /dev/mapper/XXXpN /mnt, where XXX stands for the name of the soft-RAID mapper device and N stands for the number of the partition. If you are not using ext3 but a different file system, you have of course to specify this filesystem instead of ext3.

2.) The whole problem actually comes from the fact that dmraid gives slightly different names to the mapper devices it creates for the partitions on your soft-RAID. For example, if you had /dev/mapper/nvidia_cfefjbch1 before your upgrade to kernel 2.6.27, you have now /dev/mapper/nvidia_cfefjbchp1. It seems added letter seems to be always a p (I guess this stands for "partition"), affects only the mapper devices of the partitions, but not the mapper device of the complete soft-RAID. Also, this seems to occur only if kernel 2.6.27 is used.
Now, to actually fix the mess, do the following:

a.) In your /boot/grub/menu.lst, you have to adapt all entries where the root parameter is specified in the kernel line.
For example,

kernel /boot/vmlinuz26 root=/dev/mapper/nvidia_cfefjbch1 ro

has to be changed into

kernel /boot/vmlinuz26 root=/dev/mapper/nvidia_cfefjbchp1 ro

b.) You have to adapt the entries your /etc/fstab. For example,

/dev/mapper/nvidia_cfefjbch1 / ext3 defaults 0 1

has to be changed into

/dev/mapper/nvidia_cfefjbchp1 / ext3 defaults 0 1

3.) Reboot.

Last edited by hardfalcon (2008-10-11 21:11:33)

uwolfer · 2008-10-11 21:28:20

hardfalcon: Are you sure this is because of kernel 2.6.27 (i.e. have you regenerated the boot image once before with the updated dmraid package?)

I will try your workaround later, thanks. Though I think such a change is not really acceptable... I would like to exactly know which package has introdruced this behavior.

hardfalcon · 2008-10-11 22:39:01

If you install the kernel26 package, the kernel image is always regenerated. I regenerated the kernel images after fixing menu.lst and fstab on my machine, but I doubt that this is necessary...
//EDIT: I don't know if kernel 2.6.27 is the initial cause for this, but I found out that if I booted from my Archlinux boot CD (which is from October 2007 and therefore rather outdated though), the created mapper devices had their "normal" names without the additonal p. As the boot CD didn't feature dmraid, I had to install it with pacman -Sy dmraid, so I assume the new dmraid package is not the cause of the problem...

Last edited by hardfalcon (2008-10-11 22:45:12)

uwolfer · 2008-10-12 09:13:35

Hmm, I'm still not sure... The dmraid package update to rc15 has been after the any kernel updates (at least for i686). So if you just updated dmraid, but not generated the kernel image, you would not have noticed that dmraid is broken until kernel 2.6.27 has been installed and thus the image has been regenerated.

tpowa · 2008-10-12 09:26:08

please inform me if the supposed bump to .27 is the cause, because i cannot test the dmraid thing

uwolfer · 2008-10-12 09:48:35

Ok, I can confirm now: dmraid rc15 is broken. I have just updated the kernel to .27 (but ignored dmraid), and things still work. If I update dmraid too, and regenerate the image, it does not boot anymore. I have not tried the workaround of hardfalcon yet.

tpowa · 2008-10-12 13:11:09

if it's just adding the p to your lines i could add an install message to add this, please confirm this

uwolfer · 2008-10-12 14:28:35

I can confirm now that adding 'p' before the number fixes the issue (in /etc/fstab and /boot/grub/menu.lst). Now dmraid rc15 and kernel .27 works well here.

tpowa · 2008-10-12 14:29:40

ok 'ill update rc15 and add a warning message, thanks guys for debugging this.

tiny · 2008-11-11 09:27:44

tpowa wrote:

ok 'ill update rc15 and add a warning message, thanks guys for debugging this.

What about the solution for first install? Dmraid isn't present on install disk.
I've posted my problem in another thread.

http://bbs.archlinux.org/viewtopic.php?id=58776

Arch Linux

#1 2008-10-09 18:07:09

Bootup fails - Dmraid - probably new klibc

#2 2008-10-09 18:29:41

Re: Bootup fails - Dmraid - probably new klibc

#3 2008-10-09 20:02:25

Re: Bootup fails - Dmraid - probably new klibc

#4 2008-10-09 20:18:44

Re: Bootup fails - Dmraid - probably new klibc

#5 2008-10-09 20:29:23

Re: Bootup fails - Dmraid - probably new klibc

#6 2008-10-11 09:43:09

Re: Bootup fails - Dmraid - probably new klibc

#7 2008-10-11 21:10:35

Re: Bootup fails - Dmraid - probably new klibc

#8 2008-10-11 21:28:20

Re: Bootup fails - Dmraid - probably new klibc

#9 2008-10-11 22:39:01

Re: Bootup fails - Dmraid - probably new klibc

#10 2008-10-12 09:13:35

Re: Bootup fails - Dmraid - probably new klibc

#11 2008-10-12 09:26:08

Re: Bootup fails - Dmraid - probably new klibc

#12 2008-10-12 09:48:35

Re: Bootup fails - Dmraid - probably new klibc

#13 2008-10-12 13:11:09

Re: Bootup fails - Dmraid - probably new klibc

#14 2008-10-12 14:28:35

Re: Bootup fails - Dmraid - probably new klibc

#15 2008-10-12 14:29:40

Re: Bootup fails - Dmraid - probably new klibc

#16 2008-11-11 09:27:44

Re: Bootup fails - Dmraid - probably new klibc

Board footer