Re: /dev/md0 don't start after controller change
On 12/7/06, martin f krafft <madduck@debian.org> wrote:
also sprach Andrea Ganduglia <nonews.org@gmail.com> [2006.12.05.1557 +0400]:
> But if I do this command onto RAID1 it said that md0 is still in use
> (sure! is root's partition!). If I add manually others disk (mdadm
> --add /dev/md0 /dev/sdc1) it works, but on reboot only sda1 and sdb1
> are parts of this raid, while sd{c,d,e,f}1 are mark as removed!
Please post the contents of /proc/mdstat after adding the
sd{c,d,e,f}1 components.
Hi martin, and thanks for your reply.
This is /proc/mdstat after mdadm --add /dev/md0 sd{c,d,e,f}1
Personalities : [raid0] [raid1] [raid5]
md1 : active raid5 sda2[0] sdb2[5] sde2[4] sdc2[3] sdd2[2] sdf2[1]
839845632 blocks level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
md0 : active raid1 sda1[0] sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1]
29294400 blocks [5/5] [UUUUU]
unused devices: <none>
This is after reboot!
Personalities : [raid0] [raid1] [raid5]
md1 : active raid5 sda2[0] sdb2[5] sde2[4] sdc2[3] sdd2[2] sdf2[1]
839845632 blocks level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
md0 : active raid1 sda1[0] sdb1[1]
29294400 blocks [5/2] [UU___]
unused devices: <none>
--
Openclose.it - Idee per il software libero
http://www.openclose.it
Reply to: