public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Buffer I/O error on device hdg1, system freeze.
Date: Fri, 18 Mar 2005 23:53:56 -0600	[thread overview]
Message-ID: <423BBE74.1060902@shaw.ca> (raw)
In-Reply-To: <3JuoL-3Mm-3@gated-at.bofh.it>

Nils Radtke wrote:
> Error 14 occurred at disk power-on lifetime: 2249 hours (93 days + 17
> hours)
>   When the command that caused the error occurred, the device was doing
> SMART Offline or Self-test.
> 
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 51 f8 23 3e 56 e0  Error: UNC at LBA = 0x00563e23 = 5652003
> 
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   24 00 f8 07 3e 56 10 00      00:36:28.850  READ SECTOR(S) EXT
>   25 00 00 ff 3d 56 10 00      00:36:28.850  READ DMA EXT
>   25 00 00 ff 3c 56 10 00      00:36:28.850  READ DMA EXT
>   25 00 00 ff 3b 56 10 00      00:36:28.850  READ DMA EXT
>   25 00 00 ff 3a 56 10 00      00:36:28.850  READ DMA EXT
> 
> 
> Could you please explain what these errors mean exactly and what may
> have caused them?
> 
> Might it be possible that these transmission/xxx errors be caused 
> by a bad card and/or driver?
> 
> I'm asking this as the disk never showed errors on onboard IDE ports.
> 
>         Nils
> 

This error is reported by the drive itself, indicating uncorrectable 
errors when attempting to read data from the media. It is quite unlikely 
that the controller or driver is responsible for this sort of error, as 
can occasionally be the case for DMA timeout errors. Almost certainly 
the hard drive is failing.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2005-03-19  5:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3JrTL-1C4-23@gated-at.bofh.it>
     [not found] ` <3JtCc-35h-21@gated-at.bofh.it>
     [not found]   ` <3JuoL-3Mm-3@gated-at.bofh.it>
2005-03-19  5:53     ` Robert Hancock [this message]
2005-03-18 15:29 PROBLEM: Buffer I/O error on device hdg1, system freeze lkml
2005-03-18 17:29 ` Bartlomiej Zolnierkiewicz
2005-03-18 18:25   ` Nils Radtke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=423BBE74.1060902@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox