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

Hard Drive failure, recovery partition visible, main inaccessible


  • This topic is locked This topic is locked
12 replies to this topic

#1 PCPeebrain

PCPeebrain

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:06:57 AM

Posted 29 December 2012 - 04:43 PM

I am trying to help my brother out by trying to get some data off his Dell Studio Laptop. The laptop was, we think, subject to a power surge during a lightening storm at night (router and neighbours router and computer taken out at same time)

Attempting to start the (Vista OS) laptop, you get the warning about imminent drive failure and to backup data, asking you to press F1 to continue. Doing so, you just get a black screen and nothing happens. I downloaded the Seatools app and booted from CD (it's a Samsung hard drive) and it didn't see the drive at all. I took the hard drive out and stuck it in my win7 PC. My PC hung at startup, would not start, hanging every time. I put it in a cradle and plugged it into the USB port when running. This time, it hung the PC for ages, but eventually came up with two partitions - Drive H - Dell Recovery (complete with used and free space correct) though inaccessible, and drive K - which it then brought an error up that disappeared to quick to read, saying it was no possible to mount.

repeated attempts, and I got a message saying ti was important to run a chkdsk /f - which I did. It got most of the way through, then said insufficient memory. Rebooting, I was now able to access the recovery partition, but still not the main partition.trying to access it resulted in 'k: is inaccesible, the parameter is incorrect.' I ran 'testdisk' on the advice of a friend and tried to remount. This partition no longer gives the unable to mount warning, it now just says I need to format the drive to use it. the 'freespace' and 'used space' are both zero. file format is blank.

Have I lost all hope of recovering any data from it? I've tried putting it back in my machine internally, still makes it hang so I can't use something like Captain Nero.

BC AdBot (Login to Remove)

 


#2 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:57 AM

Posted 29 December 2012 - 07:53 PM

Hi

We can make a boot CD that will allow us to take a closer look at the drive and maybe repair it.

Download the PartedMagic ISO for your computer (Click the orange DOWNLOAD button) ask me if you aren't sure.


Instructions for making a Boot CD/DVD
If you don't already have CD Writing software, download and install Infrarecorder
and place a blank CD in your CD writer then run Infrarecorder
Click WRITE IMAGE
Navigate to the PartedMagic ISO that you downloaded and click the OPEN button
Click the OK button and it should burn your CD. When it is done it will automatically eject the CD and you can close Infrarecorder, you can now use this CD to boot your computer.

Instructions For Booting From The CD
If you have any trouble booting from the CD let me know the manufacturer/model of your computer and I'll help.

When you boot the computer that has the bad drive connected to it with the PartedMagic CD that you made a menu will pop up, please select
1. Default Settings (Runs from RAM)

When it finishes booting you will notice that it looks kind of like a Windows desktop.

Check SMART status of drive
After PartedMagic loads, double-click the Disk Health icon on the desktop and then double-click the icon for your hard drive. Click on the PERFORM TESTS tab.
Make sure that the Test Type is set to Short Self-Test and click the EXECUTE button
I will need to know if it passed or not.
Next click the ERROR LOG tab and let me know if there are any entries and if there are let me know what the rows say.
Next select the ATTRIBUTES tab and let me know what the raw values are for the ID's 1, 5 and 197.
IF YOU CAN USE FIREFOX IN PARTEDMAGIC TO ACCESS THIS FORUM THEN YOU CAN SIMPLY POST THE LOG HERE THAT YOU GET BY CLICKING THE VIEW OUTPUT BUTTON

Check partitions with fdisk
At the bottom of the screen near the START button you will see a picture of a computer monitor. Click it to open a terminal window. In the terminal window type
fdisk -l
(that is fdisk SPACE DASH l as in Linux) and press ENTER
I want to see the information that it prints out. You can take a picture of the screen or use Firefox in PartedMagic to login here and copy and paste the results into your reply. As long as the text is legible, a picture will be fine.

In your reply I need to see...

  • Did it pass the Short Self-Test?
  • Any entries in the Error Log
  • The Attributes list (at least the RAW VALUES for ID's 1, 5 and 197 if you have to type them by hand in your reply)
  • The output of fdisk

There are more detailed instructions with pictures here

If you have any questions/problems, let me know.

The next tool we use will depend on the disk health results.
James

#3 PCPeebrain

PCPeebrain
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:06:57 AM

Posted 30 December 2012 - 01:51 PM

Hi James, many thanks for the help, it's seriously appreciated - going mad here!

Okay... Short self test executed, test result: Completed and reported thus, "Test Resutl: handling damage, check the self test log for more information"

Output file:


smartctl 6.0 2012-10-10 r3643 [i686-linux-3.6.10-pmagic] (local build)
Copyright © 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint M6
Device Model: SAMSUNG HM320JI
Serial Number: S19FJD0S402651
LU WWN Device Id: 5 0f0000 03196a403
Firmware Version: 2SS00_06
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: ATA8-ACS, ATA/ATAPI-7 T13/1532D revision 0
SATA Version is: SATA 2.5, 1.5 Gb/s
Local Time is: Sun Dec 30 18:34:56 2012 UTC
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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 128) The previous self-test completed having
a test element that failed and the
device is suspected of having handling
damage.
Total time to complete Offline
data collection: ( 111) 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 111) minutes.
SCT capabilities: (0x003f) 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 0x000f 001 001 051 Pre-fail Always FAILING_NOW 146050
3 Spin_Up_Time 0x0007 252 252 025 Pre-fail Always - 2687
4 Start_Stop_Count 0x0032 093 093 000 Old_age Always - 80020
5 Reallocated_Sector_Ct 0x0033 252 100 010 Pre-fail Always - 0
9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 4368
12 Power_Cycle_Count 0x0032 097 097 000 Old_age Always - 3466
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 2034
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 106
194 Temperature_Celsius 0x0022 139 103 000 Old_age Always - 33 (Min/Max 10/47)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 52379 (0 3)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 4714
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 23785
199 UDMA_CRC_Error_Count 0x0036 252 252 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x000a 252 252 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 24 (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 24 occurred at disk power-on lifetime: 4323 hours (180 days + 3 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
01 51 08 f8 a7 45 e2 Error: AMNF 8 sectors at LBA = 0x0245a7f8 = 38119416

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 f8 a7 45 e2 00 00:04:53.937 READ DMA
c8 00 f0 68 a8 45 e2 00 00:04:52.625 READ DMA
ec 00 00 00 00 00 a0 00 00:04:52.375 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:04:52.375 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 00:04:52.375 IDENTIFY DEVICE

Error 23 occurred at disk power-on lifetime: 4323 hours (180 days + 3 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
01 51 40 10 a8 43 e2 Error: AMNF 64 sectors at LBA = 0x0243a810 = 37988368

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 40 10 a8 43 e2 00 00:04:52.312 READ DMA
c8 00 20 f0 a7 43 e2 00 00:04:51.062 READ DMA
c8 00 20 a0 78 69 e5 00 00:04:51.062 READ DMA
c8 00 20 50 30 e6 e1 00 00:04:51.000 READ DMA
ec 00 00 00 00 00 a0 00 00:04:51.000 IDENTIFY DEVICE

Error 22 occurred at disk power-on lifetime: 4323 hours (180 days + 3 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
01 51 10 f0 a7 45 e2 Error: AMNF 16 sectors at LBA = 0x0245a7f0 = 38119408

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 10 f0 a7 45 e2 00 00:04:50.437 READ DMA
ec 00 00 00 00 00 a0 00 00:04:49.125 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:04:49.125 SET FEATURES [Set transfer mode]
ec 00 00 00 00 00 a0 00 00:04:49.125 IDENTIFY DEVICE

Error 21 occurred at disk power-on lifetime: 4323 hours (180 days + 3 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
01 51 40 28 a8 45 e2 Error: AMNF 64 sectors at LBA = 0x0245a828 = 38119464

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 40 28 a8 45 e2 00 00:04:49.062 READ DMA
c8 00 20 08 a8 45 e2 00 00:04:47.812 READ DMA
c8 00 08 00 a8 45 e2 00 00:04:47.812 READ DMA
c8 00 20 00 a8 e5 e1 00 00:04:47.812 READ DMA
c8 00 08 00 00 00 e0 00 00:04:22.437 READ DMA

Error 20 occurred at disk power-on lifetime: 4323 hours (180 days + 3 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
01 51 40 10 a8 43 e2 Error: AMNF 64 sectors at LBA = 0x0243a810 = 37988368

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 40 10 a8 43 e2 00 00:03:16.750 READ DMA
c8 00 20 f0 a7 43 e2 00 00:03:15.562 READ DMA
c8 00 20 a0 78 69 e5 00 00:03:15.562 READ DMA
c8 00 20 50 30 e6 e1 00 00:03:15.500 READ DMA
ec 00 00 00 00 00 a0 00 00:03:15.437 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: handling damage?? 00% 4368 0
# 2 Short offline Completed: handling damage?? 00% 4368 0
# 3 Short offline Completed: handling damage?? 00% 4368 0
# 4 Short offline Completed: handling damage?? 00% 4358 0
# 5 Short offline Completed: handling damage?? 00% 4323 0
# 6 Short offline Completed: handling damage?? 00% 4322 0
# 7 Short offline Completed: handling damage?? 00% 4321 0
# 8 Short offline Completed without error 00% 2 -
# 9 Short offline Completed without error 00% 0 -
#10 Short offline Interrupted (host reset) 20% 0 -

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Completed_handling_damage?? [00% left] (0-65535)
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.






Output from fdisk:

Welcome - Parted Magic (Linux 3.6.10-pmagic)

root@partedmagic:~# fdisk -l

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x20000000

Device Boot Start End Blocks Id System
/dev/sda1 63 369494 184716 de Dell Utility
/dev/sda2 370688 31827967 15728640 7 HPFS/NTFS/exFAT
/dev/sda3 * 31827968 625139711 296655872 7 HPFS/NTFS/exFAT

#4 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:57 AM

Posted 30 December 2012 - 04:05 PM

Good job.

The disk is showing the signs of a mechanical problem with either the heads or the armature that the heads are on. You may be able to recover some files from it but it is very close to requiring you to send it to a facility that can disassemble the drive in a proper environment with specialized tools in order for you to get your data.

Either way, the disk will need to be replaced. Now you need to go into data recovery mode.

Before we proceed I'd like to know how much data you need to recover. Do you need the whole thing like the Operating System and the Recovery partition or are you just trying to recover some specific files that are very important or irreplaceable?

Please don't try anything else with it until we come up with a suitable plan. It appears to be near permanent failure.

James

Edited by James Litten, 30 December 2012 - 04:05 PM.


#5 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:57 AM

Posted 30 December 2012 - 04:34 PM

I'm going to be starting a long job soon so let me post the technique you can try in order to recover important files.

USING A PARTEDMAGIC LINUX BOOT CD TO COPY FILES FROM A DRIVE

Sometimes when Windows won't see a disk drive it is still visible from Linux. This is mainly because Windows' drivers for mounting filesystems are more strict than Linux's. If there are a few files that are very important on the drive, you can try to copy them using this method before proceeding with a repair that may fail and make it much more difficult to recover the files.

Connect a good hard drive or USB flash stick to the computer with enough free space on it to hold all of the files that you want to recover.

Boot the computer that has the bad drive and the good drive or flash stick connected to it with the PartedMagic CD/USB that you made. A menu will pop up, please select
1. Default Settings (Runs from RAM)

Posted Image


When it finishes booting you will notice that it looks kind of like a Windows desktop. The button in the lower left works like the START button in Windows XP and allows you to select and run various programs or shutdown the computer. To make things easy, I'll just refer to this as the START button.

Click the MOUNT DEVICES button which is down by the START button.


Posted Image


You want to click the green MOUNT button next to the bad drive and the drive that you want to copy to.

FROM YOUR FDISK OUTPUT IT LOOKS LIKE YOUR DATA WILL BE ON SDA3

NOTE THE NAMES OF THE DRIVE NEXT TO THE UNMOUNT BUTTON (was MOUNT button before you clicked it) They should be something like /media/sda3 and /media/sdb1 (though yours may be different)

Posted Image

Once you have mounted both the bad drive and the new drive that we are copying to, you will notice that the File Manager window opened also when you clicked the MOUNT DEVICES button. In it you will see folders representing your drives. The File Manager window should be displaying the contents of the /media folder and your drives will be folders called sda3 and sdb1 (though yours may have different names that you got by looking next to the MOUNT button which should say UNMOUNT now).

Double click the folder for your bad drive and if you see your files and folders then simply select what you want to copy to the good drive and right-click and choose COPY. Then navigate to the folder that represents the drive you want to copy them to and right-click and choose PASTE just like if you were in Windows Explorer.

AUSTRALIEN HAS SUGGESTED OPENING A SECOND FILE MANAGER WINDOW SO YOU CAN SIMPLY DRAG AND DROP BETWEEN THE TWO I like that idea :)

After you are done, remove the CD and shutdown the computer
Click START>LOGOUT and choose SHUTDOWN THE COMPUTER and click OK.

Connect the external drive where you copied the files to a working computer and verify that they were properly copied.

Let us know if this worked or if you have any questions.

James

#6 PCPeebrain

PCPeebrain
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:06:57 AM

Posted 30 December 2012 - 05:46 PM

Hi James, basically all we need to get off the drives are a load of photo's and some important office files - a few word docs, excell docs etc.

I've just tried the method you noted above, unfortunately no joy! it takes a while trying to mount sda3, the comes up with:

ERRORS
Run: Mount/dev/sda3
Status: Finished with error (exit status 13)

ntfs_attr_pread failed:Input/output error
Failed to calculate free MFT recordds: Input/Output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
softRAID/fakeRAID hardware. In the first case run chkdsk/f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRaid/FakeRAID then first activate it
and mount a different device under the /dev/mapper/directory (e.g.
/dev/mapper/nvidia eahaabcc1). Pease see the 'dmraid' documentation
for more details.

Close


So no go on the simple route :(

#7 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:57 AM

Posted 30 December 2012 - 06:39 PM

Let's see if we can access the files from TestDisk.

Connect a good hard drive or USB flash stick to the computer with enough free space on it to hold all of the files that you want to recover.

Boot the computer that has the bad drive and the good drive or flash stick connected to it into PartedMagic again.

Mount ONLY the drive you are copying to using the MOUNT DEVICES button like I described in the previous post. Leave the mount devices and the file manager windows open, we'll be back to that.

Next open the Terminal window (the picture of the monitor down by the mount devices button in the lower left of the desktop).

IF ANY OF THESE STEPS FAIL THEN GO TO THE BOTTOM OF THIS POST AND FOLLOW THE INSTRUCTIONS FOR POSTING THE TESTDISK LOG FOR ME TO LOOK AT

In the terminal type
Type
testdisk
and press enter.
Choose CREATE and hit enter
Make sure that your bad disk is highlighted
Choose Proceed and hit enter
Select Intel and hit enter
Select Advanced and hit enter
Make sure that the correct partition is highlighted (it will probably be the one with a * next to it) and
Select List and hit enter

If you see your files and folders we can copy them from here.
There are directions at the bottom of the screen in TestDisk. I like to do a test first and try to copy just one file or folder to see if it works.

Select a file or folder that you'd like to try copying by highlighting it.
Press the colon key to select it
:
and then press upper case C to copy all selected files
SHIFT-C
Now it wants to know where to copy the file to.
Highlight the second line which is .. (two dots) and press the right arrow key and it will take you up a level.
Highlight the media folder and press the right arrow key.
You should see the disk that you mounted in there. It's probably called something like sdb1 (look at what it was called when you mounted it like /media/sdb1)
Highlight the sdb1 folder (or whatever your disk is called) and press the right arrow key.
Press
SHIFT-C
and it should copy the file there.
Leave everything open and look in the file manager window to verify that the file was copied. In the file manager window, look inside the folder for your mounted drive (sdb1 in our example but yours may be something else) and see if you see the file that you copied there. If it is there, go back to the TestDisk window and select more files and folders that you want to copy and when you choose to copy them it will put them on the drive you already chose.

Again, let us know if this works, you have any questions or if it does not work for you or you can't see the files on the bad drive.

IF IT DOES NOT WORK
Exit TestDisk and please post the contents of the testdisk.log here.
In the file manager look for the root folder in the lower left pane. Inside there you will find testdisk.log. Either open it and paste the contents here or save it to the drive you mounted and then use that in another computer to post it here. It is stored in RAM so once you turn off the computer it disappears unless you save it.

James

#8 PCPeebrain

PCPeebrain
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:06:57 AM

Posted 31 December 2012 - 08:57 AM

James, you're an absolute star - all the important files and photographs are transferring as we speak. Soon as they're done I shall exact my revenge on this hard drive with a very large hammer and much venting!

thanks again.

#9 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:57 AM

Posted 31 December 2012 - 11:46 AM

Great, I hope that you are able to get everything that you need.

Just a quick note about the specific error that your drive is showing.
AMNF (Address Mark Not Found) is an issue where a head in the hard drive can not determine where the tuning information at the beginning of a sector ends and where the data in the sector starts.

What happens is that when a drive head reads a sector on the hard drive, right before the data starts there is kind of a beep sound (not really but its the best anology I've got :) ) that tells the head "Hey, the data in this sector was written at this level so get ready to read it at the same level". That way the head can be prepared to detect the miniscule difference between the ones and zeroes represented by magnetic fields in the sector.

After this mythical 'beep' there is a special border that tells the heads "Hey, the beep is done, here comes the data." That border is the Data Address Mark and it is what is not found for some of your sectors.

For some reason, on some sectors your hard drive is not seeing that last message and can't clearly determine when the tuning beep stops and when the data starts.

What causes this? The Data Address Mark is the first real proof that a sector has been found by the head so the head could easily be trying to read a part of the platter that does not have a sector on it. Could be lots of other things too. Firmware errors preventing it from correctly reading data received by the head. Damage on the platter where it has lost some of its magnetism. Damage on the head making it unable to detect magnetism as well as it needs to. Damage to the drive that makes the head not line up with the tracks properly. I'm sure there are more possibilities :)

The reason that it is considered as "Completed_handling_damage??" handling damage is because these marks are written by the manufacturer and tested before shipping and aren't something that would be typically damaged by use of the drive.

James

#10 PCPeebrain

PCPeebrain
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:06:57 AM

Posted 31 December 2012 - 02:54 PM

Very interesting, thanks for the analogy, that's a lot easier to understand than the rather vague errors it throws up!

I guess that sort of damage could be consistent with an extreme power surge? the drive was running a full scan at the time of the surge from the lightening strike. It also blew his router, and a neighbours router and hard drive!

All important files are now recovered, so I shall be taking it apart shortly to have a poke around inside, see what goes on in there before I destroy it permanently :)

Thanks again for the help, I know my brother is extremely grateful too, although he's had a few lectures about backups...

#11 James Litten

James Litten

    Ԁǝǝ˥q


  • BC Advisor
  • 1,946 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:57 AM

Posted 31 December 2012 - 06:37 PM

Yep, an electrical event like that can definitely do it :)

James

#12 pleasepleasehelp

pleasepleasehelp

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:11:27 AM

Posted 09 September 2013 - 05:59 AM

James,

 

Hi, sorry for the lack of preamble and nicetiesEmoji_1F603.png

 

Am able to see the Folders and File on Seagate EDD but not able to access - have tried the following three methods that you have suggested

 

1. TESTDISK

http://html5.litten.com/how-to-fix-external-disk-drive-suddenly-became-raw/

 

I did the WRITE and rebooted in Windows, still unable to access EDD

Says H:\ is not accessible. The parameter is incorrect

 

 

2. http://www.bleepingcomputer.com/forums/t/481048/external-drive-showing-raw-data-after-removal-without-ejecting/

SMART test says Device Disabled, unable to run it

 

3, http://www.bleepingcomputer.com/forums/t/480044/hard-drive-failure-recovery-partition-visible-main-inaccessible/

Mounted EDD (bad drive) and partitioned HDD (good drive), able to copy from EDD but unable to paste as HDD shows "Read Only" by default

 

The above tells me I am very nearly there, need your hand holding :-)

 

Thanks

Arvind

 

p.S  - my starting point was

External Disk Drive RAW

I googled this and found you :-)

 

 

p.p.s

 

Here are some of the test logs

 

Disk /dev/sdd - 1000 GB / 931 GiB - CHS 121601 255 63
Analyse cylinder  3151/121600: 02%
Read error at 3150/254/63 (lba=50620814)

  HPFS - NTFS              0  32 33 121601  90 25 1953523712 [Seagate Backup Plus Drive]


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

Vendor:               Seagate 
Product:              Backup+ SL      
Revision:             0409
User Capacity:        1,000,204,885,504 bytes [1.00 TB]
Logical block size:   512 bytes
Logical Unit id:      0x41736d6564696120
Serial number:        NA5B2K30
Device type:          disk
Local Time is:        Mon Sep  9 20:40:29 2013 UTC
Device supports SMART and is Disabled
Temperature Warning Disabled or Not Supported
SMART Health Status: OK

Error Counter logging not supported
Device does not support Self Test logging




Compilation date: 2013-07-30T16:08:31
ext2fs lib: 1.42.8, ntfs lib: libntfs-3g, reiserfs lib: 0.3.0.5, ewf lib: none
/dev/sda: LBA, HPA, LBA48, DCO support
/dev/sda: size       312581808 sectors
/dev/sda: user_max   312581808 sectors
/dev/sda: native_max 312581808 sectors
/dev/sda: dco        312581808 sectors
/dev/sdb: LBA, HPA, LBA48, DCO support
/dev/sdb: size       312581808 sectors
/dev/sdb: user_max   312581808 sectors
/dev/sdb: native_max 312581808 sectors
/dev/sdb: dco        312581808 sectors
Warning: can't get size for Disk /dev/mapper/control - 0 B - 1 sectors, sector size=512
Hard disk list
Disk /dev/sda - 160 GB / 149 GiB - CHS 19457 255 63, sector size=512 - WDC WD1600BEVS-75RST0, S/N:WD-WXE108C58205, FW:04.01G04
Disk /dev/sdb - 160 GB / 149 GiB - CHS 19457 255 63, sector size=512 - WDC WD1600BEVS-75RST0, S/N:WD-WXE108553988, FW:04.01G04
Disk /dev/sdc - 1047 MB / 998 MiB - CHS 127 255 63, sector size=512 - JetFlash TS1GJF2B, FW:2.00
Disk /dev/sdd - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - Seagate Backup+ SL, FW:0409

Partition table type (auto): Intel
Disk /dev/sdd - 1000 GB / 931 GiB - Seagate Backup+ SL
Partition table type: Intel

Analyse Disk /dev/sdd - 1000 GB / 931 GiB - CHS 121601 255 63
Geometry from i386 MBR: head=255 sector=63
NTFS at 0/32/33
Current partition structure:
 1 * HPFS - NTFS              0  32 33 121601  90 25 1953523712 [Seagate Backup Plus Drive]

search_part()
Disk /dev/sdd - 1000 GB / 931 GiB - CHS 121601 255 63
NTFS at 0/32/33
filesystem size           1953523712
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               2
clusters_per_mft_record   -10
clusters_per_index_record 1
     HPFS - NTFS              0  32 33 121601  90 25 1953523712 [Seagate Backup Plus Drive]
     NTFS, blocksize=4096, 1000 GB / 931 GiB

Results
   * HPFS - NTFS              0  32 33 121601  90 25 1953523712 [Seagate Backup Plus Drive]
     NTFS, blocksize=4096, 1000 GB / 931 GiB
ntfs_device_testdisk_io_ioctl() unimplemented


dir_partition inode=5
   * HPFS - NTFS              0  32 33 121601  90 25 1953523712 [Seagate Backup Plus Drive]
     NTFS, blocksize=4096, 1000 GB / 931 GiB
Directory /
       5 dr-xr-xr-x     0      0         0  5-Sep-2013 06:06 .
       5 dr-xr-xr-x     0      0         0  5-Sep-2013 06:06 ..
   12626 dr-xr-xr-x     0      0         0  7-Aug-2013 10:24 $RECYCLE.BIN
   24907 dr-xr-xr-x     0      0         0 15-Aug-2013 17:09 AIIMS Award
   15651 dr-xr-xr-x     0      0         0 24-Jul-2013 23:34 APS format
   13631 dr-xr-xr-x     0      0         0  5-Sep-2013 06:01 Arvind
   13757 dr-xr-xr-x     0      0         0 30-Aug-2013 18:39 Book
   13568 dr-xr-xr-x     0      0         0 12-Jul-2013 17:04 Crisil powerpoint
   13969 dr-xr-xr-x     0      0         0 13-Aug-2013 08:43 DR SHASHI A
   15640 dr-xr-xr-x     0      0         0  7-Aug-2013 11:15 Downloads
   22138 dr-xr-xr-x     0      0         0 10-Jun-2013 06:31 Guruji photos
   13968 dr-xr-xr-x     0      0         0 27-May-2013 17:34 Handycam Uploaded Pics and Videos
   12750 dr-xr-xr-x     0      0         0 23-Feb-2013 17:39 MCQs
   24872 dr-xr-xr-x     0      0         0 13-Aug-2013 08:39 Music
   21700 dr-xr-xr-x     0      0         0 15-May-2013 07:08 Pratyusha Thesis
   22257 dr-xr-xr-x     0      0         0  8-Aug-2013 05:48 Publications
   21636 dr-xr-xr-x     0      0         0  8-Jun-2013 13:41 RECYCLER
   13570 dr-xr-xr-x     0      0         0 11-Jul-2013 18:52 Retinoblastoma
      37 dr-xr-xr-x     0      0         0  4-Aug-2012 13:51 Seagate
      87 dr-xr-xr-x     0      0         0 12-Dec-2012 20:07 Seagate Dashboard 2.0
   13612 dr-xr-xr-x     0      0         0  6-Jul-2013 19:01 Sebaceoma-for IJD-September 2012
   22329 dr-xr-xr-x     0      0         0 13-Aug-2013 08:28 Study material for Samir and Shradha
      85 dr-xr-xr-x     0      0         0  5-Apr-2013 14:05 System Volume Information
   13575 dr-xr-xr-x     0      0         0 23-Feb-2013 17:51 Traumatic Neuropathy
      43 dr-xr-xr-x     0      0         0  4-Aug-2012 13:51 Video
   13617 dr-xr-xr-x     0      0         0 23-Feb-2013 17:53 jaipur photos
   13604 dr-xr-xr-x     0      0         0 23-Feb-2013 17:52 ophthal nhl + ca
   15648 dr-xr-xr-x     0      0         0 16-Jul-2013 18:00 research projects
      35 -r--r--r--     0      0        32 17-Jul-2012 04:02 Autorun.inf
      36 -r--r--r--     0      0   1644118 26-Apr-2012 05:41 BackupPlus.ico
   24995 -r--r--r--     0      0  18858754 23-Aug-2013 21:27 Ophthalmology by Khurana 4th edition.pdf
      41 -r--r--r--     0      0  55565161  8-Jun-2012 01:31 Seagate Dashboard Installer.dmg
      42 -r--r--r--     0      0 152778464 10-Jul-2012 01:52 Seagate Dashboard Installer.exe

interface_write()
 1 * HPFS - NTFS              0  32 33 121601  90 25 1953523712 [Seagate Backup Plus Drive]

search_part()
Disk /dev/sdd - 1000 GB / 931 GiB - CHS 121601 255 63
NTFS at 0/32/33
filesystem size           1953523712
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               2
clusters_per_mft_record   -10
clusters_per_index_record 1
     HPFS - NTFS              0  32 33 121601  90 25 1953523712 [Seagate Backup Plus Drive]
     NTFS, blocksize=4096, 1000 GB / 931 GiB
Search for partition aborted

Results
   * HPFS - NTFS              0  32 33 121601  90 25 1953523712 [Seagate Backup Plus Drive]
     NTFS, blocksize=4096, 1000 GB / 931 GiB

interface_write()
 1 * HPFS - NTFS              0  32 33 121601  90 25 1953523712 [Seagate Backup Plus Drive]
simulate write!

write_mbr_i386: starting...
write_all_log_i386: starting...
No extended partition

TestDisk exited normally.


Edited by pleasepleasehelp, 09 September 2013 - 07:47 PM.


#13 hamluis

hamluis

    Moderator


  • Moderator
  • 55,874 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:57 AM

Posted 30 June 2014 - 04:08 PM

This topic is now closed.

 

If you are having hard drive problems and want to attempt to resolve such...please initiate a new topic in this forum, providing concise information that will help us to try to help you.

 

Thanks :).

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users