Re: Brocken Raid & LUKS

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

 



On 02/24/2013 01:22 PM, Stone wrote:
> Am 24.02.2013 15:15, schrieb Phil Turmel:
>> On 02/24/2013 02:10 AM, Stone wrote:
>>
>>> e2fsck: aborted
>>>
>>> the output have 711mb..
>>> do you ned more examples?
>>> what do you say to case1?
>> I think you need to see case2.  Case #1 isn't very good.

Case #2 ....
> same shit different partion.
> the logfile have 708mb
> :(


Hmm.  If one was clearly better than the other, I'd recommend you do
"fsck -y" with it.  But they are both ugly.  Not extraordinarily bad,
but bad.

I believe you should copy all three complete drives to spares, then try
"fsck -y" with case #1.  If it doesn't give you your data, put the
spares in your system and try case #2 with "fsck -y".

If neither case #1 nor case #2 give you (most of) your data, I'm out of
ideas. :-(

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