SUMMARY - 'WARNING: /sbus@3,0, fas errors'

From: Bishop, Laura (LBishop@safetycenter.navy.mil)
Date: Tue May 04 1999 - 07:05:38 CDT

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Thanks to everyone who replied with such helpful information. i've included
the replies and my original question below.
After checking all my cables, doing prtdiag, etc. Sun tech support came out
and they reseated my scsi board and replaced the terminator. Although I
already had an external terminator on the scsi i/o board, it seems replacing
it fixed my problem. Since the engineer had never heard of a terminator
going bad before i'm a little apprehensive that my problem may come back.
Although I've been running a day with no errors (these errors would start 2
mins after boot up and run non-stop) - so it certainly looks like it fixed
the problem.

Again thanks to all.

<<Re: Question on 'WARNING: /sbus@3,0, fas errors'>> <<RE: Question on
'WARNING: /sbus@3,0, fas errors'>> <<Re: Question on 'WARNING: /sbus@3,0,
fas errors'>> <<Re: Question on 'WARNING: /sbus@3,0, fas errors'>> <<Re:
Question on 'WARNING: /sbus@3,0, fas errors'>> <<RE: Question on 'WARNING:
/sbus@3,0, fas errors'>> <<Re: Question on 'WARNING: /sbus@3,0, fas
errors'>> <<Re: Question on 'WARNING: /sbus@3,0, fas errors'>> <<Re:
Question on 'WARNING: /sbus@3,0, fas errors'>>

<<Question on 'WARNING: /sbus@3,0, fas errors'>>
-----

Laura Bishop
Naval Safety Center,
Norfolk, VA
lbishop@safetycenter.navy.mil

attached mail follows:

did u try "prtdiag"...?

cheers
ram

On Fri, 30 Apr 1999 11:17:43 -0400, Bishop, Laura wrote:

> Apr 29 19:03:11 SIMS3000 unix: fas: Latched stat=0x80<IPND>
> intr=0x18<BUS,FC
> MP>
> Apr 29 19:03:11 SIMS3000 unix: fas: last msgout: IDENTIFY, last
msgin:
> DISCO
> NNECT
> Apr 29 19:03:11 SIMS3000 unix: fas: DMA
> csr=0xb2bf8810<TWOCYC,BRST1,BST0,DSB
> LEDRN,WIDE,INTEN>
> Apr 29 19:03:11 SIMS3000 unix: fas: addr=0 dmacnt=0 test=0
last=f0001f40
> las
> t_cnt=7
> Apr 29 19:03:11 SIMS3000 unix: fas: fas state:
> Apr 29 19:03:11 SIMS3000 unix: fas: count(32)=7 cmd=c2 stat=6
> stat2=
> 80 intr=0
> Apr 29 19:03:11 SIMS3000 unix: fas: step=c8 fifoflag=0
conf=17
> test=
> 1a conf2=90 conf3=83
> Apr 29 19:03:11 SIMS3000 unix: fas: Cmd dump for Target 6 Lun 0:
> Apr 29 19:03:11 SIMS3000 unix: fas: cdb=[ 0x0 0x0 0x0 0x0 0x0 0x0 ]
> Apr 29 19:03:11 SIMS3000 unix: fas: State=DATA Last State=UNKNOWN
> Apr 29 19:03:11 SIMS3000 unix: fas: pkt_state=0x3<SEL,ARB>
> pkt_flags=0x18000
> pkt_statistics=0x0
> Apr 29 19:03:11 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@0,0
> (sd0):
> Apr 29 19:03:11 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:03:11 SIMS3000 unix:
> Apr 29 19:04:27 SIMS3000 unix: fas: 10.0: cdb=[ 0x8 0x0 0x8 0x70 0x78
> 0x0 ]
> Apr 29 19:04:27 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000
(fas0):
>
> Apr 29 19:04:27 SIMS3000 unix: Connected command timeout for Target 10.0

> Apr 29 19:04:27 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@0,0
> (sd0):
> Apr 29 19:04:27 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:04:27 SIMS3000 unix:
> Apr 29 19:04:27 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@2,0
> (sd2):
> Apr 29 19:04:27 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:04:27 SIMS3000 unix:
> Apr 29 19:04:39 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@a,0
> (sd9):
> Apr 29 19:04:39 SIMS3000 unix: SCSI transport failed: reason 'timeout':
> retryin
> g command
> Apr 29 19:04:39 SIMS3000 unix:
> Apr 29 19:04:39 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@c,0
> (sd11):
> Apr 29 19:04:39 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:04:39 SIMS3000 unix:
>
> And they go on and on till 19:55 then the system seemed to just lock up -
no
> other messages.
> Laura Bishop
> Naval Safety Center,
> Norfolk, VA
> lbishop@safetycenter.navy.mil
>

_______________________________________________________
Get your free, private email at http://mail.excite.com/

attached mail follows:

Hi Laura,
We had a similar problem, and the only thing I can say for sure is that
THE 1ST SCSI PORT ON THE BACK OF THE UE3000 *MUST* BE TERMINATED! We found
this out the hard way. The problems would come and go, and finally after
filling up all 10 drive bays, it was more frequent and after 3 days with Sun
support, somebody finally said "Oh, do you have the SCSI port terminated on
the back"? Well no, I didn't, and yes it needs to, even though it should be
self-terminating. It's a known problem with 3000's. Hope that helps some.

Damon

-----Original Message-----
From: Bishop, Laura [mailto:LBishop@safetycenter.navy.mil]
Sent: Friday, April 30, 1999 10:18 AM
To: sun-managers@sunmanagers.ececs.uc.edu
Subject: Question on 'WARNING: /sbus@3,0, fas errors'

Hi, I'm getting these errors in the messages file and finally after an hour
of them last night the system froze up. I had to actually power off to get
the system to come up and Sun support said that my SCSI bus hung. I know
that target 0 is my boot disk with swap on it, and we have database files on
Target 6 - there was activity to these devices when these errors occurred.
I just need to find out is this something I need to be concerned about -
problems w/ the SCSI, or a device? Thanks for any help! I'm running
Solaris 2.6 on a UE 3000 with all current patches. Here's what the errors
look like:

Apr 29 19:02:56 SIMS3000 unix: fas: 0.0: cdb=[ 0x28 0x0 0x0 0x6d 0x57
0x0 0x
0 0x0 0x10 0x0 ]
Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000 (fas0):

Apr 29 19:02:56 SIMS3000 unix: Connected command timeout for Target 0.0
Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@0,0
(sd0):
Apr 29 19:02:56 SIMS3000 unix: SCSI transport failed: reason 'timeout':
retryin
g command
Apr 29 19:02:56 SIMS3000 unix:
Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@0,0
(sd0):
Apr 29 19:02:56 SIMS3000 unix: SCSI transport failed: reason 'reset':
retrying
command
Apr 29 19:02:56 SIMS3000 unix:
Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@a,0
(sd9):
Apr 29 19:02:56 SIMS3000 unix: SCSI transport failed: reason 'reset':
retrying
command
Apr 29 19:02:56 SIMS3000 unix:
Apr 29 19:03:11 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000 (fas0):

