LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Hard disk failing?? (https://www.linuxquestions.org/questions/linux-hardware-18/hard-disk-failing-4175454509/)

alaios 03-18-2013 06:29 AM

Hard disk failing??
 
Dear all,
in the last days I am having a problem with my hard disk. I guess this only windows (ntfs specific) as my linux works just great.

In the last days the windows have a lot of problems reading from the hard disks and when booting up windows are calling for scandisks. Indeed problems are found and fixed. As I was concerned regarding the files there, I have already finished the backups.

I would like to ask your help for some decent tool that can examine the hard disk and see what is going on in the low level (bad sectors?). This program should support ntfs partitions and being able to not mess up with my ext4-linux partitions.

I would like to thank you in advance for your help


Regards
Alex

#root 03-18-2013 07:43 AM

you must be using Segate hard drive

alaios 03-18-2013 07:51 AM

Thanks. my Yast reports it as
WD3200 so I guess it is a Western Digital

#root 03-18-2013 07:59 AM

hmm LOL ok but the above mentioned problem is common with segate

any ways.......you may try EaseUs

nagabhushan 03-18-2013 08:14 AM

use "fsck" command

H_TeXMeX_H 03-18-2013 08:20 AM

You should run a SMART long test on the drive, it also checks for bad blocks.

You can do this with 'smartctl -t long /dev/sda' or you can use one of the manufacturer's tools most of which are on the ubcd:
http://www.ultimatebootcd.com/

allend 03-18-2013 09:02 AM

Personally, I would just accept that the drive needs to be replaced. Minimise use and get a replacement. Stressing the drive with a disk test is unlikely to help.

alaios 03-18-2013 05:26 PM

Quote:

Originally Posted by allend (Post 4913869)
Personally, I would just accept that the drive needs to be replaced. Minimise use and get a replacement. Stressing the drive with a disk test is unlikely to help.

How can you be sure for that and how can you explain that the problem looks to be hitting only the ntfs partition?

allend 03-18-2013 05:51 PM

In my experience, Windows has sophisticated algorithms for maintaining the NTFS file system. If you are starting to see errors that Windows needs to recover from, then it suggests that deterioration of areas of the disk is occurring. That it is only happening on your NTFS partition may be due to the quality of the disk surface in that area, or perhaps a developing fault in the electronics that drive the head to that area of the disk.

alaios 03-18-2013 06:16 PM

Can it be also something else? This hard disk is in a three years old laptop and I wonder if I should replace the hard disk or sell it as second-hand in ebay and buy a new one?

What hard disk alternatives can a three years old laptop support. Can it support any 1TB hard disk like
http://www.amazon.de/Western-Digital...637838&sr=1-13


Smart output also given here
http://imageshack.us/photo/my-images/442/smarts.png/

allend 03-18-2013 07:26 PM

Your SMART output shows that the reallocated sector count has exceeded the threshold as well as a high multizone error count, consistent with the problem you are reporting.

rknichols 03-18-2013 10:14 PM

Quote:

Originally Posted by allend (Post 4914158)
Your SMART output shows that the reallocated sector count has exceeded the threshold as well as a high multizone error count, consistent with the problem you are reporting.

A problem is indicated when the current value is below the threshold. High numbers in the "Value" column are good.

allend 03-19-2013 12:12 AM

From http://en.wikipedia.org/wiki/S.M.A.R.T.
Quote:

Reallocated Sectors Count
The raw value normally represents a count of the bad sectors that have been found and remapped. Thus, the higher the attribute value, the more sectors the drive has had to reallocate. This allows a drive with bad sectors to continue operation; however, a drive which has had any reallocations at all is significantly more likely to fail in the near future.[
and
Quote:

Multi-Zone Error Rate
The count of errors found when writing a sector. The higher the value, the worse the disk's mechanical condition is.

alaios 03-19-2013 02:13 AM

I am confused is my hard disk at bad state or not??

alaios 03-19-2013 02:19 AM

This comes from linux smart
Quote:

smartctl -a /dev/sda
smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.1.10-1.16-default] (SUSE RPM)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Scorpio Blue Serial ATA
Device Model: WDC WD3200BEVT-22ZCT0
Serial Number: WD-WXF0A99P7681
LU WWN Device Id: 5 0014ee 20375eb73
Firmware Version: 11.01A11
User Capacity: 320,072,933,376 bytes [320 GB]
Sector Size: 512 bytes logical/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.5, 3.0 Gb/s
Local Time is: Tue Mar 19 08:17:11 2013 EET
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: ( 9960) 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: ( 118) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303f) 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 0x002f 198 198 051 Pre-fail Always - 23359
3 Spin_Up_Time 0x0027 184 183 021 Pre-fail Always - 1758
4 Start_Stop_Count 0x0032 096 096 000 Old_age Always - 4244
5 Reallocated_Sector_Ct 0x0033 186 186 140 Pre-fail Always - 111
7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0
9 Power_On_Hours 0x0032 090 090 000 Old_age Always - 7379
10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail 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 - 3402
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 75
193 Load_Cycle_Count 0x0032 124 124 000 Old_age Always - 228553
194 Temperature_Celsius 0x0022 114 074 000 Old_age Always - 33
196 Reallocated_Event_Count 0x0032 184 184 000 Old_age Always - 16
197 Current_Pending_Sector 0x0032 198 198 000 Old_age Always - 112
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 0x0009 100 253 051 Pre-fail Offline - 0

