linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Casey Boone <caseyboone@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: raidtools to mdadm
Date: Wed, 04 Apr 2007 18:56:27 -0400	[thread overview]
Message-ID: <46142D1B.2080401@tmr.com> (raw)
In-Reply-To: <46103C8B.4030001@gmail.com>

Casey Boone wrote:
> ok so i am trying to recover some data for a friend.  what i am 
> wanting to do is forcibly set up /dev/mdN to be a raid0 of /dev/sda 
> and /dev/sdb
>
> i do not want to actually change any of the contents of these drives, 
> just mount very simply as a raid0.  the raid was originally created 
> using an onboard nvidia raid on the motherboard these drives used to 
> be hooked to.  my friend thought he could shove them into another 
> windows box (that is what he was running on them) and have windows 
> recover the raid.  all this did was totally destroy the superblock on 
> one of the two drives.  dmraid now wont see them as a matched pair so 
> that is out.  the actual data areas of both drives seems to be intact, 
> but unless i can get them into raid0 i dont know how i can recover the 
> data.  it figures he gives me the drives after he makes it a notch or 
> two more of a pain :\
>
I have friends like that too. ;-)

>
> now before the advent of mdadm i would use /etc/raidtab and have no 
> issues setting up the raid device. \

I haven't used raidtools for ages, but can't you bring yourself to using 
them now? I seem to remember that there was no superblock to be written 
in a bad place, which might be an advantage. mdadm has several versions 
which write the superblock in various places on the drives, and you may 
want "none of the above."

Alternatively, if these are fairly small, write a tiny program to open 
both physical devices, read a chunk from one, then the other, repeat 
while writing to something not hosed.
>
>
> as best i can tell i am using the correct commands for what i want but 
> i pretty much get nothing but errors:
>
> root@Knoppix:/media# mdadm --build /dev/md1 --chunk=128 --level=0 
> --raid-devices=2 /dev/sda /dev/sdb
> mdadm: error opening /dev/md1: No such device or address
> root@Knoppix:/media# mdadm --build -n 2 -c 128 -l 0 /dev/md1 /dev/sda 
> /dev/sdb
> mdadm: error opening /dev/md1: No such device or address
>
>
> when i run those commands i do get /dev/mdN entries created, but they 
> do not point to a valid block device (as tested with fdisk -l and with 
> dmraid -b)
>
>
> for the life of me i dont understand why anyone would put important 
> data on a raid0, but that is what happened in this case.
>
>
> If i have to i will drop down to an older knoppix release to get 
> raidtools back, as i have never had any issues in recovering crap 
> onboard raid arrays nor windows software raid arrays under it.  i am 
> sure it can be done with mdadm but for the life of me i cannot seem to 
> figure out exactly how.
>
> any help on this would be greatly appreciated
>
> Casey 


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


  parent reply	other threads:[~2007-04-04 22:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01 23:13 raidtools to mdadm Casey Boone
2007-04-02  0:07 ` Neil Brown
2007-04-04 22:56 ` Bill Davidsen [this message]
2007-04-05  3:26   ` Casey Boone

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=46142D1B.2080401@tmr.com \
    --to=davidsen@tmr.com \
    --cc=caseyboone@gmail.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).