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

Re: My hard drive sudenly become inaccessible


  • Please log in to reply
7 replies to this topic

#1 Galiima

Galiima

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:00 PM

Posted 16 June 2014 - 02:44 AM

I am using Windows 7. It wants to format it and linux (Kubuntu) doesnt see it.

 

I have read lots about this problem. I have applied below operations. Now what must I do?

I have created a PartedMagic CD.

Started it with default settings and used TestDisk.

Chosen No Log, chosen disk, chosen Intel/PC type partition table.

Chosen Analyse | Quick Search

Then checked my files. All is shown.

But when I continue below error message is shown and operation continued.

Enter: to continue$MFTMirr does not match $MFT (record 0).

Then I write partition structure to disk.

 

Nothing has changed. My disk drive is still inaccessible.


Edited by Galiima, 16 June 2014 - 02:49 AM.


BC AdBot (Login to Remove)

 


#2 Galiima

Galiima
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:00 PM

Posted 16 June 2014 - 02:46 AM

I have used Disk Health.

Disk has passed Short Self-Test

Full report is as below:

 

 

 

smartctl 5.43 2012-06-30 r3573 [i686-linux-3.10.4-pmagic] (local build)
Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus 5400.5
Device Model:     ST9320320AS
Serial Number:    5SX0G2YM
LU WWN Device Id: 5 000c50 00e025d53
Firmware Version: 0303
User Capacity:    320,072,933,376 bytes [320 GB]
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 Jun 16 10:31:02 2014 GMT+2
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:  (0x82)    Offline data collection activity
                    was completed without error.
                    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:         (  723) seconds.
