Dear Fumihito,
first of all, thanks for your fast reply! 

1) No, ?No, I'm on amd64.  I just went to the archive ubuntu site you
suggested and found out that the following exists:

mdadm-udeb_2.6.3+200709292116+4450e59-3ubuntu1_amd64.udeb   13-Dec-2007 01:04   
76K  
mdadm-udeb_2.6.3+200709292116+4450e59-3ubuntu1_i386.udeb    13-Dec-2007 00:04   
73K  
mdadm-udeb_2.6.3+200709292116+4450e59-3ubuntu1_powerpc.udeb 13-Dec-2007 01:04   
85K  
mdadm-udeb_2.6.3+200709292116+4450e59-3ubuntu1_sparc.udeb   13-Dec-2007 01:04   
91K  

...it seems a fresh new 2.6.3 version of mdadm - maybe it cures the bug
?!?

2) First time I deal with mdadm RAID, but from experiences on other OS
with SW RAID, I learned (the hard way) that it is safe not to mess
around with driver version different than the ones that created the
arrays. But if I have no alternatives... I will try.

3) I tried to find details of this new 2.6.3, but found none. Good
common sense makes me think that the mantainer od mdadm  was aware of
the bug and solved it in this new version, making the all "scripting
from grub menu" solution unnecessary...

Suggestions?

-- 
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to