On 07/21/2014 10:00 AM, Basil Chupin wrote:
On 22/07/14 00:18, Marguerite Su wrote:
Hi,
A few days ago suddenly I can't mount /root because:
2014-07-17T03:01:17.500184+08:00 linux kernel: [16528.736353] ata1.00: failed command: WRITE FPDMA QUEUED
2014-07-17T03:01:17.841313+08:00 linux kernel: [16529.077363] end_request: I/O error, dev sda, sector 59764644
After command completion occurred, registers were: ER ST SC SN CL CH DH
40 51 08 84 ef 8f e3 Error: UNC 8 sectors at LBA = 0x038fef84 = 59764612
1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 2847
But:
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
Google says it is the hardware problem, but after a reinstall, my computer still works...and actually the disk is less than 2 years old..
Error 19579 occurred at disk power-on lifetime: 12857 hours (535 days
- 17 hours) When the command that caused the error occurred, the device was active or idle.
Can anyone help judge this? Do I have to replace the disk?
Marguerite
I have not "here is the answer" answer to your question but let me say that I have had HDD fail on me on in less than 24 hours, with others failing anything between 24 hours and 3 years, while some still working fine even after 15 years.
"Youse buys your ticket and youse take your chances".
You don't mention what brand of HDD you have but that brand will have an app. from the manufacturer which will check out your drive for any possible failures.
And, of course, if you have 'smartmontools' installed then this will do same.
From the printouts above, smartctl is available, and a long disk surface test should be done soon. That will test the disk surfaces, read/write heads, and the circuitry that handles reading and writing. The parts that get minimal testing are the interface with the disk controller, the cable to the controller, and the adapter in your computer. My sense is that the error message arises from communication between the adapter and the computer.
The manufacturer's app will likely test the entire system. If this system is a desktop, an easy thing to do is to replace the cable. On a laptop, that is generally not possible. In any case, I would be sure to have backups and a spare drive. Larry -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org