Eamonn Hamilton wrote:
Hi Guys,
I'm looking at a server with a bunch of disks that had a raid 5 with two
spares, however, one of the spares failed, the system then started
rebuilding on the other and it crashed during the rebuild.
I'm now left in the following situation :
for a in a b c d e f g h i; do mdadm --examine --scan /dev/sd${a}; done
ARRAY /dev/md0 level=raid5 num-devices=7 UUID=e1e75e8b:f9f387cd:5feed4c5:31c51eb2
ARRAY /dev/md0 level=raid5 num-devices=7 UUID=e1e75e8b:f9f387cd:5feed4c5:31c51eb2
ARRAY /dev/md0 level=raid5 num-devices=7 UUID=e1e75e8b:f9f387cd:5feed4c5:31c51eb2
ARRAY /dev/md0 level=raid5 num-devices=7 UUID=e1e75e8b:f9f387cd:5feed4c5:31c51eb2
ARRAY /dev/md0 level=raid5 num-devices=7 UUID=e1e75e8b:f9f387cd:5feed4c5:31c51eb2
ARRAY /dev/md0 level=raid5 num-devices=7 UUID=e1e75e8b:f9f387cd:8d12a2d2:3188faf0
spares=1
ARRAY /dev/md0 level=raid5 num-devices=7 UUID=e1e75e8b:f9f387cd:8d12a2d2:3188faf0
ARRAY /dev/md0 level=raid5 num-devices=7 UUID=e1e75e8b:f9f387cd:8d12a2d2:3188faf0
spares=1
ARRAY /dev/md0 level=raid5 num-devices=7 UUID=e1e75e8b:f9f387cd:8d12a2d2:3188faf0
The system complains because of the different uuids, and refuses to
recreate the array.
Is it basically stuffed, or is there something I can do to recover the
2TB filesystem that's on there ?
What can you tell us about how that happened? When (if ever) was it
running, how was it created, etc, etc.
You could probably try some things like trying to start it read-only
using --force, but don't do that yet, if you get it wrong you WILL be
likely to lose data.
--
Bill Davidsen <davidsen@xxxxxxx>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
--
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
