All of lore.kernel.org
 help / color / mirror / Atom feed
From: David T-G <davidtg+robot@justpickone.org>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: hardware recovery and RAID5 services
Date: Sat, 29 Jan 2022 10:25:21 -0500	[thread overview]
Message-ID: <20220129152521.GJ14596@justpickone.org> (raw)
In-Reply-To: <7571b432-4b19-3de4-b04d-3a46b09b0629@turmel.org>

Phil, et al --

...and then Phil Turmel said...
% 
% Hi David, et al,
% 
% The principle of "My Hard Drive Died" is Scott Moulton, a highly respected
% member of the forensics and white-hat scene here in the Atlanta Metro Area.
% 
% https://myharddrivedied.com/

Great to know!  Thanks so much.


% 
% That said, I highly recommend copying the disk showing read errors onto
% another disk, keeping the log of sectors replaced by zeros. Then performing
% a file by file backup from the degraded array, using the copy instead of the
% troubled drive.
[snip]

I think I'm about there now.  I believe I have a "virtual array" 

  diskfarm:/mnt/10Traid50md/tmp # head -4 /proc/mdstat
  Personalities : [raid6] [raid5] [raid4] [raid0] 
  md0 : active (read-only) raid5 loop12[0] loop11[3] loop10[4]
        11720265216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [U_UU]
  
  diskfarm:/mnt/10Traid50md/tmp # mdadm -E /dev/md0
  /dev/md0:
     MBR Magic : aa55
  Partition[0] :   4294967295 sectors at            1 (type ee)

which presents me a partition with an ailing XFS filesystem on it.  I'm
hopeful that in my next round of an hour or two I can dig into superblock
adventures.


Thanks to all for all of the input!

:-D
-- 
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt


  parent reply	other threads:[~2022-01-29 15:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 16:48 hardware recovery and RAID5 services David T-G
2022-01-21 19:31 ` Wols Lists
2022-01-21 19:34   ` Wols Lists
2022-01-21 19:47     ` Wols Lists
2022-01-22 14:23       ` Roger Heflin
2022-01-22 22:23         ` Phil Turmel
2022-01-23  0:20           ` anthony
2022-01-29 15:25           ` David T-G [this message]
2022-01-29 15:36           ` Wols Lists
2022-01-31 15:39             ` Nix
2022-01-31 18:59               ` Roger Heflin
2022-01-31 19:07                 ` Geoff Back
2022-01-31 19:21                   ` Phil Turmel
2022-01-31 19:46                     ` Roger Heflin
2022-01-31 20:04                     ` Geoff Back
2022-01-31 20:53                     ` Wols Lists
2022-01-29 15:21   ` David T-G

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220129152521.GJ14596@justpickone.org \
    --to=davidtg+robot@justpickone.org \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.