Apr 29 19:03:11 SIMS3000 unix: unexpected data phase: current fas state:
Apr 29 19:03:11 SIMS3000 unix: fas: Latched stat=0x80<IPND>
intr=0x18<BUS,FC
MP>
Apr 29 19:03:11 SIMS3000 unix: fas: last msgout: IDENTIFY, last msgin:
DISCO
NNECT
Apr 29 19:03:11 SIMS3000 unix: fas: DMA
csr=0xb2bf8810<TWOCYC,BRST1,BST0,DSB
LEDRN,WIDE,INTEN>
Apr 29 19:03:11 SIMS3000 unix: fas: addr=0 dmacnt=0 test=0 last=f0001f40
las
t_cnt=7
Apr 29 19:03:11 SIMS3000 unix: fas: fas state:
Apr 29 19:03:11 SIMS3000 unix: fas: count(32)=7 cmd=c2 stat=6
stat2=
80 intr=0
Apr 29 19:03:11 SIMS3000 unix: fas: step=c8 fifoflag=0 conf=17
test=
1a conf2=90 conf3=83
Apr 29 19:03:11 SIMS3000 unix: fas: Cmd dump for Target 6 Lun 0:
Apr 29 19:03:11 SIMS3000 unix: fas: cdb=[ 0x0 0x0 0x0 0x0 0x0 0x0 ]
Apr 29 19:03:11 SIMS3000 unix: fas: State=DATA Last State=UNKNOWN
Apr 29 19:03:11 SIMS3000 unix: fas: pkt_state=0x3<SEL,ARB>
pkt_flags=0x18000
pkt_statistics=0x0
Apr 29 19:03:11 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@0,0
(sd0):
Apr 29 19:03:11 SIMS3000 unix: SCSI transport failed: reason 'reset':
retrying
command
Apr 29 19:03:11 SIMS3000 unix:
Apr 29 19:04:27 SIMS3000 unix: fas: 10.0: cdb=[ 0x8 0x0 0x8 0x70 0x78
0x0 ]
Apr 29 19:04:27 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000 (fas0):

Apr 29 19:04:27 SIMS3000 unix: Connected command timeout for Target 10.0
Apr 29 19:04:27 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@0,0
(sd0):
Apr 29 19:04:27 SIMS3000 unix: SCSI transport failed: reason 'reset':
retrying
command
Apr 29 19:04:27 SIMS3000 unix:
Apr 29 19:04:27 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@2,0
(sd2):
Apr 29 19:04:27 SIMS3000 unix: SCSI transport failed: reason 'reset':
retrying
command
Apr 29 19:04:27 SIMS3000 unix:
Apr 29 19:04:39 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@a,0
(sd9):
Apr 29 19:04:39 SIMS3000 unix: SCSI transport failed: reason 'timeout':
retryin
g command
Apr 29 19:04:39 SIMS3000 unix:
Apr 29 19:04:39 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@c,0
(sd11):
Apr 29 19:04:39 SIMS3000 unix: SCSI transport failed: reason 'reset':
retrying
command
Apr 29 19:04:39 SIMS3000 unix:

And they go on and on till 19:55 then the system seemed to just lock up - no
other messages.
Laura Bishop
Naval Safety Center,
Norfolk, VA
lbishop@safetycenter.navy.mil

attached mail follows:

Laura,

There are three major possible causes:

1. Terminator not installed correctly or a differential terminator
        used for a single-ended chain (or vise-versa),
2. SCSI device on the way out,
3. cable:
        a. crimped and giving intermittent connection,
        b. cable not seated correctly, or
        c. SCSI chain too long for the connection.

For the last one there is a maximum length for all SCSI chains. This
counts all internal connections. For SCSI 1 and 2 its 3 meters (or
3 yards for you), for SCSI 3 its only 1.5 meters.
Regards,

David Evans

_________________________________________________________________________
|Oracle Corporation Australia Pty Ltd | Oracle*Mail djevans.au |
|David Evans | Internet: djevans@au.oracle.com |
|Systems Administrator | djve@acm.org |
|Australia Product Development Centre | Phone: +61-3-9209-1759 |
|5th Floor, 332 St. Kilda Road | Fax: +61-3-9690-0043 |
|Melbourne, VIC, 3004, Australia | Mobile: 0418-372-774 (personal) |
-------------------------------------------------------------------------
Any statements or comments are personal and do not represent the views of
                        Oracle Corporation Australia.

attached mail follows:

Apr 29 19:02:56 SIMS3000 unix: fas: 0.0: cdb=[ 0x28 0x0 0x0 0x6d 0x57
0x0 0x
0 0x0 0x10 0x0 ]
Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000 (fas0):

