

Copying all of the files and re-formatting. Pdisk: can't open file '/dev/rdisk1' for writing (Resource busy) 2. PDisk will not let me open the disk to be rewritten. It appears as though there are two partitions, masquerading as MS Data, assigned to the same set of blocks, with the name Yosemite. TestDisk shows some weird configurations. I have tried to create my own partition map for the drive using TestDisk to find the partitions and PDisks to create the new partition. If I boot into Windows, I can copy anything from the partition, and it works just fine, but boot back into OS X, and the partition is unreadable. The strangest part of it all is that Windows can still read the drive. The files are intact, but OS X sees it as disk1s3, and is unable to read, write, or repair the disk. The windows partition removed successfully, but the Yosemite partition immediately became unrecognizable by OS X. I opened up Disk Utility and saw that the Windows Bridge partition was still there according to OS X.

The partition deleted, but the reformat operation failed, so I figured I would boot into OS X, remove the partition, and add a new FAT 0.7 TB partition which could then be reformatted by Windows into NTFS. In Windows' disk management, I tried to remove the Windows Bridge partition and replace it with a 0.7TB NTFS partition. However, recently, I installed Windows through Bootcamp on my primary SSD. Later on, I decided that I no longer needed the Mac HD clone, since Yosemite is pretty stable at this point, so I removed it I also resized the Yosemite partition down to 300 GB since I wasn't going to write anything else to it. I then upgraded my main system to Yosemite. I had originally downloaded and installed Yosemite on a separate partition to play around with it, and then when I decided I liked it, I copied my Mavericks Mac HD onto another partition of the drive as a backup. I have an external 3TB hard drive that I use for storage with my Mac Pro. So let me fill you in on what happened here. Problem: I need to fix my hard drive's partition map Okay, so something really strange has happened, and it's a doozy, so please bear with me.
