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

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  DiskPatch (Moderators: Tom, Joep)
| | |-+  Trying to recover data from second drive
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] 2 Go Down Print
Author Topic: Trying to recover data from second drive  (Read 23010 times)
kasie23
member

Posts: 16


« on: January 19, 2011, 05:04:24 AM »

The second drive in my system became corrupt somehow and so Windows (XP) said a CHKDSK should be done. At the same time Explorer (not IE) was hanging a lot and I had to do a number of reboots.  Unfortunately on one of those I didn't cancel the scan disk and it went after my second drive. After taking a very long time it basically said there was a problem with the MFT and most of the sectors were unreadable.  Then it hung.

I downloaded the trial version of DiskPatch to see if I could repair the MFT and get to the files (the drive is listed a 'raw').  DP indicated the drive to be unhealthy.  Below is the DP Log.  Is there any hope?


.../000:02/LOG> ### LOG START ###
.../000:02/LOG> DISKPATCH 3.5.300
.../000:02/LOG> (C) 2000-2009 DIY DataRecovery
.../000:02/LOG> Contact info: http://HTTP://www.DIYDataRecovery.nl
.../000:02/LOG> MemFree: 74Kb
.../000:02/LOG> CommandLineParms: /sup
.../000:02/LOG> LogDate: 01-18-2011
.../000:02/CFG> FilePath="A:DPFILES\"
.../000:02/CFG> ReadRetries="32"
.../000:02/CFG> WriteRetries="32"
.../000:02/CFG> MaxReadErrors="32"
.../000:02/CFG> MaxWriteErrors="1"
.../000:02/CFG> LogEachReadError="1"
.../000:02/CFG> ReadDelay="0"
.../000:02/CFG> VfyFixedBadSect="1"
.../000:02/CFG> CleanAfterDOD="1"
.../000:02/CFG> DiskReset="1"
.../000:02/CFG> SectorSkip="1024"
.../000:02/CFG> AutoSaveState="1"
.../000:02/CFG> DumpFoundSectors="0"
.../000:02/CFG> FixFats="1"
.../000:02/CFG> MaxFatScan="51200"
.../000:02/CFG> MaxDataColEntries="256"
.../000:02/CFG> IgnoreF8FF="0"
.../000:02/CFG> DownSizeExt="1"
.../000:02/CFG> ScanSignature="55AA"
.../000:02/CFG> Rebuild="00"
.../000:02/13H> Ext13H installed test requested
.../000:02/13H> Disk found at 128
.../000:02/13H> Ext13H version: 2.1 / EDD-1.1
.../000:02/13H> Ext13H Support: Extended disk access functions
.../000:02/13H> Ext13H Support: Enhanced disk drive functions
.../000:02/13H> Ext13H Flags: DMA boundary errors handled transparently
.../000:02/13H> Drive Interface Info:
.../000:02/13H> Disk 128 X13H data : 16383/16/63 234375000/512
.../000:02/13H> Disk found at 129
.../000:02/13H> Ext13H version: 2.1 / EDD-1.1
.../000:02/13H> Ext13H Support: Extended disk access functions
.../000:02/13H> Ext13H Support: Enhanced disk drive functions
.../000:02/13H> Ext13H Flags: DMA boundary errors handled transparently
.../000:02/13H> Drive Interface Info:
.../000:02/13H> Disk 129 X13H data : 16383/16/63 488397168/512
.../000:02/13H> Ext13H tested ok
.../000:02/FDL> DiskList requested
.../000:02/FDL> Disk found at 128
.../000:02/FDL> Disk found at 129
### DISKLIST.ARRAY ###
__D_|________LBA_|___H_|__S_|__GB_|__GEO
128 | .234375000 | 255 | 63 | 111 | BIOS
129 | .488397168 | 255 | 63 | 232 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
.../000:02/IAS> AdmiSector found on disk 0 (128)
.../000:02/IAS> AdmiSector found on disk 1 (129)
.../000:03/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:03/EXE> Read/Write pattern test for disk 1 (129) successful
.../000:03/WAS> AdmiSectors in use : 0+ 1+
.../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:04/PFC> UDMA driver not loaded
.../000:04/PFC> Disk health 1-50
.../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> No Repair date found on disk 0 (128)
.../000:05/PFC> No Repair date found on disk 1 (129)
.../000:31/CSD> Start CheckDisk for disk 1 (129)
.../000:31/CSD> CheckDisk complete, ReadErrors 0
.../000:31/USD> Disk 1 (129) selected
.../000:32/GSC> No geo change detected for disk 1 (129)
.../000:32/WAS> AdmiSectors in use : 0+ 1+
129/000:32/USD> MBR for disk 1 (129)
129/000:32/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 9B 09 12 D5 00 00 00 01  |  .....,Dc......
448   01 00 07 FE FF FF 3F 00 00 00 42 45 1C 1D 00 00  |  .....?...BE....
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:33/VEC> Start Verify EPBR Chain for disk 1 (129)
129/000:33/VEC> Listing current partitions on disk:
129/000:37/RDS> ReadError for disk 129 at 6291525 (391 160 31), C:1, T:80h
129/002:35/VEC>     NTFS (P)                       63   488392002     (233 Gb)
129/002:35/VEC> Partition Table info for sector 0 (0 0 1)
129/002:35/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 | .488392002
..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/002:36/VEC> 55AA sig Ok
129/002:36/LOG> Boot sector dump requested at 63 (0 1 1)
129/002:40/RDS> ReadError for disk 129 at 6291525 (391 160 31), C:2, T:80h
### 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): 488392001
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 30524500
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 6A50CBA350CB73FB
........Volume Label (txt):
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/004:39/VEC> BS and BBS equal
129/004:39/VEC> Verify EPBR Chain completed
129/004:40/USD> Select disk completed
129/004:50/SCN> DiskScan requested, ScanType is 3
129/004:50/SCN> from 0 (0 0 1) to 488397167 (30401 80 63), 488397168 sectors
129/004:51/SCN> Starting QuickScan (pre-vista) at 63 (0 1 1)
129/004:51/SCN> Next QuickScan location at 488392065 (30401 0 1)
129/004:52/SCN> Next QuickScan location at 0 (0 0 1)
129/004:52/SCN> QuickScan finished
129/004:52/SCN> Starting SmartScan (pre-vista) at 0 (0 0 1) (JMP=16065, RNG=63)
129/006:48/RDS> ReadError for disk 129 at 76822829 (4781 254 63), C:3, T:80h
129/009:16/SCN> DiskScan aborted at JumpSector 76822830 (4782 0 1)
129/009:16/EXE> Analysis aborted
129/009:16/LOG> RunTime: 009:16
129/009:17/LOG> ### CLOSE LOG ###
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1476



