Connected command timeout for Target 4.0

[ponetguy2]

I have a log from my /var/adm/messages file. I'm trying to find this device that it's complaining about and trying to figure out if I should be concerned.

metadevice looks good. Everything seems okay, but I'm still unsure.

Here is the log:

Nov 7 11:02:06 xxxxx scsi: [ID 365881 kern.info] fas: 4.0: cdb=[ 0x8 0x0 0x0 0x0 0x1 0x0 ]
Nov 7 11:02:06 xxxxx scsi: [ID 107833 kern.warning] WARNING: /sbus@2,0/SUNW,fas@1,8800000 (fas0):
Nov 7 11:02:06 xxxxx Connected command timeout for Target 4.0

sd@1,0:a sd@1,0:e,raw sd@2,0:b sd@2,0:f,raw sd@3,0:c sd@3,0:g,raw sd@4,0:d sd@4,0:h,raw sd@5,0:e
sd@1,0:a,raw sd@1,0:f sd@2,0:b,raw sd@2,0:g sd@3,0:c,raw sd@3,0:h sd@4,0:d,raw sd@5,0:a sd@5,0:e,raw
sd@1,0:b sd@1,0:f,raw sd@2,0:c sd@2,0:g,raw sd@3,0:d sd@3,0:h,raw sd@4,0:e sd@5,0:a,raw sd@5,0:f
sd@1,0:b,raw sd@1,0:g sd@2,0:c,raw sd@2,0:h sd@3,0:d,raw sd@4,0:a sd@4,0:e,raw sd@5,0:b sd@5,0:f,raw
sd@1,0:c sd@1,0:g,raw sd@2,0:d sd@2,0:h,raw sd@3,0:e sd@4,0:a,raw sd@4,0:f sd@5,0:b,raw sd@5,0:g
sd@1,0:c,raw sd@1,0:h sd@2,0:d,raw sd@3,0:a sd@3,0:e,raw sd@4,0:b sd@4,0:f,raw sd@5,0:c sd@5,0:g,raw
sd@1,0:d sd@1,0:h,raw sd@2,0:e sd@3,0:a,raw sd@3,0:f sd@4,0:b,raw sd@4,0:g sd@5,0:c,raw sd@5,0:h
sd@1,0:d,raw sd@2,0:a sd@2,0:e,raw sd@3,0:b sd@3,0:f,raw sd@4,0:c sd@4,0:g,raw sd@5,0:d sd@5,0:h,raw
sd@1,0:e sd@2,0:a,raw sd@2,0:f sd@3,0:b,raw sd@3,0:g sd@4,0:c,raw sd@4,0:h sd@5,0:d,raw
# pwd
/devices/sbus@2,0/SUNW,fas@1,8800000



I'll appreciate any help or advise.

 

[ponetguy2]

i checked out everything pertaining to target 4 and lun 0 and all seems well. i did a metastat and looked at the status of any device connected to t4 and all is well. however, i'm still a little unsure.

 

[ponetguy2]

Bad disk!!!!

format command indicates a bad disk w/ b04. format command usually hangs when there is a bad disk.

vfstab entry:

/dev/dsk/c1t7d0s1 /dev/rdsk/c1t7d0s1 /b04 ufs 4 yes -

 

[Annihilannic]

format command usually hangs when there is a bad disk.

Not in my experience?

Annihilannic.

 

[daFranze]

so do I; usually a format will just read the devicetree entry. If there is a failed disk you will not get the disklabel in the format list.

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years in the domain of the OS, Backup and Storage

 

[ponetguy2]

yes, format will not read the disk entry. one will just find something like this:


10. c2t4d0 <drive not available: formatting>
/sbus@2,0/SUNW,fas@1,8800000/sd@4,0

This usually indicates a failed disk.

 

[dandan123]

Can you run format on a disk which is under VxVM control ?

 

[Annihilannic]

Yes, you can run format on it, as long as you don't actually use the "format" subcommand within the format utility to overwrite its contents, or modify the partition table or anything else destructive.

Annihilannic.

 

[dandan123]

So you can (read) scan the disk and fix bad sectors ?

 

[Annihilannic]

Yes.

Annihilannic.