[rescue] E5000 disk issue

[Francois Dion]

I've noticed an issue with my e5K. I rebooted yesterday (I rarely
reboot this box since you can do a lot dynamically) and none of my
zones were coming up. So I checked and the disk on which I have zones
was not mounted.

Ok, not a problem, I issue a mount and start my zones. Didn't think
too much of it at the time.

This morning I was loading a database on a different drive (that the
database zone has access to) and noticed how slow it was.

iostat showed 1100Kw/s and %b 96 to 100!

Isn't that kind of slow for the SCSI on the IOBoard to a ST130 with 10
K rpm U320 drives (I know it only does u160 but still). Digging in
dmesg I see:

Nov 23 12:44:41 e5000 scsi: [ID 365881 kern.info] fas:  4.0: cdb=[ 0x12 0x0
0x0
0x0 0x30 0x0 ]
Nov 23 12:44:41 e5000 scsi: [ID 107833 kern.warning] WARNING:
/sbus at 3,0/SUNW,fas
@3,8800000 (fas0):
Nov 23 12:44:41 e5000   Connected command timeout for Target 4.0
Nov 23 12:44:41 e5000 scsi: [ID 107833 kern.warning] WARNING:
/sbus at 3,0/SUNW,fas
@3,8800000 (fas0):
Nov 23 12:44:41 e5000   Target 4 reducing sync. transfer rate
Nov 23 12:44:41 e5000 scsi: [ID 107833 kern.warning] WARNING:
/sbus at 3,0/SUNW,fas
@3,8800000/sd at 2,0 (sd2):
Nov 23 12:44:41 e5000   SCSI transport failed: reason 'reset': retrying
command
Nov 23 12:44:44 e5000 scsi: [ID 107833 kern.warning] WARNING:
/sbus at 3,0/SUNW,fas
@3,8800000/sd at 2,0 (sd2):
Nov 23 12:44:44 e5000   Error for Command: write(10)               Error
Level:
Retryable
Nov 23 12:44:44 e5000 scsi: [ID 107833 kern.notice]     Requested Block:
2128694
                   Error Block: 2128694
Nov 23 12:44:44 e5000 scsi: [ID 107833 kern.notice]     Vendor: SEAGATE
                   Serial Number: 0043K81286
Nov 23 12:44:44 e5000 scsi: [ID 107833 kern.notice]     Sense Key: Unit
Attentio
n
Nov 23 12:44:44 e5000 scsi: [ID 107833 kern.notice]     ASC: 0x29 (scsi bus
rese
t occurred), ASCQ: 0x2, FRU: 0x2
Nov 23 12:44:44 e5000 scsi: [ID 193665 kern.info] sd4 at fas0: target 4 lun 0


I also have a CDROM and DDS tape on the same controller (connected
thru the front and into the 5000 chassis.

Any idea what is going on?

Francois