Welcome, Guest. Please login or register.
Did you miss your activation email?
November 21, 2017, 01:52:52 PM
Home Help Search Login Register
News:

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  DiskPatch (Moderators: Tom, Joep)
| | |-+  EFI BIOS GUID Partition Type - Continuing May Corrupt Disk Structures
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] 2 Go Down Print
Author Topic: EFI BIOS GUID Partition Type - Continuing May Corrupt Disk Structures  (Read 16389 times)
ckent1
member

Posts: 24


« on: October 16, 2013, 12:18:23 AM »

Hello,

I'm trying to create a Support Analysis File using a Window 8 system booting from a DiskPatch USB drive for a 2TB HDD having disk problems and getting the error:

"EFI BIOS GUID Partition Type - Continuing May Corrupt Disk Structures"

Please advise.
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #1 on: October 16, 2013, 09:38:42 AM »

That is just a warning, as long as you do not change anything on the disk there should be no problem. You should be able to continue the Support Analysis log procedure.
Logged

ckent1
member

Posts: 24


« Reply #2 on: October 30, 2013, 03:51:39 AM »

Thanks, Tom, I followed your advice but now have a brand new unbootable Windows 8 (ASUS P9X79-LE, i7, 16GB RAM) box!

The DiskPatch v4 Support Analysis Log completed on the bad 2TB drive (connected externally) but when I re-booted the main system the following error message appeared:

"Reboot and select proper boot device or insert boot media in selected boot device and press a key..."


I removed the 1TB GPT system disk and put it into an external enclosure and can see all the files, so just the boot code must have been corrupted. Not only is DiskPatch v4 incompatible with GPT drives but it causes corruption of the boot code!

Is DiskPatch v4 trying to write the Support Analysis Log file to the boot portion of the GPT drive as well as the USB key? This is the only thing I can think of as this should be a read-only procedure on the drive under test.

So, I am without the use of my main PC and have no way of getting it working (as of yet), and feel some compensation should be forthcoming from DIY Datarecovery as your procedures were followed exactly here (perhaps a complimentary copy of iRecover Pro, DiskPatch, etc).

Here are the steps I've tried so far (unsuccessfully) to fix the non-booting Windows 8 1TB GPT system drive:

1. Connected the 1TB drive to a Windows 7 system and tried to produce a DiskPatch v4 Support Analysis File but got the same "EFI BIOS GUID Partition Type - Continuing May Corrupt Disk Structures" error as above so didn't continue this time.

2. Re-connected the 1TB GPT drive, inserted the Win 8 Recovery DVD and started Repair your PC-->Troubleshoot--> Advanced Options--> System Restore (got the same "Reboot and select proper boot device" error above).

