From: Mark Lord <kernel@teksavvy.com>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sata_mv and Highpoint RocketRAID 230x, corruption?
Date: Fri, 22 Oct 2010 21:59:34 -0400 [thread overview]
Message-ID: <4CC24186.1040001@teksavvy.com> (raw)
In-Reply-To: <AANLkTik02CcVyzn+fMH+VxuUmwwNLZq9qM0MPz81E+1h@mail.gmail.com>
On 10-10-20 04:03 PM, Mathias Burén wrote:
..
> I'm currently not using the BIOS of the raid controller for anything
> else then staggered disk spinup. The HDD partitions start at sector
> 2048 (to get a 1MB alignment since they're 4k sector drives, WD20EARS)
> and end at the last sector.
> What I'm worried about is the corruption mentioned in dmesg, is this
> explained somewhere in more detail? Google didn't reveal much. Am I in
> danger?
Yes. Just repartition the drives to avoid the final 2GB of each drive,
and then you'll be safe.
The RocketRaid BIOS that I examined here a couple of years ago,
liked to write "metadata" over top of whatever was in certain sectors
near the end of the drive. EVEN FOR NON-RAID DRIVES.
I think it was the last even (power-of-two) multiple of 1GB or something,
so if you leave the final 2GB untouched, you're guaranteed to avoid it.
Thus the recommendation.
Cheers
next prev parent reply other threads:[~2010-10-23 1:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 20:03 sata_mv and Highpoint RocketRAID 230x, corruption? Mathias Burén
2010-10-23 1:59 ` Mark Lord [this message]
2010-10-23 2:21 ` Daniel Taylor
2010-10-23 15:21 ` Mark Lord
2010-10-23 12:57 ` Mathias Burén
2010-10-23 15:19 ` Mark Lord
2010-10-23 15:20 ` Mathias Burén
2010-10-23 15:49 ` Mark Lord
2010-10-23 16:08 ` Mathias Burén
2010-10-24 12:52 ` Mathias Burén
2010-10-25 21:26 ` Mark Lord
2010-10-25 21:31 ` Mathias Burén
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=4CC24186.1040001@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.buren@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox