feisty upgrade breaks mdadm on amd64

Matt Price matt.price at utoronto.ca
Sat Feb 3 14:41:09 UTC 2007


hi,

just tried upgrading my edgy amd64 system to feisty.  the dist=upgrade
went fine, with the usual difficulties as packages tried to overwrite
each other, but reboot now fails with both the new feisty 2.6.20-6
kernels and the old edgy 2.6.17 kernel.  The old kernels fail with the
old "kernel panic not syncing vfs unable to mount root fs on
unknown-block" error, which I'm thinking may have something to do with
udev versions.  The new kernels, however, hail with an error about
mdadm:

--------------

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/Anarres--64--main-root does not exist.  dropping to a
shell
---------------------

I have been able to start the machine using a dapper-live cd I had lying
around and the filesystems are all still fine.  this is an lvm running
on top of an mdadm RAID on 2 sata drives.  chrooting into the broken
system and trying to run dpkg-reconfigure mdadm I get the following
errors:

W: mdadm: failed to load MD subsystem.
update-initramfs: Generating /boot/initrd.img-2.6.20-6-lowlatency
W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .
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.img-2.6.17-10-generic
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.

mdadm.conf reads:

DEVICE partitions
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=a1c69140:16931871:f12033d8:e44398ce
MAILADDR root

I dont understand mdadm as well as I perhaps should and am wondering what I might do to try and fix this issue.  thanks!

matt


-- 
Matt Price
History Dept
University of Toronto
matt.price at utoronto.ca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20070203/2000be48/attachment.sig>


More information about the ubuntu-users mailing list