WWW
« Reply #1 on: January 19, 2011, 08:49:50 AM »

Hello,

Yes, there are read errors for sure in your MFT, This read attempt:
129/002:40/RDS> ReadError for disk 129 at 6291525 (391 160 31), C:2, T:80h, is where the start of the MFT is.

DiskPatch reporting a problem with the disk health means there is A disk with problems, we need a SMART diagnostic report to determine which one that is and what the severity of the problem is:
http://www.diydatarecovery.nl/dp_manual/guide_smartcheck.htm.

It is very unlikely the MFT can be repaired. Depending on the amount of unreadable sectors and the state of the disk, recovery of user data may be possible straight away using iRecover; it can handle unreadable sectors to some degree. Safest approach and sometimes the only approach is to clone the disk using DiskPatch. Then try recovering data from the clone using iRecover.

You should take into account that the disk you are recovering data from is possibly unreliable and should be replaced. Then you need a spare disk to clone to, and then to recover data from the clone you will need another disk to copy data to.
Logged

--
Kind regards,
Joep - My blog @: www.disktuna.com - Try my JPEG Repair Tool: https://youtu.be/Ox2F8QRuU5Q
kasie23
member

Posts: 16


« Reply #2 on: January 19, 2011, 12:56:56 PM »

Thank you.  I will attach the requested report a little later. It's on the diskette, but I'm using my laptop for now. 

