[3531] in Release_7.7_team
option 2 and Partition magic: Curiouser and Curiouser.
daemon@ATHENA.MIT.EDU (Bill Cattey)
Wed Sep 25 21:29:00 2002
Message-Id: <200209260128.VAA01134@discon-1.mit.edu>
To: release-team@MIT.EDU
Date: Wed, 25 Sep 2002 21:28:58 -0400
From: Bill Cattey <wdc@MIT.EDU>
After much struggle, I was able to move the IBM maintenance
partition's location on the disk to just after the NTFS partition.
(Version 7.0 of Partition magic, if you have an Ext3 filesystem
ANYWHERE on your disk, will fail to move another partition, even if
all you are doing is copying VFAT to empty space. It will make you
wait until after it has copied all the data, and then say, "Error 510,
Version of filesystem not supported." Why it should CARE about
unrelated partitions and disk blocks here is a mystery to me, and
seems like bad architecture of the software, but I digress...)
I wiped the Linux partitions, and let option 2 create filesystems at
the end of the disk all happy and sweet. Linux works. Windows
works. Booting the relocated maintenance partition works.
Partition magic does NOT work. It complains again about inability to
get drive letter for partition.
Here is expert mode output from Fdisk describing the partition table
of my T30 after all these relocations and tests:
Disk /dev/hda: 240 heads, 63 sectors, 5168 cylinders
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 1 1 0 239 63 1023 63 35410977 07
2 00 0 1 1023 239 63 1023 35411040 2494800 0c
3 00 0 1 1023 239 63 1023 37905840 40234320 05
4 00 0 0 0 0 0 0 0 0 00
5 00 239 63 1023 239 63 1023 1 1105919 82
6 00 239 63 1023 239 63 1023 1 276479 83
7 80 239 63 1023 239 63 1023 1 38851919 83
I am going to crowbar hda7 into Ext2 and see if Partition Magic is
choking for that reason.
-wdc