And they go on and on till 19:55 then the system seemed to just lock up - no
other messages.
Laura Bishop
Naval Safety Center,
Norfolk, VA
lbishop@safetycenter.navy.mil

attached mail follows:

I'd say be concerned. My first looks would be at cables and terminators,
given that you saw strange bus states too. Timeouts can be caused by
a disk losing it, but you don't usually get the strange bus phase there...

l & h,
kev

attached mail follows:

At a guess (i've only a few years experience, but have experienced a bunch
of hardware failures....) If there is more than one drive "failing"
simultaneously, it's probably the SCSI controller or the cable. May mean a
mother board replacement. Did you add/remove/ or otherise fiddle with the
cable(s) recently? That's bit me before.

If it is only 1 drive 'failing', replace the drive now and worry about
other things later.

At 11:17 AM 4/30/1999 -0400, you wrote:
>Hi, I'm getting these errors in the messages file and finally after an hour
>of them last night the system froze up. I had to actually power off to
get
>the system to come up and Sun support said that my SCSI bus hung. I know
>that target 0 is my boot disk with swap on it, and we have database files
on
>Target 6 - there was activity to these devices when these errors occurred.
>I just need to find out is this something I need to be concerned about -
>problems w/ the SCSI, or a device? Thanks for any help! I'm running
>Solaris 2.6 on a UE 3000 with all current patches. Here's what the errors
>look like:
>
>Apr 29 19:02:56 SIMS3000 unix: fas: 0.0: cdb=[ 0x28 0x0 0x0 0x6d 0x57
>0x0 0x
>0 0x0 0x10 0x0 ]
>Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000
(fas0):
>
>Apr 29 19:02:56 SIMS3000 unix: Connected command timeout for Target 0.0
>Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@0,0
>(sd0):
>Apr 29 19:02:56 SIMS3000 unix: SCSI transport failed: reason 'timeout':
>retryin
>g command
>Apr 29 19:02:56 SIMS3000 unix:
>Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@0,0
>(sd0):
>Apr 29 19:02:56 SIMS3000 unix: SCSI transport failed: reason 'reset':
>retrying
>command
>Apr 29 19:02:56 SIMS3000 unix:
>Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@a,0
>(sd9):
>Apr 29 19:02:56 SIMS3000 unix: SCSI transport failed: reason 'reset':
>retrying
>command
>Apr 29 19:02:56 SIMS3000 unix:
>Apr 29 19:03:11 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000
(fas0):
>
>Apr 29 19:03:11 SIMS3000 unix: unexpected data phase: current fas state:
>Apr 29 19:03:11 SIMS3000 unix: fas: Latched stat=0x80<IPND>
>intr=0x18<BUS,FC
>MP>
>Apr 29 19:03:11 SIMS3000 unix: fas: last msgout: IDENTIFY, last msgin:
>DISCO
>NNECT
>Apr 29 19:03:11 SIMS3000 unix: fas: DMA
>csr=0xb2bf8810<TWOCYC,BRST1,BST0,DSB
>LEDRN,WIDE,INTEN>
>Apr 29 19:03:11 SIMS3000 unix: fas: addr=0 dmacnt=0 test=0
last=f0001f40
>las
>t_cnt=7
>Apr 29 19:03:11 SIMS3000 unix: fas: fas state:
>Apr 29 19:03:11 SIMS3000 unix: fas: count(32)=7 cmd=c2 stat=6
>stat2=
>80 intr=0
>Apr 29 19:03:11 SIMS3000 unix: fas: step=c8 fifoflag=0 conf=17
>test=
>1a conf2=90 conf3=83
>Apr 29 19:03:11 SIMS3000 unix: fas: Cmd dump for Target 6 Lun 0:
>Apr 29 19:03:11 SIMS3000 unix: fas: cdb=[ 0x0 0x0 0x0 0x0 0x0 0x0 ]
>Apr 29 19:03:11 SIMS3000 unix: fas: State=DATA Last State=UNKNOWN
>Apr 29 19:03:11 SIMS3000 unix: fas: pkt_state=0x3<SEL,ARB>
>pkt_flags=0x18000
> pkt_statistics=0x0
>Apr 29 19:03:11 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@0,0
>(sd0):
>Apr 29 19:03:11 SIMS3000 unix: SCSI transport failed: reason 'reset':
>retrying
>command
>Apr 29 19:03:11 SIMS3000 unix:
>Apr 29 19:04:27 SIMS3000 unix: fas: 10.0: cdb=[ 0x8 0x0 0x8 0x70 0x78
>0x0 ]
>Apr 29 19:04:27 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000
(fas0):
>
>Apr 29 19:04:27 SIMS3000 unix: Connected command timeout for Target 10.0
>Apr 29 19:04:27 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@0,0
>(sd0):
>Apr 29 19:04:27 SIMS3000 unix: SCSI transport failed: reason 'reset':
>retrying
>command
>Apr 29 19:04:27 SIMS3000 unix:
>Apr 29 19:04:27 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@2,0
>(sd2):
>Apr 29 19:04:27 SIMS3000 unix: SCSI transport failed: reason 'reset':
>retrying
>command
>Apr 29 19:04:27 SIMS3000 unix:
>Apr 29 19:04:39 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@a,0
>(sd9):
>Apr 29 19:04:39 SIMS3000 unix: SCSI transport failed: reason 'timeout':
>retryin
>g command
>Apr 29 19:04:39 SIMS3000 unix:
>Apr 29 19:04:39 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@c,0
>(sd11):
>Apr 29 19:04:39 SIMS3000 unix: SCSI transport failed: reason 'reset':
>retrying
>command
>Apr 29 19:04:39 SIMS3000 unix:
>
>And they go on and on till 19:55 then the system seemed to just lock up -
no
>other messages.
>Laura Bishop
>Naval Safety Center,
>Norfolk, VA
>lbishop@safetycenter.navy.mil
>