Regarding cloning, do I need separate physical drives and can the data be placed on a drive that is much larger.  Also, is it better to leave the dying drive in the machine it's in (a Pentium 4 machine) or new faster one (with a core 2 duo) -- both run XP.  This latter machine also has 400 gigs free right now, and the dying drive is originally a 250 gig one. I really know little about cloning, as you can tell.
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1476



WWW
« Reply #3 on: January 19, 2011, 02:00:25 PM »

Hello,

P4, dual core, will not make much of a difference.

When you clone a disk with DiskPatch you will need at least an equally sized disk. DiskPatch copies a disk one on one. So it will just transfer contents of the 1st physical sector of the source to the 1st physical sector of the destination and so on. So it will overwrite whatever is on the destination right now including partition table information etc.. The destination disk needs to be dedicated to receive the recovery, you can't clone to a disk and keep the previous data on that disk as well. If the destination is larger, DiskPatch stops where the source disk ends.
Logged

--
Kind regards,
Joep - My blog @: www.disktuna.com - Try my JPEG Repair Tool: https://youtu.be/Ox2F8QRuU5Q
kasie23
member

Posts: 16


« Reply #4 on: January 19, 2011, 02:50:14 PM »

Below is the SMART report on the 2 drives (it looks as if both are failing, although clearly the second drive is in worse shape).

After cloning the drive -- if it's possible, can I recover to the larger drive on the system with the large drive or do I need yet again another dedicated, so to speak, drive.  

Also, I mentioned the processor difference because in another thread one of the moderators wrote that DiskPatch doesn't necessarily do well with a P4 system.  

SMART DRIVE Report:


Detected Controllers

  Disk Controller 1
    Device Vendor . . . . . . . . . . . . . : 8086
    Device ID . . . . . . . . . . . . . . . : 244B
    Device  . . . . . . . . . . . . . . . . : Intel ICH2 IDE Controller
    Device Location . . . . . . . . . . . . : Bus 0, Device 31, Function 1
    Device Ports  . . . . . . . . . . . . . : FFA0-FFAF

