Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Corrupted External Drive Problems


Best Answer Lucky Dearly , 15 April 2016 - 07:31 PM

chkdsk still gives the same error message when I ran chkdsk /r on the infected drive. Guess i'll have to reformat it Drive works after the reformat, currently restoring the backed up data to t... Go to the full post »


  • Please log in to reply

#1
Lucky Dearly

Lucky Dearly

    Member

  • Member
  • PipPipPip
  • 294 posts

Hey all

 

Got a bit of a major problem on my hands, my 1TB Western Digital external drive has suddenly gone corrupt. I tried to run chkdsk using an admin prompt but everytime it gives me the error message "unable to determine volume version and state. chkdsk aborted". Also trying to access the drive gives me the error message "D:\ is not accessible. the disk structure is corrupt and unreadable"

 

I hope it's possible to fix the drive without having to reformat it, got a lot of personal family pictures on the drive as well as other files.


Edited by Lucky Dearly, 12 April 2016 - 03:52 AM.

  • 0

Advertisements


#2
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,752 posts

Gday Lucky Dearly/

If you have any backup software running, disable it.

We need to see the drive structure of D.   Please open disk management, Make sure to go full screen, take a screen shot and add to your next reply. 

Instructions if you are not sure of the steps to take, > http://pcsupport.abo...-management.htm


  • 0

#3
Lucky Dearly

Lucky Dearly

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 294 posts

jadf8h.jpg

 

here's what it looks like. as you can see the D drive is the problem drive


Edited by Lucky Dearly, 13 April 2016 - 12:17 AM.

  • 0

#4
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,752 posts

Sorry for the delay, had other commitments. 

(D) Partition is now RAW, something went wrong with the file structure, Windows can't read any Data, it should be NTFS.

Please download and install the free ver of Recuvafrom the bottom of this page, > http://www.piriform.com/recuva

Run the basic Wizard, info on this page, > http://www.piriform....ard-wizard-mode

Note, If you are able to to find the files you want, you will need a destination for saving those files. 


  • 0

#5
Lucky Dearly

Lucky Dearly

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 294 posts

I'll give those a shot, hopefully I can repair this thing without losing files.


  • 0

#6
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,752 posts

:thumbsup: 

Recuva won't actually repair the drive, it is only a means of hopefully recovering your Data.


  • 0

#7
terry1966

terry1966

    Member 1K

  • Member
  • PipPipPipPip
  • 1,003 posts

once you've backed up and recovered your data as iammmy instructed it will then be safe to try and repair the partition table.

 

with luck after it's repaired everything will be still be there and usable again, i'd use testdisk to do the repair.

full instructions on where to get testdisk and how to do the repair are here at this blog :-  http://html5.litten....nly-became-raw/

 

:popcorn:


  • 0

#8
Lucky Dearly

Lucky Dearly

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 294 posts

okay currently running testdisk right now. on the third screen when I choose the partition type the hint shows None partition.

 

Oh wait, nevermind. I selected the wrong thing. I think I got this now. I was selecting the drive itself instead of the partition. Now the hint shows intel instead

 

Edit: Hmm this isn't good. after the deep scan I hit P to look at the files and I get an error saying "can't open filesystem. filesystem seems damaged"

 

Edit: Now my pc crashed twice with the drive plugged in.


Edited by Lucky Dearly, 15 April 2016 - 03:51 AM.

  • 0

#9
terry1966

terry1966

    Member 1K

  • Member
  • PipPipPipPip
  • 1,003 posts

have you backed up all your data on the drive?

did the drive pass a smart test?

are you sure your choosing the correct drive to work with after selecting the no log option? what drive options show up eg. /dev/sda, /dev/sdb, /dev/sdc etc.?

 

have you tried to write anything to the drive yet?? (don't!!!)

 

no idea why your pc crashed but using testdisk should not effect or crash your os (unless of course you use it to make changes to your os drive.), so there might be a problem elsewhere with your pc.

 

can you provide screenshots of :-

1. your drive options after the no log option,

2. what is shown after you do the quick search on the drive, (do not hit the enter key to get to the option to run a deeper search.)

3. and last what is shown when you hit p to show the files after the quick search.

 

:popcorn:


Edited by terry1966, 15 April 2016 - 08:07 AM.

  • 0

#10
Lucky Dearly

Lucky Dearly

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 294 posts

nope i didn't try to write anything yet, I'll post the screenshots as soon as I can get them. I get two options in testdisk. sda and sdb. sda being my main drive which is good and sdb being the external drive as well as options for both the C: and D: drives

 

as for the crashes I think it was something else and not the scan that did that.

 

as for the quick search when I pressed P it displayed the damaged filesystem error message. Same thing after a deep scan too

 

here's what I got from the S.M.A.R.T. scan.

 

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win8(64)] (sf-5.43-1)
Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD10JMVW-11S5XS0
Serial Number:    WD-WXE1C22C5739
LU WWN Device Id: 5 0014ee 6ad0e2f88
Firmware Version: 01.01A01
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Fri Apr 15 12:20:47 2016 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART STATUS RETURN: incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
     was never started.
     Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 121) The previous self-test completed having
     the read element of the test failed.
