On Thu, 30 Nov 2006, Jim Cornette wrote:
Don Raikes wrote:
Ok, the fdisk -l /dev/sda shows:
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 711 17538 135170910 7 HPFS/NTFS
/dev/sda2 1 710 5703043+ b W95 FAT32
/dev/sda3 17539 29649 97281607+ 83 Linux
/dev/sda4 29650 30401 6040440 5 Extended
/dev/sda5 29650 30388 5935986 82 Linux swap /
Solaris
Partition table entries are not in disk order
I agree with the comment from Scott below. The starting partition is
/dev/sda2 (1 through 710) but for some reason fdisk wants to call the (711
through 17538) /dev/sda1.
This output at least is easier for me than the Partition magic which I never
used before.
I haven't been following this thread, so I don't know what the OP's issue
was, but...
It used to be the case that Windows didn't much like partition tables
where the numebring wasn't in order from cylinder 1 to the end. No
Windows partitioning tool that I know of would create a partition table
like this.
You can fix the order with fdisk commands 'x' then 'f' then 'w'. If you
do, you may need to fix grub.conf, fstab, lvm, and/or reinstall grub. If
Windows was originally on the disk, I have no idea what might have already
broken or what might break if it was working and you fix the partition
table.
Jim
If I read this correctly your boot(windows partition) is hda1 which grub
calls hd0,0 in your grub.conf you are telling grub to boot hd0,1 (which
is the #2 partition (hda2 in fdisk language) make the rootnoverify line
rootnoverify (hd0,0)
and you should be o.k.
Scott
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs
