From: Michael Evans <mjevans1983@gmail.com>
To: "Kristleifur Daðason" <kristleifur@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID5 on broken RocketRaid 1640 - data format?
Date: Fri, 29 Jan 2010 23:15:47 -0800 [thread overview]
Message-ID: <4877c76c1001292315y16b4a8eay8e73a9d35727506d@mail.gmail.com> (raw)
In-Reply-To: <73e903671001291155g761f2dc8rb6e02541525929ba@mail.gmail.com>
On Fri, Jan 29, 2010 at 11:55 AM, Kristleifur Daðason
<kristleifur@gmail.com> wrote:
> Hi,
>
> A good pal of mine once had a 4x400GB RAID5 array running on a
> RocketRaid 1640 controller. The controller broke, and due to
> complexity and his understandable lack of RAID expertise, the drives
> are sitting in a drawer. I want to try to help.
>
> Do you excellent list dwellers know what data format the 1640 uses on
> the disks? Is there any Linux RAID tool that can work with the data
> off the disks?
>
> In case it's relevant, the system was running Windows, and there was a
> single NTFS filesystem over the array. I'm pretty sure the array was
> created on the BIOS side.
>
> Many thanks!
> -- Kristleifur
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Load the drives in to a computer as spare drives, DO NOT WRITE TO THEM
(make sure your OS doesn't try to automount either).
Try mdadm --examine on the raw devices and any partitions you can see.
If mdadm recognizes the meta-data format there is a very good chance
the array can be brought online, try to do that in read-only mode
(read the mdadm manual).
Examine the result, it may contain partitions or a filesystem that can
be mounted via something like ntfs-3g. If you get that far I
recommend running a CHECK on the array (Before making it read/write)
and validating that there are no errors. If you get errors you /may/
want to make a backup of the entire device.
I know that old drives from a 4-port hardware raid card I used one
time kept showing meta-data (in the syslog) unknown/not recognized,
but I don't believe it was a highpoint 1640. There have also been
improvements since then.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-01-30 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 19:55 RAID5 on broken RocketRaid 1640 - data format? Kristleifur Daðason
2010-01-30 7:15 ` Michael Evans [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=4877c76c1001292315y16b4a8eay8e73a9d35727506d@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=kristleifur@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).