Total time to complete Offline
data collection:   (18900) seconds.
Offline data collection
capabilities:     (0x7b) SMART execute Offline immediate.
     Auto Offline data collection on/off support.
     Suspend Offline collection upon new
     command.
     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:   (   2) minutes.
Extended self-test routine
recommended polling time:   ( 205) minutes.
Conveyance self-test routine
recommended polling time:   (   5) minutes.
SCT capabilities:         (0x70b5) SCT Status 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     0x002f   167   145   051    Pre-fail  Always       -       65851
  3 Spin_Up_Time            0x0027   181   170   021    Pre-fail  Always       -       1941
  4 Start_Stop_Count        0x0032   085   085   000    Old_age   Always       -       15555
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   073   073   000    Old_age   Always       -       20424
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   097   097   000    Old_age   Always       -       3543
192 Power-Off_Retract_Count 0x0032   196   196   000    Old_age   Always       -       3171
193 Load_Cycle_Count        0x0032   173   173   000    Old_age   Always       -       83747
194 Temperature_Celsius     0x0022   121   099   000    Old_age   Always       -       26
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       28
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 19 (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 19 occurred at disk power-on lifetime: 20264 hours (844 days + 8 hours)
  When the command that caused the error occurred, the device was in standby mode.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 02 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e1 00 02 00 00 00 00 00      01:58:19.788  IDLE IMMEDIATE
  ec 00 01 00 00 00 00 00      01:58:19.787  IDENTIFY DEVICE
  e0 00 0a 00 00 00 00 00      01:48:21.658  STANDBY IMMEDIATE
  e1 00 02 00 00 00 00 00      01:48:13.257  IDLE IMMEDIATE
  ec 00 01 00 00 00 00 00      01:48:13.256  IDENTIFY DEVICE

Error 18 occurred at disk power-on lifetime: 20264 hours (844 days + 8 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
  -- -- -- -- -- -- --
  04 51 02 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e1 00 02 00 00 00 00 00      01:48:13.257  IDLE IMMEDIATE
  ec 00 01 00 00 00 00 00      01:48:13.256  IDENTIFY DEVICE
  b0 d0 00 00 4f c2 00 00      01:46:57.828  SMART READ DATA
  b0 d0 00 00 4f c2 00 00      01:42:48.192  SMART READ DATA

Error 17 occurred at disk power-on lifetime: 20263 hours (844 days + 7 hours)
  When the command that caused the error occurred, the device was in standby mode.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 02 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e1 00 02 00 00 00 00 00      01:13:22.693  IDLE IMMEDIATE
  ec 00 01 00 00 00 00 00      01:13:22.692  IDENTIFY DEVICE
  e0 00 0a 00 00 00 00 00      00:47:41.793  STANDBY IMMEDIATE
  e1 00 02 00 00 00 00 00      00:47:33.392  IDLE IMMEDIATE
  ec 00 01 00 00 00 00 00      00:47:33.391  IDENTIFY DEVICE

Error 16 occurred at disk power-on lifetime: 20263 hours (844 days + 7 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
  -- -- -- -- -- -- --
  04 51 02 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e1 00 02 00 00 00 00 00      00:47:33.392  IDLE IMMEDIATE
  ec 00 01 00 00 00 00 00      00:47:33.391  IDENTIFY DEVICE
  b0 d0 00 00 4f c2 00 00      00:46:09.909  SMART READ DATA
  b0 d0 00 00 4f c2 00 00      00:42:00.272  SMART READ DATA

Error 15 occurred at disk power-on lifetime: 20263 hours (844 days + 7 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
  -- -- -- -- -- -- --
  04 51 02 00 00 00 00

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  e1 00 02 00 00 00 00 00      00:11:14.986  IDLE IMMEDIATE
  ec 00 01 00 00 00 00 00      00:11:14.985  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%     20424         136920880

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.


Edited by Lucky Dearly, 15 April 2016 - 01:27 PM.

  • 0

Advertisements


#11
Lucky Dearly

Lucky Dearly

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 294 posts

and here's the screenshots from testdisk

 

6p5gg3.jpg

 

fmjbzr.jpg

 

11t6a0p.jpg


  • 0

#12
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,752 posts

Did you run Recuva?

Did you backup drive D?


  • 0

#13
Lucky Dearly

Lucky Dearly

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 294 posts

yeah I was running recuva just now to backup all the family photos I got on the drive. I found this error when scanning the files on recuva "Failed to scan the following drives D:: unable to read MFT"

 

I also got a better look at the files while in recuva, all the files in the drive are marked with ? instead of the file names I had on them. Other than that the data is all there intact on the drive. just need to fix the filesystem


Edited by Lucky Dearly, 15 April 2016 - 05:17 PM.

  • 0

#14
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,752 posts

Looks like the Master File Table is corrupt.

Please wait for terry to instruct as I am not that good with TestDisk. 


  • 0

#15
Lucky Dearly

Lucky Dearly

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 294 posts

okay I'll wait then


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP