[2925] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

Annonying SCSI reset when r/w to drive

daemon@ATHENA.MIT.EDU (Brendan Miller)
Sat Dec 13 15:25:06 1997

Date: 	Sat, 13 Dec 1997 12:10:36 -0800
From: Brendan Miller <brmiller@wco.com>
To: linux-scsi@vger.rutgers.edu
Reply-To: Brendan Miller <brmiller@wco.com>


I have a Buslogic BT-958 with a 4.5G Quantum Atlass II on the "wide" connector,
and a 1G Seagate ST31230N, a Toshiba CDROM, and an IOMEGA ZIP drive on the
narrow chain.

The partitions are set up as follows:

/dev/sda (Seagate ST31230N): 64 heads, 32 sectors, 1010 cylinders
Units = cylinders of 2048 * 512 bytes

   Device Boot   Begin    Start      End   Blocks   Id  System
/dev/sda1   *        1        1      300   307184    6  DOS 16-bit >=32M
/dev/sda2          301      301      364    65536   83  Linux native
/dev/sda3          365      365     1010   661504    6  DOS 16-bit >=32M

/dev/sdb (Quantum Atlas II): 64 heads, 32 sectors, 4341 cylinders
Units = cylinders of 2048 * 512 bytes

   Device Boot   Begin    Start      End   Blocks   Id  System
/dev/sdb1            1        1      800   819184    6  DOS 16-bit >=32M
/dev/sdb2          801      801      864    65536   83  Linux native
/dev/sdb3          865      865      928    65536   82  Linux swap
/dev/sdb4          929      929     4341  3494912    5  Extended
/dev/sdb5          929      929      992    65520   83  Linux native
/dev/sdb6          993      993     1792   819184   83  Linux native
/dev/sdb7         1024     1793     2192   409584   83  Linux native
/dev/sdb8         2048     2193     3192  1023984   83  Linux native
/dev/sdb9         3072     3193     4341  1176560   83  Linux native

Now, here's how everything works: /dev/sda1 is my boot paritition and also
has DOS on it.  /dev/sda2 was going to be a backup root partition that I 
could use in case I lost my normal root partition on /dev/sdb2.  I also
boot Linux from /dev/sda2 using the NT boot-loader.  /dev/sdb3 is currently
unused.  /dev/sdb1 is my NT partition, /dev/sdb2 is my Linux root, and the
rest of /dev/sdb are Linux partitions.

NTLDR is on /dev/sda1 and has a menu that includes DOS (/dev/sda1), NT
(/dev/sdb2), and Linux (/dev/sda2).  All this works.  But I want to 
use the /dev/sda3 partition as a storage partition (formatted as msdos,
used as VFAT) to store both Windows and Linux stuff.  But everytime I
mount the partition and try to read or write to it, this is what I get:


Dec  9 18:42:16 xenon kernel: scsi : aborting command due to timeout : pid 1543703, scsi0, channel 0, id 0, lun 0 Write (6) 1a bc 39 f4 00
Dec  9 18:42:16 xenon kernel: scsi0: Aborting CCB #1543717 to Target 0
Dec  9 18:42:16 xenon kernel: scsi : aborting command due to timeout : pid 1543704, scsi0, channel 0, id 0, lun 0 Write (6) 1a bd 2d 0c 00
Dec  9 18:42:16 xenon kernel: scsi0: Aborting CCB #1543718 to Target 0
Dec  9 18:42:16 xenon kernel: scsi : aborting command due to timeout : pid 1543707, scsi0, channel 0, id 1, lun 0 Read (6) 1f 09 5a 02 00
Dec  9 18:42:16 xenon kernel: scsi0: Aborting CCB #1543721 to Target 1
Dec  9 18:42:16 xenon kernel: scsi : aborting command due to timeout : pid 1543708, scsi0, channel 0, id 1, lun 0 Read (10) 00 00 23 02 30 00 00 02 00

this is repeated for awhile, and then

Dec  9 18:42:17 xenon kernel: SCSI host 0 abort (pid 1543703) timed out - resetting
Dec  9 18:42:17 xenon kernel: SCSI bus is being reset for host 0 channel 0.
Dec  9 18:42:17 xenon kernel: scsi0: Sending Bus Device Reset CCB #1543734 to Target 0
Dec  9 18:42:17 xenon kernel: SCSI host 0 abort (pid 1543704) timed out - resetting
Dec  9 18:42:17 xenon kernel: SCSI bus is being reset for host 0 channel 0.
Dec  9 18:42:17 xenon kernel: scsi0: Unable to Reset Command to Target 0 - Reset
 Pending
Dec  9 18:42:17 xenon kernel: SCSI host 0 abort (pid 1543707) timed out - resetting

we do this for awhile, and finnaly

Dec  9 18:42:18 xenon kernel: scsi0: Resetting BusLogic BT-958 due to Target 0
Dec  9 18:42:18 xenon kernel: scsi0: *** BusLogic BT-958 Initialized Successfully ***

It works for awhile, and then

Dec  9 18:42:38 xenon kernel: scsi : aborting command due to timeout : pid 1543728, scsi0, channel 0, id 0, lun 0 Write (6) 1a c2 09 f4 00
Dec  9 18:42:38 xenon kernel: scsi0: Aborting CCB #1543761 to Target 0
Dec  9 18:42:38 xenon kernel: scsi : aborting command due to timeout : pid 1543729, scsi0, channel 0, id 0, lun 0 Write (6) 1a c2 fd f4 00
Dec  9 18:42:38 xenon kernel: scsi0: Aborting CCB #1543762 to Target 0

and it all starts over again.

What's the deal?

Brendan Miller






home help back first fref pref prev next nref lref last post