public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Gentoo on a Dell XPS 13 Ultrabook
Date: Sun, 4 Mar 2012 13:45:47 -0800	[thread overview]
Message-ID: <CAK2H+eeHe_xjC=5+6wJxG9VJdrkPaeDcoQrgpxFtOUNp+4tASw@mail.gmail.com> (raw)
In-Reply-To: <CAN0CFw3k1uu+xxn0_WWSntT0dFePVrhf_E1J=1fe=yT5zdiO4Q@mail.gmail.com>

On Sun, Mar 4, 2012 at 1:09 PM, Grant <emailgrant@gmail.com> wrote:
> [snip]
>>> 1. fdisk won't let me specify a start block before 2048 even though I
>>> deleted all partitions.
>>>
>>
>> That's normal. It's a long story, but Windows Vista and Windows 7 expects
>> the first partition to start at sector 2048.
>>
>> You can force a lower number by toggling "DOS compatibility"; this should
>> let you start the first partition as low as sector 63.
>>
>> HOWEVER, make sure that all partitions begin at multiples of 8 (e.g., 64,
>> 72, 80, and so on); this will save you a lot of grief if it happens that the
>> hard disk you're using has 4KiB-sectors.
>
> I just looked up the start block for my other systems and they're all
> on 63.  Is performance impacted on all of these systems since they
> aren't started on 64?
>
> - Grant
>

The performance is only impacted if the sector size is something other
 than 512 bytes. The newer 4K sector size used by some higher density
drives requires that you start partitions on a sector boundary or they
will perform badly. There isn't an actually performance need to
actually start on 2048 but the fdisk-type developer folks are doing
that to be more compatible with newer Windows installations.

HTH,
Mark



  reply	other threads:[~2012-03-04 21:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  2:12 [gentoo-user] Gentoo on a Dell XPS 13 Ultrabook Grant
2012-03-02  8:01 ` Alan McKinnon
2012-03-02 20:29   ` Grant
2012-03-02 23:03     ` Neil Bothwick
2012-03-02 23:35       ` Grant
2012-03-02 23:05 ` [gentoo-user] " walt
2012-03-02 23:39   ` Grant
2012-03-03 17:50     ` Grant
2012-03-03 18:13       ` Pandu Poluan
2012-03-03 18:15         ` Pandu Poluan
2012-03-03 18:22           ` Pandu Poluan
2012-03-03 18:24             ` Pandu Poluan
2012-03-03 20:12         ` Joshua Murphy
2012-03-04 20:12           ` Grant
2012-03-04 20:34             ` Alex Schuster
2012-03-05  1:53               ` Pandu Poluan
2012-03-05 13:40                 ` Alex Schuster
2012-03-05  1:58             ` Pandu Poluan
2012-03-04 20:02         ` Grant
2012-03-04 20:06           ` Grant
2012-03-04 21:09         ` Grant
2012-03-04 21:45           ` Mark Knecht [this message]
2012-03-04 21:56             ` Grant
2012-03-04 22:07               ` Alan McKinnon
2012-03-04 22:36                 ` Grant
2012-03-05  2:19                   ` Pandu Poluan
2012-03-05  2:12                 ` Pandu Poluan
2012-03-05  2:06               ` Pandu Poluan
2012-03-05 21:41                 ` Mark Knecht
2012-03-05 16:00               ` Alex Schuster
2012-03-05 16:33                 ` Pandu Poluan
2012-03-05 20:17                   ` Alan McKinnon
2012-03-05 21:33                 ` Joshua Murphy

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='CAK2H+eeHe_xjC=5+6wJxG9VJdrkPaeDcoQrgpxFtOUNp+4tASw@mail.gmail.com' \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.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