Hi Kevin,
On 11/04/2013 08:51 AM, Kevin Wilson wrote:
> Good day All,
[snip /]
Good report, BTW.
> 1. Hexedit the drive status information in the superblocks and set it
> to what we require to assemble
You would have to be very brave to try that, and very confident that you
complete understood the on-disk raid metadata.
> 2. Run the create option of mdadm with precisely the original
> configuration of the pack to overwrite the superblock information
This is a valid option, but should always be the *last* resort.
Your research missed the recommended *first* option:
mdadm --assemble --force ....
[snip /]
> Mdadm examine for each drive:
> /dev/sda4:
> Events : 18538
> Device Role : Active device 0
> Array State : AAA. ('A' == active, '.' == missing)
> /dev/sdb4:
> Events : 18538
> Device Role : Active device 1
> Array State : .AA. ('A' == active, '.' == missing)
> /dev/sdc4:
> Events : 18538
> Device Role : Active device 2
> Array State : ..A. ('A' == active, '.' == missing)
> /dev/sdd4 is the faulty drive that now shows up as 4GB.
Check /proc/mdstat and then use mdadm --stop to make sure any partial
assembly of these devices is gone. Then
mdadm -Afv /dev/md3 /dev/sd[abc]4
Save the output so you can report it to this list if it fails. You
should end up with the array running in degraded mode.
Use fsck as needed to deal with the detritus from the power losses, then
make your backups.
HTH,
Phil
--
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
