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

External disk rescue


  • Please log in to reply
126 replies to this topic

#1 syl2013

syl2013

  • Members
  • 73 posts
  • OFFLINE
  •  
  • Local time:03:20 PM

Posted 28 January 2013 - 04:56 PM

Hi, I'm using ddrescue from a partedmagic bootable CD launched in RAM memory to make an image of a 1 TB (dev/sdd) external disk into another 1 TB (dev/sdc1) external disk. The partition editor shows me each of them have 931.51GB of total space. The disk from which I'm doing the image has probably damaged the boot and partition tables, as the file format is not recognized anymore (unable to determine fstype specify with -t).

The problem is that the rescue is never performed, and no rescuelog is written neither. When making the image of the entire disk and specifying to write the logfile in a different disk, in NTFS format, I get an error as follows:
Copying nont-tried blocks...

ddrescue: write error: No space left on device

The error doesn't spcify the device without space. But the disk for saving the image is new and empty. So I don't know if the error is due to a requirement of space concerning the logfile or additional space for making the image.

After getting this error, I tried to make an image of one of the partitions of the damaged disk and the error remains the same. But when I varied the destiny of the rescue logfile to a partition in the computer in fat32 the error changed to the following:

ddrescue: Error writing logfile: 'media/sdb2/rescuelog.log' : No space left on device

Does anybody knows the space requierements for making an image of a disk, for log and the image?

Any ideas on how to proceed and make the image is welcome.

Thanks in advance,

Silvia

BC AdBot (Login to Remove)

 


#2 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:20 AM

Posted 28 January 2013 - 05:34 PM

Hello Silvia. :welcome: to the BleepingComputer forums.

The only possible option available to you given the two 1TB hard drives is to clone one to the other:
  • In order to create an image of a 1TB hard drive, more space would be needed than what is available on the partition of a 1TB hard drive: A larger hard drive (and partition) would be required.
Is cloning an option for you? Did you have any particular reason to want to create an image (image file)?

With all your hardware connected, let's have a look at what is available. Please indicate which device is the intended source and which is the intended destination and the location where you intend to save the log file.

At the PartedMagic Desktop:
  • Open a terminal window:
    • Locate the black screen/monitor icon (ROXTerm) along the bar at the bottom of the Desktop screen (third icon from the left-side edge).
    • Click on the ROXTerm icon to open a terminal window.
  • At the prompt, type:

    fdisk -l

    Note: There is a space between "fdisk" and "-l".
    That is a lower case L as in Llama and not a ONE.

  • ... and press <ENTER>.
  • Drag your mouse over the output to select it all.
  • Right-click somewhere in the area selected > Copy
    (In the next step, you will paste this in a reply.)
