I had a similar occurrence (Bug 188120) when installing Hardy build 20080131.2 on a dual boot Windows 2000/ OpenSuse10.3 on two disks, one with a single partition (Win2k) and one with 4 partitions (2xntfs, swap and root). All 5 partitions were screwed up. Windows install thought they were write protected and MSDOS fdisk would not recognise them at all. The only way I could recover them was with MaxBlast, by rebuilding the partitions from scratch. Even then, one partition reported 2Tb free space and one reported 0% free space but this corrected itself after loading data onto them and defragmenting.
I had a similar occurrence (Bug 188120) when installing Hardy build 20080131.2 on a dual boot Windows 2000/ OpenSuse10.3 on two disks, one with a single partition (Win2k) and one with 4 partitions (2xntfs, swap and root). All 5 partitions were screwed up. Windows install thought they were write protected and MSDOS fdisk would not recognise them at all. The only way I could recover them was with MaxBlast, by rebuilding the partitions from scratch. Even then, one partition reported 2Tb free space and one reported 0% free space but this corrected itself after loading data onto them and defragmenting.