Welcome, Guest. Please login or register.
Did you miss your activation email?
June 20, 2019, 07:30:12 AM
Home Help Search Login Register
News:

+  DIY DataRecovery.nl Support forum
|-+  Recent Posts
Pages: [1] 2 3 ... 10

 1 
 on: May 17, 2019, 07:09:55 AM 
Started by MASTER260 - Last post by Joep
Hello,

can you tell me which version you used, so what download URL? Did you run a setup or the stand lone version?

 2 
 on: May 17, 2019, 05:56:12 AM 
Started by MASTER260 - Last post by MASTER260
Hi.  Whenever I try to recover my files, it says thread creation error.  FYI, the scan's progress bar never got past half way, so the files I tried to recover were after I pressed cancel, but, still.

Please help.

Thanks,
M260.


EDIT: nvm, I chose quick scan instead of long scan, and the progress bar actually completed and I could recover my files.

 3 
 on: March 26, 2019, 08:06:29 AM 
Started by ocotillo - Last post by ocotillo
First of all thank you for answering the doubt and if you think it is better to move the post, up to you.

I try to fix with iRecover and I will update de post.

Best regards.

 4 
 on: March 23, 2019, 04:21:47 PM 
Started by ocotillo - Last post by Joep
Added to that, DiskPatch sees 3 1 TB or so disks which I assume are your array members. Since we see the separate disks rather than the entire array as one unit, the RAID is not active at this level.

 5 
 on: March 23, 2019, 02:06:54 PM 
Started by ocotillo - Last post by Tom
Without more details it is hard to offer advice but in general you should not use DiskPatch to fix this particular problem. DiskPatch will not deal with EFI RAID setups very well so your best bet would be iRecover.

 6 
 on: March 22, 2019, 01:16:22 PM 
Started by ocotillo - Last post by ocotillo
Dear all,

I am trying to fix RAID 5, with 3 disks.

First of all, I download the last version of DiskPatch, I create the USB, restart the computer and when DiskPatch starts, a text saying "EFI / GUID partition type encountered" appear and don't let continue.

I run the test and this is the ressult:


.../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: 2Kb
.../000:01/LOG> CommandLineParms: /sup
.../000:01/LOG> LogDate: 03-22-2019
.../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 : 1022/235/63 15138816/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> Ext13H Flags: DMA boundary errors handled transparently
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 129 X13H data : 56065/255/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> Ext13H Flags: DMA boundary errors handled transparently
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 130 X13H data : 56065/255/63 1953525168/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> Ext13H Flags: DMA boundary errors handled transparently
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 131 X13H data : 56065/255/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
.../000:01/FDL> Disk found at 130
.../000:01/FDL> Disk found at 131
### DISKLIST ###
__D_|________LBA_|___H_|__S_|___GB_|__GEO_|___SS_
128 | ..15138816 | 255 | 63 | ...7 | FIXD | .512
129 | 1953525168 | 255 | 63 | .931 | BIOS | .512
130 | 1953525168 | 255 | 63 | .931 | BIOS | .512
131 | 1953525168 | 255 | 63 | .931 | BIOS | .512
.../000:01/EXE> !- EFI BIOS / GUID partition type found on disk 2 (130)
.../000:01/EXE> !- EFI BIOS / GUID partition type found on disk 3 (131)
.../000:03/IAS> AdmiSector found on disk 0 (128)
.../000:03/IAS> AdmiSector found on disk 1 (129)
.../000:03/IAS> AdmiSector found on disk 2 (130)
.../000:03/IAS> AdmiSector found on disk 3 (131)
.../000:03/KEY> DEMO/1

The threr disks that I want to recover are 129, 130 and 131 but I don't know that is possible to continue.

Could you give some information and if it is possible to recover the information?

Best regards!!!


 7 
 on: January 11, 2019, 09:06:09 PM 
Started by mlepottier - Last post by mlepottier
Ah, thanks for the reply.  So it sounds like I'm up the proverbial creek.

I will try DDrescue first and failing that the irecover method. 

Thanks for your help.

 8 
 on: January 11, 2019, 07:47:53 PM 
Started by mnsnownutt - Last post by Tom
Sorry:

http://www.diydatarecovery.nl/downloads/Demo/DiskPatchX_Setup.exe

 9 
 on: January 11, 2019, 07:46:34 PM 
Started by mlepottier - Last post by Tom
DiskPatch, because of its age, doesn't deal with disks larger than 2Tb, so cloning this disk with DiskPatch is not a very good idea. Also, the error (and the large amount of them) indicates that the disk is in a pretty bad state. Getting a full clone for this one seems unlikely, but if you have no options (as in, no backup) I suppose you could try something like ddrescue (linux open source tool), which can be found on the "systemrescuecd" (google it, you'll find it easy enough). This will require some studying but is likely to give you a better shot than DiskPatch.
Another way to go is to create an image of the problem disk (with our iRecover) and then try to lift data from that image (also with iRecover).
Some NAS systems use a proprietary storage format, or a Linux storage format, so that too may be a hurdle. I don't know off-hand how WD does this.

 10 
 on: January 11, 2019, 07:35:49 PM 
Started by mnsnownutt - Last post by mnsnownutt
What version?  Nothing linked in your response. 

Pages: [1] 2 3 ... 10


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!