Welcome, Guest. Please login or register.
Did you miss your activation email?
June 20, 2019, 03:38:34 PM
Home Help Search Login Register
News: For support on DIY DataRecovery.nl products visit www.disktuna.com

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  DiskPatch (Moderators: Tom, Joep)
| | |-+  EFI BIOS DiskPatch startup problem
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: EFI BIOS DiskPatch startup problem  (Read 11183 times)
alwing
member

Posts: 10


« on: December 02, 2013, 06:58:25 PM »

Started DiskPatch from USB stick - immediately after starting got error message "EFI BIOS/GUID partition type found, continuing may corrupt disk structure. Continue?" I didn't.

Can you shed any light on this?

The disk I was hoping to analyse/fix is an external USB drive. This is a drive which I had erroneously begun to start using as a recovery drive, before I realised that Windows was doing something I didn't want it to.
Logged
alwing
member

Posts: 10


« Reply #1 on: December 02, 2013, 07:02:45 PM »

Sorry I posted this as a new topic before seeing the same problem further down the topic list. I will read that and see what the outcome was.
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #2 on: December 02, 2013, 08:31:39 PM »

First, make sure you have the latest DiskPatch before continuing. The latest version has a fix that prevents actual data loss in certain rare cases.
Could you post the dp.log file you have? That should allow me to see what's going on.
Logged

alwing
member

Posts: 10


« Reply #3 on: December 03, 2013, 08:59:49 AM »


.../000:01/LOG> ### LOG START ###
.../000:01/LOG> DISKPATCH 4.0.300
.../000:01/LOG> (C) 2000-2013 DIY DataRecovery
.../000:01/LOG> Contact info: www.DIYDataRecovery.nl
.../000:01/LOG> MemFree: 57Kb
.../000:01/LOG> CommandLineParms:
.../000:01/LOG> LogDate: 12-02-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 120999936/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 234441648/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: Cylinder/head/sector info is valid
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 130 X13H data : 16383/16/63 976773168/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 | .120999936 | .16 | 63 | ..57 | BIOS | .512
129 | .234441648 | 255 | 63 | .111 | BIOS | .512
130 | .976773168 | 255 | 63 | .465 | BIOS | .512
..0 | .........0 | ..0 | .0 | ...0 | BIOS | ...0
.../000:01/RDS> ReadError for disk 129 at 0 (0 0 1), C:1, T:80h (Timeout)
.../000:22/EXE> !- EFI BIOS / GUID partition type found on disk 2 (130)
.../000:24/LOG> RunTime: 000:24
.../000:24/LOG> ### CLOSE LOG ###

Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #4 on: December 03, 2013, 10:13:55 AM »

The EFI warning is for the 465Gb disk, is that the disk you need to fix?

Also, there is a read error on disk 129, the 111Gb disk. That is serious so please also create a health report:
http://www.diydatarecovery.nl/dp_manual/guide_smartcheck.htm

Can you tell a bit more about what went wrong, and what the problems are that are now occurring (please include error messages and say for which disk the problem exists) ?
Logged

alwing
member

Posts: 10


« Reply #5 on: December 04, 2013, 11:07:29 AM »

Problem drive is 111GB and is a portable USB drive.
Problem started when I wanted to create a recovery drive for my laptop. I thought I could do this by creating a second partition on the USB drive and using that as the location for the recovery data. I shrunk the already existing partition to around 80GB, leaving the rest for recovery.
I only realised my error when Windows started writing to the drive and not to the partition I had created and pointed it to. I cancelled the recovery creation process, but too late.
I now have, it seems, two partitions on the drive one with the Windows created bootable recovery format (around 30GB) and the other labelled as free space (around 80GB). However, the 80GB appears to have at least some of my original data in it, but I cannot access it.
I scanned the partition with another piece of software and it showed a list of some of my files that could apparently be recovered, but I did not take any further action than that.

I did a smart scan, but I'm not sure it has done the right drive, because I connected the drive after I had booted from the DiskPatch bootable USB stick. I did this as I didn't want the machine to boot from the USB drive:

Detected Controllers

  Disk Controller 1
    Device Vendor . . . . . . . . . . . . . : 8086
    Device ID . . . . . . . . . . . . . . . : 1E03
    Device  . . . . . . . . . . . . . . . . : Intel
    Device Location . . . . . . . . . . . . : Bus 0, Device 31, Function 2
    Device Ports  . . . . . . . . . . . . . : 3088-308F, 3094-3097, 3080-3087, 3090-3093, 3060-307F

Let me know if I need to do this again.

Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #6 on: December 04, 2013, 01:03:16 PM »

Hmm, not good.
The problem drive has damaged data structures (because of the shrinking/overwriting) AND there are read problems. Because we can not tell how bad the disk's health is it's tricky to give detailed advice, but you basically have 2 options:
1. repairing will not happen, given what happened to the disk. All you can hope for is getting the data from the disk. Use iRecover to copy data from the disk (iRecover can handle read errors).
2. if the contents of the disk are very important you should consider cloning the disk first, to deal with the read error problem. You can then work with the cloned disk, recovering the data (you'll need iRecover for this, again).
Logged

alwing
member

Posts: 10


« Reply #7 on: December 04, 2013, 02:37:11 PM »

I'm sure I tried irecover at somepoint before, but I'll give it a go.
Logged
alwing
member

Posts: 10


« Reply #8 on: December 05, 2013, 07:45:07 PM »

I purchased the latest version(thanks for the discount) and ran irecover. It has recovered a large number of files,but there were quite a few more that are corrupted. I take it that if the file icon is red then there is no chance of recovery?

Thanks for your help, it is very much appreciated.
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #9 on: December 05, 2013, 09:12:16 PM »

Well, no. The red icon means that the file could not be validated, so the chances of recovery are less than good. It's just an indication, to get a quick idea of the situation. It's always best to recover as much as possible and then sort through the resulting files.
In all, some 'red icons' are to be expected in your scenario.
Logged

Pages: [1] 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!