Open Firefox (the Firefox icon is on the Desktop:
  • Hopefully you will have an internet connection already.
  • Go to www.bleepingcomputer.com/forums, sign in and find your topic.
  • Paste the output of fdisk -l in your reply.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#3 syl2013

syl2013
  • Topic Starter

  • Members
  • 73 posts
  • OFFLINE
  •  
  • Local time:03:20 PM

Posted 28 January 2013 - 08:33 PM

Hello, thank you.

I need to make the image for then recovering the files in the image and don't stress the damaged hard disk. Can you please tell me how much space do I need for this operation so I can get it?

The damaged disk (source) has 3 partitions [ dev/sdd1, dev/sdd2----(dev/sdd5, dev/sdd6) ], is it possible to make individual images and recover each of them with TestDisk individually? If so, what are the requirements or which is the proportion of space?

I have 46,3 GiB distributed in 5 partitions on the workstation and 62 GiB in the laptop. Both with 2GB in RAM.

If the cloning allows me to recover the files, is an option.

Best regards,

Silvia

Edited by syl2013, 28 January 2013 - 08:48 PM.


#4 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:20 AM

Posted 28 January 2013 - 08:46 PM

Cloning (using ddrescue) is certainly the way I would be going in your case. That would be an exact replica of the troubled hard drive. You could then attempt a repair/recovery on the cloned copy.

Re: the troubled hard drive ... "the damaged hard disk"
Do you have any reason to suspect a problem with the actual hard drive itself? Have you tested the hard drive or examined its condition?

Edited to add ... if you wanted to create an image file of the 1TB hard drive, I suggest that you would want to have a destination hard drive having a partition with at least 1.1TB of free space.

Edited by AustrAlien, 28 January 2013 - 09:31 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#5 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:20 AM

Posted 28 January 2013 - 09:03 PM

Let's have a look at the condition of "the damaged hard disk".

At the PartedMagic Desktop:
  • Double-click the Disk Health icon on the Desktop.
  • In the GSmartControl window that opens, double-click on the device that represents the hard drive.
  • In the Device Information window that opens, click View Output.
    A Smartctl Output window will open.
  • Right-click in the text output > Select All.
  • Right-click in the selected area > Copy.
In the next step you will paste this text into your topic reply.
At the PartedMagic Desktop:
  • Double-click on the Firefox icon to open the Firefox browser window.
  • Enter the BC forums address www.bleepingcomputer.com/forums in the address box and press <ENTER>.
  • Sign in to the forums and locate your topic.
  • Paste the text from the Smartctl Output window in a reply to your topic.

    Note: Please enclose the pasted report in CODE tags so that the spacing/formatting is preserved.
  • Firstly, click on the "Insert code snippet" button Posted Image
  • You will then see the "start" and "end" code tags (highlighted in dark blue/selected in the image) in the text box.
  • Click between the two tags to insert the cursor between the tags and then press <Ctrl+V> to paste the report there.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#6 syl2013

syl2013
  • Topic Starter

  • Members
  • 73 posts
  • OFFLINE
  •  
  • Local time:03:20 PM

Posted 28 January 2013 - 11:31 PM

Hello.

I suspect of the troubled disk because I was defragmenting it (the 3 partitions simultaneously) in Windows 7 and at the 68% of the defragmentation process of the last one the PC was blocked so I turned it off with the power button. After rebooting the disk wasn't recognized anymore.

I opened the Disk Health program but the disk has disabled the SMART option, if I enable it, is information exposed to any risk?

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MK..59GSM (AF)
Device Model:     TOSHIBA MK1059GSM
LU WWN Device Id: 5 000039 321c83a8d
Firmware Version: GL001U
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 1.5 Gb/s (current: 1.5 Gb/s)
Local Time is:    Mon Jan 28 22:05:33 2013 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Disabled

SMART Disabled. Use option -s with argument 'on' to enable it.
(override with '-T permissive' option)

Thanks.

Edited by syl2013, 28 January 2013 - 11:32 PM.


#7 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:20 AM

Posted 28 January 2013 - 11:50 PM

It does seem at this stage that the hard drive may have a problem. If the data on the problem hard drive is important to you, then I suggest you proceed to clone it firstly (create a backup of your important data) before doing anything else.

With a view to cloning, I would like to check the number of sectors on each of the source and the destination hard drives. To do this please post the output of fdisk -l (see post #2) with both external hard drives connected.

If you are willing and prepared to proceed with cloning, please identify both the source and destination hard drives clearly, and let me know where you intend saving a log (a flashdrive is always a good place for this). If you do this, I will be able to prepare the ddrescue command for you to use for the cloning operation.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#8 syl2013

syl2013
  • Topic Starter

  • Members
  • 73 posts
  • OFFLINE
  •  
  • Local time:03:20 PM

Posted 29 January 2013 - 12:18 AM

Yes I have to do the backup, that was my intention with the image creation and until now, it is, for the disk clonation.

This is the report of the troubled disk (source):

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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: 0x764f457e

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1   *          63   612365669   306182803+   b  W95 FAT32
/dev/sdd2       612365670  1953520064   670577197+   f  W95 Ext'd (LBA)
/dev/sdd5       612365733  1226755529   307194898+   b  W95 FAT32
/dev/sdd6      1226755593  1953520064   363382236    b  W95 FAT32

The report of the new disk for the backup (destiny):
Disk /dev/sdc: 1000.2 GB, 1000202043392 bytes
255 heads, 63 sectors/track, 121600 cylinders, total 1953519616 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: 0x0002846e

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1            2048  1953519615   976758784    7  HPFS/NTFS/exFAT

Workstation internal disks report:
Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 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: 0x8c308c30

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63   102398309    51199123+   7  HPFS/NTFS/exFAT
/dev/sda2       102398310   268414019    83007855    f  W95 Ext'd (LBA)
/dev/sda3       268414020   488392064   109989022+   7  HPFS/NTFS/exFAT
/dev/sda5       102398373   268414019    83007823+   7  HPFS/NTFS/exFAT

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 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: 0x8c618c61

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63   268414019   134206978+   7  HPFS/NTFS/exFAT
/dev/sdb2       268414020   309363704    20474842+   b  W95 FAT32
/dev/sdb3       309363705   488392064    89514180    7  HPFS/NTFS/exFAT

Edited by syl2013, 29 January 2013 - 12:24 AM.


#9 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:20 AM

Posted 29 January 2013 - 12:43 AM

Unfortunately the intended destination hard drive is smaller (has less sectors) than the source hard drive.
  • Disk /dev/sdd: total 1953525168 sectors <<< source
  • Disk /dev/sdc: total 1953519616 sectors >>> destination
I cannot guarantee that the cloning operation will be a success, and have to advise against trying it under the intended circumstance:
  • The destination (compared with the source) should have an equal or larger number of sectors.

Re: the troubled external hard drive
Can the troubled hard drive be conveniently removed from the enclosure?
  • It is always best to connect a troubled hard drive directly to the motherboard of a computer rather than attempt to access it via a USB adapter/connection for the purposes of diagnosis, recovery and repair ... if at all possible.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#10 syl2013

syl2013
  • Topic Starter

  • Members
  • 73 posts
  • OFFLINE
  •  
  • Local time:03:20 PM

Posted 29 January 2013 - 12:59 AM

Hi Austr Alien, thank you I'm going to find another disk and be back. Would you recomend me a disk please?

About opening the enclosure I don't think is easy, is an ADATA Classic CH94. I don't know how to open it and I will need the cable from the disk to the motherboard.

By the way, I run the disk health program to the internal disks and I found they have errors. And now I'm worried about them. If I post or attach the reports here can you help me with that too?

Best regards,

Silvia

Edited by syl2013, 29 January 2013 - 01:01 AM.


#11 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:20 AM

Posted 29 January 2013 - 01:05 AM

... I run the disk health program to the internal disks and I found they have errors. And now I'm worried about them. If I post or attach the reports here can you help me with that too?

Post them, yes. I'll have a look and let you know if there's anything you need be concerned about.

I'll post again shortly with suggestions for another hard drive suitable for cloning to.

Edited by AustrAlien, 29 January 2013 - 01:05 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#12 syl2013

syl2013
  • Topic Starter

  • Members
  • 73 posts
  • OFFLINE
  •  
  • Local time:03:20 PM

Posted 29 January 2013 - 01:13 AM

Hi, thank you I appreciate your help.

Here it is the health report of one of the internal disks:

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Deskstar T7K500
Device Model:     Hitachi HDT725025VLA380
LU WWN Device Id: 5 000cca 310d1e787
Firmware Version: V5DOA52A
User Capacity:    250,059,350,016 bytes [250 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA/ATAPI-7 T13/1532D revision 1
Local Time is:    Tue Jan 29 01:06:36 2013 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: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
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: 		( 4949) 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: 	 (  83) 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     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   109   109   024    Pre-fail  Always       -       344 (Average 344)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       1515
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       14
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       12528
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1504
192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       1924
193 Load_Cycle_Count        0x0012   099   099   000    Old_age   Always       -       1924
194 Temperature_Celsius     0x0002   133   133   000    Old_age   Always       -       45 (Min/Max 15/56)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       14
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       36
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   253   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 20462 (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 20462 occurred at disk power-on lifetime: 8783 hours (365 days + 23 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 05 60 9c 08 e8  Error: UNC 5 sectors at LBA = 0x08089c60 = 134782048

  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 08 5d 9c 08 e0 00      08:22:05.800  READ DMA EXT
  25 00 08 55 9c 08 e0 00      08:22:05.800  READ DMA EXT
  25 00 08 4d 9c 08 e0 00      08:22:05.800  READ DMA EXT
  25 00 18 81 79 d5 e0 00      08:22:05.800  READ DMA EXT
  25 00 08 45 9c 08 e0 00      08:22:05.800  READ DMA EXT

Error 20461 occurred at disk power-on lifetime: 8783 hours (365 days + 23 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 45 60 9c 08 e8  Error: UNC 69 sectors at LBA = 0x08089c60 = 134782048

  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 25 9c 08 e0 00      08:22:00.900  READ DMA EXT
  25 00 80 a5 9b 08 e0 00      08:22:00.900  READ DMA EXT
  25 00 80 25 9b 08 e0 00      08:22:00.900  READ DMA EXT
  25 00 80 a5 9a 08 e0 00      08:22:00.900  READ DMA EXT
  25 00 80 25 9a 08 e0 00      08:22:00.900  READ DMA EXT

Error 20460 occurred at disk power-on lifetime: 7321 hours (305 days + 1 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 c5 60 9c 08 e8  Error: UNC 197 sectors at LBA = 0x08089c60 = 134782048

  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 00 25 9c 08 e0 00      14:31:35.500  READ DMA EXT
  25 00 00 25 9b 08 e0 00      14:31:35.500  READ DMA EXT
  25 00 3e 7d db 04 e0 00      14:31:35.500  READ DMA EXT
  25 00 63 15 db 04 e0 00      14:31:35.500  READ DMA EXT
  25 00 13 f5 da 04 e0 00      14:31:35.500  READ DMA EXT

Error 20459 occurred at disk power-on lifetime: 7321 hours (305 days + 1 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 c5 60 9c 08 e8  Error: UNC 197 sectors at LBA = 0x08089c60 = 134782048

  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 00 25 9c 08 e0 00      14:31:30.600  READ DMA EXT
  25 00 00 25 9b 08 e0 00      14:31:30.600  READ DMA EXT
  25 00 2a c5 da 04 e0 00      14:31:30.500  READ DMA EXT
  25 00 15 ad da 04 e0 00      14:31:30.500  READ DMA EXT
  25 00 80 2d da 04 e0 00      14:31:30.500  READ DMA EXT

Error 20458 occurred at disk power-on lifetime: 6571 hours (273 days + 19 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 c5 60 9c 08 e8  Error: UNC 197 sectors at LBA = 0x08089c60 = 134782048

  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 00 25 9c 08 e0 00      14:25:32.400  READ DMA EXT
  25 00 00 25 9b 08 e0 00      14:25:32.400  READ DMA EXT
  25 00 00 25 9a 08 e0 00      14:25:32.400  READ DMA EXT
  25 00 00 1d 82 01 e0 00      14:25:32.400  READ DMA EXT
  25 00 08 1d 41 7d e0 00      14:25:32.400  READ DMA EXT

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%     12528         -

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.

The health report of the other internal disk:

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Deskstar T7K500
Device Model:     Hitachi HDT725025VLA380
LU WWN Device Id: 5 000cca 310d274bc
Firmware Version: V5DOA52A
User Capacity:    250,059,350,016 bytes [250 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA/ATAPI-7 T13/1532D revision 1
Local Time is:    Tue Jan 29 01:08:17 2013 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: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
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: 		( 4949) 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: 	 (  83) 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     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   108   108   024    Pre-fail  Always       -       345 (Average 345)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       1514
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   099   099   000    Old_age   Always       -       12520
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1502
192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       1936
193 Load_Cycle_Count        0x0012   099   099   000    Old_age   Always       -       1936
194 Temperature_Celsius     0x0002   133   133   000    Old_age   Always       -       45 (Min/Max 15/56)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   253   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 15 (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 15 occurred at disk power-on lifetime: 8640 hours (360 days + 0 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 ec 9b d7 df e2  Error: UNC 236 sectors at LBA = 0x02dfd79b = 48224155

  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 00 87 d7 df e0 00      09:01:24.900  READ DMA EXT
  25 00 00 87 d6 df e0 00      09:01:24.600  READ DMA EXT
  25 00 00 87 d5 df e0 00      09:01:18.900  READ DMA EXT
  25 00 00 87 d4 df e0 00      09:01:18.800  READ DMA EXT
  35 00 08 c7 4d 60 e0 00      09:01:18.800  WRITE DMA EXT

Error 14 occurred at disk power-on lifetime: 8640 hours (360 days + 0 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 19 6e d6 df e2  Error: UNC 25 sectors at LBA = 0x02dfd66e = 48223854

  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 00 87 d5 df e0 00      09:01:18.900  READ DMA EXT
  25 00 00 87 d4 df e0 00      09:01:18.800  READ DMA EXT
  35 00 08 c7 4d 60 e0 00      09:01:18.800  WRITE DMA EXT
  35 00 60 5f c0 5f e0 00      09:01:18.800  WRITE DMA EXT
  35 00 10 5f b2 68 e0 00      09:01:18.800  WRITE DMA EXT

Error 13 occurred at disk power-on lifetime: 8640 hours (360 days + 0 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 ec 9b d7 df e2  Error: UNC 236 sectors at LBA = 0x02dfd79b = 48224155

  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 00 87 d7 df e0 00      09:01:14.000  READ DMA EXT
  25 00 00 87 d6 df e0 00      09:01:13.200  READ DMA EXT
  25 00 00 87 d5 df e0 00      09:01:04.400  READ DMA EXT
  25 00 00 87 d4 df e0 00      09:01:04.300  READ DMA EXT
  25 00 00 87 d3 df e0 00      09:01:04.300  READ DMA EXT

Error 12 occurred at disk power-on lifetime: 8640 hours (360 days + 0 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 19 6e d6 df e2  Error: UNC 25 sectors at LBA = 0x02dfd66e = 48223854

  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 00 87 d5 df e0 00      09:01:04.400  READ DMA EXT
  25 00 00 87 d4 df e0 00      09:01:04.300  READ DMA EXT
  25 00 00 87 d3 df e0 00      09:01:04.300  READ DMA EXT
  25 00 00 87 d2 df e0 00      09:01:04.300  READ DMA EXT
  25 00 00 87 d1 df e0 00      09:01:04.300  READ DMA EXT

Error 11 occurred at disk power-on lifetime: 7317 hours (304 days + 21 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 19 6e d6 df e2  Error: UNC 25 sectors at LBA = 0x02dfd66e = 48223854

  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 00 87 d5 df e0 00      12:32:05.400  READ DMA EXT
  25 00 00 87 d4 df e0 00      12:32:05.300  READ DMA EXT
  25 00 80 df fd 8d e0 00      12:32:05.300  READ DMA EXT
  35 00 08 27 5f 60 e0 00      12:32:05.300  WRITE DMA EXT
  25 00 08 9f 4f 60 e0 00      12:32:05.300  READ DMA EXT

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%     12520         -

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.


#13 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:20 AM

Posted 29 January 2013 - 01:29 AM

Attributes relating to failing/failed sectors on the hard drive:
Device Model:     Hitachi HDT725025VLA380
LU WWN Device Id: 5 000cca 310d1e787
Firmware Version: V5DOA52A
User Capacity:    250,059,350,016 bytes [250 GB]

  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       14
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       14
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       36
Reference: http://en.wikipedia.org/wiki/S.M.A.R.T.

14 sectors have confirmed as "bad" and not to be used again, and their use replaced by spare sectors.
36 sectors have been reported to be troublesome/unreadable and are awaiting action (checking).

This hard drive is failing and should be replaced ASAP! :exclame:

The other hard drive appears to be OK. I notice you have run a Short Self-Test on it. Run the Long Self-Test and then post the report again.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#14 syl2013

syl2013
  • Topic Starter

  • Members
  • 73 posts
  • OFFLINE
  •  
  • Local time:03:20 PM

Posted 29 January 2013 - 01:35 AM

Ok. And errors are caused by power failures? Can I do something for a partial fix before replacing it?

#15 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:06:20 AM

Posted 29 January 2013 - 01:36 AM

... I'm going to find another disk and be back. Would you recomend me a disk please?

Unless you require the portability of a small (2.5") hard drive, I suggest the best option is a "desktop" (3.5") hard drive in an enclosure with its own power supply. I suggest a capacity of 1.5 or (if you wish to image instead of clone and also recover files to the same hard drive ?) 2TB would do nicely for the current purpose.

Another advantage of connecting hard drives directly to the motherboard (especially for imaging or cloning) is that you get data transfer at maximum speed, whereas using a USB connection slows things down a lot! For this, both source and destination hard drives would need to be connected directly to the motherboard.

It may be possible to disassemble the ADATA Classic CH94 and remove the hard drive. I googled "ADATA Classic CH94 disassembly" and it appears there is a youtube video there demonstrating disassembly but I have not looked at it.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users