Fixboot & Fixmbr changed my drive from fat32 to fat16 partiton only show 10mb

[dataspinlog]

Thank you.  I did receive the information.  Will you clarify something?  Image recovery, I trust that doesn't mean picture on your pc but only relates to a picture device.

[Joep]

iRecover image recovery mode is specifically tailored to recover photos from a digital camera memory card

[dataspinlog]

Greetings,

Thanks, the irecovery found most of the missing files I needed.  I only wished I used this product first.

Can iRecover read from a source disk and write directly to a destination disk on the fly
without the building process?

For this iRecover process, I increase my memory by adding 512MB memory to 256MB.
What is the best setting? I used 256MB for read and 256MB for write leaving 256MB for irecovery.
is 512MB my working memory since you state 256MB is subtracted from the total memory?

is there a way to create a disaster plan with diskpatch or an automactick disk cloneing processing via network whereby I would always have a complete working backup that would boot without any fuss?

[Joep]

Hello,

Thanks, the irecovery found most of the missing files I needed.  I only wished I used this product first.

Did you scan the original disk or the cloned disk?

Can iRecover read from a source disk and write directly to a destination disk on the fly
without the building process?

I don't understand the question. For recovering files, iRecover needs to scan a disk first.

For this iRecover process, I increase my memory by adding 512MB memory to 256MB.
What is the best setting? I used 256MB for read and 256MB for write leaving 256MB for irecovery.
is 512MB my working memory since you state 256MB is subtracted from the total memory?

More memory is better. The more files iRecover detects, the more memory it requires. Regarding settings: I assume you refer to the settings on the runtime panel, best leave those as they are. They will only be benificial in specific scenarios (such as recovering from a USB device).

[dataspinlog]

I scanned the cloned disk but I'm thinking I should do the original disk.  I then would get more files possibly.

iRecover needs to scan a disk first.

I was attempting to adk can iRecovery do a read/write on the fly similare to copy paste direct to the destination disk?

More memory is better. The more files iRecover detects, the more memory it requires. Regarding settings: I assume you refer to the settings on the runtime panel, best leave those as they are. They will only be benificial in specific scenarios (such as recovering from a USB device).

wow! I just wondering if increasing the setting would increase the speed of the read or writing process.

is there a way to create a disaster plan with diskpatch or an automactick disk cloneing processing via network whereby I would always have a complete working backup that would boot without any fuss?

[Tom]

is there a way to create a disaster plan with diskpatch or an automactick disk cloneing processing via network whereby I would always have a complete working backup that would boot without any fuss?

No, not as such. You'll have to think of other ways to do that. And it's not really our place to advice; we're here for recovery, not prevention.

can iRecovery do a read/write on the fly similare to copy paste direct to the destination disk?

No.

About that scanning the original disk/ "I wish I used this first":
The original disk is in a bad state, there's no guarantee that scanning that disk won't kill it, or even allow you to copy files from it. iRecover can handle bad sectors, and in reality you would probably get files from it, but in general the route you followed now (clone first, then work with the clone) is the best way to go. What you COULD do is, now that you have most of your stuff back, do an iRecover scan of the original disk: you have the clone and you have already recovered most, so a run on the original bad disk may yield a few more files than you already have. But, it can also damage the disk even further. In the end that's up to you.

[dataspinlog]

we're here for recovery, not prevention.

I guess this is a fine line because once a data recover process has began and you have a backup, IMHO, prevention has started.

I cloned the failing 20GB to the 80GB and then cloned the 80GB to the 120GB.  
Being that at the end of the day I would like the 80GB HDD to be my working drive and the 120GB to be my cloning HDD, is so I will always have a larger drive to use for cloning.

So as soon as I get my partition strategy thought out for the 80GB and OS installed i will do iRecover on the original failing 20GB HDD.

what be the best iRecover settings to use on the original 20GB HDD?

[Tom]

I guess this is a fine line because once a data recover process has began and you have a backup, IMHO, prevention has started.

?

From the manual:

"Timeout" - set to 200 ms unless doing RAID recovery.
"Retry attempts" - set to 1 unless the analysis is unacceptably slow. To increase speed, set to 0.
"Avoid repeated retries" - enable.
"Skip factor" - set to 32, unless the analysis is unacceptably slow. To increase speed, gradually increase "Skip factor" until satisfactory speed is achieved.

I myself would go with a sector skip size that equals the cluster size, to start with. Or perhaps even lower, to sort of try to catch as many reads as possible. Say 8 or 4 or so. If that causes severe slowdown, increase the value.

[dataspinlog]

thanks for your reply. 

I will used your suggestions.