3. Ran Repair your PC-->Troubleshoot--> Advanced Options-->Automatic Repair (says Automatic Repair couldn't repair your PC).

4. Ran chkdsk /offlinescanandfix from the command prompt (only found some free space marked as allocated in the volume bitmap and no other errors). Tried rebooting and got the same error.

The only procedures I haven't tried are the 'Refresh your PC' and 'Reset your PC' options (both requiring me to re-install some or all of my apps).

Tom, you have been great help so far but I am very disappointed with the results here.

Your advice?
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #3 on: October 30, 2013, 09:54:40 AM »

Would it be possible to see the log of the session that (according to you) caused the boot issue? If you can't find the correct log just send/attach them all (please ZIP em first).

I must stress that DiskPatch doesn't change anything on a disk, unless the user initiates changes (through a repair or other action). In addition the Trial version doesn't even allow disk changes (in case you've been running the Trial version so far). We wouldn't be much of a recovery company if our tools caused more problems than they solve, so I'm pretty sure that we are not the cause of this. Still, to be sure I'd like to see the log files I mentioned.

Any chance this is caused by changing settings in the BIOS to accommodate the USB booting? Perhaps disabling EFI functions that leads to not being able to boot from a GPT disk? This is supported by the fact that the disk is normally accessible when connected as a secondary disk: if the GPT would be corrupted, volume access would not be possible at all.

Something else I'd really like to know: is the Windows 8 boot disk a GPT disk? I ask because this isn't a default way of doing things (though it could be for Win8, I haven't read up on that yet).
Logged

ckent1
member

Posts: 24


« Reply #4 on: October 30, 2013, 05:23:27 PM »

Tom, here is the Support Analysis Log file from the session causing the failed boot issue (first post from my other thread: Failed HDD started on October 18, 2013, 06:27:28 PM). I have been without the use of my main PC for over a week now:

.../000:01/LOG> ### LOG START ###
.../000:01/LOG> DISKPATCH 4.0.200
.../000:01/LOG> (C) 2000-2013 DIY DataRecovery
.../000:01/LOG> Contact info: www.DIYDataRecovery.nl
.../000:01/LOG> MemFree: 66Kb
.../000:01/LOG> CommandLineParms: /sup
.../000:01/LOG> LogDate: 10-17-2013
.../000:01/CFG> FilePath="C:DPFILES\"
.../000:01/CFG> ReadRetries="32"
.../000:01/CFG> WriteRetries="32"
.../000:01/CFG> MaxReadErrors="32"
.../000:01/CFG> MaxWriteErrors="1"
.../000:01/CFG> ReadDelay="0"
.../000:01/CFG> LogEachReadError="1"
.../000:01/CFG> WriteAfterReadError="1"
.../000:01/CFG> VfyFixedBadSect="1"
.../000:01/CFG> CleanAfterDOD="1"
.../000:01/CFG> DiskReset="1"
.../000:01/CFG> SectorSkip="1024"
.../000:01/CFG> AutoSaveState="1"
.../000:01/CFG> DumpFoundSectors="0"
.../000:01/CFG> FixFats="1"
.../000:01/CFG> MaxFatScan="51200"
.../000:01/CFG> MaxDataColEntries="256"
.../000:01/CFG> IgnoreF8FF="0"
.../000:01/CFG> DownSizeExt="1"
.../000:01/CFG> ScanSignature="55AA"
.../000:01/CFG> Rebuild="00"
.../000:01/13H> Ext13H installed test requested
.../000:01/13H> Disk found at 128
.../000:01/13H> Ext13H version: 2.1 / EDD-1.1
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Ext13H Support: Enhanced disk drive functions
.../000:01/13H> Ext13H Flags: Cylinder/head/sector info is valid
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 128 X13H data : 1024/16/63 2017280/512
.../000:01/13H> Disk found at 129
.../000:01/13H> Ext13H version: 2.1 / EDD-1.1
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Ext13H Support: Enhanced disk drive functions
.../000:01/13H> Ext13H Flags: Cylinder/head/sector info is valid
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 129 X13H data : 1024/255/63 3907029168/512
.../000:01/13H> Disk found at 130
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Ext13H Support: Enhanced disk drive functions
.../000:01/13H> Ext13H Flags: DMA boundary errors handled transparently
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 130 X13H data : 16383/16/63 1250263728/512
.../000:01/13H> Ext13H tested ok
.../000:01/FDL> DiskList requested
.../000:01/FDL> Disk found at 128
.../000:01/FDL> Disk found at 129
.../000:01/FDL> Disk found at 130
### DISKLIST ###
__D_|________LBA_|___H_|__S_|___GB_|__GEO_|___SS_
128 | ...2017280 | .16 | 63 | ...0 | BIOS | .512
129 | 3907029168 | 255 | 63 | 1863 | BIOS | .512
130 | 1250263728 | 255 | 63 | .596 | BIOS | .512
..0 | .........0 | ..0 | .0 | ...0 | BIOS | ...0
.../000:01/IAS> AdmiSector found on disk 0 (128)
.../000:01/IAS> AdmiSector init complete for disk 1 (129)
.../000:01/IAS> AdmiSector init complete for disk 2 (130)
.../000:02/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:02/EXE> Read/Write pattern test for disk 1 (129) successful
.../000:03/EXE> Read/Write pattern test for disk 2 (130) successful
.../000:03/WAS> AdmiSectors in use : 0+ 1+ 2+
.../000:03/KEY> DEMO/1
.../000:03/PFC> PQstuff signature not detected on disk 0 (128)
.../000:03/PFC> PQstuff signature not detected on disk 1 (129)
.../000:03/PFC> PQstuff signature not detected on disk 2 (130)
.../000:03/PFC> Disk health 50-100
.../000:05/PFC> Partition State backup not found on disk 0 (128)
.../000:05/PFC> Partition State backup not found on disk 1 (129)
.../000:05/PFC> Partition State backup not found on disk 2 (130)
.../000:05/PFC> No Repair date found on disk 0 (128)
.../000:05/PFC> No Repair date found on disk 1 (129)
.../000:05/PFC> No Repair date found on disk 2 (130)
.../001:30/CSD> Start CheckDisk for disk 1 (129)
.../001:30/CSD> 0 (0 0 1)
.../001:30/CSD> 16064 (0 254 63)
.../001:30/CSD> 3907024065 (243201 0 1)
.../001:30/CSD> 3907029167 (243201 80 63)
.../001:30/CSD> CheckDisk complete, ReadErrors 0
.../001:30/USD> Disk 1 (129) selected
.../001:30/GSC> First DP run, geo info for disk 1 (129) not yet recorded
.../001:34/WAS> AdmiSectors in use : 0+ 1+ 2+
129/001:34/USD> MBR for disk 1 (129)
129/001:34/LOG> SectorDump requested at 0 (0 0 1)
###
000   33 C0 8E D0 BC 00 7C FB 50 07 50 1F FC BE 1B 7C  |  3м.|P.P..|
016   BF 1B 06 50 57 B9 E5 01 F3 A4 CB BD BE 07 B1 04  |  ..PW.˽..
032   38 6E 00 7C 09 75 13 83 C5 10 E2 F4 CD 18 8B F5  |  8n.|.u...
048   83 C6 10 49 74 19 38 2C 74 F6 A0 B5 07 B4 07 8B  |  .It.8,t ..
064   F0 AC 3C 00 74 FC BB 07 00 B4 0E CD 10 EB F2 88  |  <.t....
080   4E 10 E8 46 00 73 2A FE 46 10 80 7E 04 0B 74 0B  |  N.F.s*F.~..t.
096   80 7E 04 0C 74 05 A0 B6 07 75 D2 80 46 02 06 83  |  ~..t. .uҀF..
112   46 08 06 83 56 0A 00 E8 21 00 73 05 A0 B6 07 EB  |  F..V..!.s. .
128   BC 81 3E FE 7D 55 AA 74 0B 80 7E 10 00 74 C8 A0  |  >}Ut.~..t
144   B7 07 EB A9 8B FC 1E 57 8B F5 CB BF 05 00 8A 56  |  .멋.W˿..V
160   00 B4 08 CD 13 72 23 8A C1 24 3F 98 8A DE 8A FC  |  ...r#$?ފ
176   43 F7 E3 8B D1 86 D6 B1 06 D2 EE 42 F7 E2 39 56  |  Cцֱ.B9V
192   0A 77 23 72 05 39 46 08 73 1C B8 01 02 BB 00 7C  |  .w#r.9F.s....|
208   8B 4E 02 8B 56 00 CD 13 73 51 4F 74 4E 32 E4 8A  |  N.V..sQOtN2
224   56 00 CD 13 EB E4 8A 56 00 60 BB AA 55 B4 41 CD  |  V..V.`UA
240   13 72 36 81 FB 55 AA 75 30 F6 C1 01 74 2B 61 60  |  .r6Uu0.t+a`
256   6A 00 6A 00 FF 76 0A FF 76 08 6A 00 68 00 7C 6A  |  j.j..v..v.j.h.|j
272   01 6A 10 B4 42 8B F4 CD 13 61 61 73 0E 4F 74 0B  |  .j.B.aas.Ot.
288   32 E4 8A 56 00 CD 13 EB D6 61 F9 C3 49 6E 76 61  |  2V..aInva
304   6C 69 64 20 70 61 72 74 69 74 69 6F 6E 20 74 61  |  lid partition ta
320   62 6C 65 00 45 72 72 6F 72 20 6C 6F 61 64 69 6E  |  ble.Error loadin
336   67 20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74  |  g operating syst
352   65 6D 00 4D 69 73 73 69 6E 67 20 6F 70 65 72 61  |  em.Missing opera
368   74 69 6E 67 20 73 79 73 74 65 6D 00 00 00 00 00  |  ting system.....
384   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
400   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
416   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
432   00 00 00 00 00 2C 44 63 38 2F 92 FE 00 00 00 01  |  .....,Dc8/....
448   01 00 07 FE FF FF 3F 00 00 00 D1 70 E0 E8 00 00  |  .....?...p..
464   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
480   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
496   00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA  |  ..............U
###
129/001:34/VEC> Start Verify EPBR Chain for disk 1 (129)
129/001:34/VEC> Listing current partitions on disk:
129/001:34/VEC>     NTFS (P)                       63  3907023057    (1863 Gb)
129/001:34/VEC> Partition Table info for sector 0 (0 0 1)
129/001:34/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..07 | ....0...1...1 | .1023.254..63 | ........63 | 3907023057
..2 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
129/001:34/VEC> 55AA sig Ok
129/001:34/LOG> Boot sector dump requested at 63 (0 1 1)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 240
......Hidden Sectors (dec): 63
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 3907023056
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 244188941
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): BAD8334CD83305E3
........Volume Label (txt):
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/001:34/VEC> BS and BBS equal
129/001:34/VEC> Verify EPBR Chain completed
129/001:34/USD> Select disk completed
129/003:15/SCN> DiskScan requested, ScanType is 3
129/003:15/SCN> from 0 (0 0 1) to 3907029167 (243201 80 63), 3907029168 sectors
129/003:15/SCN> Starting QuickScan (pre-vista) at 63 (0 1 1)
129/003:15/SCN> Next QuickScan location at 3907023120 (243200 240 1)
129/003:16/SCN> Next QuickScan location at 0 (0 0 1)
129/003:16/SCN> QuickScan finished
129/003:16/SCN> Starting SmartScan (pre-vista) at 0 (0 0 1) (JMP=16065, RNG=63)
129/624:49/SCN> SmartScan finished
129/624:49/SCN> DiskScan completed
129/624:49/SCN> ReadErrors for disk 1 (129): 0
129/830:09/LOG> DataCollection items found: 8 / 1
### DATACOLLECTION, FULL ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL_|_F
001 | 129 | ........63 | ...NTFS | ..BS | ........63 | 3907023057 | PRI | .
002 | 129 | 3907023119 | ...NTFS | .BBS | ........63 | 3907023057 | PRI | .
003 | 129 | .........0 | ...NTFS | PTE1 | ........63 | 3907023057 | PRI | .
004 | 129 | ........63 | ...NTFS | ..BS | ........63 | 3907023057 | PRI | I
005 | 129 | .179429994 | ...NTFS | ..BS | .179429994 | .........1 | PRI | .
006 | 129 | .566757183 | ..FAT32 | PTE1 | 3067168663 | 2506779213 | LOG | .
007 | 129 | 3671141697 | EZDRIVE | PTE1 | .823301569 | 4166358685 | LOG | .
008 | 129 | 3907024064 | ...NTFS | .BBS | .....16128 | 3907007937 | LOG | .
129/830:09/LOG> DataCollection items found: 8 / 1
### DATACOLLECTION, CLEANED ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL
001 | 129 | ........63 | ...NTFS | ..BS | ........63 | 3907023057 | PRI
002 | 129 | 3907023119 | ...NTFS | .BBS | ........63 | 3907023057 | PRI
003 | 129 | .........0 | ...NTFS | PTE1 | ........63 | 3907023057 | PRI
005 | 129 | .179429994 | ...NTFS | ..BS | .179429994 | .........1 | PRI
006 | 129 | .566757183 | ..FAT32 | PTE1 | 3067168663 | 2506779213 | LOG
007 | 129 | 3671141697 | EZDRIVE | PTE1 | .823301569 | 4166358685 | LOG
008 | 129 | 3907024064 | ...NTFS | .BBS | .....16128 | 3907007937 | LOG
129/830:09/LOG> PartList items created: 5
### PARTLIST ###
SEQ_|____TYPE_|_PTE_|__BS_|_BBS_|F8FF_|___S_|___L_|__PL_|_C_|___R
001 | ...NTFS | ..3 | ..1 | ..2 | ..0 | ..3 | ..3 | ..3 | 3 | ..A
002 | ...NTFS | ... | ... | ..8 | ..0 | ..8 | ..8 | ..8 | 1 | ..B
003 | ...NTFS | ... | ..5 | ... | ..0 | ..5 | ..5 | ..5 | 1 | ..B
004 | EZDRIVE | ..7 | ..0 | ..0 | ..0 | ..7 | ..7 | ..7 | 1 | ..-
005 | ..FAT32 | ..6 | ... | ... | ... | ..6 | ..6 | ..6 | 1 | ...
### PARTLIST, INTERPRETED ###
SEQ_|____TYPE_|______START_|_____LENGTH_|________END_|__PL_|___R_|___A
001 | ...NTFS | ........63 | 3907023057 | 3907023119 | PRI | ..A | ..X
002 | ...NTFS | .....16128 | 3907007937 | 3907024064 | LOG | ..B | ..X
003 | ...NTFS | .179429994 | .........1 | .179429994 | PRI | ..B | ..?
004 | EZDRIVE | .823301569 | 4166358685 | .694692957 | LOG | ..- | ..?
005 | ..FAT32 | 3067168663 | 2506779213 | 1278980579 | LOG | ... | ..?
129/830:09/SST> SaveState requested for disk 1 (129)
129/830:13/WAS> AdmiSectors in use : 0+ 1+ 2+
129/830:14/SST> SaveState completed for disk 1 (129)
129/830:14/EXE> Analysis complete
129/830:21/LOG> RunTime: 830:21
129/830:21/LOG> ### CLOSE LOG ###



The corrupted boot drive is showing as:
 130 | 1250263728 | 255 | 63 | .596 | BIOS | .512
but is actually 1TB (GPT).

Tom, it looks like whoever wrote the DiskPatch v4 program recognized it causes disk corruption, hence the "EFI BIOS GUID Partition Type - Continuing May Corrupt Disk Structures" warning message when creating the Support Analysis Log file, which was why I contacted you on Oct. 16, 2013, to verify it was safe to continue.

I tried resetting the BIOS to factory default but the same boot error message above still appears.

Were you the DiskPatch v4 developer?
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #5 on: October 30, 2013, 06:55:21 PM »

This log does not have the EFI warning in it. In addition, the disk that is checked in this log is not a GPT disk. So nothing's indicated as wrong in this particular log.

I'm not sure what is going on with that size thing, I've never seen DiskPatch get that wrong. Are you sure that the disk size is 1TB, and is it possible to show me how you determined that (screenshot, log from other tools you have used) ? If you're up for it run the SMART diagnosis from the DiskPatch Start menu ("Create a S.M.A.R.T. report") and post the resulting log, that should allow me an even more detailed look at the hardware. Note though that this will only work well if the disk that is checked is connected directly (no USB).

Any chance you can create a support analysis log for the disk that is currently giving you trouble, the main bootable win8 disk? If you don't trust DiskPatch with the disk you can use the forensic switch, this will make sure that NOTHING is written to the disk.
To use forensic mode, select "DiskPatch Options (troubleshooting)" from the first start menu that appears after booting the DiskPatch boot disk, and select "Start DiskPatch in Forensic Mode". When prompted to select a disk to protect, select the disk you wish to be excluded from any and all writing.

Sorry to put you to work like this but I'm just as anxious as you are to find out what is going on here, and if possible I'd like to fix it.

DiskPatch is designed by both of us at DIY, the coding is mine.

Quote
Tom, it looks like whoever wrote the DiskPatch v4 program recognized it causes disk corruption, hence the "EFI BIOS GUID Partition Type - Continuing May Corrupt Disk Structures" warning message when creating the Support Analysis Log file, which was why I contacted you on Oct. 16, 2013, to verify it was safe to continue.
It was safe. Corruption might only occur if the user actually runs a repair on the disk, or uses other means to change anything on the disk. Running a support analysis log is NOT part of that. If I am at fault here it is for not explaining the situation and the consequences well enough, but I thought that being concise was the best course of action with that particular message.
This is from the manual, and explains it well:

"If you continue past this warning and perform a repair, the GUID partition description data (NOT the actual partitions!) might be damaged. This doesn't have to be as problematic as it sounds: if you have GUID type partitions but you can't access them, rebuilding the partition table with DiskPatch (which will result in a MBR type partition layout) may very well give you access again. You could say that you would have converted the GUID partition setup to a MBR setup. In such case it wouldn't be all that dramatic that the GUID partition description data is gone; you have access to the partitions and can copy your data to a safe place. After that you could always repartition the disk as GUID if you wish."
Logged

ckent1
member

Posts: 24


« Reply #6 on: October 31, 2013, 05:28:19 AM »

Thanks, Tom. Here is the DiskPatch Support Analysis that caused corruption in the 1TB Windows 8 system drive (the previous DP support log posted above was done using my Windows 7 laptop not the Windows 8 box hence the 640 (596) GB HDD - too many systems / HDDs to keep track of).

It looks like I only went as far the Select Disk stage and aborted, and it still corrupted the drive:


.../000:01/LOG> ### LOG START ###
.../000:01/LOG> DISKPATCH 4.0.200
.../000:01/LOG> (C) 2000-2013 DIY DataRecovery
.../000:01/LOG> Contact info: www.DIYDataRecovery.nl
.../000:01/LOG> MemFree: 62Kb
.../000:01/LOG> CommandLineParms: /sup
.../000:01/LOG> LogDate: 10-17-2013
.../000:01/CFG> FilePath="C:DPFILES\"
.../000:01/CFG> ReadRetries="32"
.../000:01/CFG> WriteRetries="32"
.../000:01/CFG> MaxReadErrors="32"
.../000:01/CFG> MaxWriteErrors="1"
.../000:01/CFG> ReadDelay="0"
.../000:01/CFG> LogEachReadError="1"
.../000:01/CFG> WriteAfterReadError="1"
.../000:01/CFG> VfyFixedBadSect="1"
.../000:01/CFG> CleanAfterDOD="1"
.../000:01/CFG> DiskReset="1"
.../000:01/CFG> SectorSkip="1024"
.../000:01/CFG> AutoSaveState="1"
.../000:01/CFG> DumpFoundSectors="0"
.../000:01/CFG> FixFats="1"
.../000:01/CFG> MaxFatScan="51200"
.../000:01/CFG> MaxDataColEntries="256"
.../000:01/CFG> IgnoreF8FF="0"
.../000:01/CFG> DownSizeExt="1"
.../000:01/CFG> ScanSignature="55AA"
.../000:01/CFG> Rebuild="00"
.../000:01/13H> Ext13H installed test requested
.../000:01/13H> Disk found at 128
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Ext13H Support: Enhanced disk drive functions
.../000:01/13H> Ext13H Flags: Cylinder/head/sector info is valid
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 128 X13H data : 2001/16/63 2017280/512
.../000:01/13H> Disk found at 129
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 129 X13H data : 16383/16/63 1953525168/512
.../000:01/13H> Disk found at 130
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 130 X13H data : 16383/16/63 3519069872/512
.../000:01/13H> Disk found at 131
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 131 X13H data : 16383/16/63 1565565872/512
.../000:01/13H> Ext13H tested ok
.../000:01/FDL> DiskList requested
.../000:01/FDL> Disk found at 128
.../000:01/FDL> Disk found at 129
.../000:01/FDL> Disk found at 130
.../000:01/FDL> Disk found at 131
### DISKLIST ###
__D_|________LBA_|___H_|__S_|___GB_|__GEO_|___SS_
128 | ...2017280 | .16 | 63 | ...0 | BIOS | .512
129 | 1953525168 | 255 | 63 | .931 | BIOS | .512
130 | 3519069872 | 255 | 63 | 3726 | BIOS | .512
131 | 1565565872 | 255 | 63 | 2794 | BIOS | .512
.../000:01/EXE> !- EFI BIOS / GUID partition type found on disk 1 (129)
.../000:01/EXE> !- EFI BIOS / GUID partition type found on disk 3 (131)
.../000:20/IAS> AdmiSector init complete for disk 0 (128)
.../000:20/IAS> AdmiSector init complete for disk 1 (129)
.../000:20/IAS> AdmiSector found on disk 2 (130)
.../000:20/IAS> AdmiSector init complete for disk 3 (131)
.../000:21/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:21/EXE> Read/Write pattern test for disk 1 (129) successful
.../000:22/EXE> Read/Write pattern test for disk 2 (130) successful
.../000:22/EXE> Read/Write pattern test for disk 3 (131) successful
.../000:22/WAS> AdmiSectors in use : 0+ 1+ 2+ 3+
.../000:22/KEY> DEMO/1
.../000:22/PFC> PQstuff signature not detected on disk 0 (128)
.../000:22/PFC> PQstuff signature not detected on disk 1 (129)
.../000:22/PFC> PQstuff signature not detected on disk 2 (130)
.../000:22/PFC> PQstuff signature not detected on disk 3 (131)
.../000:22/PFC> Disk health not checked
.../000:24/PFC> Partition State backup not found on disk 0 (128)
.../000:24/PFC> Partition State backup not found on disk 1 (129)
.../000:24/PFC> Partition State backup not found on disk 2 (130)
.../000:24/PFC> Partition State backup not found on disk 3 (131)
.../000:24/PFC> No Repair date found on disk 0 (128)
.../000:24/PFC> No Repair date found on disk 1 (129)
.../000:24/PFC> No Repair date found on disk 2 (130)
.../000:24/PFC> No Repair date found on disk 3 (131)
.../001:37/USD> No source / disk selected
.../001:37/USD> Select disk completed
.../001:37/LOG> RunTime: 001:37
.../001:37/LOG> ### CLOSE LOG ###



Here is the SMART report (not much here) and the new DiskPatch Support Analysis log for the corrupted 1TB Win 8 boot disk (this drive show up with an exclamation point next to DP Disk Health).

SMART
Detected Controllers

  Disk Controller 1
    Device Vendor . . . . . . . . . . . . . : 8086
    Device ID . . . . . . . . . . . . . . . : 1D02
    Device  . . . . . . . . . . . . . . . . : Intel
    Device Location . . . . . . . . . . . . : Bus 0, Device 31, Function 2
    Device Ports  . . . . . . . . . . . . . : F070-F077, F060-F063, F050-F057, F040-F043, F020-F03F




.../000:01/LOG> ### LOG START ###
.../000:01/LOG> DISKPATCH 4.0.200
.../000:01/LOG> (C) 2000-2013 DIY DataRecovery
.../000:01/LOG> Contact info: www.DIYDataRecovery.nl
.../000:01/LOG> MemFree: 62Kb
.../000:01/LOG> CommandLineParms: /sup
.../000:01/LOG> LogDate: 10-30-2013
.../000:01/CFG> FilePath="C:DPFILES\"
.../000:01/CFG> ReadRetries="32"
.../000:01/CFG> WriteRetries="32"
.../000:01/CFG> MaxReadErrors="32"
.../000:01/CFG> MaxWriteErrors="1"
.../000:01/CFG> ReadDelay="0"
.../000:01/CFG> LogEachReadError="1"
.../000:01/CFG> WriteAfterReadError="1"
.../000:01/CFG> VfyFixedBadSect="1"
.../000:01/CFG> CleanAfterDOD="1"
.../000:01/CFG> DiskReset="1"
.../000:01/CFG> SectorSkip="1024"
.../000:01/CFG> AutoSaveState="1"
.../000:01/CFG> DumpFoundSectors="0"
.../000:01/CFG> FixFats="1"
.../000:01/CFG> MaxFatScan="51200"
.../000:01/CFG> MaxDataColEntries="256"
.../000:01/CFG> IgnoreF8FF="0"
.../000:01/CFG> DownSizeExt="1"
.../000:01/CFG> ScanSignature="55AA"
.../000:01/CFG> Rebuild="00"
.../000:01/13H> Ext13H installed test requested
.../000:01/13H> Disk found at 128
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Ext13H Support: Enhanced disk drive functions
.../000:01/13H> Ext13H Flags: Cylinder/head/sector info is valid
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 128 X13H data : 2001/16/63 2017280/512
.../000:01/13H> Disk found at 129
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 129 X13H data : 16383/16/63 1953525168/512
.../000:01/13H> Ext13H tested ok
.../000:01/FDL> DiskList requested
.../000:01/FDL> Disk found at 128
.../000:01/FDL> Disk found at 129
### DISKLIST ###
__D_|________LBA_|___H_|__S_|___GB_|__GEO_|___SS_
128 | ...2017280 | .16 | 63 | ...0 | BIOS | .512
129 | 1953525168 | 255 | 63 | .931 | BIOS | .512
..0 | .........0 | ..0 | .0 | ...0 | BIOS | ...0
..0 | .........0 | ..0 | .0 | ...0 | BIOS | ...0
.../000:01/EXE> !- EFI BIOS / GUID partition type found on disk 1 (129)
.../000:05/IAS> AdmiSector found on disk 0 (128)
.../000:05/IAS> AdmiSector found on disk 1 (129)
.../000:06/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:07/EXE> Read/Write pattern test for disk 1 (129) successful
.../000:07/WAS> AdmiSectors in use : 0+ 1+
.../000:07/KEY> DEMO/1
.../000:07/PFC> PQstuff signature not detected on disk 0 (128)
.../000:07/PFC> PQstuff signature not detected on disk 1 (129)
.../000:07/PFC> Disk health not checked
.../000:08/PFC> Partition State backup not found on disk 0 (128)
.../000:08/PFC> Partition State backup not found on disk 1 (129)
.../000:08/PFC> No Repair date found on disk 0 (128)
.../000:08/PFC> No Repair date found on disk 1 (129)
.../000:29/CSD> Start CheckDisk for disk 1 (129)
.../000:29/CSD> 0 (0 0 1)
.../000:29/CSD> 16064 (0 254 63)
.../000:29/CSD> 1953520065 (121601 0 1)
.../000:29/CSD> 1953525167 (121601 80 63)
.../000:29/CSD> CheckDisk complete, ReadErrors 0
.../000:29/USD> Disk 1 (129) selected
.../000:29/GSC> First DP run, geo info for disk 1 (129) not yet recorded
.../000:29/WAS> AdmiSectors in use : 0+ 1+
129/000:29/USD> MBR for disk 1 (129)
129/000:29/LOG> SectorDump requested at 0 (0 0 1)
###
000   33 C0 8E D0 BC 00 7C 8E C0 8E D8 BE 00 7C BF 00  |  3м.|ؾ.|.
016   06 B9 00 02 FC F3 A4 50 68 1C 06 CB FB B9 04 00  |  ...Ph....
032   BD BE 07 80 7E 00 00 7C 0B 0F 85 0E 01 83 C5 10  |  .~..|.....
048   E2 F1 CD 18 88 56 00 55 C6 46 11 05 C6 46 10 00  |  .V.UF..F..
064   B4 41 BB AA 55 CD 13 5D 72 0F 81 FB 55 AA 75 09  |  AU.]r.Uu.
080   F7 C1 01 00 74 03 FE 46 10 66 60 80 7E 10 00 74  |  ..t.F.f`~..t
096   26 66 68 00 00 00 00 66 FF 76 08 68 00 00 68 00  |  &fh....f.v.h..h.
112   7C 68 01 00 68 10 00 B4 42 8A 56 00 8B F4 CD 13  |  |h..h..BV..
128   9F 83 C4 10 9E EB 14 B8 01 02 BB 00 7C 8A 56 00  |  .....|V.
144   8A 76 01 8A 4E 02 8A 6E 03 CD 13 66 61 73 1C FE  |  v.N.n..fas.
160   4E 11 75 0C 80 7E 00 80 0F 84 8A 00 B2 80 EB 84  |  N.u.~...
176   55 32 E4 8A 56 00 CD 13 5D EB 9E 81 3E FE 7D 55  |  U2V..]랁>}U
192   AA 75 6E FF 76 00 E8 8D 00 75 17 FA B0 D1 E6 64  |  un.v..u.d
208   E8 83 00 B0 DF E6 60 E8 7C 00 B0 FF E6 64 E8 75  |  .`|..du
224   00 FB B8 00 BB CD 1A 66 23 C0 75 3B 66 81 FB 54  |  ...f#u;fT
240   43 50 41 75 32 81 F9 02 01 72 2C 66 68 07 BB 00  |  CPAu2..r,fh..
256   00 66 68 00 02 00 00 66 68 08 00 00 00 66 53 66  |  .fh....fh....fSf
272   53 66 55 66 68 00 00 00 00 66 68 00 7C 00 00 66  |  SfUfh....fh.|..f
288   61 68 00 00 07 CD 1A 5A 32 F6 EA 00 7C 00 00 CD  |  ah....Z2.|..
304   18 A0 B7 07 EB 08 A0 B6 07 EB 03 A0 B5 07 32 E4  |  . .. .. .2
320   05 00 07 8B F0 AC 3C 00 74 09 BB 07 00 B4 0E CD  |  ...<.t....
336   10 EB F2 F4 EB FD 2B C9 E4 64 EB 00 24 02 E0 F8  |  .+d.$.
352   24 02 C3 49 6E 76 61 6C 69 64 20 70 61 72 74 69  |  $.Invalid parti
368   74 69 6F 6E 20 74 61 62 6C 65 00 45 72 72 6F 72  |  tion table.Error
384   20 6C 6F 61 64 69 6E 67 20 6F 70 65 72 61 74 69  |   loading operati
400   6E 67 20 73 79 73 74 65 6D 00 4D 69 73 73 69 6E  |  ng system.Missin
416   67 20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74  |  g operating syst
432   65 6D 00 00 00 63 7B 9A D5 0B EB 0D 00 00 00 00  |  em...c{......
448   02 00 EE FF FF FF 01 00 00 00 FF FF FF FF 00 00  |  ...............
464   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
480   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
496   00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA  |  ..............U
###
129/000:29/VEC> Start Verify EPBR Chain for disk 1 (129)
129/000:29/VEC> Listing current partitions on disk:
129/000:29/VEC>  UNKNOWN (P)        (Err)           1  4294967295    (2048 Gb)
129/000:29/VEC> Partition Table info for sector 0 (0 0 1)
129/000:29/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..EE | ....0...0...2 | .1023.255..63 | .........1 | 4294967295
..2 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
129/000:29/VEC> 55AA sig Ok
129/000:29/LOG> Boot sector dump requested at 1 (0 0 2)
### BootSectorDump for BStype FAT16
...........Jump Code (hex): 454649
............OEM Name (txt): PART...
....Bytes per Sector (dec): 23552
.Sectors per Cluster (dec): 0
....Reserved Sectors (dec): 0
...........FAT count (dec): 227
....Root Entry Count (dec): 4294944297
..Total Sectors (16) (dec): 206
....Media Descriptor (hex): 00
.......FAT Size (16) (dec): 0
...Sectors per Track (dec): 1
.....Heads per Track (dec): 0
......Hidden Sectors (dec): 0
..Total Sectors (32) (dec): 1953525167
........Drive Number (hex): 00
............Reserved (hex): 00
......Boot Signature (hex): 00
...........Volume ID (hex): 00002200
........Volume Label (txt): mpt
..Filesystem Type ID (txt):   !)
....Sector Signature (hex): 0000
1st FAT not found at      : 1 (0 0 2)
2nd FAT not found at      : 1 (0 0 2)
129/000:29/CF8> FAT sectors are equal
129/000:29/LOG> SectorDump requested at 1 (0 0 2)
###
     EFI PART... mpt....".. =" mp ...........
     ........... ........... ........... ...........
     ........... ........... ........... ...........
     ........... ........... ........... ...........
