All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Timothy Weaver <timothyweaver@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Convert RAID1 to standard ext2
Date: Mon, 13 Aug 2007 17:52:45 -0400	[thread overview]
Message-ID: <46C0D2AD.8040308@tmr.com> (raw)
In-Reply-To: <a85387af0708130114xab0edbfs9b521da6a19fd96a@mail.gmail.com>

Timothy Weaver wrote:
> Hi,
>
> I had 2x750GB drives in a RAID1 configuration in a D-Link NAS
> (DNS-323) device with embedded Linux as an ext2 volume. The
> configuration was corrupted and the NAS no longer saw the RAID.
>
> I put the drives in another Linux box and was able to use mdadm to
> scan the drives. It recognized the RAID1 configuration and created the
> RAID device at /dev/md0. Unfortunately, it says it is corrupt and
> cannot be mounted. I tried using e2fsck / fsck but it says the
> superblock is corrupt. Trying to use copies of the superblock were
> unsuccessful.
>
> I am confident the data is still there and want to get to it. Is there
> a way to take one of the drives and convert it from being in the RAID1
> set to just a standard ext2 partition in a non-destructive way? I
> figured this should be possible with the second drive just to be sure
> not to destroy both copies of the data.

Try a read-only loopback mount of the partition (either). However, I 
think you're missing something else, although I don't have a clue what. 
Unless the O/S started writing bad data or the hardware got sick, you 
should be able to recover. In any case this allows you to do something 
non-destructive and use offset= depending on the superblock location.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


      reply	other threads:[~2007-08-13 21:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13  8:14 Convert RAID1 to standard ext2 Timothy Weaver
2007-08-13 21:52 ` Bill Davidsen [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=46C0D2AD.8040308@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=timothyweaver@gmail.com \
    /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.