From: Matt Domsch <Matt_Domsch@dell.com>
To: Kit Gerrits <kit@gerritsacc.nl>
Cc: "'Salyzyn, Mark'" <mark_salyzyn@adaptec.com>, linux-scsi@vger.kernel.org
Subject: Re: Disk errors
Date: Mon, 31 Jan 2005 17:55:24 -0600 [thread overview]
Message-ID: <20050131235524.GE24164@lists.us.dell.com> (raw)
In-Reply-To: <20050131233655.0990DC4@frisbee.gerritsacc.nl>
On Tue, Feb 01, 2005 at 12:41:13AM +0100, Kit Gerrits wrote:
> But if the PERC (controller) handles disk errors, what could cause:
>
> I/O Error Dev 08:05 Sector 529712
>
> I would assume that this error is generated by the harddrive, but shouldn't
> the controller catch SCSI errors (and relocate sectors automagically)?
In this case, the RAID controller is reporting the I/O error. It may
be that you've got bad sectors on more than one physical disk, in the
same stripe, and the RAID controller can't fix them.
Thanks,
Matt
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2005-01-31 23:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 18:21 Disk errors Salyzyn, Mark
2005-01-31 23:41 ` Kit Gerrits
2005-01-31 23:55 ` Matt Domsch [this message]
2005-02-01 2:05 ` Guy
-- strict thread matches above, loose matches on Subject: below --
2005-02-02 14:12 Disk Errors Salyzyn, Mark
2005-02-03 8:18 ` Andi Kleen
2005-02-15 5:56 ` Douglas Gilbert
2005-02-01 18:24 Salyzyn, Mark
2005-02-02 3:55 ` Douglas Gilbert
2005-02-03 18:50 ` Bryan Henderson
2005-02-01 15:56 Cress, Andrew R
2005-02-01 12:50 Salyzyn, Mark
2005-02-01 8:53 Kit Gerrits
2005-02-01 12:43 ` Douglas Gilbert
2005-02-01 18:01 ` Bryan Henderson
2005-01-31 17:11 Disk errors Cress, Andrew R
[not found] <60807403EABEB443939A5A7AA8A7458BB51FD1@otce2k01.adaptec.com>
2005-01-31 16:43 ` Kit Gerrits
2005-01-31 14:46 Cress, Andrew R
2005-01-31 15:22 ` Kit Gerrits
2005-01-31 14:27 Kit Gerrits
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=20050131235524.GE24164@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=kit@gerritsacc.nl \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.