In previous post you all advised my 60GB HDD was not a good option for cloning so i used the 80GB HDD.  I now have the 60GB in another machine(AMD w/389MB memory) running WinXp home and its booting and operating ok. 

Since I got most of the data back, I'm not worried too much about time at this moment.  As before I had no data to work with and was in panic mode.

Would I be taking a risk attaching my failing 20GB HDD as a slave to the 60GB and using iRecover to recover my file from the 20GB to the 60GB?

Does making the 20GB a slave to the 60GB in another type machine change any settings or data  concerning the recovery of my data using iRecover?

Since, with your help, determining the 80GB is a good HDD and the Dell is a faster machine, I realize I really need to use that machine for work and not tie it up doing recovery tasks.

your guidance is greatly appreciated.  thank you.

[Tom]

Would I be taking a risk attaching my failing 20GB HDD as a slave to the 60GB and using iRecover to recover my file from the 20GB to the 60GB?

I don't see how.

Does making the 20GB a slave to the 60GB in another type machine change any settings or data  concerning the recovery of my data using iRecover?

No.

[dataspinlog]

Thanks you. 

This is something to think about...a disk that isn't good enough for use as a cloning destination HDD is good enough for use as a destination file recovery HDD when using iRecover.  Interesting...

This experience has been an eye opener.

[Joep]

Hello,

The 'no risk' thing was an 'in general remark': you do not put a disk at risk by copying data to it using iRecover. You have posted so many logs over the past period that you mentioning your 60 GB disk didn't make us immediately realize that was disk with bad smart numbers.

What I said for this disk still stands:

The Hard Disk "Model ID  . . . . . . . . . . : WDC WD600JB-00CRA1" is not a real good shape even though the disk manufacturer set tresholds are not yet in sight. It has reallocated sectors in the past. if this were my disk I'd back it up and test it. If the test doesn't show new problems I'd definitely monitor this disk with some like HD Sentinel. If it's condition appears stable then there is probably no need for alarm.

if the WDC WD600JB-00CRA1 does not reveal problems during a read-only surface scan (you can do that with the DiskPatch trial) it can be used as well.

[dataspinlog]

Thanks.  This process has been a journey.

You have posted so many logs over the past period that you mentioning your 60 GB disk didn't make us immediately realize that was disk with bad smart numbers.

yes, this is the same 60GB HDD that I started with at the beginning of this data rescue journey.

I'd definitely monitor this disk with some like HD Sentinel.

I did look at HD Sentinel when you mention it but I had the 80GB HDD as an option and I put the 60GB to the side.  And now that things are coming together and I have most of my data, I will take a look again at HD Sentinel.

if the WDC WD600JB-00CRA1 does not reveal problems during a read-only surface scan (you can do that with the DiskPatch trial) it can be used as well.

I will do a read-only surface scan test on the 60GB and post the results.  If all is good, move forward with using HD Sentinel for the monitoring of the HDD. and if monitoring is good and stable, move forward with the iRecover for the files.  Do I have the plan correct?

[dataspinlog]

60GB HDD installed on an AMD computer

.../000:05/LOG> ### LOG START ###
.../000:05/LOG> DISKPATCH 3.5.300
.../000:05/LOG> (C) 2000-2009 DIY DataRecovery
.../000:05/LOG> Contact info: http://HTTP://www.DIYDataRecovery.nl
.../000:05/LOG> MemFree: 74Kb
.../000:05/LOG> CommandLineParms:
.../000:05/LOG> LogDate: 03-26-2010
.../000:05/CFG> FilePath="A:DPFILES\"
.../000:05/CFG> ReadRetries="0"
.../000:05/CFG> WriteRetries="32"
.../000:05/CFG> MaxReadErrors="32"
.../000:05/CFG> MaxWriteErrors="1"
.../000:05/CFG> LogEachReadError="1"
.../000:05/CFG> ReadDelay="0"
.../000:05/CFG> VfyFixedBadSect="1"
.../000:05/CFG> CleanAfterDOD="1"
.../000:05/CFG> DiskReset="0"
.../000:05/CFG> SectorSkip="8"
.../000:05/CFG> AutoSaveState="1"
.../000:05/CFG> DumpFoundSectors="0"
.../000:05/CFG> FixFats="1"
.../000:05/CFG> MaxFatScan="51200"
.../000:05/CFG> MaxDataColEntries="256"
.../000:05/CFG> IgnoreF8FF="0"
.../000:05/CFG> DownSizeExt="1"
.../000:05/CFG> ScanSignature="55AA"
.../000:05/CFG> Rebuild="00"
.../000:05/13H> Ext13H installed test requested
.../000:05/13H> Disk found at 128
.../000:05/13H> Ext13H version: 2.1 / EDD-1.1
.../000:05/13H> Ext13H Support: Extended disk access functions
.../000:05/13H> Ext13H Support: Enhanced disk drive functions
.../000:05/13H> Ext13H Flags: Cylinder/head/sector info is valid
.../000:05/13H> Drive Interface Info:
.../000:05/13H> Disk 128 X13H data : 7297/255/63 117226305/512
.../000:05/13H> Ext13H tested ok
.../000:05/FDL> DiskList requested
.../000:05/FDL> Disk found at 128
### DISKLIST.ARRAY ###
__D_|________LBA_|___H_|__S_|__GB_|__GEO
128 | .117226305 | 255 | 63 | .55 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
.../000:05/IAS> AdmiSector found on disk 0 (128)
.../000:06/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:06/WAS> AdmiSectors in use : 0+
.../000:07/KEY> 1812O9O197/4
.../000:07/PFC> PQstuff signature not detected on disk 0 (128)
.../000:07/PFC> UDMA driver not loaded
.../000:07/PFC> Disk health 1-50
.../000:09/PFC> Partition State backup not found on disk 0 (128)
.../000:09/PFC> No Repair date found on disk 0 (128)
.../000:20/MNU> - Main, Select Disk
.../000:27/CSD> Start CheckDisk for disk 0 (128)
.../000:27/CSD> CheckDisk complete, ReadErrors 0
.../000:27/USD> Disk 0 (128) selected
.../000:27/GSC> Geo for disk 0 (128) changed since last DP run
.../000:27/GSC> Geo info on disk 0 (128) (old)   : 0117231408255063
.../000:27/GSC> Current geo info for disk 0 (128): 0117226305255063
.../000:39/GSC> Selected geo for disk 0 (128) is 255/63
.../000:39/WAS> AdmiSectors in use : 0+
128/000:39/USD> MBR for disk 0 (128)
128/000:39/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  |  ??>?}U?t.?~..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??.??B??9V
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.`??U?A?
240   13 72 36 81 FB 55 AA 75 30 F6 C1 01 74 2B 61 60  |  .r6??U?u0??.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  |  2??V.?.??a??Inva
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 CA 16 CB 16 00 00 80 01  |  .....,Dc?.?...?.
448   01 00 07 FE FF FF 3F 00 00 00 41 7C FC 06 00 00  |  ...?..?...A|?...
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?
###
128/000:40/VEC> Start Verify EPBR Chain for disk 0 (128)
128/000:40/VEC> Listing current partitions on disk:
128/000:40/VEC>     NTFS (P)    (no name)          63   117210177      (56 Gb)
128/000:40/VEC> Partition Table info for sector 0 (0 0 1)
128/000:40/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 .128 | ..07 | ....0...1...1 | .1023.254..63 | ........63 | .117210177
..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
128/000:40/VEC> 55AA sig Ok
128/000:40/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): 255
......Hidden Sectors (dec): 63
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 117210176
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 7325636
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): FA58BA3958B9F50B
........Volume Label (txt): (no name)
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
128/000:41/VEC> BS and BBS equal
128/000:41/VEC> Verify EPBR Chain completed
128/000:41/USD> Select disk completed
128/001:08/MNU> - Main, Disk Ops
128/001:11/MNU> - Disk Ops, Surface Scan (RO)
128/001:27/SUR> Start RO Surface Scan, from 63 to 117210239
128/001:27/SUR> Read/Write Errors reset; Read/Write Errors until now : 0/0
128/154:26/SUR> Surface Scan completed
128/166:03/SUR> Surface Scan end, R/W Errors/Reallocated is 0/0/0
128/168:03/MNU> - Main, Utilities
128/168:49/MNU> - Main, Options
128/168:56/MNU> - Main, Utilities
128/169:04/MNU> - Main, Disk Ops
128/169:10/MNU> - Main, Repairs
128/169:35/MNU> - Main, Quit
128/169:35/LOG> RunTime: 169:35
128/169:35/LOG> ### CLOSE LOG ###



Detected Controllers

  Disk Controller 1
    Device Vendor . . . . . . . . . . . . . : 1022
    Device ID . . . . . . . . . . . . . . . : 7409
    Device Location . . . . . . . . . . . . : Bus 0, Device 7, Function 1
    Device Ports  . . . . . . . . . . . . . : F000-F00F

Physical Disk Information - Disk: #0

  Hard Disk Summary
    Hard Disk Number  . . . . . . . . . . . : 0
    Interface . . . . . . . . . . . . . . . : IDE/ATA
    Connection  . . . . . . . . . . . . . . : PM
    Hard Disk Model ID  . . . . . . . . . . : WDC WD600JB-00CRA1
    Hard Disk Revision  . . . . . . . . . . : 17.07W17
    Hard Disk Serial Number . . . . . . . . : WD-WMA8F2603958
    Hard Disk Total Size  . . . . . . . . . : 67080 MB
    Current Temperature:  . . . . . . . . . : ?
    Power on time . . . . . . . . . . . . . : 467 days, 0 hours
    Health: . . . . . . . . . . . . . . . . : 21 %
    Performance:  . . . . . . . . . . . . . : 90 %

  ATA Information
    Hard Disk Cylinders . . . . . . . . . . : 28733
    Hard Disk Heads . . . . . . . . . . . . : 16
    Hard Disk Sectors . . . . . . . . . . . : 255
    Total Sectors . . . . . . . . . . . . . : 117231408
    ATA Revision  . . . . . . . . . . . . . : 5
    Bytes Per Sector  . . . . . . . . . . . : 600
    Buffer Size . . . . . . . . . . . . . . : 8192 KB
    Multiple Sectors  . . . . . . . . . . . : 16
    Error Correction Bytes  . . . . . . . . : 40
    Unformatted Capacity  . . . . . . . . . : 67080 MB
    Maximum PIO Mode  . . . . . . . . . . . : 4
    Maximum Multiword DMA Mode  . . . . . . : 2
    Maximum UDMA Mode . . . . . . . . . . . : 100 MB/s (5)
    Active UDMA Mode  . . . . . . . . . . . : 66 MB/s (4)
    Minimum multiword DMA transfer time . . : 120 ns
    Recommended multiword DMA transfer time : 120 ns
    Minimum PIO transfer time without IORDY : 120 ns
    Minimum PIO transfer time with IORDY  . : 120 ns
    ATA Control Byte  . . . . . . . . . . . : Valid

  Acoustic Management Configuration
    Acoustic Management . . . . . . . . . . : Supported
    Acoustic Management . . . . . . . . . . : Enabled
    Current Acoustic Level  . . . . . . . . : Max performance and volume (FEh)
    Recommended Acoustic Level  . . . . . . : Min performance and volume (80h)

  EIDE Properties
    Read Ahead Buffer . . . . . . . . . . . : Supported
    DMA . . . . . . . . . . . . . . . . . . : Supported
    Ultra DMA . . . . . . . . . . . . . . . : Supported
    S.M.A.R.T.  . . . . . . . . . . . . . . : Supported
    Power Management  . . . . . . . . . . . : Supported
    Write Cache . . . . . . . . . . . . . . : Supported
    Host Protected Area . . . . . . . . . . : Supported
    Advanced Power Management . . . . . . . : Not Supported
    Power Up In Standby . . . . . . . . . . : Not Supported
    48-bit LBA Addressing . . . . . . . . . : Not Supported
    Device Configuration Overlay  . . . . . : Supported
    IORDY Support . . . . . . . . . . . . . : Supported
    Read/Write DMA Queue  . . . . . . . . . : Not Supported
    NOP Command . . . . . . . . . . . . . . : Not Supported
    Trusted Computing . . . . . . . . . . . : Not Supported
    64-bit World Wide ID  . . . . . . . . . : Not Supported
    Streaming . . . . . . . . . . . . . . . : Not Supported
    Media Card Pass Through . . . . . . . . : Not Supported
    General Purpose Logging . . . . . . . . : Not Supported
    Error Logging . . . . . . . . . . . . . : Supported
    CFA Feature Set . . . . . . . . . . . . : Not Supported
    Long Physical Sectors (1) . . . . . . . : Not Supported
    Long Logical Sectors  . . . . . . . . . : Not Supported
    Write-Read-Verify . . . . . . . . . . . : Not Supported
    NV Cache Feature  . . . . . . . . . . . : Not Supported
    NV Cache Power Mode . . . . . . . . . . : Not Supported

  S.M.A.R.T. Details
    Off-line data collection  . . . . . . . : Suspended by interrupting command from host
    Self test execution status  . . . . . . : Succesfully completed
    Total time to complete off-line data ...: 2340 seconds
    Execute off-line immediate  . . . . . . : Supported
    Abort/restart off-line by host  . . . . : Not Supported
    Off-line read scanning  . . . . . . . . : Supported
    Short Self-test . . . . . . . . . . . . : Supported
    Extended Self-test  . . . . . . . . . . : Supported
    Conveyance self-test  . . . . . . . . . : Supported
    Selective self-test . . . . . . . . . . : Not Supported
    Save data before/after power saving mode: Supported
    Enable/Disable attribute autosave . . . : Supported
    Error logging capability  . . . . . . . : Supported
    Short self-test estimated time  . . . . : 2 minutes
    Extended self-test estimated time . . . : 43 minutes
    Conveyance self-test estimated time . . : 5 minutes

  Security Mode
    Security Mode . . . . . . . . . . . . . : Supported
    Security Erase  . . . . . . . . . . . . : Not Supported
    Security Erase Time . . . . . . . . . . : Not Supported
    Security Enhanced Erase Feature . . . . : Not Supported
    Security Enhanced Erase Time  . . . . . : Not Supported
    Security Enabled  . . . . . . . . . . . : No
    Security Locked . . . . . . . . . . . . : No
    Security Frozen . . . . . . . . . . . . : No
    Security Counter Expired  . . . . . . . : No
    Security Level  . . . . . . . . . . . . : High

  Serial ATA Features
    S-ATA Compliance  . . . . . . . . . . . : No
    S-ATA I Signaling Speed (1.5 Gps) . . . : Not Supported
    S-ATA II Signaling Speed (3 Gps)  . . . : Not Supported
    Receipt Of Power Management Requests ...: Not Supported
    PHY Event Counters  . . . . . . . . . . : Not Supported
    Non-Zero Buffer Offsets In DMA Setup FIS: Not Supported
    DMA Setup Auto-Activate Optimization  . : Not Supported
    Device Initiating Interface Power Man...: Not Supported
    In-Order Data Delivery  . . . . . . . . : Not Supported
    Asynchronous Notification . . . . . . . : Not Supported
    Software Settings Preservation  . . . . : Not Supported
    Native Command Queuing  . . . . . . . . : Not Supported
    Queue Length  . . . . . . . . . . . . . : Not Supported

  S.M.A.R.T.
    1  : Raw Read Error Rate            Threshold=51  Value=200 Worst=199 Data=000000000000 Status=OK                        Flags=Error-rate, Statistical, Critical
    3  : Spin Up Time                   Threshold=21  Value=100 Worst=93  Data=000000000FFB Status=OK                        Flags=Performance, Statistical, Critical
    4  : Start/Stop Count               Threshold=40  Value=99  Worst=99  Data=000000000787 Status=OK                        Flags=Self Preserving, Event Count, Statistical
    5  : Reallocated Sectors Count      Threshold=140 Value=193 Worst=193 Data=000000000067 Status=OK                        Flags=Self Preserving, Event Count, Statistical, Critical
    7  : Seek Error Rate                Threshold=51  Value=200 Worst=200 Data=000000000000 Status=OK                        Flags=Error-rate, Statistical, Critical
    9  : Power-On Time Count            Threshold=0   Value=85  Worst=85  Data=000000002BC8 Status=OK (Always passing)       Flags=Self Preserving, Event Count, Statistical
    10 : Spin Retry Count               Threshold=51  Value=100 Worst=100 Data=000000000000 Status=OK                        Flags=Event Count, Statistical, Critical
    11 : Drive Calibration Retry Count  Threshold=51  Value=100 Worst=100 Data=000000000000 Status=OK                        Flags=Event Count, Statistical, Critical
    12 : Drive Power Cycle Count        Threshold=0   Value=99  Worst=99  Data=0000000005BA Status=OK (Always passing)       Flags=Self Preserving, Event Count, Statistical
    196: Reallocation Event Count       Threshold=0   Value=165 Worst=165 Data=000000000023 Status=OK (Always passing)       Flags=Self Preserving, Event Count, Statistical
    197: Current Pending Sector Count   Threshold=0   Value=200 Worst=200 Data=000000000000 Status=OK (Always passing)       Flags=Event Count, Statistical
    198: Off-Line Uncorrectable Sect... Threshold=0   Value=200 Worst=200 Data=000000000000 Status=OK (Always passing)       Flags=Event Count, Statistical
    199: Ultra ATA CRC Error Count      Threshold=0   Value=200 Worst=253 Data=000000000000 Status=OK (Always passing)       Flags=Error-rate, Statistical
    200: Write Error Rate               Threshold=51  Value=200 Worst=192 Data=000000000000 Status=OK                        Flags=Error-rate, Critical

I'm surprised in some changes between a dell machine and an AMD machine.

your recommendations please, thank you

[Joep]

Hello,

Changes? To be bluntly honest I do not feel like going over all those logs again. For as little as 40 Euros you can have a brand new internal or external hard disk where iRecover can copy data to.