>> /proc/mdstat:
>> Personalities : [linear] [raid0] [raid1] [raid5]
>> read_ahead 1024 sectors
>> md4 : inactive sdc2[2]
>> blocks
>>
>> The thing is that I have no spare-discs available in my system and
>> that "spare" disc _is_ the one that has always been the second mirror
>> of /dev/md4.
>>
>
> It looks like maybe it was /dev/sdc that failed and when you rebooted
> without it, the old sdd was renamed to sdc.
>
> In any case, if the failed drive is really dead, the best you can hope
> for it
> mdadm -C /dev/md1 -l 1 -n 2 /dev/sdc2 missing
> and hope the data on it is recent enough.
> Note: this will not change the data on sdc2. It will only change the
> superblock and allow you to access what is there.
Ok, now the status is after the following command:
>mdadm -v --assemble /dev/md5 /dev/md3 /dev/md4
mdadm: looking for devices for /dev/md5
mdadm: /dev/md3 is identified as a member of /dev/md5, slot 0.
mdadm: /dev/md4 is identified as a member of /dev/md5, slot 1.
mdadm: added /dev/md4 to /dev/md5 as 1
mdadm: added /dev/md3 to /dev/md5 as 0
mdadm: /dev/md5 assembled from 1 drive - not enough to start the array.
/proc/mdstat:
Personalities : [linear] [raid0] [raid1] [raid5]
read_ahead 1024 sectors
md5 : inactive md3[0] md4[1]
0 blocks
md4 : active raid1 sdc2[0]
60034880 blocks [2/1] [U_]
md3 : active raid1 hdg2[2] hde2[1]
58616640 blocks [2/1] [_U]
Any ideas ? :)
Regards,
Tomi Orava
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
