mdadm broken after feisty upgrade, no boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: mdadm
after dist-upgrade to feisty, boot fails with mdadm errors. this is an amd64 system with lvm running over a simple mdadm raid; worked unproblematically in edgy and dapper.
boot errors:
-----
loading, please wait
bogl_init failed: setting screen size: cannot allocate memory
screen init failed
mdadm: no devices listed in conf file were found.
volume group not found
check root- bootarg cat /proc/cmdline
or missing modules, devices: cat /proc/modules ls /dev
alert! /dev/mapper/
shell
-------
chrooting into the broken system from a dapper livecd, I find that the filesystems are all still intact. trying to run dpkg-reconfigure mdadm givesthis output:
-------------------
W: mdadm: failed to load MD subsystem.
update-initramfs: Generating /boot/initrd.
W: mdadm: unchecked configuration file: /etc/mdadm/
W: mdadm: please read /usr/share/
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate temporary mdadm.conf file.
W: mdadm: using the unchecked file and hoping for the best...
update-initramfs: Generating /boot/initrd.
W: udev hook script requires at least kernel version 2.6.19
W: not generating requested initramfs for kernel 2.6.17-10-generic
invoke-rc.d: initscript mdadm-raid, action "start" failed.
-------
my /etc/mdadm/
-------------------
DEVICE partitions
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=a1c69140:
MAILADDR root
=------
system is pretty well unusable so of course I appreciate any guidance you can give! thanks,
matt
Changed in mdadm: | |
status: | Unconfirmed → Confirmed |
It is a known problem that is being worked out. At the moment the only workaround is to
run a couple of commands from the command line when you are dropped to the shell at boot time.
basically you need to start the raid manually, and then:
lvm vgscan
lvm vgchange -a y
exit
Fabio
PS Yes i am aware this is not optimal but as i said a fix shold land sometimes next week.