[Expired for mdadm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mdadm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/418803
Ti
[Expired for lvm2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lvm2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/418803
Titl
** Changed in: lvm2 (Ubuntu)
Status: New => Incomplete
** Changed in: mdadm (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/418803
Title:
dm-linear: l
Today, I reproduced for the third time the error after installing mdadm
to get more and better info:
Yes, there was a /etc/mdadm/mdadm.conf file before installing mdadm.
Changed this to mmadmin.conf. After installing mdamd (2.6.7.1-1ubuntu13)
a new /etc/mdadm/mdadm.conf appears. With diff mmadmin.
Didn't you write "A apt-get remove mdadm doesn't fix the error." in the
bug description, you may want to clarify the description a bit.
--
dm-linear: lookup failed / mdadm: breaks boot
https://bugs.launchpad.net/bugs/418803
You received this bug notification because you are a member of Ubuntu
Bug
Hm, I'm sorry I can't trace this down to other bugs then and help
finding the cause. Maybe superblock metadata are found on your disks is
causing mdadm to wait for arrays. You could add if installing mdadm did
create a /etc/mdadm/mdadm.conf with ARRAY definitions? Since you did not
purge mdadm it s