Offline data collection
capabilities:              (0x73) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    No Offline surface scan supported.
                    Self-test supported.
                    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:      ( 119) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x103f)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   115   091   006    Pre-fail  Always       -       88986180
  3 Spin_Up_Time            0x0003   099   096   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   097   097   020    Old_age   Always       -       3565
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       1
  7 Seek_Error_Rate         0x000f   083   060   030    Pre-fail  Always       -       222398241
  9 Power_On_Hours          0x0032   084   084   000    Old_age   Always       -       14516
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       4
 12 Power_Cycle_Count       0x0032   097   097   020    Old_age   Always       -       3300
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   004   004   000    Old_age   Always       -       96
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       6
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   063   048   045    Old_age   Always       -       37 (Min/Max 35/37)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   094   094   000    Old_age   Always       -       13349
194 Temperature_Celsius     0x0022   037   052   000    Old_age   Always       -       37 (0 14 0 0 0)
195 Hardware_ECC_Recovered  0x001a   044   027   000    Old_age   Always       -       88986180
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 97 (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 97 occurred at disk power-on lifetime: 12436 hours (518 days + 4 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 00 ea e3 e1 05  Error: UNC at LBA = 0x05e1e3ea = 98690026

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 e5 e3 e1 e5 00      01:10:21.213  READ DMA
  27 00 00 00 00 00 e0 00      01:10:21.212  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      01:10:21.204  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      01:10:21.196  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      01:10:21.168  READ NATIVE MAX ADDRESS EXT

Error 96 occurred at disk power-on lifetime: 12436 hours (518 days + 4 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 00 ea e3 e1 05  Error: UNC at LBA = 0x05e1e3ea = 98690026

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 e5 e3 e1 e5 00      01:10:18.781  READ DMA
  27 00 00 00 00 00 e0 00      01:10:18.780  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      01:10:18.772  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      01:10:18.764  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      01:10:18.732  READ NATIVE MAX ADDRESS EXT

Error 95 occurred at disk power-on lifetime: 12436 hours (518 days + 4 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 00 ea e3 e1 05  Error: UNC at LBA = 0x05e1e3ea = 98690026

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 e5 e3 e1 e5 00      01:10:16.402  READ DMA
  c8 00 08 8d e5 e1 e5 00      01:10:16.390  READ DMA
  c8 00 08 85 e5 e1 e5 00      01:10:16.041  READ DMA
  27 00 00 00 00 00 e0 00      01:10:15.928  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      01:10:15.920  IDENTIFY DEVICE

Error 94 occurred at disk power-on lifetime: 12436 hours (518 days + 4 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 00 ea e3 e1 05  Error: UNC at LBA = 0x05e1e3ea = 98690026

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 e5 e3 e1 e5 00      01:10:13.447  READ DMA
  ca 00 08 2d bf 26 ee 00      01:10:13.446  WRITE DMA
  ca 00 40 05 aa 25 ee 00      01:10:13.446  WRITE DMA
  ca 00 10 e5 a9 25 ee 00      01:10:13.445  WRITE DMA
  ca 00 08 cd a9 25 ee 00      01:10:13.445  WRITE DMA

Error 93 occurred at disk power-on lifetime: 12436 hours (518 days + 4 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 00 ea e3 e1 05  Error: UNC at LBA = 0x05e1e3ea = 98690026

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 e5 e3 e1 e5 00      01:10:10.835  READ DMA
  ca 00 20 6d a9 25 ee 00      01:10:10.835  WRITE DMA
  ca 00 08 85 a4 24 ee 00      01:10:10.834  WRITE DMA
  ca 00 10 5d a4 24 ee 00      01:10:10.834  WRITE DMA
  ca 00 08 45 a4 24 ee 00      01:10:10.833  WRITE DMA

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     14516         -
# 2  Short offline       Completed without error       00%     14515         -
# 3  Short offline       Completed without error       00%     14501         -

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.



#3 JohnC_21

JohnC_21

  • Members
  • 24,299 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:00 PM

Posted 16 June 2014 - 01:45 PM

If you can see your files, I would copy them to an external drive first.

 

After doing a Quick Search, select the partition it finds and then press "P" to see a list of your files. Then back out to the main menu. Select Advanced.Select Boot. Is the Boot Sector listed as Okay? If not post back. 

 

In the following windows you will see an option to repair the MFT from the Mirror. After repairing the MFT, go back and do another QuickSearch, select the partition, check your files with the "P" key to see if they are present. If so write the partition table.

 

Warning, if this goes bad it would be harder to retrieve any files so I would copy over any important files first before attempting the MFT repair.

 

I believe the drive shows of pre-fail because of the Reallocated Sector Count.

 

 

step6.jpg


Edited by JohnC_21, 16 June 2014 - 01:57 PM.


#4 Galiima

Galiima
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:00 PM

Posted 17 June 2014 - 03:20 AM

Thanks JohnC_21

 

Boot Sector is Okay. Report is below.

Now I will try to copy the files first.

 

-------------------------------------------------------------

TestDisk 6.14, Data Recovery Utility, July 2013

Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63
     Partition                  Start        End    Size in sectors
 1 * HPFS - NTFS              0   1  1 121600 254 63 1953520002 [Iomega_HDD]

Boot sector
Status: OK

Backup boot sector
Status: OK

Sectors are identical.

A valid NTFS Boot sector must be present in order to access
any data; even if the partition is not bootable.
 


Edited by Galiima, 17 June 2014 - 03:23 AM.


#5 JohnC_21

JohnC_21

  • Members
  • 24,299 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:00 PM

Posted 17 June 2014 - 07:13 AM

You may find it a little difficult to copy using Testdisk in Parted Magic. When you select the files using ":" and then "C" to copy you have to use the left and right arrow keys to change directories. The hard drive that you are copying to has to be mounted first.

 

There is also the Windows Version of TestDisk that can be a little easier to work as the default location to copy the files to is the directory you started TestDisk in. In the linux version, the default is on the CD if that is what you used and of course you cannot copy back to that.

 

I explain how to move through the directories using the Windows version here. Using Parted Magic would be similar but the recovery drive would be sda1..sda2.. depending on how many partitions are in the drive. If you have any questions post back. Just remember to be sure you are not writing back to the drive you are recovering from.

 

Edit: The instructions assume you have the TestDisk folder on the desktop of an admin account.


Edited by JohnC_21, 17 June 2014 - 07:21 AM.


#6 Galiima

Galiima
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:00 PM

Posted 17 June 2014 - 07:22 AM

Really a perfect timed message.

I couldn't manage to use Testdisk. Now I will read the links you have mentioned.

I will be carefull about not writing the drive I try to recover.

 

Thanks



#7 Galiima

Galiima
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:00 PM

Posted 17 June 2014 - 08:19 AM

Problem solved! :-)

 

I have falsely used "c" key instead of "C" key. Because of this I couldn't managed to copy my files with TestDisk.

Your message made everything clear. Now I am copying my files. Then I will repair the MFT.

 

Thank you so much JohnC_21



#8 JohnC_21

JohnC_21

  • Members
  • 24,299 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:00 PM

Posted 17 June 2014 - 08:28 AM

After repairing the MFT you may have to still write a new partition table.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users