From: Mike Berger <lists@mike01.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID 5 Recovery Help Needed
Date: Sat, 17 Jan 2009 12:51:07 -0600 [thread overview]
Message-ID: <4972289B.30607@mike01.com> (raw)
In-Reply-To: <49722439.3060103@tmr.com>
Bill Davidsen wrote:
>
> Depending on your distribution, I would not be surprised to see your
> array assemble just fine with or without an ARRAY line, it seems some
> try harder than others and I just noticed that the system I use most
> has only "super minor" lines for the first three arrays and nothing
> for the rest, yet arrays 0..6 all come up at boot.
>
> However, the bad news is that many distributions don't do ext4 very
> well, and may mount an ext4 file system as ext3, resulting in damage
> which gets worse if you write to it. I would suggest starting the
> array, unmounted, running fsck.ext4 on the array, and seeing if it
> offers any hope of recovery. If so, after the fsck mount the array
> *read-only* and see what's there.
>
> Some distributions seem to need "ext4" on the boot command line to
> detect the file system type for mounting. Of course if it's in fstab
> it should work correctly, but I wouldn't bet the farm on it.
>
> --
> Bill Davidsen <davidsen@tmr.com>
> "Woe unto the statesman who makes war without a reason that will still
> be valid when the war is over..." Otto von Bismark
>
>
I have an ext4 partition on another drive working flawlessly, so I don't
think it is or was being mounted incorrectly as ext3. I have a feeling
the ext4 boot option is needed for the root partition in the cases you
mention.
Thanks for the suggestions. I've tried a dry run (-n) of fsck without
success, but put off doing a full fsck for fear of corrupting the data
were it to be recoverable. I will try the full fsck before abandoning
all hope.
Mike
prev parent reply other threads:[~2009-01-17 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 19:35 RAID 5 Recovery Help Needed Mike Berger
2009-01-16 20:42 ` Joe Landman
2009-01-16 21:09 ` Mike Berger
[not found] ` <49722439.3060103@tmr.com>
2009-01-17 18:51 ` Mike Berger [this message]
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=4972289B.30607@mike01.com \
--to=lists@mike01.com \
--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 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).