Am 14.04.2011 22:19, schrieb James:
> 
>> *Head scratch* This, uhm, looks odd. No clue what to make of it.
> 
> Ahhh,
> 
> Don't give up just yet?
> 
> I issued these commands:
> 
> mdadm --create /dev/md127 --level=1 --raid-devices=2
>  --metadata=0.90 /dev/sda1 /dev/sdb1
> 
> mdadm --create /dev/md125 --level=1 --raid-devices=2 
> --metadata=0.90 /dev/sda3 /dev/sdb3
> mdadm: /dev/sda3 appears to be part of a raid array:
>     level=raid1 devices=2 ctime=Thu Apr 14 13:22:32 2011
> mdadm: /dev/sdb3 appears to be part of a raid array:
>     level=raid1 devices=2 ctime=Thu Apr 14 13:22:32 2011
> Continue creating array? y
> 
> 
>  mdadm --create /dev/md126 --level=1 --raid-devices=2 
> --metadata=0.90 /dev/sda2 /dev/sdb2
> 
> I'm not sure if I just wiped the drives clean (empty)?
> 
> If so, I'll have to start over.....?
> 

Ouch, I didn't think of that. Well, I guess it will not wipe it, it will
merely re-sync the disks. Since they have been mirrors of each other
before this action, you might be lucky and it keeps working.

> mdadm  --detail /dev/md1  
> mdadm: cannot open /dev/md1: No such file or directory
> 
> same now for md2 and md3...
> 

Well, at least you are rid of the duplicate arrays.

> Look (ma no hands!):
> 
> livecd gentoo # mdadm --detail /dev/md125
> /dev/md125:
>         Version : 0.90
>   Creation Time : Thu Apr 14 14:15:21 2011
>      Raid Level : raid1
>      Array Size : 1948227584 (1857.97 GiB 1994.99 GB)
>   Used Dev Size : 1948227584 (1857.97 GiB 1994.99 GB)
>    Raid Devices : 2
>   Total Devices : 2
> Preferred Minor : 125
>     Persistence : Superblock is persistent
> 
>     Update Time : Thu Apr 14 15:51:46 2011
>           State : clean, resyncing
>  Active Devices : 2
> Working Devices : 2
>  Failed Devices : 0
>   Spare Devices : 0
> 
>  Rebuild Status : 37% complete
> 
>            UUID : fa800cdb:33955cfd:cb201669:f728008a (local to host livecd)
>          Events : 0.6
> 
>     Number   Major   Minor   RaidDevice State
>        0       8        3        0      active sync   /dev/sda3
>        1       8       19        1      active sync   /dev/sdb3
> 
> 
[...]
> We'll see in a few hours....
> 
> 
> James
> 

You can keep using it while it re-syncs. Re-syncing just means that you
do not have any redundancy, yet. You can still read/write on the array.
You will get or manipulate whatever mdadm thinks is the correct value
for each block. That's also what will end up on both disks, ultimately.
I guess you can even reboot but since your setup is not really
persistent, I wouldn't try it.

Regards,
Florian Philipp

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to