Chad Price
Systems Manager
University of Nebraska Medical Center
600 S 42nd St
Omaha, NE 68506-6495
cprice@molbio.unmc.edu
(402) 559-9527
(402) 559-4077 (FAX)

attached mail follows:

>From my similar experience you may be having a failing component. In my case
I was getting this generic scsi reset message, but it turned out to be a bad
internal disk, luckily not the root disk. The problem went away after I
replaced the disk.

-Sundar

Apr 29 19:02:56 SIMS3000 unix: fas: 0.0: cdb=[ 0x28 0x0 0x0 0x6d 0x57
0x0 0x
0 0x0 0x10 0x0 ]
Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000 (fas0):

And they go on and on till 19:55 then the system seemed to just lock up - no
other messages.
Laura Bishop
Naval Safety Center,
Norfolk, VA
lbishop@safetycenter.navy.mil

attached mail follows:

Laura,

The command time outs could be related to tagged queueing, especially if you

have a lot of I/O going. You can adjust the max_throttle by setting it lower
in
the /etc/system file,, trying it low and adjusting up if you want to:

* Solaris sd driver taq queueing problems/sd_max_throttle
(default=256)
* Solution: set sd_max_throttle, in /etc/system, to a lower value
* Total value is this value x no. of SCSI targets:
set sd:sd_max_throttle = 16

Kitty

--Kitty Ferguson System Administrator - CSMT
ferguson@hao.ucar.edu NCAR - High Altitude Observatory
tel: (303)497-1556 P.O. Box 3000
fax: (303)497-1589 Boulder, CO 80307-3000

ps - Are you the Laura Bishop I knew from the Ingres Users Group?

