Re: broken raid level 5 array caused by user error

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

 



On 11/10/2015 07:06 PM, Mathias Mueller wrote:
> Hi Phil
> 
>> Hmmm.  Very strange.  Let's see the dump of the start of the data area
>> of all four partitions:
>>
>> for x in /dev/sd[efgh]1 ; do echo -e "\n$x\n" ; dd if=$x skip=2048
>> count=16 2>/dev/null |hexdump -C ; done

Very good.

sdf1 is definitely first.  sdh1 is definitely last.  I don't see
anything obviously wrong with the superblock.  The handful of fields
I've looked at are appropriate, including the magic number, write
timestamp, and last mount point.  (/srv).

So, I fully expected one of those first four combinations to work.  I
don't know why they didn't.

The fsck version dates to 2013, so it might be something related to
that.  My next step would be to try all of this after booting into a
modern environment, like the rescue cd from sysrescuecd.org.  Recheck
serial numbers and device names again, if you do that.

If that fails the same way, I'm at a loss.  You might want to point the
ext4 mailing list at this thread's archive and ask for advice.  There's
some possibility of trying various backup superblocks if they can be
located -- I'm not confident enough to advise you on that.

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



[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