Re: corrupt raid 5

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

 



>>>>> "Lorac" == Lorac Thelmwood <lorac.web@xxxxxxxxx> writes:
>> 
Lorac> First I can't start the array because it complains about a bad
Lorac> superblock.

Have you tried forcing the start of the array with the --force flag?
Something like this:

	mdadm -A --run /dev/md1

Please give the output of the command.  

Lorac> What's the output of 'cat /proc/mdstat' and 'mdadm
>> --detail /dev/md?' where ? is the number of your raid 5 array?

Lorac> debian:~# cat /proc/mdstat
Lorac> Personalities : [raid1] [raid5]
Lorac> md1 : inactive hdh1[4] hdc1[0] hdg1[3] hdf1[2] hde1[1]
Lorac>       976791680 blocks

This is the key info, the array is assembled, but it hasn't been
started properly, probably because of the missing disk.  Try the --run
args as above and see what it does for you.

See how it says 'inactive', this means you need to get it running
first.  

Good luck,
John
-
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