> From sun-managers-relay@sunmanagers.ececs.uc.edu Fri Apr 30 10:40 MDT 1999
> From: "Bishop, Laura" <LBishop@safetycenter.navy.mil>
> To: sun-managers@sunmanagers.ececs.uc.edu
> Subject: Question on 'WARNING: /sbus@3,0, fas errors'
> Date: Fri, 30 Apr 1999 11:17:43 -0400
>
> Hi, I'm getting these errors in the messages file and finally after an
hour
> of them last night the system froze up. I had to actually power off to
get
> the system to come up and Sun support said that my SCSI bus hung. I know
> that target 0 is my boot disk with swap on it, and we have database files
on
> Target 6 - there was activity to these devices when these errors occurred.
> I just need to find out is this something I need to be concerned about -
> problems w/ the SCSI, or a device? Thanks for any help! I'm running
> Solaris 2.6 on a UE 3000 with all current patches. Here's what the errors
> look like:
>
> Apr 29 19:02:56 SIMS3000 unix: fas: 0.0: cdb=[ 0x28 0x0 0x0 0x6d 0x57
> 0x0 0x
> 0 0x0 0x10 0x0 ]
> Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000
(fas0):
>
> Apr 29 19:02:56 SIMS3000 unix: Connected command timeout for Target 0.0
> Apr 29 19:02:56 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@0,0
> (sd0):
> Apr 29 19:02:56 SIMS3000 unix: SCSI transport failed: reason 'timeout':
> retryin
> g command
> Apr 29 19:02:56 SIMS3000 unix:
> Apr 29 19:02:56 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@0,0
> (sd0):
> Apr 29 19:02:56 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:02:56 SIMS3000 unix:
> Apr 29 19:02:56 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@a,0
> (sd9):
> Apr 29 19:02:56 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:02:56 SIMS3000 unix:
> Apr 29 19:03:11 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000
(fas0):
>
> Apr 29 19:03:11 SIMS3000 unix: unexpected data phase: current fas state:
> Apr 29 19:03:11 SIMS3000 unix: fas: Latched stat=0x80<IPND>
> intr=0x18<BUS,FC
> MP>
> Apr 29 19:03:11 SIMS3000 unix: fas: last msgout: IDENTIFY, last msgin:
> DISCO
> NNECT
> Apr 29 19:03:11 SIMS3000 unix: fas: DMA
> csr=0xb2bf8810<TWOCYC,BRST1,BST0,DSB
> LEDRN,WIDE,INTEN>
> Apr 29 19:03:11 SIMS3000 unix: fas: addr=0 dmacnt=0 test=0
last=f0001f40
> las
> t_cnt=7
> Apr 29 19:03:11 SIMS3000 unix: fas: fas state:
> Apr 29 19:03:11 SIMS3000 unix: fas: count(32)=7 cmd=c2 stat=6
> stat2=
> 80 intr=0
> Apr 29 19:03:11 SIMS3000 unix: fas: step=c8 fifoflag=0 conf=17
> test=
> 1a conf2=90 conf3=83
> Apr 29 19:03:11 SIMS3000 unix: fas: Cmd dump for Target 6 Lun 0:
> Apr 29 19:03:11 SIMS3000 unix: fas: cdb=[ 0x0 0x0 0x0 0x0 0x0 0x0 ]
> Apr 29 19:03:11 SIMS3000 unix: fas: State=DATA Last State=UNKNOWN
> Apr 29 19:03:11 SIMS3000 unix: fas: pkt_state=0x3<SEL,ARB>
> pkt_flags=0x18000
> pkt_statistics=0x0
> Apr 29 19:03:11 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@0,0
> (sd0):
> Apr 29 19:03:11 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:03:11 SIMS3000 unix:
> Apr 29 19:04:27 SIMS3000 unix: fas: 10.0: cdb=[ 0x8 0x0 0x8 0x70 0x78
> 0x0 ]
> Apr 29 19:04:27 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000
(fas0):
>
> Apr 29 19:04:27 SIMS3000 unix: Connected command timeout for Target 10.0
> Apr 29 19:04:27 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@0,0
> (sd0):
> Apr 29 19:04:27 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:04:27 SIMS3000 unix:
> Apr 29 19:04:27 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@2,0
> (sd2):
> Apr 29 19:04:27 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:04:27 SIMS3000 unix:
> Apr 29 19:04:39 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@a,0
> (sd9):
> Apr 29 19:04:39 SIMS3000 unix: SCSI transport failed: reason 'timeout':
> retryin
> g command
> Apr 29 19:04:39 SIMS3000 unix:
> Apr 29 19:04:39 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@c,0
> (sd11):
> Apr 29 19:04:39 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:04:39 SIMS3000 unix:
>
> And they go on and on till 19:55 then the system seemed to just lock up -
no
> other messages.
> Laura Bishop
> Naval Safety Center,
> Norfolk, VA
> lbishop@safetycenter.navy.mil
>