Physical Disk Information - Disk: #0

  Hard Disk Summary
    Hard Disk Number  . . . . . . . . . . . : 0
    Interface . . . . . . . . . . . . . . . : IDE/ATA
    Connection  . . . . . . . . . . . . . . : PM
    Hard Disk Model ID  . . . . . . . . . . : WDC WD1200JB-75CRA0
    Hard Disk Revision  . . . . . . . . . . : 16.06V16
    Hard Disk Serial Number . . . . . . . . : WD-WMA8C3237375
    Hard Disk Total Size  . . . . . . . . . : 134110 MB
    Current Temperature:  . . . . . . . . . : ?
    Power on time . . . . . . . . . . . . . : 1468 days, 11 hours
    Health: . . . . . . . . . . . . . . . . : 16 %
    Performance:  . . . . . . . . . . . . . : 100 %

  ATA Information
    Hard Disk Cylinders . . . . . . . . . . : 16383
    Hard Disk Heads . . . . . . . . . . . . : 16
    Hard Disk Sectors . . . . . . . . . . . : 63
    Total Sectors . . . . . . . . . . . . . : 234375000
    ATA Revision  . . . . . . . . . . . . . : 5
    Bytes Per Sector  . . . . . . . . . . . : 600
    Buffer Size . . . . . . . . . . . . . . : 8192 KB
    Multiple Sectors  . . . . . . . . . . . : 16
    Error Correction Bytes  . . . . . . . . : 40
    Unformatted Capacity  . . . . . . . . . : 134110 MB
    Maximum PIO Mode  . . . . . . . . . . . : 4
    Maximum Multiword DMA Mode  . . . . . . : 2
    Maximum UDMA Mode . . . . . . . . . . . : 100 MB/s (5)
    Active UDMA Mode  . . . . . . . . . . . : 100 MB/s (5)
    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  . . . . . . . . : Min performance and volume (80h)
    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 . . . . . . . . . . . . . : Not 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 ...: 4680 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 . . . : 87 minutes
    Conveyance self-test estimated time . . : 5 minutes

  Security Mode
    Security Mode . . . . . . . . . . . . . : Not 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=198 Data=000000000000 Status=OK                        Flags=Error-rate, Statistical, Critical
    3  : Spin Up Time                   Threshold=21  Value=95  Worst=94  Data=000000001770 Status=OK                        Flags=Performance, Statistical, Critical
    4  : Start/Stop Count               Threshold=40  Value=97  Worst=97  Data=000000000DC6 Status=OK                        Flags=Self Preserving, Event Count, Statistical
    5  : Reallocated Sectors Count      Threshold=140 Value=184 Worst=184 Data=0000000000FB Status=OK                        Flags=Self Preserving, Event Count, Statistical, Critical
    7  : Seek Error Rate                Threshold=51  Value=100 Worst=253 Data=000000000000 Status=OK                        Flags=Error-rate, Statistical, Critical
    9  : Power-On Time Count            Threshold=0   Value=52  Worst=52  Data=0000000089AB 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=97  Worst=97  Data=000000000C99 Status=OK (Always passing)       Flags=Self Preserving, Event Count, Statistical
    196: Reallocation Event Count       Threshold=0   Value=112 Worst=112 Data=000000000058 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=200 Data=000000000000 Status=OK                        Flags=Error-rate, Critical

