Welcome, Guest. Please login or register.
Did you miss your activation email?
May 21, 2013, 07:32:41 AM
Home Help Search Login Register
News: Before posting, please read sticky topics!

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  DiskPatch (Moderators: Tom, Joep)
| | |-+  external drive missing data
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: 1 [2] 3 Go Down Print
Author Topic: external drive missing data  (Read 4564 times)
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1145


WWW
« Reply #15 on: May 12, 2012, 09:45:03 PM »

Not years, but yes, the state of the disk can be the cause. Also make sure all disks involved are connected directly to a controller, no USB etc. Do not use the UDMA function, as explained in the manual in the clone section (UDMA should not be used when a disk is potentially not ok).
Logged

slracer1
member

Posts: 25


« Reply #16 on: May 15, 2012, 12:00:58 AM »

So the new drive was an external that my girlfriend bought and cloning with that isnt working. It looks like I would destroy the case tryng to get it out and she wants to use it after... so plan B!

I have another internal SATA drive, a seagate 7200.12 500GB that passes seatools long test. unfortunately, it must have hit 70deg at some point as SMART has been tripped. Will that cause any issues cloning with it? Better yet is there some way of resetting SMART?

So I started the clone process from the dying drive to this drive. And so far it looks very good. It is going very fast. I'll report back when I have more info.
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1145


WWW
« Reply #17 on: May 15, 2012, 09:31:15 AM »

Excellent.
Not sure what you mean by tripped. Depending on the software used you can get a warning, for instance iRecover stops processing when heat becomes an issue. If it was just a warning it shouldn't be a problem, just make sure that the cooling in the box is according to spec.

Remember that cloning happens outside of Windows, so there's no smart test possible during the clone. As such you must make sure that the disk(s) can not overheat during the clone process. Usually that means building them into the machine as described, checking all fans and closing the cover to make sure the air flow is as it should be.
Logged

slracer1
member

Posts: 25


« Reply #18 on: May 15, 2012, 05:38:04 PM »

The clone was successful. It said the 2nd pass was not necessary since there were no errors.
I made sure both drives stayed nice and cool during the clone.
By "tripped" I mean every time the computer boots up with that 500GB drive attached it reports SMART status as bad. Seatools said it was because at some point in the past it got too hot (>70C). It seems fine now and even passed a Seagate seatools long test.

What next? I'll create another support analysis log and post it up for you.
Logged
slracer1
member

Posts: 25


« Reply #19 on: May 15, 2012, 06:14:18 PM »

Support analysis log file from the new cloned drive:



.../000:01/LOG> ### LOG START ###
.../000:01/LOG> DISKPATCH 3.5.300
.../000:01/LOG> (C) 2000-2011 DIY DataRecovery
.../000:01/LOG> Contact info: http://HTTP://www.DIYDataRecovery.nl
.../000:01/LOG> MemFree: 70Kb
.../000:01/LOG> CommandLineParms: /sup
.../000:01/LOG> LogDate: 05-14-2012
.../000:01/CFG> FilePath="A:DPFILES\"
.../000:01/CFG> ReadRetries="32"
.../000:01/CFG> WriteRetries="32"
.../000:01/CFG> MaxReadErrors="32"
.../000:01/CFG> MaxWriteErrors="1"
.../000:01/CFG> LogEachReadError="1"
.../000:01/CFG> ReadDelay="0"
.../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> Drive Interface Info: ATA
.../000:01/13H> Disk 128 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
### DISKLIST.ARRAY ###
__D_|________LBA_|___H_|__S_|__GB_|__GEO
128 | .976773168 | 255 | 63 | 465 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
.../000:01/IAS> AdmiSector found on disk 0 (128)
.../000:02/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:02/WAS> AdmiSectors in use : 0+
.../000:02/KEY> DEMO/1
.../000:02/PFC> PQstuff signature not detected on disk 0 (128)
.../000:02/PFC> UDMA driver not loaded
.../000:02/PFC> Disk health 1-50
.../000:03/PFC> Partition State backup not found on disk 0 (128)
.../000:03/PFC> No Repair date found on disk 0 (128)
.../000:12/CSD> Start CheckDisk for disk 0 (128)
.../000:12/CSD> CheckDisk complete, ReadErrors 0
.../000:12/USD> Disk 0 (128) selected
.../000:12/GSC> No geo change detected for disk 0 (128)
.../000:12/WAS> AdmiSectors in use : 0+
128/000:12/USD> MBR for disk 0 (128)
128/000:12/LOG> SectorDump requested at 0 (0 0 1)
###
000   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
016   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
032   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
048   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
064   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
080   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
096   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
112   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
128   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
144   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
160   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
176   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
192   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
208   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
224   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
240   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
256   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
272   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
288   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
304   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
320   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
336   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
352   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
368   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
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 00 00 00 73 8F DA EB 00 00 80 01  |  ........s...
448   01 00 06 FE 7F 04 3F 00 00 00 86 FA 3F 00 00 00  |  ....?...?...
464   41 05 0C FE FF FF C5 FA 3F 00 FC DB 02 25 00 00  |  A....?..%..
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:12/VEC> Start Verify EPBR Chain for disk 0 (128)
128/000:12/VEC> Listing current partitions on disk:
128/000:12/VEC>    FAT16 (P)          FAT          63     4192902       (2 Gb)
128/000:12/VEC>    FAT32 (P)        (Err)     4192965   620944380     (296 Gb)
128/000:12/VEC> Partition Table info for sector 0 (0 0 1)
128/000:12/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 .128 | ..06 | ....0...1...1 | ..260.254..63 | ........63 | ...4192902
..2 ...0 | ..0C | ..261...0...1 | .1023.254..63 | ...4192965 | .620944380
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
128/000:12/VEC> 55AA sig Ok
128/000:12/LOG> Boot sector dump requested at 63 (0 1 1)
### BootSectorDump for BStype FAT16
...........Jump Code (hex): E9A901
............OEM Name (txt): BOOTWIZ0
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 64
....Reserved Sectors (dec): 1
...........FAT count (dec): 2
....Root Entry Count (dec): 512
..Total Sectors (16) (dec): 0
....Media Descriptor (hex): F8
.......FAT Size (16) (dec): 256
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 63
..Total Sectors (32) (dec): 4192865
........Drive Number (hex): 80
............Reserved (hex): 00
......Boot Signature (hex): 29
...........Volume ID (hex): 413A994F
........Volume Label (txt): FAT
..Filesystem Type ID (txt): FAT16
....Sector Signature (hex): AA55
..........1st FAT at      : 64 (0 1 2)
..........2nd FAT at      : 320 (0 5 6)
128/000:12/CF8> FAT sectors are equal
128/000:12/LOG> SectorDump requested at 576 (0 9 10)
###
     FAT         APPS        B .I.n.f.o. .S.y.s.t.e.
     SYSTEM~1    IMAGES      CONFIG      CODES       
     TXTCODES    WAD         ........... ...........
     ........... ........... ........... ...........
