Bootrec /nt60 C: killed my partition table and added a rogue efi partition

I had an issue originally with my system freezing every time I left it idle for a period. I traced it to possibly an ATI error, incompatibility or problem. Chkdsk was ran but I was not able to fully diagnose this for sure untill the REAL, BIG, problem happened. I was going to update my bios with the Gigabyte bios flash utility and decided to reboot and see what version I had before I upgraded and I accidentally pressed 'Delete' trying to enter the BIOS right when it went to the next screen where it says DMI Pool data which activated the 'press any key to ....' start Gigibyte's ExpressRecovery2. I exited out of ExpressRevocery 2 and should not have caused any issues, and even if I pressed 'OK' to run it, as I understand it would try to build a recovery partition at the end of your boot disk IF you had unallowcated space there and if not, spit out a message that there 'was not any space' and let you reboot.

After this, the system would not boot back into Windows 7. It appeared to be loading but then would reboot. I thought the BCD or partition boot record had acquired corruption so I loaded the DVD and started the startup recovery which ran for 1.5 hours and said there was partition table corruption that it fixed.

Rebooted but then it was in this infinite loop where it went back and forth from the "windows boot manager windows failed to start 0xc000000e ....... the disk is not accessible" to the Boot Manager saying to put in the Windows Disk and 'press any key to boot it' but when I put in the windows disk it would just reboot to the bios and end up right back in the same spot.

So I ran startup recovery two more times with the same result.

Then I ran diskpart and it did not show any partitions on the disk that had Windows 7 when in fact it had 2 Primaries and extended with 3 logical data partitions on this 1TB HDD which should have looked like so:

SIZE FS LABEL

100MB ...........NTFS........... System Researved

80GB .............NTFS........... Windows 7

818GB ..................Extended

160GB ...........NTFS.......... Data

70GB ............NTFS......... Data

260GB ..................... Unallowcated

10GB .............NTFS........ Data

180 ..............NTFS....... Data

160 ................NTFS..... Data

I then booted into UBCD and ran TestDisk which found all of the partitions and rewrote the partition tables and I thought I was finally getting somewhere.

I then rebooted and I think it may have spit out an error that said something about a boot record problem.

I read how to rebuild MBR or boot record which was to enter into the cmd "bootrect /nt60 C:

Yes, that was bootrecT, as that is what it said to do and not bootrec as I notice so9me other tutorials tell you. boocrec command previously met with a message saying it was an unknown command. I don't know what the difference would be between bootrec and bootrect.

It still does not boot so then I decide to boot into GParted recovery cd since it has other diag tools and I notice right of that my partitions on this disk now look like the following:

SIZE FS LABEL

100MB ................NTFS...... System Researved

30GB ..................NTFS...... (blank)

9.5GB .................FAT16 .... (blank)

892GB ..................Extended

21.4GB ............... Unallowcated

1.4MiB ................FAT16 .......EFISECTOR

22.4 ...................Unallowcated

160GB ..................... Data

70GB ..................... Data

260GB ..................... Unallowcated

10GB ...............NTFS......... Data

180 .................NTFS ........ Data

160 ..................NTFS ........ Data

How in the world did this happen? It seams that MS engineers just decided what EVERYONE must be using EFI and if you want to rebuild your boot records that the bootrec just puts it in there and rearranges your partitioning scheme and tables on top of it and thus destroying your partition tables and data.

Is there any way to remedy this? Or at least get all of my data back? This is really aggravating and I feel like I have been violated. All I wanted to do was rebuild the BCD after fixing the partition tables. Never had this kind of issue in the easy days back with XP.

Continue reading...