Physical Disk Information - Disk: #1

  Hard Disk Summary
    Hard Disk Number  . . . . . . . . . . . : 1
    Interface . . . . . . . . . . . . . . . : IDE/ATA
    Connection  . . . . . . . . . . . . . . : PS
    Hard Disk Model ID  . . . . . . . . . . : ST3250823A
    Hard Disk Revision  . . . . . . . . . . : 3.02
    Hard Disk Serial Number . . . . . . . . : 5ND04AK9
    Hard Disk Total Size  . . . . . . . . . : 238475 MB
    Current Temperature:  . . . . . . . . . : 43 C (109 F)
    Power on time . . . . . . . . . . . . . : 774 days, 23 hours
    Health: . . . . . . . . . . . . . . . . : 9 %
    Performance:  . . . . . . . . . . . . . : 100 %

  ATA Information
    Hard Disk Cylinders . . . . . . . . . . : 25769
    Hard Disk Heads . . . . . . . . . . . . : 16
    Hard Disk Sectors . . . . . . . . . . . : 63
    Total Sectors . . . . . . . . . . . . . : 488397168
    ATA Revision  . . . . . . . . . . . . . : 7
    Bytes Per Sector  . . . . . . . . . . . : 512
    Buffer Size . . . . . . . . . . . . . . : 8192 KB
    Multiple Sectors  . . . . . . . . . . . : 16
    Error Correction Bytes  . . . . . . . . : 4
    Unformatted Capacity  . . . . . . . . . : 238475 MB
    Maximum PIO Mode  . . . . . . . . . . . : 4
    Maximum Multiword DMA Mode  . . . . . . : 2
    Maximum UDMA Mode . . . . . . . . . . . : 100 MB/s (5)
    Active UDMA Mode  . . . . . . . . . . . : 100 MB/s (5)
    Minimum multiword DMA transfer time . . : 120 ns
    Recommended multiword DMA transfer time : 120 ns
    Minimum PIO transfer time without IORDY : 240 ns
    Minimum PIO transfer time with IORDY  . : 120 ns
    ATA Control Byte  . . . . . . . . . . . : Valid

  Acoustic Management Configuration
    Acoustic Management . . . . . . . . . . : Not Supported
    Acoustic Management . . . . . . . . . . : Disabled
    Current Acoustic Level  . . . . . . . . : Default (00h)
    Recommended Acoustic Level  . . . . . . : Min performance and volume (80h)

  EIDE Properties
    Read Ahead Buffer . . . . . . . . . . . : Not 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 . . . . . . . . . : 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 . . . . . . . . : 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  . . . . . . . : Succesfully completed
    Self test execution status  . . . . . . : Succesfully completed
    Total time to complete off-line data ...: 430 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  . . . . . . . . . : Not Supported
    Selective self-test . . . . . . . . . . : Supported
    Save data before/after power saving mode: Supported
    Enable/Disable attribute autosave . . . : Supported
    Error logging capability  . . . . . . . : Supported
    Short self-test estimated time  . . . . : 1 minutes
    Extended self-test estimated time . . . : 84 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=6   Value=52  Worst=47  Data=000005AD3BC9 Status=OK                        Flags=Error-rate, Performance, Statistical, Critical
    3  : Spin Up Time                   Threshold=0   Value=98  Worst=98  Data=000000000000 Status=OK (Always passing)       Flags=Statistical, Critical
    4  : Start/Stop Count               Threshold=20  Value=96  Worst=96  Data=0000000011C5 Status=OK                        Flags=Self Preserving, Event Count, Statistical
    5  : Reallocated Sectors Count      Threshold=36  Value=100 Worst=100 Data=000000000025 Status=OK                        Flags=Self Preserving, Event Count, Statistical, Critical
    7  : Seek Error Rate                Threshold=30  Value=84  Worst=60  Data=0000126FB233 Status=OK                        Flags=Error-rate, Performance, Statistical, Critical
    9  : Power-On Time Count            Threshold=0   Value=79  Worst=79  Data=0000000048A7 Status=OK (Always passing)       Flags=Self Preserving, Event Count, Statistical
    10 : Spin Retry Count               Threshold=97  Value=100 Worst=100 Data=000000000000 Status=OK                        Flags=Event Count, Statistical, Critical
    12 : Drive Power Cycle Count        Threshold=20  Value=98  Worst=98  Data=000000000811 Status=OK                        Flags=Self Preserving, Event Count, Statistical
    194: HDD Temperature                Threshold=0   Value=43  Worst=52  Data=000F0000002B Status=OK (Always passing)       Flags=Self Preserving, Statistical
    195: Hardware ECC Recovered         Threshold=0   Value=52  Worst=46  Data=000005AD3BC9 Status=OK (Always passing)       Flags=Event Count, Error-rate, Statistical
    197: Current Pending Sector Count   Threshold=0   Value=96  Worst=96  Data=00000000005F Status=OK (Always passing)       Flags=Event Count, Statistical
    198: Off-Line Uncorrectable Sect... Threshold=0   Value=96  Worst=96  Data=00000000005F Status=OK (Always passing)       Flags=Event Count
    199: Ultra ATA CRC Error Count      Threshold=0   Value=200 Worst=200 Data=000000000000 Status=OK (Always passing)       Flags=Self Preserving, Event Count, Error-rate, Performance, Statistical
    200: Write Error Rate               Threshold=0   Value=100 Worst=253 Data=000000000000 Status=OK (Always passing)       Flags=
    202: Data Address Mark Errors       Threshold=0   Value=100 Worst=253 Data=000000000000 Status=OK (Always passing)       Flags=Self Preserving, Event Count, Statistical
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #5 on: January 19, 2011, 03:36:25 PM »

Quote
After cloning the drive -- if it's possible, can I recover to the larger drive on the system with the large drive or do I need yet again another dedicated, so to speak, drive.
I don't get this. It's simple: you need a reliable target disk of at least the same size as the source/problem disk for a successful clone. You should be able to deduce the rest, for your particular situation.
So, if you need to clone/recover from these two disks (because they are not normally accessible), get a fresh reliable disk and:
- clone disk 1
- recover data from the clone
- wipe the cloned target disk (to make sure no left-over data messes up the recovery of the next disk)
- clone disk 2
- recover data from the clone

