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