###
129/000:29/VEC> Verify EPBR Chain completed
129/000:29/USD> Select disk completed
129/000:43/SCN> DiskScan requested, ScanType is 3
129/000:43/SCN> from 0 (0 0 1) to 1953525167 (121601 80 63), 1953525168 sectors
129/000:43/SCN> Starting QuickScan (vista) at 2048 (0 32 33)
129/000:43/SCN> Next QuickScan location at 616448 (38 94 57)
129/000:44/SCN> Next QuickScan location at 819200 (50 253 12)
129/000:44/SCN> Next QuickScan location at 0 (0 0 1)
129/000:45/SCN> QuickScan finished
129/000:45/SCN> Starting SmartScan (vista) at 0 (0 0 1)
129/000:45/RDS> Read past EOD intercept for disk 129 at 4294967295 (267349 89 4)
129/102:34/SCN> SmartScan finished
129/102:34/SCN> DiskScan completed
129/102:34/SCN> ReadErrors for disk 1 (129): 0
129/104:21/LOG> DataCollection items found: 10 / 4
### DATACOLLECTION, FULL ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL_|_F
001 | 129 | ......2048 | ...NTFS | ..BS | ......2048 | ....614400 | PRI | .
002 | 129 | ....616447 | ...NTFS | .BBS | ......2048 | ....614400 | PRI | .
003 | 129 | ....616454 | ..FAT32 | .BBS | ....616448 | ....202752 | PRI | .
004 | 129 | ....616448 | ..FAT32 | ..BS | ....616448 | ....202752 | PRI | .
005 | 129 | ......2048 | ...NTFS | ..BS | ......2048 | ....614400 | PRI | I
006 | 129 | ....616447 | ...NTFS | .BBS | ......2048 | ....614400 | PRI | I
007 | 129 | ....616448 | ..FAT32 | ..BS | ....616448 | ....202752 | PRI | I
008 | 129 | ....616454 | ..FAT32 | .BBS | ....616448 | ....202752 | PRI | I
009 | 129 | ...1081344 | ...NTFS | ..BS | ...1081344 | 1952442368 | PRI | .
010 | 129 | 1953523711 | ...NTFS | .BBS | ...1081344 | 1952442368 | PRI | .
129/104:21/LOG> DataCollection items found: 10 / 4
### DATACOLLECTION, CLEANED ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL
001 | 129 | ......2048 | ...NTFS | ..BS | ......2048 | ....614400 | PRI
002 | 129 | ....616447 | ...NTFS | .BBS | ......2048 | ....614400 | PRI
003 | 129 | ....616454 | ..FAT32 | .BBS | ....616448 | ....202752 | PRI
004 | 129 | ....616448 | ..FAT32 | ..BS | ....616448 | ....202752 | PRI
009 | 129 | ...1081344 | ...NTFS | ..BS | ...1081344 | 1952442368 | PRI
010 | 129 | 1953523711 | ...NTFS | .BBS | ...1081344 | 1952442368 | PRI
129/104:21/LOG> PartList items created: 3
### PARTLIST ###
SEQ_|____TYPE_|_PTE_|__BS_|_BBS_|F8FF_|___S_|___L_|__PL_|_C_|___R
001 | ...NTFS | ... | ..1 | ..2 | ..0 | ..1 | ..1 | ..1 | 2 | ..A
002 | ..FAT32 | ... | ..4 | ..3 | ... | ..4 | ..4 | ..4 | 2 | ..B
003 | ...NTFS | ... | ..9 | .10 | ..0 | ..9 | ..9 | ..9 | 2 | ..A
### PARTLIST, INTERPRETED ###
SEQ_|____TYPE_|______START_|_____LENGTH_|________END_|__PL_|___R_|___A
001 | ...NTFS | ......2048 | ....614400 | ....616447 | PRI | ..A | ..V
002 | ..FAT32 | ....616448 | ....202752 | ....819199 | PRI | ..B | ..V
003 | ...NTFS | ...1081344 | 1952442368 | 1953523711 | PRI | ..A | ..V
129/104:21/SST> SaveState requested for disk 1 (129)
129/104:21/WAS> AdmiSectors in use : 0+ 1+
129/104:21/SST> SaveState completed for disk 1 (129)
129/104:21/EXE> Analysis complete
129/104:24/LOG> RunTime: 104:24
129/104:24/LOG> ### CLOSE LOG ###