Or just do disk 2 if disk 1 is still good enough to access and copy files to safety. After all this replace both disks a.s.a.p. and don't use them for storage anymore.

Forget about the P4 and potential DiskPatch problems; it's not an issue. That was a faux-pas on my part.
Logged

kasie23
member

Posts: 16


« Reply #6 on: January 19, 2011, 03:50:12 PM »

Thank you for your reply.  This all may be simple to you, but it isn't to someone who's never done it before! 

Joep said: Then you need a spare disk to clone to, and then to recover data from the clone you will need another disk to copy data to. 

I'm focusing on disk 2 for now. From his comment it suggested that I need to buy 2 new drives.  I understand now that the target drive for cloning should be clean and at least 250 gigs.  My question was about the recovery phase and whether it needs to be yet another clean drive (or one that I don't mind being wiped) or can the target location be part of another drive already in use.

Regarding cloning, can the target drive be external?  Since I'm likely to have read errors in the second pass are there certain options I should use?
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #7 on: January 19, 2011, 08:59:18 PM »

Quote
Joep said: Then you need a spare disk to clone to, and then to recover data from the clone you will need another disk to copy data to.
Indeed, and correctly so.
Quote
I'm focusing on disk 2 for now. From his comment it suggested that I need to buy 2 new drives.
Well, essentially yes. You need one drive to receive the clone, and you need a location to save files -to- when recovering from that clone. This may be a drive or a USB key or whatever, as long as it's big enough to hold the stuff you're pulling from the clone (so a USB key is probably not the best choice; I put that there to list examples and hopefully clarify things).

You'll be using DiskPatch to clone the disk, and then iRecover to scan the cloned disk and copy files from there to safety.
Logged

kasie23
member

Posts: 16


« Reply #8 on: January 19, 2011, 11:52:23 PM »

Thank you again.  Let me rephrase my last question.  Given the unhealthy state of drive 2, should I use the default cloning options of DiskPatch, or do you think some changes should be made, either in the cloning process itself or in the logging process?
Logged
kasie23
member

Posts: 16


« Reply #9 on: January 20, 2011, 12:09:19 AM »

And another question. Is it possible to just use Irecover?  I was looking at Maggie's thread again and saw that Irecover can also clone a disk image and try to recover files from that.
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1476



WWW
« Reply #10 on: January 20, 2011, 09:20:25 AM »

Hello,

Yes. iRecover can create an image file (rather than doing a disk to disk copy). Those image files can then be processed by iRecover as if they were hard disks.
Logged

--
Kind regards,
Joep - My blog @: www.disktuna.com - Try my JPEG Repair Tool: https://youtu.be/Ox2F8QRuU5Q
kasie23
member

Posts: 16


« Reply #11 on: January 20, 2011, 02:06:02 PM »

Given that I may only have one shot at getting the data on the failing drive to another location, which would be better to use, DiskPatch or iRecover? 

BTW I assume it doesn't matter if the target disk is a different type (IDE vs SATA) from the source.
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #12 on: January 20, 2011, 02:19:46 PM »

It depends on how you want to do this. Both ways have merits and drawbacks, but there is no one better way. And if there would be, it's impossible for us to tell because we can never have all the facts (unless we would have direct access to the hardware, which is impossible). So do what you think looks like the most pleasant way to do this.

And, you assume correctly.
Logged

kasie23
member

Posts: 16


« Reply #13 on: January 20, 2011, 02:57:57 PM »

I don't suppose you'd want to elaborate a bit on those merits and drawbacks Smiley.
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #14 on: January 20, 2011, 03:21:02 PM »

Not really, knowing that wouldn't make a difference to you. And it would be mostly about things such as user friendliness and money spent on tools (you can figure this out for yourself). Like I said, I won't make any predictions on results or procedures, go for what you think suits you best.
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!