SCSI: aborting command due to timeout

SCSI: aborting command due to timeout

Post by Xiaoqin Qi » Thu, 24 May 2001 03:29:13



Hi,

Recently we have a PC installed RedHat 6.2 with 2.2.14-5.0smp kernel
experiencing problems with SCSI. We have two SCSI hard disk in this
machine. The problem is sometimes the kernel falls into continuos loop
of messages like

May 22 07:34:49 asap kernel: scsi : aborting command due to timeout :
pid 14258, scsi0, channel 0, id 1, lun 0 Read (10) 00 00 31 d8 e0 00 00
10 00
May 22 07:34:49 asap kernel: scsi : aborting command due to timeout :
pid 14259, scsi0, channel 0, id 1, lun 0 Read (10) 00 00 31 d8 f8 00 00
70 00
May 22 07:34:49 asap kernel: scsi : aborting command due to timeout :
pid 14260, scsi0, channel 0, id 1, lun 0 Read (10) 00 00 24 41 00 00 00
08 00
May 22 07:34:51 asap kernel: SCSI host 0 abort (pid 14259) timed out -
resetting
May 22 07:34:51 asap kernel: SCSI bus is being reset for host 0 channel
0.
May 22 07:34:54 asap kernel: (scsi0:0:1:0) Synchronous at 20.0
Mbyte/sec, offset 15.
May 22 07:35:25 asap kernel: scsi : aborting command due to timeout :
pid 14430, scsi0, channel 0, id 1, lun 0 Read (10) 00 00 32 25 58 00 00
80 00
May 22 07:35:25 asap kernel: scsi : aborting command due to timeout :
pid 14431, scsi0, channel 0, id 1, lun 0 Read (10) 00 00 32 25 d8 00 00
80 00
May 22 07:35:25 asap kernel: scsi : aborting command due to timeout :
pid 14432, scsi0, channel 0, id 1, lun 0 Read (10) 00 00 28 29 e0 00 00
08 00
May 22 07:35:27 asap kernel: SCSI host 0 abort (pid 14431) timed out -
resetting
May 22 07:35:27 asap kernel: SCSI bus is being reset for host 0 channel
0.
May 22 07:35:30 asap kernel: (scsi0:0:1:0) Synchronous at 20.0
Mbyte/sec, offset 15.

