Re: messed up raid5 array

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> One disk failed in my four disk raid5 array this morning. I think I messed
> up a bit, anyway it ended with that I removed all disks from the raid
array.
> Now when I add them again they show up as spares and I have no main disks
at
> all. Is there a way to force the three remaining disks (excluding the
faulty
> one) to be an array again and not lose the current data? If I do --create,
> mdadm warns me that they are already a part of md1, yes but just as
spares!
> If I let mdadm do --create, I suppose I lose all the data? What can I do?

Replying to myself here... Can I do something like "mkraid --force" with
mdadm? I don't have any raidtab and would prefer not to make one. I know
about the -f flag but what I want to do is to not add the disks as spares, I
want them back as the normal maindisks. The data on them should be OK, but I
suppose some raid meta data is wrong?

Regards, Henrik

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux