After a few months I had a corrupted partition table again.
Therefore we can conclude that it is not only important to
let the first logical partition start at the start of the
extended partition, but that it is also necessary to let
every next logical partition start precisely at the end
of the previous logical partition - unlike what was concluded
before.
Interesting enough, while I used to loose all logical partitions,
now I lost all logical partitions except the first one.
So we can also conclude that the first logical partition entry
in the partition table, that doesn't start at the end of the last
logical partition is what gets lost.
I hope this is something that gets fixed, or otherwise I suggest
the `fdisk' is changed to warn people about possible 'gaps'.
I run kernel 2.0.33
Carlo
PS As an example, here is my current partition table. Note that
/dev/hda6 and on got lost (after re-writing of the partition
table to disk, no data was lost and a normal reboot was
possible, as usual). Note that 356 != 358.
Disk /dev/hda: 128 heads, 63 sectors, 779 cylinders
Units = cylinders of 8064 * 512 bytes
Device Boot Begin Start End Blocks Id System
/dev/hda1 * 1 1 261 1052320+ 7 OS/2 HPFS
/dev/hda2 262 262 294 133056 82 Linux swap
/dev/hda3 * 295 295 306 48384 83 Linux native
/dev/hda4 307 307 779 1907136 5 Extended
/dev/hda5 307 307 356 201568+ 83 Linux native
/dev/hda6 358 358 382 100800 83 Linux native
/dev/hda7 383 383 407 100800 83 Linux native
/dev/hda8 408 408 432 100800 83 Linux native
/dev/hda9 433 433 444 48384 83 Linux native
/dev/hda10 445 445 456 48384 83 Linux native
/dev/hda11 457 457 481 100800 83 Linux native
/dev/hda12 482 482 506 100800 83 Linux native
/dev/hda13 507 507 556 201600 83 Linux native
/dev/hda14 557 557 779 899136 83 Linux native
PS2 I am not subbed to this list.
-- carlo@runaway.xs4all.nl, Run @ IRC.ircd development: http://www.xs4all.nl/~carlo17/ircd-dev
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu