On Sun, 9 Mar 2014 11:34:56 +0100 Federico Foschini <undicizeri@xxxxxxxxx> wrote: > Hello, > I've consolidated the state of the system, these are the details: > > http://pastebin.com/k7wGpw8F (why do people insist on use pastebin rather than just including all the info directly in the email !?!?!) Based on this info the first thing to do it mdadm /dev/md1 --add /dev/md0 and wait for it to rebuild. Then you need to make sure it starts properly on reboot... What do you have in /etc/mdadm.conf (or maybe /etc/mdadm/mdadm.conf on ubuntu) ?? What is in that file in the initrd? zcat /boot/initrd | cpio -i --to-stdout etc/mdadm.conf md0 needs to be listed before md1. If not you should change that. However it could just be that Ubuntu's boot process is broken for multi-level arrays - it is easy to get wrong and not often tested. > > Notice how /dev/md0 has the Name : petra:md1 and /dev/md1 doesn't have > any superblock. Also it appears there is an old mdadm superblock on > /dev/sda1 with my previous array configuration. md1 does not have a superblock because it is not part of any array. The components that make up md1 have superblocks. As suggested by others, mdadm --zero-super /dev/sda1 will remove that old superblock. You can also remove the partition tables from /dev/sd[ab]1 with dd if=/dev/zero count=1 > /dev/sda1 etc. NeilBrown > > So now what I'm trying to achive is this configuration: removing the > hold partitions /dev/sda1 and /dev/sdb1 with the old superblock (by > the way how is it possible i'm using an array with /dev/sda and > /dev/sdb while these devices contains an old partition?) Configuring > correctly the raid 1 array with /dev/sdd and /dev/md0 > > 2014-03-09 9:31 GMT+01:00 Federico Foschini <undicizeri@xxxxxxxxx>: > > Done and rebooted. I'm in the same condition as before. Also when I > > update the initrd a message said "/dev/md1 doesn't appear to be > > active" > > > > 2014-03-09 8:58 GMT+01:00 Can Jeuleers <can.jeuleers@xxxxxxxxx>: > >> On 03/08/2014 09:23 PM, Federico Foschini wrote: > >>> What is going on? Why /dev/md1 is now inactive and /dev/sdd is busy? > >> > >> I don't know Federico, but have you tried updating your initrd and > >> rebooting? So that the assembly that takes place at boot uses the same > >> configuration as it would post-boot? > >> > > > > > > > > -- > > Federico Foschini. > > >
Attachment:
signature.asc
Description: PGP signature
