From: Roman Mamedov <rm@romanrm.ru>
To: Andriano <chief000@gmail.com>
Cc: NeilBrown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: RAID6 issues
Date: Tue, 13 Sep 2011 14:44:24 +0600 [thread overview]
Message-ID: <20110913144424.64348c41@natsu> (raw)
In-Reply-To: <CAGZH0-f+e80W36VMZMHrTakTxUHO2nppO9xHSTmHh6QV_Mo2Fg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
On Tue, 13 Sep 2011 17:51:56 +1000
Andriano <chief000@gmail.com> wrote:
> Apparently you're right
> blockdev --getsz /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg
> /dev/sdh /dev/sdi /dev/sdj /dev/sdk
> 3907027055
> 3907027055
> 3907029168
> 3907029168
> 3907029168
> 3907029168
> 3907027055
> 3907029168
> 3907029168
> 3907029168
>
> sdb, sdc and sdh - are smaller and they are problem disks
>
> So what would be a solution to fix this issue?
You mentioned you use Gigabyte EP35C-DS3 motherboard. Gigabyte BIOSes are known to cut off about 1 MByte or so from the end of HDDs (on the onboard controller, and maybe just the one on Port 0), setting an HPA area and storing a copy of the BIOS there. That's known as "(Virtual) Dual/Triple/Quad BIOS". Google for "gigabyte bios hpa" and you'll find a lot of reports about this problem. You can check if you can disable that "feature" in BIOS setup, but older boards did not have such option.
To restore the native capacity of the drives you can use "hdparm -N" (see its man page), while disks are on the non-onboard controller.
In the future, create your RAID from partitions, and leave 8-10 MB of space in the end of each disk for cases like these.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-09-13 8:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 6:14 RAID6 issues Andriano
2011-09-13 6:25 ` NeilBrown
2011-09-13 6:33 ` Andriano
2011-09-13 6:44 ` NeilBrown
2011-09-13 7:05 ` Andriano
2011-09-13 7:38 ` NeilBrown
2011-09-13 7:51 ` Andriano
2011-09-13 8:10 ` NeilBrown
2011-09-13 8:12 ` Alexander Kühn
2011-09-13 8:44 ` Roman Mamedov [this message]
2011-09-13 8:57 ` Andriano
2011-09-13 9:05 ` Andriano
2011-09-13 10:29 ` Roman Mamedov
2011-09-13 10:44 ` Andriano
2011-09-13 13:45 ` Andriano
2011-09-27 18:46 ` Thomas Fjellstrom
2011-09-27 19:14 ` Stan Hoeppner
2011-09-27 21:04 ` Thomas Fjellstrom
2011-09-28 2:47 ` Stan Hoeppner
2011-09-28 6:52 ` Thomas Fjellstrom
2011-09-28 6:03 ` Mikael Abrahamsson
2011-09-28 6:53 ` Thomas Fjellstrom
-- strict thread matches above, loose matches on Subject: below --
2011-09-13 14:24 NeilBrown
2011-06-16 20:28 raid6 issues Chad Walker
2011-06-18 19:48 ` Chad Walker
2011-06-18 19:55 ` Chad Walker
2011-06-18 23:01 ` NeilBrown
2011-06-18 23:14 ` Chad Walker
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=20110913144424.64348c41@natsu \
--to=rm@romanrm.ru \
--cc=chief000@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).