###
128/000:12/LOG> Boot sector dump requested at 4192965 (261 0 1)
### BootSectorDump for BStype FAT32
...........Jump Code (hex): 574246
............OEM Name (txt): S%....
....Bytes per Sector (dec): 256
.Sectors per Cluster (dec): 1
....Reserved Sectors (dec): 257
...........FAT count (dec): 1
....Root Entry Count (dec): 257
..Total Sectors (16) (dec): 257
....Media Descriptor (hex): 01
.......FAT Size (16) (dec): 257
...Sectors per Track (dec): 257
.....Heads per Track (dec): 257
......Hidden Sectors (dec): 16843009
..Total Sectors (32) (dec): 16843009
.......FAT Size (32) (dec): 16843009
......Extended Flags (hex): 0101
.............Version (hex): 0101
........Root Cluster (dec): 16843009
.............FS Info (dec): 257
...........Backup BS (dec): 257
............Reserved (hex): 010101010101010101010101
........Drive Number (hex): 01
............Reserved (hex): 01
......Boot Signature (hex): 01
...........Volume ID (hex): 01010101
........Volume Label (txt):
..Filesystem Type ID (txt): 
....Sector Signature (hex): 0000
1st FAT not found at      : 4193222 (261 4 6)
2nd FAT not found at      : 21036231 (1309 113 28)
128/000:12/CF8> FAT sectors are not equal
128/000:12/LOG> SectorDump requested at 37879238 (2357 222 48)
###
     ^.%G'6.9ʜ ..@w f.XF=.. (3X.L
     ۈ{k. C.+c. LOy̜co ..^%9O.
     6R?. mAZ"..'I 4y'j nc1
     S.\gH. u..-oK' x|4`[z e_ϵ*..
###
128/000:13/VEC> BS and BBS not equal, dump follows;
128/000:13/LOG> Boot sector dump requested at 4192971 (261 0 7)
### BootSectorDump for BStype FAT32 (B)
...........Jump Code (hex): 524D46
............OEM Name (txt): E68.....
....Bytes per Sector (dec): 0
.Sectors per Cluster (dec): 0
....Reserved Sectors (dec): 0
...........FAT count (dec): 0
....Root Entry Count (dec): 0
..Total Sectors (16) (dec): 0
....Media Descriptor (hex): 00
.......FAT Size (16) (dec): 0
...Sectors per Track (dec): 7261
.....Heads per Track (dec): 4294943646
......Hidden Sectors (dec): 0
..Total Sectors (32) (dec): 541478209
.......FAT Size (32) (dec): 1819766594
......Extended Flags (hex): 6E69
.............Version (hex): 3A67
........Root Cluster (dec): 1852395552
.............FS Info (dec): 30050
...........Backup BS (dec): 29811
............Reserved (hex): 000000000000000000737265
........Drive Number (hex): 00
............Reserved (hex): 00
......Boot Signature (hex): 00
...........Volume ID (hex): 00000000
........Volume Label (txt):
..Filesystem Type ID (txt):         
....Sector Signature (hex): 0000
128/000:13/VEC> Verify EPBR Chain completed
128/000:13/USD> Select disk completed
128/000:25/SCN> DiskScan requested, ScanType is 3
128/000:25/SCN> from 0 (0 0 1) to 976773167 (60801 80 63), 976773168 sectors
128/000:25/SCN> Starting QuickScan (pre-vista) at 63 (0 1 1)
128/000:25/SCN> Next QuickScan location at 4192928 (260 254 27)
128/000:26/SCN> Next QuickScan location at 0 (0 0 1)
128/000:26/SCN> QuickScan finished
128/000:26/SCN> Starting SmartScan (pre-vista) at 0 (0 0 1) (JMP=16065, RNG=63)
128/026:56/SCN> SmartScan finished
128/026:56/SCN> DiskScan completed
128/026:56/SCN> ReadErrors for disk 0 (128): 0
128/030:01/LOG> DataCollection items found: 8 / 2
### DATACOLLECTION.ARRAY, FULL ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL_|_F
001 | 128 | ........63 | ..FAT16 | ..BS | ........63 | ...4192865 | PRI | .
002 | 128 | ........64 | ..FAT16 | F8FF | ........63 | .......... | PRI | .
003 | 128 | .........0 | ..FAT16 | PTE1 | ........63 | ...4192902 | PRI | .
004 | 128 | .........0 | ..FAT32 | PTE2 | ...4192965 | .620944380 | PRI | .
005 | 128 | ........63 | ..FAT16 | ..BS | ........63 | ...4192865 | PRI | I
006 | 128 | ........64 | ..FAT16 | F8FF | ........63 | .......... | PRI | I
007 | 128 | .625137344 | ...NTFS | .BBS | ........63 | .625137282 | PRI | .
008 | 128 | .976768064 | ...NTFS | .BBS | .409593240 | .567174825 | PRI | .
128/030:01/LOG> DataCollection items found: 8 / 2
### DATACOLLECTION.ARRAY, CLEANED ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL
001 | 128 | ........63 | ..FAT16 | ..BS | ........63 | ...4192865 | PRI
002 | 128 | ........64 | ..FAT16 | F8FF | ........63 | .......... | PRI
003 | 128 | .........0 | ..FAT16 | PTE1 | ........63 | ...4192902 | PRI
004 | 128 | .........0 | ..FAT32 | PTE2 | ...4192965 | .620944380 | PRI
007 | 128 | .625137344 | ...NTFS | .BBS | ........63 | .625137282 | PRI
008 | 128 | .976768064 | ...NTFS | .BBS | .409593240 | .567174825 | PRI
128/030:01/LOG> PartList items created: 5
### PARTLIST.ARRAY ###
SEQ_|____TYPE_|_PTE_|__BS_|_BBS_|F8FF_|___S_|___L_|__PL_|_C_|___R
001 | ..FAT16 | ..3 | ... | ..0 | ..6 | ..3 | ..3 | ..3 | 3 | ..B
002 | ..FAT16 | ... | ..1 | ..0 | ..6 | ..1 | ..1 | ..1 | 3 | ..A
003 | ...NTFS | ... | ... | ..7 | ..0 | ..7 | ..7 | ..7 | 1 | ..B
004 | ..FAT32 | ..4 | ... | ... | ... | ..4 | ..4 | ..4 | 1 | ...
005 | ...NTFS | ... | ... | ..8 | ..0 | ..8 | ..8 | ..8 | 1 | ..B
### PARTLIST.ARRAY.INTERPRETED ###
SEQ_|____TYPE_|______START_|_____LENGTH_|________END_|__PL_|___R_|___A
001 | ..FAT16 | ........63 | ...4192902 | ...4192964 | PRI | ..B | ..X
002 | ..FAT16 | ........63 | ...4192865 | ...4192927 | PRI | ..A | ..X
003 | ...NTFS | ........63 | .625137282 | .625137344 | PRI | ..B | ..X
004 | ..FAT32 | ...4192965 | .620944380 | .625137344 | PRI | ... | ..X
005 | ...NTFS | .409593240 | .567174825 | .976768064 | PRI | ..B | ..X
128/030:01/SST> SaveState requested for disk 0 (128)
128/030:01/WAS> AdmiSectors in use : 0+
128/030:02/SST> SaveState completed for disk 0 (128)
128/030:02/EXE> Analysis complete
128/030:05/LOG> RunTime: 030:05
128/030:05/LOG> ### CLOSE LOG ###

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


WWW
« Reply #20 on: May 15, 2012, 10:22:41 PM »

Excellent, good thinking on the new support log.

Well, the clone worked okay so the damage has also been copied. So we can start the same repair as before, as a first step. Any chance you can run that Boot Sector repair you tried before? Make sure that the undo feature is working, and try to rebuild the boot sector for that second partition. Also, post the resulting log.
So this one: http://www.diydatarecovery.nl/dp_manual/guide_fatbsrepair.htm

On my second check I noticed that this disk also has a SMART warning. Not sure why, I'll need a fresh SMART log for that, so if you can, please include a fresh SMART log too. This is all becoming quite the project...
Logged

slracer1
member

Posts: 25


« Reply #21 on: May 15, 2012, 11:09:07 PM »

New SMART log!



Detected Controllers

  Disk Controller 1
    Device Vendor . . . . . . . . . . . . . : 10DE
    Device ID . . . . . . . . . . . . . . . : 03EC
    Device  . . . . . . . . . . . . . . . . : NVidia
    Device Location . . . . . . . . . . . . : Bus 0, Device 6, Function 0
    Device Ports  . . . . . . . . . . . . . : FFA0-FFAF

  Disk Controller 2
    Device Vendor . . . . . . . . . . . . . : 10DE
    Device ID . . . . . . . . . . . . . . . : 03F6
    Device  . . . . . . . . . . . . . . . . : NVidia
    Device Location . . . . . . . . . . . . : Bus 0, Device 8, Function 0
    Device Ports  . . . . . . . . . . . . . : E400-E407, E080-E083, E000-E007, DC00-DC03, D880-D88F

Physical Disk Information - Disk: #0

  Hard Disk Summary
    Hard Disk Number  . . . . . . . . . . . : 0
    Interface . . . . . . . . . . . . . . . : S-ATA II
    Connection  . . . . . . . . . . . . . . : 2
    Hard Disk Model ID  . . . . . . . . . . : ST3500410AS
    Hard Disk Revision  . . . . . . . . . . : CC34
    Hard Disk Serial Number . . . . . . . . : 5VM0T8BQ
    Hard Disk Total Size  . . . . . . . . . : 476940 MB
    Current Temperature:  . . . . . . . . . : 23 C (73 F)
    Power on time . . . . . . . . . . . . . : 605 days, 3 hours
    Health: . . . . . . . . . . . . . . . . : 0 %
    Performance:  . . . . . . . . . . . . . : 100 %

  ATA Information
    Hard Disk Cylinders . . . . . . . . . . : 16383
    Hard Disk Heads . . . . . . . . . . . . : 16
    Hard Disk Sectors . . . . . . . . . . . : 63
    Total Sectors . . . . . . . . . . . . . : 976773168
    ATA Revision  . . . . . . . . . . . . . : 7
    Bytes Per Sector  . . . . . . . . . . . : 512
    Buffer Size . . . . . . . . . . . . . . : 16384 KB
    Multiple Sectors  . . . . . . . . . . . : 16
    Error Correction Bytes  . . . . . . . . : 4
    Unformatted Capacity  . . . . . . . . . : 476940 MB
    Maximum PIO Mode  . . . . . . . . . . . : 4
    Maximum Multiword DMA Mode  . . . . . . : 2
    Maximum UDMA Mode . . . . . . . . . . . : 150 MB/s (6)
    Active UDMA Mode  . . . . . . . . . . . : 150 MB/s (6)
    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  . . . . . . . . : Default (00h)
    Recommended Acoustic Level  . . . . . . : Max performance and volume (FEh)

  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 . . . . . . . . . . : 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  . . . . . . . . . : 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 . . . . . . . . . . . : Supported, Disabled
    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 ...: 600 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 . . . . . . . . . . : 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 . . . : 96 minutes
    Conveyance self-test estimated time . . : 2 minutes

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

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

  S.M.A.R.T.
    1  : Raw Read Error Rate            Threshold=6   Value=116 Worst=99  Data=00000634989C Status=OK                        Flags=Error-rate, Performance, Statistical, Critical
    3  : Spin Up Time                   Threshold=0   Value=97  Worst=97  Data=000000000000 Status=OK (Always passing)       Flags=Statistical, Critical
    4  : Start/Stop Count               Threshold=20  Value=100 Worst=100 Data=0000000001A4 Status=OK                        Flags=Self Preserving, Event Count, Statistical
    5  : Reallocated Sectors Count      Threshold=36  Value=1   Worst=1   Data=000000000FFF Status=Pre-failure: Data loss... Flags=Self Preserving, Event Count, Statistical, Critical
    7  : Seek Error Rate                Threshold=30  Value=76  Worst=60  Data=0000028E628D Status=OK                        Flags=Error-rate, Performance, Statistical, Critical
    9  : Power-On Time Count            Threshold=0   Value=84  Worst=84  Data=0000000038BB 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=100 Worst=100 Data=0000000001A7 Status=OK                        Flags=Self Preserving, Event Count, Statistical
    183: Vendor-specific                Threshold=0   Value=100 Worst=100 Data=000000000000 Status=OK (Always passing)       Flags=
    184: Vendor-specific                Threshold=99  Value=100 Worst=100 Data=000000000000 Status=OK                        Flags=Self Preserving, Event Count, Statistical
    187: Vendor-specific                Threshold=0   Value=100 Worst=100 Data=000000000000 Status=OK (Always passing)       Flags=Self Preserving, Event Count, Statistical
    188: Vendor-specific                Threshold=0   Value=100 Worst=98  Data=000300030004 Status=OK (Always passing)       Flags=Self Preserving, Event Count, Statistical
    189: Vendor-specific                Threshold=0   Value=99  Worst=99  Data=000000000001 Status=OK (Always passing)       Flags=Self Preserving, Event Count, Error-rate, Statistical
    190: Airflow Temperature            Threshold=45  Value=77  Worst=49  Data=000017170017 Status=OK                        Flags=Self Preserving, Statistical
    194: HDD Temperature                Threshold=0   Value=23  Worst=51  Data=001100000017 Status=OK (Always passing)       Flags=Self Preserving, Statistical
    195: Hardware ECC Recovered         Threshold=0   Value=39  Worst=16  Data=00000634989C Status=OK (Always passing)       Flags=Event Count, Error-rate, Statistical
    197: Current Pending Sector Count   Threshold=0   Value=100 Worst=100 Data=000000000000 Status=OK (Always passing)       Flags=Event Count, Statistical
    198: Off-Line Uncorrectable Sect... Threshold=0   Value=100 Worst=100 Data=000000000000 Status=OK (Always passing)       Flags=Event Count
    199: Ultra ATA CRC Error Count      Threshold=0   Value=200 Worst=198 Data=00000000054F Status=OK (Always passing)       Flags=Self Preserving, Event Count, Error-rate, Performance, Statistical
    240: Head Flying Hours              Threshold=0   Value=100 Worst=253 Data=C37200003D68 Status=OK (Always passing)       Flags=
    241: Vendor-specific                Threshold=0   Value=100 Worst=253 Data=00007C163EA6 Status=OK (Always passing)       Flags=
    242: Vendor-specific                Threshold=0   Value=100 Worst=253 Data=0000B90ABBD8 Status=OK (Always passing)       Flags=
Logged
slracer1
member

Posts: 25


« Reply #22 on: May 15, 2012, 11:29:02 PM »

ok, there are 2 partitions a 2GB and a 296GB. I ran the boot sector repair on the 2GB partition and got the following:

Checking boot sector location    (green "done")
FAT16 boot sector validation      (red "done")
Validating FAT                             (red "done")

Data could not be determined, repair aborted

Boot sector status: failed
FAT status:  failed

I'll report on the 296GB partition soon....
Logged
slracer1
member

Posts: 25


« Reply #23 on: May 15, 2012, 11:34:06 PM »

296GB partition:

Checking boot sector location...    (green "done")
FAT32 boot sector validation ...    (red "done")
Validating FAT...                            (skipped)

Data could not be determined, repair aborted

Boot sector status: failed
FAT status:  unknown

There ya go, it took a really long time.
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1154


WWW
« Reply #24 on: May 16, 2012, 09:34:52 AM »

What do you expect to be on there? Because such a large FAT32 partition is unlikely. And what happened to the disk? you discovered Windows shows partition as unformatted. Did you experiment with any boot management software? What was the disk used for, what was stored on it? I am wondering why there is a FAT16 partition labeled bootwiz (think that's acronis) and a FAT32 partition Windows would never create on it's own (max 32 GB).

What was on the disk you cloned to? Because now there's also an NTFS partition detected during the scan.

Quote
5  : Reallocated Sectors Count      Threshold=36  Value=1   Worst=1   Data=000000000FFF Status=Pre-failure: Data loss... Flags=Self Preserving, Event Count, Statistical, Critical

If that latest SMART log comes from the disk that you cloned to, it's not a very healthy disk; overall disk health in that log shows 0%.
Logged

--
Kind regards,
Joep
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1145


WWW
« Reply #25 on: May 16, 2012, 09:49:00 AM »

Both BS repairs not working means that
- the boot sectors could not be rebuilt (too much corruption), or
- the volumes are not actually of the type specified (FAT) in the partition table, or
- the volumes are not in the location that is specified in the partition table.

So indeed, do you know anything about the volumes that should be on that disk, like type and size?
Logged

slracer1
member

Posts: 25


« Reply #26 on: May 16, 2012, 05:36:37 PM »

The only use of the drive was to store some WII games. I am told it had a lot. There was never an OS or anything like that.

It just stopped working (games no longer found on the drive) one day. When I put it into my machine, windows thinks the big partition is not formatted. I did not try any other fixing software.

The disk I cloned TO did have an NTFS install of XP but I stopped using that disk a while back. I didnt mind that the clone process would destroy the old data. We can get rid of that NTFS partition if you like.

sadly I dont know what volumes are supposed to be on this drive. Really all I know is that it was an external drive with a bunch of games.
My girlfriend bought it that way from some place up in Canada. I imagine the seller using imaging software to mass produce these.
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1145


WWW
« Reply #27 on: May 16, 2012, 09:33:12 PM »

Well, then based on what has happened and where we are now I'm fairly convinced that this isn't going to work out; it seems a repair is not going to happen. You could let iRecover analyze the disk, if only to see if it can tell us more about what's on there, and if the analysis comes to helpful conclusions it may even be possible to recover some stuff from the drive, but getting this back to working as it did is unlikely.
I would suggest an iRecover run, you can use the Trial version to analyze the disk, see what comes up.
If you decide to do this, select the disk in the selection screen, not the volumes that are listed. See what iRecover makes of it.
Logged

slracer1
member

Posts: 25


« Reply #28 on: May 17, 2012, 04:44:42 AM »

ok, thanks for all the help thus far. You have been very patient throughout this adventure Smiley

I started iRecover now and will let you know what it finds tomorrow.

cheers
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1145


WWW
« Reply #29 on: May 17, 2012, 11:00:14 AM »

No worries. Too bad we didn't succeed but I'm quite curious about what is on that disk and what happened. The damage is quite severe and that doesn't "just happen".
Logged

Pages: 1 [2] 3 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.17 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!