Your advice?
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #7 on: October 31, 2013, 10:18:08 AM »

The SMART diag not finishing is a bad sign, but without details there isn't much I can say about this. You could try a full screen run of the smart tool to see why it doesn't detect any disks. We'll save that for later.

The following procedure will reverse any changes that DiskPatch may have made to that disk. Once you've done this the disk should be as it was before you ran DiskPatch. That means that if this doesn't change anything the cause should be found somewhere else. The boot error message you receive still suggests that this is a BIOS or disk hardware issue, and not a Windows boot issue. But, as I have little experience with EFI/GPT booting in combination with Windows 8 we'll have to keep an open mind.
Follow the steps exactly, and be sure to select the correct disk (the Windows 8 problem disk):

- Start DiskPatch
- Select the correct disk
- Go to "Utilities"
- Go to "Disk Editor", press enter through the undo notification and the "not scanned" info message until you see the disk sector screen
- Press F4 ("goto disk sector")
- Enter "29" (without the quotes)
- You should now see the DiskPatch admi sector, recognizable by the RESERVEDBYDIYDDR string at the bottom right. If you don't see this, abort now
- Press the "Del" key ("wipe the sector"), confirm the action
- Press "Escape" to exit the Disk Editor
- Exit DiskPatch, do not do anything else

