- Joined
- Jun 13, 2010
- Messages
- 12
- Mac
- Classic Mac
- Mobile Phone
Re: MultiBeast 2.0.0- MBR changes?
Hey peoples-
I'm still in a state of shock at the apparent corruption of the boot record or partition table which has happened since installing OSX and Multibeast etc. I'm trying to work out if this is a one-off or if there's something inherent in my setup and the way Multibeast/chameleon works that means maybe my setup is no good for this kind of tinkering.
My win7 data drive (d drive) has disappeared and is showing only as E: RAW partition. I believe something may have happened when using multibeast to select the Win7 partition to boot into. My D drive was protected using bitlocker (win7 Ultimate)- and was last seen before my OSX attempts- I'm not sure if the change to AHCI did some damage to it (have since reverted to IDE, but still it's not showing up) OR if I selected the wrong option at the Multibeast boot screen, and some changes were made to the drive?
My first attempt at multibooting presented me with 3 options- Snow Leopard, System Reserved (with a windows icon) and NTFS (windows icon)... I selected the NTFS one the first time, and I suspect this is where things went wrong. I think that may have been my D drive, Multibeast has attempted to boot it- and something has since changed in the partition table.... That partition has not been showing up since- either in Win7, or as a boot option in Multibeast.
I've researched & tried several "data recovery" tools, but so far none have even made a successful pass at scanning the drive (bad boot record or something)- it's not meant to be a bootable drive anyway?
I would be overjoyed if someone can help me recover my D drive, and also let me know if this is safe to try ever again with Multibeast etc...
Thanks in advance... =)
Hey peoples-
I'm still in a state of shock at the apparent corruption of the boot record or partition table which has happened since installing OSX and Multibeast etc. I'm trying to work out if this is a one-off or if there's something inherent in my setup and the way Multibeast/chameleon works that means maybe my setup is no good for this kind of tinkering.
My win7 data drive (d drive) has disappeared and is showing only as E: RAW partition. I believe something may have happened when using multibeast to select the Win7 partition to boot into. My D drive was protected using bitlocker (win7 Ultimate)- and was last seen before my OSX attempts- I'm not sure if the change to AHCI did some damage to it (have since reverted to IDE, but still it's not showing up) OR if I selected the wrong option at the Multibeast boot screen, and some changes were made to the drive?
My first attempt at multibooting presented me with 3 options- Snow Leopard, System Reserved (with a windows icon) and NTFS (windows icon)... I selected the NTFS one the first time, and I suspect this is where things went wrong. I think that may have been my D drive, Multibeast has attempted to boot it- and something has since changed in the partition table.... That partition has not been showing up since- either in Win7, or as a boot option in Multibeast.
I've researched & tried several "data recovery" tools, but so far none have even made a successful pass at scanning the drive (bad boot record or something)- it's not meant to be a bootable drive anyway?
I would be overjoyed if someone can help me recover my D drive, and also let me know if this is safe to try ever again with Multibeast etc...
Thanks in advance... =)