and the machine hangs (it seems it can't do any IO operations anymore).

Is there anyone know the reason for this problem and how to fix it?

Thank you very much!

Xiaoqin

 
 
 

SCSI: aborting command due to timeout

Post by Joshua Baker-LePai » Thu, 24 May 2001 03:58:59



> Recently we have a PC installed RedHat 6.2 with 2.2.14-5.0smp kernel
> experiencing problems with SCSI. We have two SCSI hard disk in this
> machine. The problem is sometimes the kernel falls into continuos loop
> of messages like
> May 22 07:34:49 asap kernel: scsi : aborting command due to timeout :
> pid 14258, scsi0, channel 0, id 1, lun 0 Read (10) 00 00 31 d8 e0 00 00
> 10 00

*snip*

More than likely, the disk at ID1 is dying.  There's also the laundry
list of usual suspects -- check your termination, your cable length,
etc.  It's also possible that the SCSI controller itself is dying.  Test
the system with one drive in, then with the other.

Oh, and backup while you can...

--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

 
 
 

SCSI: aborting command due to timeout

Post by Xiaoqin Qi » Thu, 24 May 2001 06:52:53


Hi Joshua,

Thank you for your information. I checked my log file and found that the
aborting error messages are for scsi0  id 1 and id 5. I know the id 1 is a
hard disk and id 5 is a CD-ROM. And I also have another hard disk with id 0
which is in the same SCSI bus of the other two equipments. Does it mean both
id 1 and id 5 are dying? Or the controller has some problem? If the
controller has some problem, why there is no error message for id 0?

Is there any other way we can do some more investigation?

Thanks,

Xiaoqin



> > Recently we have a PC installed RedHat 6.2 with 2.2.14-5.0smp kernel
> > experiencing problems with SCSI. We have two SCSI hard disk in this
> > machine. The problem is sometimes the kernel falls into continuos loop
> > of messages like

> > May 22 07:34:49 asap kernel: scsi : aborting command due to timeout :
> > pid 14258, scsi0, channel 0, id 1, lun 0 Read (10) 00 00 31 d8 e0 00 00
> > 10 00
> *snip*

> More than likely, the disk at ID1 is dying.  There's also the laundry
> list of usual suspects -- check your termination, your cable length,
> etc.  It's also possible that the SCSI controller itself is dying.  Test
> the system with one drive in, then with the other.

> Oh, and backup while you can...

> --
> Joshua Baker-LePain
> Department of Biomedical Engineering
> Duke University

 
 
 

SCSI: aborting command due to timeout

Post by Joshua Baker-LePai » Thu, 24 May 2001 20:35:23



> Thank you for your information. I checked my log file and found that the
> aborting error messages are for scsi0  id 1 and id 5. I know the id 1 is a
> hard disk and id 5 is a CD-ROM. And I also have another hard disk with id 0
> which is in the same SCSI bus of the other two equipments. Does it mean both
> id 1 and id 5 are dying? Or the controller has some problem? If the
> controller has some problem, why there is no error message for id 0?

There's a reason that many people refer to SCSI as black magic.  ;)  A
problem somewhere in the chain can cause problems all over the chain.  It's
possible (but unlikely) that both the hard drive and CD are dying.  I'd
start to suspect the adapter though.

Quote:> Is there any other way we can do some more investigation?

Well, as I said, I would start removing components and stressing the
system.  Boot with only the first hard drive (ID 0) connected to the
SCSI chain and do same major reading and writing -- does it stay up?
Do the same with the hard drive at ID1, and with one hard drive and
the CD reader.  Find out if it's a component causing the problems.
There may also be a disk check utility in the SCSI BIOS.

If there's problems in all those cases, then either the controller is
going, or you've got cabling/termination issues.  How are you terminating
the chain?  Active termination is always best.  Are you sure the controller
is terminating its end of the chain (assuming all components are internal)?
Put all the components in another system (on another SCSI card) one by one
and see if they work there.  Basically, you're in for a lot of
troubleshooting.

When was the last time you sacrificed a goat (black, of course) to your
SCSI chain?  That could be the issue too... ;)

Good luck.

--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

 
 
 

1. Help needed ! (scsi : aborting command due to timeout)

Hello there:
        I am trying to install linux with the hareware below:
                     TP4XE55
                     AHA 1542CF
                     Quantum TRB850S
                     32 MB -6 (16X2) RAM
                     PCI CN970EBT NIC
 But when I start to boot from boot disk (scsinet1, ascnet1), I got the
message below:
X-Newsreader: TIN [version 1.2 PL2]

scsi : adaptec 1542
scsi : 1 host
scsi : aborting command due to timeout : pid 0, scsi0, id0, lun 0 0x00 00 00
00 00 00
SCSI host 0 abort() timed out - resetting
Sent BUS DEVICE RESET to target 0
Sending DID_RESET for target 0
Sending DID_RESET for target 0
Sending DID_RESET for target 0
Sending DID_RESET for target 0
Sending DID_RESET for target 0
Sending DID_RESET for target 0

        This message repeats infinity.........

        Could anyone please help me??

        I used Intel MB last month & found that it wasn't as stable as I
wanted, so I am now cswitching it to TP4XE55, strange....

Ken

--







Kent Nyiau Sin Kian from Malaysia. A Junior in MIS, National Central Univ.
*****************************************************************************
Love Hwong Chang Ching. Care of her for the rest of her life.
*****************************************************************************
23 y  168cm 55kg black hair brown eyes spec.
Reading Writting Thinking Singing
*****************************************************************************

2. Do I still need modules-1.2.8 patch with 1.2.10

3. scsi: aborting command due to timeout

4. Voice Systems

5. SCSI: aborting command due to timeout....?

6. test

7. SCSI: Aborting command due to TIMEOUT

8. Video card driver (TGUI9440AGi)

9. scsi aborting command due to timeout

10. scsi : aborting command due to timeout: Anyone?

11. SCSI - aborting command due to timeout

12. SCSI: aborting command due to timeout

13. SCSI Adaptec AHA1542[BC] Aborting command due to timeout