Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

1 TB external hard drive failure - lost files


  • Please log in to reply
10 replies to this topic

#1 tolawr

tolawr

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:12:31 AM

Posted 27 March 2013 - 12:29 PM

Using Windows 7

Hitachi 1 TB portable hard drive connected via USB

Have access to two separate computers and the same problem registers on each


A portable hard drive which I use to edit and store video information as well as backup some music recently began registering error messages when plugged into any computer. Windows prompts me to check for and repair errors on the hard drive and only a limited amount of information still displays. When I try to repair, it seems to just freeze at 0% progress for hours though I am going to let it sit overnight tonight and see if it's just incredibly slow. Upon further inspection, I noticed that the hard drive seems to have changed from NTFS to exFAT (without any prompting from me, of course.). The missing files are of all sizes, however, not just those exceeding 4 gigs. I am using a copy of minitool power data recovery (v6.6) but it doesn't seem to be finding anything new. I am about to try a scan with Stellar Phoenix v 6.1 but I don't expect much.

This problem occurred after a round of video editing in which I had just finished exporting a test file of around 20 gigs. I watched a bit of it, found some problems and decided to go to bed and finish editing in the morning. I turned off my laptop, unplugged everything and went home for the night and turned both on the next day to my predicament. The files I am trying to recover are several ~4gig AVCHD video files in .avi format and a fairly large ~20gig h264 .mov file.

If there's not a way to recover the data is there a reasonable explainetion as to why this might have happened in the first place? I assume the answer is that technology just fails sometimes but it still seems odd that it happened to occur as soon as I finished exporting a fairly large file and that the system is now recognized incorrectly as exFAT instead of NTFS. Any insight is much appreciated.

-T.O.



BC AdBot (Login to Remove)

 


#2 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:31 PM

Posted 27 March 2013 - 03:32 PM

Hi

 

What model is the Hitachi?

I recall that some models had an overheating issue. Do you think yours got very hot ever?

 

James



#3 tolawr

tolawr
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:12:31 AM

Posted 27 March 2013 - 03:39 PM

XL1000

Apparently this has happened to someone else

 

http://www.fixya.com/support/t9615921-hitachi_external_hard_drive



#4 tolawr

tolawr
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:12:31 AM

Posted 27 March 2013 - 03:42 PM

...and it's very possible it got hot over the course of the write process but that should have created an error before I powered off, no?



#5 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:31 PM

Posted 27 March 2013 - 04:01 PM

We can try to take a look at the SMART data for the drive to see if there is any physical damage and then try to look at the file system.

 

To look at the SMART data try using GSmartControl.

Get a copy of GSmartControl for Windows
http://prdownload.berlios.de/gsmartcontrol/gsmartcontrol-0.8.7-win32.zip?download
Unzip it and run gsmartcontrol.exe

Double-click your drive and click the VIEW OUTPUT button and copy and paste the resulting report in your reply so we can look at it.

 

Let us know if you have any problems or questions.

James



#6 tolawr

tolawr
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:12:31 AM

Posted 28 March 2013 - 12:24 PM

We can try to take a look at the SMART data for the drive to see if there is any physical damage and then try to look at the file system.

 

To look at the SMART data try using GSmartControl.

Get a copy of GSmartControl for Windows
http://prdownload.berlios.de/gsmartcontrol/gsmartcontrol-0.8.7-win32.zip?download
Unzip it and run gsmartcontrol.exe

Double-click your drive and click the VIEW OUTPUT button and copy and paste the resulting report in your reply so we can look at it.

 

Let us know if you have any problems or questions.

James

Doing this afternoon.



#7 tolawr

tolawr
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:12:31 AM

Posted 01 April 2013 - 11:39 AM

We can try to take a look at the SMART data for the drive to see if there is any physical damage and then try to look at the file system.

 

To look at the SMART data try using GSmartControl.

Get a copy of GSmartControl for Windows
http://prdownload.berlios.de/gsmartcontrol/gsmartcontrol-0.8.7-win32.zip?download
Unzip it and run gsmartcontrol.exe

Double-click your drive and click the VIEW OUTPUT button and copy and paste the resulting report in your reply so we can look at it.

 

Let us know if you have any problems or questions.

James

Hey,

Sorry it took me a bit, I had to use my system for a bunch of other projects that were due. The output is here:



smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win7(64)-sp1] (sf-5.43-1)
Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
 
=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Deskstar 7K1000.C
Device Model:     Hitachi HDS721010CLA332
Serial Number:    JP6921HD1A59PM
LU WWN Device Id: 5 000cca 373d2b728
Firmware Version: JP4OA3EA
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Mon Apr 01 12:37:31 2013 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
 
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
 