attached mail follows:

On Fri, 30 Apr 1999, Bishop, Laura wrote:

> Hi, I'm getting these errors in the messages file and finally after
> an hour of them last night the system froze up...

Reset, timeout and phase errors are definitely a sign of a problem.
First you should check for proper cabling and termination. The error
messages (timeouts, resets, unexpected data phase) all point to a
problem with the SCSI bus. However I've seen similar problems with
bad drivers (I wouldn't expect the fas driver to be bad though), power
supplies (which supplies the SCSI termination voltage) and fans (which
cool the power supplies).

If that's not the problem you should look at the devices on the SCSI
bus. Perhaps one has a power supply problem. Then try to discover if
there is a problem report for any of your SCSI devices ... maybe one
needs a flash/prom upgrade. You could also check the fas
configuration values in /kernel/drv/fas.conf (see fas(7D)) and the
SCSI options in the eeprom and finally in /etc/system.

Good luck,

Rgds,

-H-

Harvey M Wamboldt ^ E-Mail: harvey@iotek.ns.ca
MDA Inc 1000 Windmill Rd. Suite 60 ^ Fax: (902)468-2278
Dartmouth NS, B3B 1L7, Canada ^ Phone: (902)481-3531

attached mail follows:

Laura,

I had the same problem here in Brazil with my EU3000. I solved it changing
the
/etc/system file by adding
the following lines at the end:

set scsi_options=0x358
set scsi_reset_delay=10000

This changes the way the scsi controler accesses the data on the drive, but
I
must warn you that this is only
a temporary mesure because now the controler will be accessing the drive
much
more slower than before.
Every time you reconfigure your devices the scsi controler identifies the
kind of drive you have and chooses the best possible parameters for it and
if
you add those lines you are actually telling him that you have a slower
drive
then the one you really have. When I took the SA-286 at SUN Education the
same
thing happened with the SparkStation I was working and the SUN teacher said
that
when this happens it's got something do to unclean shutdowns. He also told
me
that you must backup all information on the file system and reformat the
partitions for the problem to relly go away. After all that is done, you
can
restore the information with the backup.

Hope I of any help

Ivan de Aquino
System Administrator
SENAI/CIET
http://www.ciet.senai.br

Bishop, Laura wrote:

> Hi, I'm getting these errors in the messages file and finally after an
hour
> of them last night the system froze up. I had to actually power off to
get
> the system to come up and Sun support said that my SCSI bus hung. I know
> that target 0 is my boot disk with swap on it, and we have database files
on
> Target 6 - there was activity to these devices when these errors occurred.
> I just need to find out is this something I need to be concerned about -
> problems w/ the SCSI, or a device? Thanks for any help! I'm running
> Solaris 2.6 on a UE 3000 with all current patches. Here's what the errors
> look like:
>
> Apr 29 19:02:56 SIMS3000 unix: fas: 0.0: cdb=[ 0x28 0x0 0x0 0x6d 0x57
> 0x0 0x
> 0 0x0 0x10 0x0 ]
> Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000
(fas0):
>
> Apr 29 19:02:56 SIMS3000 unix: Connected command timeout for Target 0.0
> Apr 29 19:02:56 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@0,0
> (sd0):
> Apr 29 19:02:56 SIMS3000 unix: SCSI transport failed: reason 'timeout':
> retryin
> g command
> Apr 29 19:02:56 SIMS3000 unix:
> Apr 29 19:02:56 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@0,0
> (sd0):
> Apr 29 19:02:56 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:02:56 SIMS3000 unix:
> Apr 29 19:02:56 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@a,0
> (sd9):
> Apr 29 19:02:56 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:02:56 SIMS3000 unix:
> Apr 29 19:03:11 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000
(fas0):
>
> Apr 29 19:03:11 SIMS3000 unix: unexpected data phase: current fas state:
> Apr 29 19:03:11 SIMS3000 unix: fas: Latched stat=0x80<IPND>
> intr=0x18<BUS,FC
> MP>
> Apr 29 19:03:11 SIMS3000 unix: fas: last msgout: IDENTIFY, last msgin:
> DISCO
> NNECT
> Apr 29 19:03:11 SIMS3000 unix: fas: DMA
> csr=0xb2bf8810<TWOCYC,BRST1,BST0,DSB
> LEDRN,WIDE,INTEN>
> Apr 29 19:03:11 SIMS3000 unix: fas: addr=0 dmacnt=0 test=0
last=f0001f40
> las
> t_cnt=7
> Apr 29 19:03:11 SIMS3000 unix: fas: fas state:
> Apr 29 19:03:11 SIMS3000 unix: fas: count(32)=7 cmd=c2 stat=6
> stat2=
> 80 intr=0
> Apr 29 19:03:11 SIMS3000 unix: fas: step=c8 fifoflag=0 conf=17
> test=
> 1a conf2=90 conf3=83
> Apr 29 19:03:11 SIMS3000 unix: fas: Cmd dump for Target 6 Lun 0:
> Apr 29 19:03:11 SIMS3000 unix: fas: cdb=[ 0x0 0x0 0x0 0x0 0x0 0x0 ]
> Apr 29 19:03:11 SIMS3000 unix: fas: State=DATA Last State=UNKNOWN
> Apr 29 19:03:11 SIMS3000 unix: fas: pkt_state=0x3<SEL,ARB>
> pkt_flags=0x18000
> pkt_statistics=0x0
> Apr 29 19:03:11 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@0,0
> (sd0):
> Apr 29 19:03:11 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:03:11 SIMS3000 unix:
> Apr 29 19:04:27 SIMS3000 unix: fas: 10.0: cdb=[ 0x8 0x0 0x8 0x70 0x78
> 0x0 ]
> Apr 29 19:04:27 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000
(fas0):
>
> Apr 29 19:04:27 SIMS3000 unix: Connected command timeout for Target 10.0
> Apr 29 19:04:27 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@0,0
> (sd0):
> Apr 29 19:04:27 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:04:27 SIMS3000 unix:
> Apr 29 19:04:27 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@2,0
> (sd2):
> Apr 29 19:04:27 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:04:27 SIMS3000 unix:
> Apr 29 19:04:39 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@a,0
> (sd9):
> Apr 29 19:04:39 SIMS3000 unix: SCSI transport failed: reason 'timeout':
> retryin
> g command
> Apr 29 19:04:39 SIMS3000 unix:
> Apr 29 19:04:39 SIMS3000 unix: WARNING:
/sbus@3,0/SUNW,fas@3,8800000/sd@c,0
> (sd11):
> Apr 29 19:04:39 SIMS3000 unix: SCSI transport failed: reason 'reset':
> retrying
> command
> Apr 29 19:04:39 SIMS3000 unix:
>
> And they go on and on till 19:55 then the system seemed to just lock up -
no
> other messages.
> Laura Bishop
> Naval Safety Center,
> Norfolk, VA
> lbishop@safetycenter.navy.mil

attached mail follows:

Apr 29 19:02:56 SIMS3000 unix: fas: 0.0: cdb=[ 0x28 0x0 0x0 0x6d 0x57
0x0 0x
0 0x0 0x10 0x0 ]
Apr 29 19:02:56 SIMS3000 unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000 (fas0):

And they go on and on till 19:55 then the system seemed to just lock up - no
other messages.
Laura Bishop
Naval Safety Center,
Norfolk, VA
lbishop@safetycenter.navy.mil

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:19 CDT