You provided the following partition table:
> Boot Begin Start End Blocks Id System
> /dev/hdc1 63 63 130976 65457 82 Linux Swap
> /dev/hdc2 * 130977 130977 2588354 1228689 83 Linux native
> /dev/hdc3 2322431 2588355 6684362 2048004 6 DOS 16-bit >=32M
> /dev/hdc4 6386687 6684363 8418815 867226+ 6 DOS 16-bit >=32M
> (v)erify gives:
> Warning: partition 2 overlays partition 3.
> partition 3 overlays partition 4.
> 60 unallocated sectors.
This should be OK for linux, despite the warning. As I
understand it, fdisk gets values for the begin column from the bios,
but the other columns are calculated by fdisk. The bios figures are
wrong when they refer to cylinders above 1024. The verify results are
based on the bios data, and always show overlaps in disks with over
1024 cylinders. For example, here is the partition table for my
first drive:
Disk /dev/hda: 15 heads, 63 sectors, 14475 cylinders
Units = cylinders of 945 * 512 bytes
Device Boot Begin Start End Blocks Id System
/dev/hda1 * 1 1 1104 521608+ 6 DOS 16-bit >=32M
/dev/hda2 1024 1105 10348 4367790 85 Linux extended
/dev/hda3 10240 10349 12412 975240 83 Linux native
/dev/hda4 12288 12413 14475 974767+ 83 Linux native
/dev/hda5 1024 1105 5440 2048728+ 83 Linux native
/dev/hda6 5120 5441 6091 307566 83 Linux native
/dev/hda7 5120 6092 6222 61866 82 Linux swap
/dev/hda8 6144 6223 8285 974736 83 Linux native
/dev/hda9 8192 8286 8502 102501 83 Linux native
/dev/hda10 8192 8503 10348 872203+ 83 Linux native
Command (m for help): v
Warning: partition 3 overlaps partition 4.
Warning: partition 1 overlaps partition 5.
Warning: partition 5 overlaps partition 6.
Warning: partition 5 overlaps partition 7.
Warning: partition 6 overlaps partition 7.
Warning: partition 7 overlaps partition 8.
Warning: partition 8 overlaps partition 9.
Warning: partition 3 overlaps partition 10.
Warning: partition 8 overlaps partition 10.
Warning: partition 9 overlaps partition 10.
Logical partition 5 not entirely in partition 2
390333 unallocated sectors
Despite these warnings, I use all of these partitions regularly,
with no problems.
The DOS fdisk table you sent is weird! It appears to be a
mixture of DOS' fdisk /status command with the partition table from a
normal fdisk command. Your 549 mb drive would be C: in DOS
nomenclature, the CD would be D:, and your 4.3 gb drive E:, so that
partition table is partly right in its drive letter assignments. Is
the CD properly jumpered as a slave? I don't really think that would
cause such problems. I don't think the LILO information in the MBR
would cause any problems for DOS.
Does your bios support LBA? If so, is it enabled or disabled? I
suggest you switch it and see if that has any effect. If your bios
doesn't support LBA, DOS can't recognize more than 1024 cylinders
unless you run one of the programs the the disk manufacturers
provide. I don't know how these work, and I don't know if linux will
read the disk correctly after one of them is installed, so I have
never tried one.
To sum up: I think your drive, as partitioned, will work fine in
linux, but I don't know what you should do about the DOS partitions.
There is a better chance of making it work if you put the DOS
partition first in the drive. Linux doesn't care where it is, except
that I understand if you use LILO the boot partition must be within
the first 1024 cylinders. (I use loadlin, and am not familiar with
LILO details.)
Good Luck
--
_
|_) _ |_ Robert D. Hilliard <[EMAIL PROTECTED]>
|_) (_) |_) Palm City, FL USA PGP Key ID: A8E40EB9
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
