Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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/
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.
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?
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.
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?
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.
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.
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.
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 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
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
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
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
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.