| 1 |
On Sun, Mar 4, 2012 at 1:09 PM, Grant <emailgrant@×××××.com> wrote: |
| 2 |
> [snip] |
| 3 |
>>> 1. fdisk won't let me specify a start block before 2048 even though I |
| 4 |
>>> deleted all partitions. |
| 5 |
>>> |
| 6 |
>> |
| 7 |
>> That's normal. It's a long story, but Windows Vista and Windows 7 expects |
| 8 |
>> the first partition to start at sector 2048. |
| 9 |
>> |
| 10 |
>> You can force a lower number by toggling "DOS compatibility"; this should |
| 11 |
>> let you start the first partition as low as sector 63. |
| 12 |
>> |
| 13 |
>> HOWEVER, make sure that all partitions begin at multiples of 8 (e.g., 64, |
| 14 |
>> 72, 80, and so on); this will save you a lot of grief if it happens that the |
| 15 |
>> hard disk you're using has 4KiB-sectors. |
| 16 |
> |
| 17 |
> I just looked up the start block for my other systems and they're all |
| 18 |
> on 63. Is performance impacted on all of these systems since they |
| 19 |
> aren't started on 64? |
| 20 |
> |
| 21 |
> - Grant |
| 22 |
> |
| 23 |
|
| 24 |
The performance is only impacted if the sector size is something other |
| 25 |
than 512 bytes. The newer 4K sector size used by some higher density |
| 26 |
drives requires that you start partitions on a sector boundary or they |
| 27 |
will perform badly. There isn't an actually performance need to |
| 28 |
actually start on 2048 but the fdisk-type developer folks are doing |
| 29 |
that to be more compatible with newer Windows installations. |
| 30 |
|
| 31 |
HTH, |
| 32 |
Mark |
Archives