| 1 |
Am Dienstag, 9. Februar 2010 schrieb Frank Steinmetzger: |
| 2 |
|
| 3 |
> > 4) Everything I've done so far leave me with messages about partition |
| 4 |
> > 1 not ending on a cylinder boundary. Googling on that one says don't |
| 5 |
> > worry about it. I don't know... |
| 6 |
|
| 7 |
Well since only the start of a partition determines its alignment with |
| 8 |
hardware sectors, I think it's really not that important. Worst case: mkfs |
| 9 |
truncates the last few sectors to make it a multiple of its cluster size. |
| 10 |
|
| 11 |
> Anyway, mine's like this, just to throw it into the pot to the others |
| 12 |
> ( those # are added by me to show their respective use ) |
| 13 |
> |
| 14 |
> eisen # fdisk -l -u /dev/sda |
| 15 |
> |
| 16 |
> Disk /dev/sda: 500.1 GB, 500107862016 bytes |
| 17 |
> 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors |
| 18 |
> Units = sectors of 1 * 512 = 512 bytes |
| 19 |
> Disk identifier: 0x80178017 |
| 20 |
> |
| 21 |
> Device Boot Start End Blocks Id System |
| 22 |
> /dev/sda1 * 63 25157789 12578863+ 7 HPFS/NTFS # Windows |
| 23 |
> /dev/sda2 25157790 88084394 31463302+ 7 HPFS/NTFS # Games |
| 24 |
> /dev/sda3 88084395 127941659 19928632+ 83 Linux # / |
| 25 |
> /dev/sda4 127941660 976768064 424413202+ 5 Extended |
| 26 |
> /dev/sda5 127941723 288816569 80437423+ 83 Linux # /home |
| 27 |
> /dev/sda6 288816633 780341309 245762338+ 83 Linux # music |
| 28 |
> /dev/sda7 813113973 976703804 81794916 83 Linux # X-Plane |
| 29 |
> /dev/sda8 * 976703868 976768064 32098+ 83 Linux # |
| 30 |
> /boot /dev/sda9 780341373 813113909 16386268+ 7 HPFS/NTFS # |
| 31 |
> Win7 test |
| 32 |
|
| 33 |
I have started amending my partitioning scheme, starting at the rear. Since my |
| 34 |
backup drive has exactly the same scheme, I’m working on that and then |
| 35 |
restore my local drive from it, so I need as little time in a LiveCD |
| 36 |
environment as possible. |
| 37 |
|
| 38 |
I have reset sdb7 to use boundaries divisible by 64. |
| 39 |
Old range begin%64 size%64 New range begin%64 size%64 |
| 40 |
813113973-976703804 0.8281 0.125 813113984-976703935 0 0 |
| 41 |
|
| 42 |
And guess what - the speed of truecrypt at creating a new container doubled. |
| 43 |
With the old scheme, it started at 13.5 MB/s, now it started at 26-odd. I’m |
| 44 |
blaming that cap on the USB connection to the drive, though it’s gradually |
| 45 |
getting more: after 2/3 of the partition, it’s at 27.7. |
| 46 |
|
| 47 |
So sdb7 now ends at sector 976703935. Interestingly, I couldn’t use the |
| 48 |
immediate next sector for sdb8: |
| 49 |
start for sdb8 response by fdisk |
| 50 |
976703936 sector already allocated |
| 51 |
976703944 Value out of range. First sector... (default 976703999): |
| 52 |
|
| 53 |
The first one fdisk offered me was exactly 64 sectors behind the end sector of |
| 54 |
sdb7 (976703999), which would leave a space of those mysterious 62 “empty” |
| 55 |
sectors in between. So I used 976704000, which is divisable by 64 again, |
| 56 |
though it’s not that relevant for a partition of 31 MB. :D |
| 57 |
|
| 58 |
As soon as truecrypt is finished, I'm going to solidify my findings by |
| 59 |
performing this on another partition, and I’ll also see what happens if I |
| 60 |
start at a start sector of k*64+1. Just out of curiousity. :-) |
| 61 |
-- |
| 62 |
Gruß | Greetings | Qapla' |
| 63 |
Crayons can take you more places than starships. (Guinan) |
Archives