The capacity of PHYSICALDRIVE0 is ...
60138 Cylinders x 165 Heads x 63 Sectors Per Track x 512 BytesPerSector = 320GB
Similarly, the capacities for PHYSICALDRIVE1 and PHYSICALDRIVE2 are ...
24792 x 255 x 63 x 512 = 204GB
121600 x 255 x 63 x 512 = 1000GB
PHYSICALDRIVE0 has two partitions.
Partition #1 has a size of 7.5GB and a type of 0x11. This is probably a rescue partition of some kind. The following page suggests that it may be a hidden OS/2 partition.
http://www.win.tue.nl/~aeb/partitions/partition_types-1.html
The partition table in the MBR is indicating that the second partition is an NTFS (0x07) partition with a size of 610400448 sectors, ie 312.5 GB.
However, the volume information in the boot sector doesn't match the information in the partition table. For example, NumberSectors = 141538319, which equates to only 72.5 GB.
Since 72.5 + 7.5 = 80, it appears that you have expanded the size of the partition to fill the drive (7.5 + 312.5), but you have left the NTFS volume within it untouched. That is, you now have a 72.5 GB NTFS volume inside a 312.5 GB partition.
The simplest solution would have been to leave the original partition size at 72.5GB, and then use Disk Management to create an additional partition in the remaining 240GB of unallocated space.
Alternatively, you need intelligent software that understands how to expand an NTFS volume to fill the partition allocated to it. Acronis True Image would have been able to do this.