I don't think it is related to Bug 115616. Yes, mdadm make's my machine unbootable, because mdadm and lvm2 are for some reasons not compatible. Needs a recovery disk to chroot in the error disk. *When mounting the /boot from the error disk*: I am able to do apt-get remove mdadm which cause regenerating of the initrd.img-2.6.28-14-server. Then the error disk will boot well.
2010/4/1 ceg <[email protected]> > > Thanks for responding. Oh I see, my comment about changing the partition > type was under the assumption of type fd Linux raid autodetect. > > Looking for the message you reported, could it be a little different and > rather unrelated to mdadm? (Bug #115616 > http://forum.ubuntuusers.de/topic/device-mapper-device-lookup- > failure/#post-767892). > > As you didn't actually write that mdadm made your machine unbootable > while installed, this actually issue seems resolved (as well as the > actual Bug #115616). Thanks again. > > > ** Changed in: mdadm (Ubuntu) > Status: New => Invalid > > -- > initramfs images not recreated during *un*-install > https://bugs.launchpad.net/bugs/418803 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “mdadm” package in Ubuntu: Invalid > > Bug description: > After installing mdadm on a running ubuntu 9.04 and doing nothing more than > reboot. It give a device mapper, dm-linear, Device loopup failed. This is > because of the 8e partition type. A apt-get remove mdadm doesn't fix the > error. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/418803/+subscribe > -- dm-linear, lookup failed https://bugs.launchpad.net/bugs/418803 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
