Re: problem with grub in redhat 9 (dual boot win98)

From: Alex Hunsley (alex.hunsley_at_blueyonder.munge.co.uk)
Date: 09/24/03 

Date: Wed, 24 Sep 2003 15:31:35 +0100

mjt wrote:
> Alex Hunsley wrote:
>
>
>>all help greatly appreciated!
>
>
> ... can you give us the output of:
> # fdisk -l /dev/hd*
> .

yup. (I'm going in using knoppix 3.2 btw.)

Disk /dev/hda: 6481 MB, 6481293312 bytes
255 heads, 63 sectors/track, 787 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

    Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 93 Amoeba
/dev/hda2 14 722 5695042+ 83 Linux
/dev/hda3 723 787 522112+ 82 Linux swap

Disk /dev/hda1: 106 MB, 106896384 bytes
255 heads, 63 sectors/track, 12 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/hda2: 5831 MB, 5831723520 bytes
255 heads, 63 sectors/track, 709 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/hda3: 534 MB, 534643200 bytes
255 heads, 63 sectors/track, 65 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/hdb: 4324 MB, 4324368384 bytes
255 heads, 63 sectors/track, 525 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

    Device Boot Start End Blocks Id System
/dev/hdb1 * 1 525 4217031 b Win95 FAT32

Disk /dev/hdb1: 4318 MB, 4318239744 bytes
255 heads, 63 sectors/track, 524 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

      Device Boot Start End Blocks Id System
/dev/hdb1p1 ? 120513 235786 925929529+ 68 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
      phys=(116, 100, 32) logical=(120512, 47, 32)
Partition 1 has different physical/logical endings:
      phys=(288, 101, 46) logical=(235785, 20, 46)
Partition 1 does not end on cylinder boundary.
/dev/hdb1p2 ? 82801 116350 269488144 79 Unknown
Partition 2 has different physical/logical beginnings (non-Linux?):
      phys=(357, 32, 43) logical=(82800, 34, 51)
Partition 2 has different physical/logical endings:
      phys=(0, 13, 10) logical=(116349, 218, 61)
Partition 2 does not end on cylinder boundary.
/dev/hdb1p3 ? 33551 120595 699181456 53 OnTrack DM6 Aux3
Partition 3 has different physical/logical beginnings (non-Linux?):
      phys=(345, 32, 19) logical=(33550, 137, 11)
Partition 3 has different physical/logical endings:
      phys=(324, 77, 19) logical=(120594, 153, 54)
Partition 3 does not end on cylinder boundary.
/dev/hdb1p4 ? 86812 86813 10668+ 49 Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
      phys=(87, 1, 0) logical=(86811, 142, 3)
Partition 4 has different physical/logical endings:
      phys=(335, 78, 2) logical=(86812, 225, 45)
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order

(I also get :
Disk /dev/hda1 doesn't contain a valid partition table
Disk /dev/hda2 doesn't contain a valid partition table
Disk /dev/hda3 doesn't contain a valid partition table
should I worry about this?
Also, a load of "unsupported command in request queue" stuff came up
that dosen't seem to be going to stdout or stderr....)

thanks!
alex

Relevant Pages

  • RE: Maxtor Mini External Hard Drive
    ... 255 heads, 63 sectors/track, 4870 cylinders ... Partition 1 has different physical/logical beginnings: ...
    (Ubuntu)
  • Atapi ZIP 100, still no worky worky
    ... Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel ... Device Boot Start End Blocks Id System ... 255 heads, 63 sectors/track, 9729 cylinders ...
    (alt.os.linux.suse)
  • Running LVM to repartition HD question
    ... 255 heads, 63 sectors/track, 9729 cylinders ... Disk /dev/dm-0 doesn't contain a valid partition table ...
    (Fedora)
  • Re: 10.2 partitioning. Sucks!
    ... should be erased (and will be if there is no separate /boot partition). ... 255 heads, 63 sectors/track, 9729 cylinders ...
    (alt.os.linux.suse)
  • Re: Help!: debian partitioning
    ... which helps keep the number of cylinders to ... partition and the entire rest of the array for your data. ... correct block so the head gets to it at the right time, ... useful for optimizing hardware tests (which is why it's often called ...
    (comp.os.linux.setup)