Re: Fwd: I will pay money for the correct RAID recovery instructions

["John Stoffel" <john@stoffel.org>]

Another> Sorry to state the obvious but......  To restore the degraded
Another> array would (based on the info you've posted) likely take
Another> longer then temporarily moving the data to a different set of
Another> drives.

How do you figure this?  He hasn't posted any useful data on his array
at all.  We know it's six 3Tb disks in RAID10, so that's at most 9Tb
of data.  Moving 3Tb (bad disk ddrescue'd onto new disk) is only 3Tb
to move.  Then the resync will of course take time.  

But if he doesn't have the spare disk space, it's probably the only way.

Another> As time seems to be a major consideration here (likely/possible
Another> failure of sde) then surely the optimal strategy has to be to get the
Another> data off first, then look at the rebuilding the degraded array?

Another> Just my 2c

Another> On 17 October 2014 15:05, John Stoffel <john@stoffel.org> wrote:
>> 
>> 
>> Ian,
>> 
>> It would also help if you posted the details of your setup using:
>> 
>> cat /proc/partitions
>> cat /proc/mdstat
>> 
>> mdadm -D /dev/md#
>> - for each of the devices above.
>> 
>> mdadm -E /dev/sd<drive><#>
>> - for each disk or partition in the array from above.
>> 
>> 
>> 
>> But the suggestions to ddrescue the going bad drive onto a new disk is
>> a good one.  On my debian system, I would do the following:
>> 
>> sudo apt-get install gddrescue
>> ddrescue /dev/sde /dev/sdf /var/tmp/ddrecue-sde.log
>> 
>> and see how that goes.
>> 
>> Good luck,
>> John
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Another> --
Another> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
Another> the body of a message to majordomo@vger.kernel.org
Another> More majordomo info at  http://vger.kernel.org/majordomo-info.html