From: Stan Hoeppner <stan@hardwarefreak.com>
To: Aaron Scheiner <blue@aquarat.za.net>
Cc: NeilBrown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Grub-install, superblock corrupted/erased and other animals
Date: Fri, 05 Aug 2011 05:32:25 -0500 [thread overview]
Message-ID: <4E3BC6B9.8050803@hardwarefreak.com> (raw)
In-Reply-To: <CADz4AWE20OdL4VecVOrOH5X-UqdB4BA00AW33YbYEtD1z30acA@mail.gmail.com>
On 8/5/2011 5:04 AM, Aaron Scheiner wrote:
> I followed your advice and ran a scalpel instance for every drive in
> the array. The scanning process finished this morning yay (and
> obviously went a lot faster).
Glad I could help.
...
> So now the next step would have been to re-create the array and check
Unless Neil has some hex editor (or other similar) trick up his sleeve
that would allow you to manually recreate the sectors you hosed
installing grub..
> if a file system check finds something... but because of the offsets
> that probably won't work ?
If you are able to use the Force to assemble the disks in the correct
order, getting the raid device back up and running, then run 'xfs_repair
-n /dev/md0' to do the check. The '-n' means "no modify". xfs_repair
is better than xfs_check in many aspects. They are two separate code
paths that serve the same function, but they behave a little differently
under the hood.
> Thanks again :)
Wish I could have helped you recover the array. When a patient comes
through emergency with 3 GSWs to the forehead and no pulse, there's
nothing that can be done. :(
--
Stan
next prev parent reply other threads:[~2011-08-05 10:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 12:16 Grub-install, superblock corrupted/erased and other animals Aaron Scheiner
2011-08-02 6:39 ` NeilBrown
2011-08-02 8:01 ` Stan Hoeppner
2011-08-02 16:24 ` Aaron Scheiner
2011-08-02 16:41 ` Stan Hoeppner
2011-08-02 21:13 ` Aaron Scheiner
2011-08-03 4:02 ` Stan Hoeppner
2011-08-02 16:16 ` Aaron Scheiner
2011-08-03 5:01 ` NeilBrown
2011-08-03 8:59 ` Aaron Scheiner
2011-08-03 9:20 ` NeilBrown
2011-08-05 10:04 ` Aaron Scheiner
2011-08-05 10:32 ` Stan Hoeppner [this message]
2011-08-05 11:28 ` Aaron Scheiner
2011-08-05 12:16 ` NeilBrown
2011-08-03 7:13 ` Stan Hoeppner
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=4E3BC6B9.8050803@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=blue@aquarat.za.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).