lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <497CD30D.80203@tmr.com>
Date:	Sun, 25 Jan 2009 16:01:01 -0500
From:	Bill Davidsen <davidsen@....com>
To:	Alan Cox 
	<public-alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@...h.gmane.org>
CC:	Jaswinder Singh Rajput 
	<public-jaswinderlinux-Re5JQEeQqe8AvxtiuMwx3w@...h.gmane.org>,
	Kernel Testers List 
	<public-kernel-testers-u79uwXL29TY76Z2rM5mHXA@...h.gmane.org>,
	linux-kernel 
	<public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@...h.gmane.org>,
	"Rafael J. Wysocki" <public-rjw-KKrjLPT3xs0@...h.gmane.org>,
	James Bottomley 
	<public-James.Bottomley-JuX6DAaQMKPCXq6kfMZ53/egYHeGw8Jk@...h.gmane.org>
Subject: Re: hdb: status error: error=0x40 <3>{ UncorrectableError }



Alan Cox wrote:
> On Mon, 26 Jan 2009 02:09:56 +0530
> Jaswinder Singh Rajput <jaswinderlinux-Re5JQEeQqe8AvxtiuMwx3w@...lic.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.

-- 
Bill Davidsen <davidsen@....com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