From: "Eric D. Mudama" <edmudama@gmail.com>
To: TJ <linux@tjworld.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"OGAWA Hirofumi" <hirofumi@mail.parknet.co.jp>,
"Neil Brown" <neilb@suse.de>
Subject: Re: [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions
Date: Thu, 1 Feb 2007 17:10:33 -0700 [thread overview]
Message-ID: <311601c90702011610t1cb75d67if3c40347f373d7ad@mail.gmail.com> (raw)
In-Reply-To: <1170373838.30201.45.camel@butch.lan.tjworld.net>
On 2/1/07, TJ <linux@tjworld.net> wrote:
> ---- short extract ---
> DC202XX: Primary channel reset.
> ide2: reset: success
> hde: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hde: task_in_intr: error=0x04 { DriveStatusError }
> ide: failed opcode was: unknown
> end_request: I/O error, dev hde, sector 238276076
> printk: 8 messages suppressed.
> Buffer I/O error on device hde2, logical block 47279294
> hde: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hde: task_in_intr: error=0x04 { DriveStatusError }
> ide: failed opcode was: unknown
> hde: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
...
> The Model number is Maxtor 6Y060L0.
In the log you posted, the drive posted 51/04 to your out-of-bounds
request, but these are 59/04, do they span the end of the device or
something?
I'd be surprised if the drive clunked because of an out of range
command, that model of drive used a very mature interface firmware
with many generations of testing and qualification.
next prev parent reply other threads:[~2007-02-02 0:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 23:50 TJ
2007-02-01 22:26 ` Andrew Morton
2007-02-01 22:47 ` Eric D. Mudama
2007-02-01 23:50 ` TJ
2007-02-02 0:10 ` Eric D. Mudama [this message]
2007-02-02 0:25 ` TJ
2007-02-01 1:50 TJ
[not found] <fa.vUjkpPQXmle+uox6D228qG85KCU@ifi.uio.no>
2007-02-01 4:20 ` Robert Hancock
2007-02-01 11:27 ` TJ
2007-02-01 19:12 ` Phillip Susi
2007-02-01 20:42 ` Alan
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=311601c90702011610t1cb75d67if3c40347f373d7ad@mail.gmail.com \
--to=edmudama@gmail.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@tjworld.net \
--cc=neilb@suse.de \
/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®