From: Alexander Clausen <alex@gc-web.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: 4k sector size and WD20EARS
Date: Thu, 08 Apr 2010 19:04:05 +0200 [thread overview]
Message-ID: <4BBE0C85.2020904@gc-web.de> (raw)
In-Reply-To: <yq17hoix78i.fsf@sermon.lab.mkp.net>
On 04/08/2010 06:02 PM, Martin K. Petersen wrote:
> For unknown reasons these drive report themselves as 512-byte drives
> despite using 4096-byte sectors internally.
ouch.
> However, recent fdisk/parted will align on a 1MB boundary by
> default which happens do the trick in this particular case
> Alexander> 1 Primary 0 3907024064 63 3907024065 Linux (83) None
> Alexander> alex@hal:~$
> No, you should shift the start sector using the fdisk's advanced menu.
I created this partition table using cfdisk (util-linux 2.17 from debian/experimental). I guess even
that is too old?
I now re-created the partition table using fdisk from util-linux-ng git and got this:
Command (m for help): p
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
81 heads, 63 sectors/track, 765633 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x2afff6d1
Device Boot Start End Blocks Id System
/dev/sdb1 2048 3907029167 1953513560 83 Linux
but:
$ sudo cfdisk -P s /dev/sdb
FATAL ERROR: Bad primary partition 0: Partition ends in the final partial cylinder
bug?
thanks for the help,
Alexander
next prev parent reply other threads:[~2010-04-08 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 14:20 4k sector size and WD20EARS Alexander Clausen
2010-04-08 16:02 ` Martin K. Petersen
2010-04-08 16:12 ` Mikael Abrahamsson
2010-04-08 16:33 ` Martin K. Petersen
2010-04-08 17:00 ` Mikael Abrahamsson
2010-04-08 18:56 ` Martin K. Petersen
2010-04-08 17:04 ` Alexander Clausen [this message]
2010-04-09 2:14 ` Martin K. Petersen
2010-04-12 12:34 ` Karel Zak
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=4BBE0C85.2020904@gc-web.de \
--to=alex@gc-web.de \
--cc=linux-ide@vger.kernel.org \
--cc=martin.petersen@oracle.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