mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Kernel Testers List <kernel-testers@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: hdb: status error: error=0x40 <3>{ UncorrectableError }
Date: Mon, 26 Jan 2009 02:40:42 +0530	[thread overview]
Message-ID: <3f9a31f40901251310g38ecfe61t97e119533215d271@mail.gmail.com> (raw)
In-Reply-To: <497CD30D.80203@tmr.com>

On Mon, Jan 26, 2009 at 2:31 AM, Bill Davidsen <davidsen@tmr.com> wrote:
>
>
> Alan Cox wrote:
>>
>> On Mon, 26 Jan 2009 02:09:56 +0530
>> Jaswinder Singh Rajput
>> <jaswinderlinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>
>>> Hello all,
>>>
>>> I added extra IDE drive I get similar messages like below so I replace
>>> it another drive but I am still getting similar error messages on
>>> 2.6.29-rc2-tip:
>>>
>>> hdb: status error: status=0x59 { DriveReady SeekComplete DataRequest
>>> Error }
>>> hdb: status error: error=0x40 <3>{ UncorrectableError },
>>> LBAsect=208845, sector=0
>>
>> Uncorrectable Error is an error from the drive, not the kernel. Looks
>> like you have bad sectors on that drive.
>>
> He noted that he tried another drive, so unless he has a pile of bad drives
> it's probably something else. Being "hdb" may indicate that it's connected
> to the same controller as "hda" and might not be jumpered for slave. Or it
> might be a bad cable, a controller which doesn't like two drives, a dubious
> power connector, etc. Or if he doesn't have an hda, perhaps the kernel
> doesn't like a secondary drive without a primary.
>
> Being hdb instead of sdb with a new kernel indicates he is using a config
> which may get a lot less testing these days, perhaps?
>
> In any case, I doubt he had two bad drives, so something else is more
> likely.
>

But earlier both was working fine on some another machines.

--
JSR

  reply	other threads:[~2009-01-25 21:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-25 20:39 Jaswinder Singh Rajput
2009-01-25 20:46 ` Alan Cox
2009-01-25 21:01   ` Bill Davidsen
2009-01-25 21:10     ` Jaswinder Singh Rajput [this message]
2009-01-25 21:49       ` Bartlomiej Zolnierkiewicz
2009-01-25 21:55         ` Bartlomiej Zolnierkiewicz
     [not found]         ` <3f9a31f40901252031l3bb0ec39nd077ff8f13df73bd@mail.gmail.com>
2009-01-26  5:30           ` Jaswinder Singh
2009-01-26  5:40             ` Jaswinder Singh
2009-01-26  8:43               ` Jaswinder Singh Rajput
     [not found]             ` <D4601E4C-56E9-4701-A36B-0E07A7437381@usgs.gov>
2009-01-26  6:39               ` [Rocks-Discuss] " Jaswinder Singh Rajput
     [not found]             ` <A2A0D2B1-F9AB-4CB2-AFB1-F341ADBAB959@usgs.gov>
2009-01-26 12:02               ` Alan Cox
2009-01-25 20:46 ` strawks
2009-01-25 21:02   ` Jaswinder Singh Rajput

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=3f9a31f40901251310g38ecfe61t97e119533215d271@mail.gmail.com \
    --to=jaswinderlinux@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davidsen@tmr.com \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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

all inboxes | Powered by JetHome®