From: Marc MERLIN <marc@merlins.org>
To: d tbsky <tbskyd@gmail.com>
Cc: list Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: new drive is 4 sectors shorter, can it be used for swraid5 array?
Date: Sun, 27 Mar 2022 19:05:12 -0700 [thread overview]
Message-ID: <20220328020512.GP4113@merlins.org> (raw)
In-Reply-To: <CAC6SzHKFga59KpzhRhE-sz3K5z+=LUXfyxSB14KaOj7DCxCj-Q@mail.gmail.com>
On Sun, Mar 27, 2022 at 04:40:38PM +0800, d tbsky wrote:
> Marc MERLIN <marc@merlins.org>
> > New drive is 4 sectors shorter, so I assume I can't use it as a replacement in my md5
> > array because it's 4 sectors too short, or does swraid5 not need the last few sectors
> > of a drive?
>
> 4 sectors shorter are common for external hard drives (sold from
> seagate,toshiba,etc). if you attach the drive to internal sata port or
> normal usb enclosure(not sold from disk vendors),you will get back
> normal disk size. so maybe you want to check what connect to your
> disk.
OMG, using a USB adapter eats 4 setors? I had no idea...
Sure enough, I did connect the drives via USB for diagnosis since I had
run out of sata ports.
Thanks for the hint.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2022-03-28 2:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 3:08 new drive is 4 sectors shorter, can it be used for swraid5 array? Marc MERLIN
2022-03-18 7:54 ` Wols Lists
2022-03-18 12:30 ` Roman Mamedov
2022-03-19 4:10 ` Marc MERLIN
2022-03-19 10:14 ` Wols Lists
2022-03-19 22:02 ` Marc MERLIN
2022-03-21 19:35 ` Nix
2022-03-19 10:45 ` Roman Mamedov
2022-03-26 18:01 ` Tom Mitchell
2022-03-26 18:29 ` Wols Lists
2022-03-27 8:40 ` d tbsky
2022-03-28 2:05 ` Marc MERLIN [this message]
2022-03-29 0:13 ` Chris Murphy
2022-03-29 1:55 ` d tbsky
2022-03-30 2:33 ` Andy Smith
2022-04-02 12:48 ` d tbsky
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=20220328020512.GP4113@merlins.org \
--to=marc@merlins.org \
--cc=linux-raid@vger.kernel.org \
--cc=tbskyd@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;
as well as URLs for NNTP newsgroup(s).