SMART Error Log Version: 1
ATA Error Count: 22858 (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 22858 occurred at disk power-on lifetime: 7374 hours (307 days + 6 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 2c 7f e4 40 Error: WP at LBA = 0x00e47f2c = 14974764

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 10 e8 29 7c 01 00 03:46:29.525 WRITE FPDMA QUEUED
61 08 08 98 28 7a 01 00 03:46:29.524 WRITE FPDMA QUEUED
61 08 f0 68 3f 53 06 00 03:46:29.524 WRITE FPDMA QUEUED
61 08 c8 a8 b4 81 01 00 03:46:29.524 WRITE FPDMA QUEUED
61 08 b0 b8 29 7c 01 00 03:46:29.524 WRITE FPDMA QUEUED

Error 22857 occurred at disk power-on lifetime: 7374 hours (307 days + 6 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 2c 7f e4 40 Error: UNC at LBA = 0x00e47f2c = 14974764

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 28 80 08 7f e4 24 00 03:46:25.969 READ FPDMA QUEUED
60 40 78 ba 80 91 12 00 03:46:25.969 READ FPDMA QUEUED
60 80 70 60 68 25 0e 00 03:46:25.969 READ FPDMA QUEUED
61 03 68 60 36 a3 09 00 03:46:25.969 WRITE FPDMA QUEUED
60 40 60 10 cb e8 01 00 03:46:25.969 READ FPDMA QUEUED

Error 22856 occurred at disk power-on lifetime: 7374 hours (307 days + 6 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 2c 7f e4 40 Error: WP at LBA = 0x00e47f2c = 14974764

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 18 a0 28 7a 01 00 03:46:22.588 WRITE FPDMA QUEUED
61 08 10 b0 32 7b 01 00 03:46:22.588 WRITE FPDMA QUEUED
61 08 08 90 28 7a 01 00 03:46:22.587 WRITE FPDMA QUEUED
61 08 00 98 28 7a 01 00 03:46:22.587 WRITE FPDMA QUEUED
61 01 f8 c8 d8 ff 02 00 03:46:22.586 WRITE FPDMA QUEUED

Error 22855 occurred at disk power-on lifetime: 7374 hours (307 days + 6 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 2c 7f e4 40 Error: UNC at LBA = 0x00e47f2c = 14974764

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 28 80 08 7f e4 24 00 03:46:19.106 READ FPDMA QUEUED
60 38 78 3a 80 91 12 00 03:46:19.105 READ FPDMA QUEUED
60 80 70 10 67 25 0e 00 03:46:19.105 READ FPDMA QUEUED
60 20 68 40 36 dd 01 00 03:46:19.105 READ FPDMA QUEUED
60 38 60 62 e0 86 01 00 03:46:19.105 READ FPDMA QUEUED

Error 22854 occurred at disk power-on lifetime: 7374 hours (307 days + 6 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 2c 7f e4 40 Error: UNC at LBA = 0x00e47f2c = 14974764

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 40 0e 07 a7 01 00 03:46:15.868 READ FPDMA QUEUED
61 08 38 a0 28 7a 01 00 03:46:15.868 WRITE FPDMA QUEUED
60 1b 30 16 07 a7 01 00 03:46:15.868 READ FPDMA QUEUED
61 08 28 98 32 7b 01 00 03:46:15.867 WRITE FPDMA QUEUED
60 28 20 08 7f e4 24 00 03:46:15.867 READ FPDMA QUEUED

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 60% 7378 31108065

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.



All times are GMT -5. The time now is 06:55 PM.