MBR disk overwritten by rogue GPT based installer
Posted: 15 Aug 2018, 12:47
Hi,
I've had an unfortunate incident where a chrome os installer targeted the wrong disk during an install (yes it never even asked).
In short, a working MBR disk containing windows 7 (NTFS) was overwritten by a new GPT parition table with umpteen new partitions.
I've tried photorec but nothing useful happens there.
So, when using testdisk, using a deepscan I can find what appear to the the existing MBR partitions (i only want the data off it).
But attempts to restore the MBR partitions have failed so far (i created an img via dd so I can always revert back to the original overwritten state).
Where I'm confused, is the restore process, specifically as my original scheme was MBR and the disk is not detected as GPT.
I specify intel / pc, should I leave it as GPT?
It's quite difficult to set which partitions to recover as they overlap.
Am I flogging a dead horse?
Thanks for any help / comments.
Kind regards,
Neil
I've had an unfortunate incident where a chrome os installer targeted the wrong disk during an install (yes it never even asked).
In short, a working MBR disk containing windows 7 (NTFS) was overwritten by a new GPT parition table with umpteen new partitions.
I've tried photorec but nothing useful happens there.
So, when using testdisk, using a deepscan I can find what appear to the the existing MBR partitions (i only want the data off it).
But attempts to restore the MBR partitions have failed so far (i created an img via dd so I can always revert back to the original overwritten state).
Where I'm confused, is the restore process, specifically as my original scheme was MBR and the disk is not detected as GPT.
I specify intel / pc, should I leave it as GPT?
It's quite difficult to set which partitions to recover as they overlap.
Am I flogging a dead horse?
Thanks for any help / comments.
Kind regards,
Neil