General SMART Values:
Offline data collection status:  (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
without error or no self-test has ever 
been run.
Total time to complete Offline 
data collection: (10105) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine 
recommended polling time: (   1) minutes.
Extended self-test routine
recommended polling time: ( 168) minutes.
SCT capabilities:       (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
 
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   135   135   054    Pre-fail  Offline      -       96
  3 Spin_Up_Time            0x0007   150   150   024    Pre-fail  Always       -       280 (Average 225)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       1384
  5 Reallocated_Sector_Ct   0x0033   092   092   005    Pre-fail  Always       -       167
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   140   140   020    Pre-fail  Offline      -       30
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       13404
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       133
192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       1471
193 Load_Cycle_Count        0x0012   099   099   000    Old_age   Always       -       1471
194 Temperature_Celsius     0x0002   206   206   000    Old_age   Always       -       29 (Min/Max 13/63)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       181
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       170
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
 
SMART Error Log Version: 1
ATA Error Count: 883 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
 
Error 883 occurred at disk power-on lifetime: 13402 hours (558 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 80 5f 24 01 00  Error: UNC 128 sectors at LBA = 0x0001245f = 74847
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 80 5f 24 01 e0 00  28d+00:34:07.551  READ DMA EXT
  ef 03 46 00 00 00 a0 00  28d+00:34:07.545  SET FEATURES [Set transfer mode]
  25 00 80 df 23 01 a0 04  28d+00:34:07.441  READ DMA EXT
  25 00 80 df 23 01 e0 00  28d+00:33:49.139  READ DMA EXT
  ef 03 46 00 00 00 a0 00  28d+00:33:49.132  SET FEATURES [Set transfer mode]
 
Error 882 occurred at disk power-on lifetime: 13402 hours (558 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 80 df 23 01 00  Error: UNC 128 sectors at LBA = 0x000123df = 74719
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 80 df 23 01 e0 00  28d+00:33:49.139  READ DMA EXT
  ef 03 46 00 00 00 a0 00  28d+00:33:49.132  SET FEATURES [Set transfer mode]
  25 00 80 5f 23 01 a0 04  28d+00:33:49.030  READ DMA EXT
  25 00 80 5f 23 01 e0 00  28d+00:33:30.829  READ DMA EXT
  ef 03 46 00 00 00 a0 00  28d+00:33:30.823  SET FEATURES [Set transfer mode]
 
Error 881 occurred at disk power-on lifetime: 13402 hours (558 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 80 5f 23 01 00  Error: UNC 128 sectors at LBA = 0x0001235f = 74591
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 80 5f 23 01 e0 00  28d+00:33:30.829  READ DMA EXT
  ef 03 46 00 00 00 a0 00  28d+00:33:30.823  SET FEATURES [Set transfer mode]
  25 00 80 df 22 01 a0 04  28d+00:33:30.719  READ DMA EXT
  25 00 80 df 22 01 e0 00  28d+00:33:12.519  READ DMA EXT
  ef 03 46 00 00 00 a0 00  28d+00:33:12.513  SET FEATURES [Set transfer mode]
 
Error 880 occurred at disk power-on lifetime: 13402 hours (558 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 80 df 22 01 00  Error: UNC 128 sectors at LBA = 0x000122df = 74463
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 80 df 22 01 e0 00  28d+00:33:12.519  READ DMA EXT
  ef 03 46 00 00 00 a0 00  28d+00:33:12.513  SET FEATURES [Set transfer mode]
  25 00 80 5f 22 01 a0 04  28d+00:33:12.409  READ DMA EXT
  25 00 80 5f 22 01 e0 00  28d+00:32:54.208  READ DMA EXT
  ef 03 46 00 00 00 a0 00  28d+00:32:54.202  SET FEATURES [Set transfer mode]
 
Error 879 occurred at disk power-on lifetime: 13402 hours (558 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 80 5f 22 01 00  Error: UNC 128 sectors at LBA = 0x0001225f = 74335
 
  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 80 5f 22 01 e0 00  28d+00:32:54.208  READ DMA EXT
  ef 03 46 00 00 00 a0 00  28d+00:32:54.202  SET FEATURES [Set transfer mode]
  25 00 80 df 21 01 a0 04  28d+00:32:54.099  READ DMA EXT
  25 00 80 df 21 01 e0 00  28d+00:32:35.899  READ DMA EXT
  ef 03 46 00 00 00 a0 00  28d+00:32:35.893  SET FEATURES [Set transfer mode]
 
SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]
 
 
SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


#8 inou81

inou81

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:31 PM

Posted 01 April 2013 - 12:37 PM

Hi everyone,

 

I'm new to this forum. When I saw this post I thought I might be able to help.

 

I have seen this problem before recovering a security DVR system. If your sure the file extension is .avi and .mov, PhotoRec and Rstudio should be able to recover your files. PhotoRec is free. If your file extensions are raw .264, you will need to add a custom file type to either program. In my case PhotoRec actually did a better job than rstudio. Be aware the PhotoRec is strictly a raw recovery. You will loose the file names and metadata but your files will be recovered. Let me know if you need help with the .264 file extension.



#9 tolawr

tolawr
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:12:31 AM

Posted 01 April 2013 - 01:55 PM

Hi everyone,

 

I'm new to this forum. When I saw this post I thought I might be able to help.

 

I have seen this problem before recovering a security DVR system. If your sure the file extension is .avi and .mov, PhotoRec and Rstudio should be able to recover your files. PhotoRec is free. If your file extensions are raw .264, you will need to add a custom file type to either program. In my case PhotoRec actually did a better job than rstudio. Be aware the PhotoRec is strictly a raw recovery. You will loose the file names and metadata but your files will be recovered. Let me know if you need help with the .264 file extension.

 

Hey,

I just got photorec and am ready to add the formats. I double checked and one file type is .mts while the other is .mov. Assist on using the software correctly? Thanks!
 
EDIT: will search for avi as well to make sure I dont miss anything.


Edited by tolawr, 01 April 2013 - 01:55 PM.


#10 inou81

inou81

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:31 PM

Posted 01 April 2013 - 02:58 PM

See this tutorial and let me know if you still have questions.

http://www.cgsecurity.org/wiki/PhotoRec_Step_By_Step

If it is a file type photorec doesnt have a deffinition for you will have to use a hex editior to find the definition.

Lets start with the initial scan and see if we can find what you are looking for.  Be advised, the scan is not a quick process. Plan to let this run a couple days.



#11 inou81

inou81

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:31 PM

Posted 01 April 2013 - 04:00 PM

From a quick read if you check m2t and m2ts, it should pickup your mts files.  If not you will have to create a custom sig.  Let me know how it goes.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users