From: Jens Axboe <axboe@suse.de>
To: Rick Jansen <rick@rockingstone.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DriveReady SeekComplete Error
Date: Fri, 4 Jun 2004 11:59:00 +0200 [thread overview]
Message-ID: <20040604095900.GO1946@suse.de> (raw)
In-Reply-To: <20040604095409.GL18885@web1.rockingstone.nl>
On Fri, Jun 04 2004, Rick Jansen wrote:
> On Fri, Jun 04, 2004 at 10:43:02AM +0100, John Bradford wrote:
> > Please post more information. First, what size is the disk?
> >
> > The LBAsect number suggests an access around 108 Gb. If the disk is smaller
> > than this, then it would appear that a request was made for a non-existant
> > sector.
> >
> > Is the LBAsect number the same in each error? What is the machine doing
> > when the errors occur?
> >
> > John.
>
> Here's some more information about the disk from the boot log.
> I also found some StatusErrors in there.
>
> May 10 11:14:07 web3 kernel: hda: Maxtor 6Y120P0, ATA DISK drive
> May 10 11:14:07 web3 kernel: hda: max request size: 128KiB
> May 10 11:14:07 web3 kernel: hda: 240121728 sectors (122942 MB)
> w/7936KiB Cache, CHS=65535/16/63, UDMA(133)
> May 10 11:14:07 web3 kernel: hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
> May 10 11:14:07 web3 kernel: hda: task_no_data_intr: status=0x51 {
> DriveReady SeekComplete Error }
> May 10 11:14:07 web3 kernel: hda: task_no_data_intr: error=0x04 {
> DriveStatusError }
> May 10 11:14:07 web3 kernel: hda: Write Cache FAILED Flushing!
>
> Thats a different error then what it gives me occasionaly. Googling this
> error lead me to believe this is a bug in the ide driver, that my disk
> doesnt support some flush command.
It is, what kernel are you using?
--
Jens Axboe
next prev parent reply other threads:[~2004-06-04 9:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 7:54 DriveReady SeekComplete Error Rick Jansen
2004-06-04 9:02 ` Daniel Egger
2004-06-04 9:38 ` John Bradford
2004-06-04 9:43 ` John Bradford
2004-06-04 9:54 ` Rick Jansen
2004-06-04 9:59 ` Jens Axboe [this message]
2004-06-04 10:02 ` Rick Jansen
2004-06-04 10:08 ` Jens Axboe
2004-06-04 13:02 ` Andy Hawkins
2004-06-04 13:41 ` Daniel Egger
2004-06-04 13:53 ` Rick Jansen
2004-06-04 14:05 ` John Bradford
2004-06-04 14:18 ` Rick Jansen
2004-06-04 19:32 ` Bruce Allen
2004-06-04 14:15 ` Daniel Egger
2004-06-04 14:09 ` John Bradford
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 10:15 mattia
2004-06-04 10:22 ` Jens Axboe
2004-06-04 11:44 ` Bartlomiej Zolnierkiewicz
2004-06-04 11:56 ` Jens Axboe
2004-06-04 12:15 ` Bartlomiej Zolnierkiewicz
2004-06-04 12:17 ` Jens Axboe
2004-06-04 12:40 ` Bartlomiej Zolnierkiewicz
2004-06-04 21:55 ` Ed Tomlinson
2004-06-04 19:58 ` Eric D. Mudama
2004-06-05 13:48 ` mattia
2004-07-13 12:30 Dhruv Matani
2004-07-13 12:32 ` Dwayne Rightler
[not found] ` <40F3D4AC.9050407@gardenali.biz>
2004-07-13 14:27 ` Dhruv Matani
2004-07-13 14:29 ` Dhruv Matani
2004-07-13 14:47 ` Dhruv Matani
2004-07-13 15:01 ` Bartlomiej Zolnierkiewicz
2004-07-13 12:44 Piszcz, Justin Michael
2004-07-13 15:57 ` Dwayne Rightler
2004-07-13 17:23 Piszcz, Justin Michael
2004-07-14 20:10 ` Dwayne Rightler
2004-07-15 4:08 ` Dhruv Matani
2004-07-26 14:32 ` Dhruv Matani
2004-07-26 14:51 ` Dwayne Rightler
2004-08-20 3:22 ` Dhruv Matani
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=20040604095900.GO1946@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rick@rockingstone.nl \
/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