From: "David M. Strang" <dstrang@shellpower.net>
To: Forrest Taylor <ftaylor@redhat.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: raid5: Disk failure on sdm, disabling device
Date: Wed, 31 Aug 2005 17:01:07 -0400 [thread overview]
Message-ID: <00ab01c5ae6f$1bb27410$c100a8c0@NCNF5131FTH> (raw)
In-Reply-To: 1125521616.3194.22.camel@x1-6-00-0d-60-fd-e8-4c
On Wed, 2005-08-31 at 14:55, Forrest Taylor wrote:
>On Wed, 2005-08-31 at 14:45, David M. Strang wrote:
>> > On Wed, 2005-08-31 at 14:39, Forrest Taylor wrote:
>> > If you are running 2.4 kernel, did you try running rescan-scsi-bus.sh
>> > (http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh)?
>>
>> uname -ar
>> Linux abyss 2.6.11.12 #2 SMP Thu Jul 21 07:49:40 UTC 2005 i686 unknown
>> unknown GNU/Linux
>>
>> Will it work on 2.6?
>
> I thought that it was integrated into 2.6 kernels (I guess that I was
> wrong). In the header of the file, Kurt says that he tested in on a
> 2.6.11 kernel, so I assume that it would work on a 2.6 kernel ;o)
OK, well - ignore my moron attack on the previous reply; I adjusted it to
scan for 30 ids, instead of just 7.
Host adapter 0 (aic7xxx) found.
Host adapter 1 (aic7xxx) found.
Host adapter 2 (qla2xxx) found.
Scanning hosts 0 1 2 channels 0 for
SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
23 24 25 26 27 28 29 30 , LUNs 0
Scanning for device 1 0 6 0 ....
OLD: Host: scsi1 Channel: 00 Id: 06 Lun: 00
Vendor: HP Model: Ultrium 1-SCSI Rev: E34A
Type: Sequential-Access ANSI SCSI revision: 03
Scanning for device 2 0 0 0 ....
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 1 0 ...
OLD: Host: scsi2 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 2 0 ...
OLD: Host: scsi2 Channel: 00 Id: 02 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 3 0 ...
OLD: Host: scsi2 Channel: 00 Id: 03 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 4 0 ...
OLD: Host: scsi2 Channel: 00 Id: 04 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 5 0 ...
OLD: Host: scsi2 Channel: 00 Id: 05 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 6 0 ...
OLD: Host: scsi2 Channel: 00 Id: 06 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 7 0 ...
OLD: Host: scsi2 Channel: 00 Id: 07 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 8 0 ...
OLD: Host: scsi2 Channel: 00 Id: 08 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 9 0 ...
OLD: Host: scsi2 Channel: 00 Id: 09 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 10 0 ...
OLD: Host: scsi2 Channel: 00 Id: 10 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 11 0 ...
OLD: Host: scsi2 Channel: 00 Id: 11 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 12 0 ...
OLD: Host: scsi2 Channel: 00 Id: 12 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 13 0 ...
OLD: Host: scsi2 Channel: 00 Id: 13 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 14 0 ...
OLD: Host: scsi2 Channel: 00 Id: 14 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 15 0 ...
OLD: Host: scsi2 Channel: 00 Id: 15 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 16 0 ...
OLD: Host: scsi2 Channel: 00 Id: 16 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 17 0 ...
OLD: Host: scsi2 Channel: 00 Id: 17 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 18 0 ...
OLD: Host: scsi2 Channel: 00 Id: 18 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 19 0 ...
OLD: Host: scsi2 Channel: 00 Id: 19 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 20 0 ...
OLD: Host: scsi2 Channel: 00 Id: 20 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 21 0 ...
OLD: Host: scsi2 Channel: 00 Id: 21 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 22 0 ...
OLD: Host: scsi2 Channel: 00 Id: 22 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 23 0 ...
OLD: Host: scsi2 Channel: 00 Id: 23 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 24 0 ...
OLD: Host: scsi2 Channel: 00 Id: 24 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 25 0 ...
OLD: Host: scsi2 Channel: 00 Id: 25 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 26 0 ...
OLD: Host: scsi2 Channel: 00 Id: 26 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Scanning for device 2 0 27 0 ...
OLD: Host: scsi2 Channel: 00 Id: 27 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
0 new device(s) found.
0 device(s) removed.
It sees the device in question:
Scanning for device 2 0 12 0 ...
OLD: Host: scsi2 Channel: 00 Id: 12 Lun: 00
Vendor: SEAGATE Model: ST373405FC Rev: DF00
Type: Direct-Access ANSI SCSI revision: 03
Is there something a little deeper to this error message?
Aug 31 04:48:15 abyss kernel: scsi2 (12:0): rejecting I/O to offline device
Aug 31 04:48:15 abyss kernel: raid5: Disk failure on sdm, disabling device.
-- David
next prev parent reply other threads:[~2005-08-31 21:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 19:26 raid5: Disk failure on sdm, disabling device David M. Strang
2005-08-31 19:28 ` Forrest Taylor
2005-08-31 19:38 ` David M. Strang
2005-08-31 19:29 ` Michael Tokarev
2005-08-31 19:41 ` David M. Strang
2005-08-31 20:07 ` Michael Tokarev
2005-08-31 20:28 ` David M. Strang
2005-08-31 20:35 ` Michael Tokarev
2005-08-31 20:39 ` Forrest Taylor
2005-08-31 20:45 ` David M. Strang
2005-08-31 20:53 ` David M. Strang
2005-08-31 20:59 ` Forrest Taylor
2005-08-31 20:53 ` Forrest Taylor
2005-08-31 21:01 ` David M. Strang [this message]
2005-08-31 21:02 ` Forrest Taylor
2005-08-31 21:05 ` David M. Strang
2005-08-31 21:29 ` Michael Tokarev
2005-08-31 21:34 ` David M. Strang
2005-08-31 22:19 ` Forrest Taylor
2005-09-01 7:38 ` David M. Strang
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='00ab01c5ae6f$1bb27410$c100a8c0@NCNF5131FTH' \
--to=dstrang@shellpower.net \
--cc=ftaylor@redhat.com \
--cc=linux-raid@vger.kernel.org \
/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