That's it. Now test the result.

Edit: we actually do have another thing we can look at if this doesn't help.
Logged

Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #8 on: October 31, 2013, 11:17:31 AM »

One additional question: to boot Windows 8 you must use EFI, to boot DiskPatch you must use the (real mode) BIOS. Sorry if this is obvious, but are you sure you use the correct mode when attempting to boot from that Windows 8 disk?
Logged

ckent1
member

Posts: 24


« Reply #9 on: October 31, 2013, 06:39:32 PM »

Here are some selected results from my Acronis 2014 System Report (attached below):

fdisk.txt says: warning: GPT header CRC is invalid

gdisk.txt says:

GPT fdisk (gdisk) version 0.8.4

Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!

Caution! After loading partitions, the CRC doesn't check out!
Warning! Main partition table CRC mismatch! Loaded backup partition table
instead of main partition table!

Warning! One or more CRCs don't match. You should repair the disk!

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: damaged

****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): D180A221-F129-4CCB-9E8E-3DE7FDC72220
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 3437 sectors (1.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          616447   300.0 MiB   2700  Basic data partition
   2          616448          819199   99.0 MiB    EF00  EFI system partition
   3          819200         1081343   128.0 MiB   0C01  Microsoft reserved part
   4         1081344      1953523711   931.0 GiB   0700  Basic data partition


uefi_vars.txt says:

Boot variables are allowed on this system

***
Could not obtain Boot Entries Enumerator, UEFI is not enabledCould not obtain Boot Order, UEFI is not enabled


I'm not sure how to run a SMART DP scan in full screen. Can you elaborate?

Do you still want me to undo the changes using the DP Disk editor?




[attachment deleted by admin]
Logged
ckent1
member

Posts: 24


« Reply #10 on: October 31, 2013, 07:56:02 PM »

Tom, I deleted the DiskPatch admi sector, RESERVEDBYDIYDDR but still get the same boot error.
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #11 on: October 31, 2013, 08:38:22 PM »

All of this does indeed seem to point in the direction of your original assumption.

Our next thought was to restore the GPT backup, something you should be able to do with the tools you have at hand, it seems. As I personally have no experience with this procedure in combination with the tools you have there I'm not in a good position to advise you at the moment. I'm not sure how knowledgeable you are when it comes to this, but I would say that if you know what you're doing (you seem to have some experience here, and you have the Acronis tools) restoring the GPT backup is the thing to try.

Another approach is fixing the current GPT, in whatever way possible. There are several tools out there (including gdisk, which you seem to have already found) that should allow this, but I'll have to do some testing here before I can give solid advice on this.

We'll look at this from here and see what we can come up with, we should have something within a day or so.

After you deleted that reserved sector with DiskPatch, the situation should be as it was before. Do the GPT checks you ran still give the CRC errors, as shown in the logs above, after your DiskPatch actions?

Note: do not run DiskPatch again; as soon as you start DiskPatch it will recreate that reserved sector. Any further actions should be with GPT aware software, or (if we do need DiskPatch) in forensic mode.
Logged

Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #12 on: October 31, 2013, 09:55:52 PM »

I have done several tests and I can not reproduce the problem. It seems that the EFI itself is not happy with any change to the GPT. Windows doesn't mind (which explains why you could connect the disk to a PC and see the contents without problems).

Do you use the EFI "secure boot" option ?
Logged

ckent1
member

Posts: 24


« Reply #13 on: October 31, 2013, 10:44:08 PM »

Here's the new gdisk.txt after removing DiskPatch admi sector, RESERVEDBYDIYDDR:

GPT fdisk (gdisk) version 0.8.4

Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: damaged

****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): D180A221-F129-4CCB-9E8E-3DE7FDC72220
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 3437 sectors (1.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          616447   300.0 MiB   2700  Basic data partition
   2          616448          819199   99.0 MiB    EF00  EFI system partition
   3          819200         1081343   128.0 MiB   0C01  Microsoft reserved part
   4         1081344      1953523711   931.0 GiB   0700  Basic data partition
GPT fdisk (gdisk) version 0.8.4

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************


Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sdb: 247807 sectors, 121.0 MiB
Logical sector size: 512 bytes
Disk identifier (GUID): A263696A-0507-4995-B11C-09306684BF39
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 247773
Partitions will be aligned on 1-sector boundaries
Total free space is 29 sectors (14.5 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              63          247806   121.0 MiB   0700  Microsoft basic data
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #14 on: October 31, 2013, 11:12:55 PM »

I've been testing Gdisk and it seems it should be pretty simple to repair the original GPT by using the backup. The main GPT is largely okay, the volumes seem correct and valid. The only problem seems to be the header and that can be recovered. Before we attempt this it would be nice to verify the situation, and for that I'd need a few sector dumps. We'll need DiskPatch for that, so make sure to use the earlier mentioned Forensic mode.

Just in case you missed that:
"To use forensic mode, select "DiskPatch Options (troubleshooting)" from the first start menu that appears after booting the DiskPatch boot disk, and select "Start DiskPatch in Forensic Mode". When prompted to select a disk to protect, select the disk you wish to be excluded from any and all writing."

Again, sorry to put you to work like this.

- start DiskPatch in forensic mode, select the correct disk (the win8 problem disk) as the disk to be protected
- from the DiskPatch main menu select "select disk", select the win8 disk
- go to "Utilities", then "Disk Editor"
- once you have the sector screen, press F4 and type 1, press enter
- you are now looking at the GPT header. Press F10 and select "dump sector to log"
- exit the menu (press Escape once)
- press "page down" once, this should put you at the first block of the GPT
- again, press F10 and select "dump sector to log"
- exit the menu and from the sector screen press ctrl-end, this should put you at the very end of the disk looking at the GPT backup header
- again, press F10 and select "dump sector to log"
- exit the menu, press F4 and enter 29
- again, press F10 and select "dump sector to log"
- exit the menu, exit the editor and exit DiskPatch
- post the resulting DP.LOG

Edit: I'm off to bed now but I can tell you that I've successfully restored a GPT after damaging an original GPT in a way similar to your current situation. I've used Gdisk for it and the whole process was pretty self explanatory. I used the Windows version of Gdisk from the author's website.
http://rodsbooks.com/gdisk/
If you like I'll put up an in-depth explanation tomorrow morning.
Logged

Pages: [1] 2 Go Up Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.20 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!