After upgrade linux-firmware (20100606-1) lvm root will not be loaded

ruy_lopez · 2010-06-21 19:43:02

Hello,

I'm a newbie, although arch has been running for 2 years now on my server.
after I've upgraded the system today with linux-firmware (20100606-1) (from kernel26-firmware(2.6.33.4-1), coreutils (8.5-2), dri2proto (2.3-1) udev (157-1),initscripts (2010.06-2) and mkinitcpio (0.6.6-1), I did not see any errors and rebooted.

The result was an error that my LVM root could not be created.

I have a /boot that is outside lvm and then my root and home etc are in the lvm.

When looking closer at the creation of the kernel26.img I noticed that the usual usb, keymap and lvm2 were not created.

Why he did not make it now like before I do not know (maybe because of the upgrade of the mkinicpio?)

I've booted my system with sysresccd and edited the /etc/mkinitcpio.conf to include usb, keymap and lvm2 (in the order it normally is created)

Now the problem is that I do not have a clue how to solve how to build the new image, since I can not boot into my system to run the command:
/sbin/mkinitcpio -k 2.6.34-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img

I've tried it with the lvm root and my boot mounted and then run an adjusted command but it does not work because it needs stuff from /sbin (like gen_init_cpio.

I've tried starting up from the arch2010.05 CD but after lvmdiskscan I get an error that the device-mapper driver is missing in the kernel.
(I've did a "modprobe md_mod" and "modeprobe -l | grep md-mod" shows kernel/drivers/md/md-mod.ko so I figure it is loaded.
How can I solve this?

Last edited by ruy_lopez (2010-06-21 19:49:10)

nogoma · 2010-06-21 19:55:16

If you need to regenerate your initcpio, you can chroot into your arch install from the rescue CD environment. So, if you have your install root mounted as /mnt in your rescue CD environment (and whatever other LVM volumes mounted under it as appropriate):

# mount -o bind /dev /mnt/dev
# mount -t proc none /mnt/proc
# chroot /mnt /bin/bash

Now you should be able to regenerate your initcpio for your install. For device-mapper support, I believe you want the dm-mod module, not md-mod.

ruy_lopez · 2010-06-21 21:10:40

# chroot /mnt /bin/bash

Here I get an error.

chroot: cannot run command '/bin/bash' : Exec format error
the same with /bin/sh and without /bin/bash the error is

chroot: cannot run command '/bin/zsh': No such file or directory

Just an update:
With the arch 2010.5 CD I can change root and made a new image but it does not work.

I've only added lvm2 like this:
HOOKS="base udev autodetect pata scsi sata usb keymap lvm2 filesystems"

then when running the command:

/sbin/mkinitcpio -k 2.6.34-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img

there is an error
find: '/sys/devices/': No such file or directory.

when booting with the new image still the error comes up:
root device '/dev/mapper/lvmroot' doesn't exist.\Attempting to creat it.
ERROR: Unable to determine major/minor number of root device '/dev/mapper/lvmroot'.

You are bing dropped to a recovery shell.

Last edited by ruy_lopez (2010-06-21 21:49:26)

.:B:. · 2010-06-21 21:29:56

The linux-firmware upgrade has nothing to do with your error; a faulty initcpio rebuild sounds more likely.

ruy_lopez · 2010-06-21 22:38:07

This is a part of the error message that is still remaining:

:: LRunning Hook [keymap]
:: Loading keymap... done.
:: Running Hook [lvm2]
Scanning logical volumes
  Reading all physical volumes. This may take a while...
  No volume groups found
Activating logical volumes...
  No volume groups found
Waiting 10 seconds for device /dev/mapper/lvmroot ...
root device '/dev/mapper/lvmroot' doesn't exist.\Attempting to creat it.
ERROR: Unable to determine major/minor number of root device '/dev/mapper/lvmroot'.

You are being dropped to a recovery shell.

modprobe - l
kernel/drivers/md/dm-region-hash.ko
kernel/drivers/md/dm-log.ko
kernel/drivers/md/dm-snapshot.ko
kernel/drivers/md/dm-mod.ko
kernel/drivers/md/dm-mirror.ko
kernel/fs/reiserfs/reiserfs.ko
kernel/fs/jbd2/jbd2.ko
kernel/fs/jbd/jbd.ko
kernel/fs/ext3/ext3.ko
kernel/fs/ext2/ext2.ko
kernel/fs/ntfs/ntfs.ko
kernel/fs/mbcache.ko
kernel/fs/udf/udf.ko
kernel/fs/ext4/ext4.ko
kernel/lib/crc-itu-t.ko
kernel/lib/crc16.ko

So dm-mod is loaded and it seems he is processing the hook but he can not find the volumegroups.
With the rescue disk I can mount them so they are all right.

where should I look now? Any hints.

Last edited by ruy_lopez (2010-06-21 22:41:45)

ruy_lopez · 2010-06-22 17:22:31

Update:

The normal image did not work but the fallback without autodetect does work when recreated.
When I used that to boot I could create the normal image and it works.

I only saw an error about not able to lock the filesystem but the error came by to quick.
I've to look it up.

Arch Linux

#1 2010-06-21 19:43:02

After upgrade linux-firmware (20100606-1) lvm root will not be loaded

#2 2010-06-21 19:55:16

Re: After upgrade linux-firmware (20100606-1) lvm root will not be loaded

#3 2010-06-21 21:10:40

Re: After upgrade linux-firmware (20100606-1) lvm root will not be loaded

#4 2010-06-21 21:29:56

Re: After upgrade linux-firmware (20100606-1) lvm root will not be loaded

#5 2010-06-21 22:38:07

Re: After upgrade linux-firmware (20100606-1) lvm root will not be loaded

#6 2010-06-22 17:22:31

Re: After upgrade linux-firmware (20100606-1) lvm root will not be loaded

Board footer