[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Does "I/O error" mean hardware problem?





On Mon, Nov 22, 2010 at 2:26 PM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
Yuwen Dai put forth on 11/21/2010 11:44 PM:
> Dear all,
>
> My Debian Lenny constantly reports "disk I/O error on block xxxxxxx" when
> booting, then it runs e2fschk and reports some files are missing. I'd
> formated the partition but the problem still occurs.  The hardware is an
> Dell E6400 which has a Diagnostic tool.  I'd run the tool, but it said
> there's no error on the hard disk.  The Dell tech support says if the
> diagnostic tool doesn't report error, that means hard disk is OK.  So I have
> no proof that it's a hardware problem.  But the Linux filesystem(ext3) keeps
> corrupt, which is terrible.  Do you have any suggestion?

The output from

~# smartctl -a /dev/sdX

would be helpful.

Hi stan,

The output of smartctl -a /dev/sda is:

=== START OF INFORMATION SECTION ===
Device Model:     TOSHIBA MK2556GSYF
Serial Number:    409JT12DT
Firmware Version: LJ001D
User Capacity:    250,059,350,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Tue Nov 23 09:38:41 2010 CST
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
...

...
 Error 472 occurred at disk power-on lifetime: 1512 hours (63 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 41 02 ea d5 8b 40

  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 00 ea d5 8b 40 00      00:27:35.521  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      00:27:35.518  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      00:27:35.517  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 00      00:27:35.517  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      00:27:35.517  READ NATIVE MAX ADDRESS EXT

Error 471 occurred at disk power-on lifetime: 1512 hours (63 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.
...

Is this meaningful?

Best regards,
Yuwen

 
--
Stan



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] 4CEA0D00.90605@hardwarefreak.com" target="_blank">http://lists.debian.org/[🔎] 4CEA0D00.90605@hardwarefreak.com



Reply to: