[SunHELP] metadb -i shows error

Sat Mar 20 22:59:58 CST 2004

I would have to concur that the disk looks like it is going bad from the 
info I see.  If it was the controller all your targets would be showing 
issues.  From what I see, the meta db's on that disk are not masters so you 
should be able to delete them, change the disk and then add them 
later.  Depending on your RAID setup make sure you have a good backup of 
the data if you can get it.

Good luck.

Bret

At 05:19 PM 3/19/04 -0500, you wrote:
>After many years of carefree use of Disksuite on an E450 with Solaris 8, I'm
>seeing my first error. metadb -i shows:
>
>       W   p  l          16              1034            /dev/dsk/c2t3d0s0
>       W   p  l          1050            1034            /dev/dsk/c2t3d0s0
>       W   p  l          2084            1034            /dev/dsk/c2t3d0s0
>
>the W indicating a write error.
>
>dmesg also reports:
>
>Mar 19 15:37:24 deathstar scsi: [ID 365881 kern.info] /pci at 4,4000/scsi at 4
>(glm6):
>Mar 19 15:37:24 deathstar       Cmd (0xa7a1470) dump for Target 3 Lun 0:
>Mar 19 15:37:24 deathstar scsi: [ID 365881 kern.info] /pci at 4,4000/scsi at 4
>(glm6):
>Mar 19 15:37:24 deathstar               cdb=[ 0xa 0x0 0x8 0x4c 0x1 0x0 ]
>Mar 19 15:37:24 deathstar scsi: [ID 365881 kern.info] /pci at 4,4000/scsi at 4
>(glm6):
>Mar 19 15:37:24 deathstar       pkt_flags=0x4000 pkt_statistics=0x61 
>pkt_state=0x7
>Mar 19 15:37:24 deathstar scsi: [ID 365881 kern.info] /pci at 4,4000/scsi at 4
>(glm6):
>Mar 19 15:37:24 deathstar       pkt_scbp=0x0 cmd_flags=0x18e1
>Mar 19 15:37:24 deathstar scsi: [ID 107833 kern.warning] WARNING:
>/pci at 4,4000/scsi at 4 (glm6):
>Mar 19 15:37:24 deathstar       Disconnected tagged cmd(s) (1) timeout for 
>Target
>3.0
>Mar 19 15:37:24 deathstar genunix: [ID 408822 kern.info] NOTICE: glm6: fault
>detected in device; service still available
>Mar 19 15:37:24 deathstar genunix: [ID 611667 kern.info] NOTICE: glm6:
>Disconnected tagged cmd(s) (1) timeout for Target 3.0
>Mar 19 15:37:24 deathstar glm: [ID 401478 kern.warning] WARNING:
>ID[SUNWpd.glm.cmd_timeout.6018]
>Mar 19 15:37:24 deathstar scsi: [ID 107833 kern.warning] WARNING:
>/pci at 4,4000/scsi at 4 (glm6):
>Mar 19 15:37:24 deathstar       got SCSI bus reset
>Mar 19 15:37:24 deathstar genunix: [ID 408822 kern.info] NOTICE: glm6: fault
>detected in device; service still available
>Mar 19 15:37:24 deathstar genunix: [ID 611667 kern.info] NOTICE: glm6: got
>SCSI bus reset
>Mar 19 15:37:24 deathstar scsi: [ID 107833 kern.warning] WARNING:
>/pci at 4,4000/scsi at 4/sd at 3,0 (sd93):
>Mar 19 15:37:24 deathstar       SCSI transport failed: reason 'timeout': 
>retrying
>command
>Mar 19 15:37:42 deathstar scsi: [ID 107833 kern.warning] WARNING:
>/pci at 4,4000/scsi at 4/sd at 3,0 (sd93):
>Mar 19 15:37:42 deathstar       Error for Command: 
>write                   Error
>Level: Fatal
>Mar 19 15:37:42 deathstar scsi: [ID 107833 kern.notice]         Requested 
>Block: 2124
>Error Block: 2124
>Mar 19 15:37:42 deathstar scsi: [ID 107833 kern.notice]         Vendor: 
>SEAGATE
>Serial Number: 0031V0MYN4
>Mar 19 15:37:42 deathstar scsi: [ID 107833 kern.notice]         Sense Key: 
>Not Ready
>Mar 19 15:37:42 deathstar scsi: [ID 107833 kern.notice]         ASC: 0x4 
>(<vendor
>unique code 0x4>), ASCQ: 0x1, FRU: 0x2
>Mar 19 15:37:53 deathstar scsi: [ID 107833 kern.warning] WARNING:
>/pci at 4,4000/scsi at 4/sd at 3,0 (sd93):
>Mar 19 15:37:53 deathstar       Error for Command: 
>write                   Error
>Level: Fatal
>Mar 19 15:37:53 deathstar scsi: [ID 107833 kern.notice]         Requested 
>Block: 51
>Error Block: 51
>Mar 19 15:37:53 deathstar scsi: [ID 107833 kern.notice]         Vendor: 
>SEAGATE
>Serial Number: 0031V0MYN4
>Mar 19 15:37:53 deathstar scsi: [ID 107833 kern.notice]         Sense Key: 
>Not Ready
>Mar 19 15:37:53 deathstar scsi: [ID 107833 kern.notice]         ASC: 0x4 
>(<vendor
>unique code 0x4>), ASCQ: 0x1, FRU: 0x2
>Mar 19 15:38:03 deathstar scsi: [ID 107833 kern.warning] WARNING:
>/pci at 4,4000/scsi at 4/sd at 3,0 (sd93):
>Mar 19 15:38:03 deathstar       Error for Command: 
>write                   Error
>Level: Fatal
>Mar 19 15:38:03 deathstar scsi: [ID 107833 kern.notice]         Requested 
>Block: 1085
>Error Block: 1085
>Mar 19 15:38:03 deathstar scsi: [ID 107833 kern.notice]         Vendor: 
>SEAGATE
>Serial Number: 0031V0MYN4
>Mar 19 15:38:03 deathstar scsi: [ID 107833 kern.notice]         Sense Key: 
>Not Ready
>Mar 19 15:38:03 deathstar scsi: [ID 107833 kern.notice]         ASC: 0x4 
>(<vendor
>unique code 0x4>), ASCQ: 0x1, FRU: 0x2
>
>sd93 is c2t3
>
>so my questions are:
>
>As I have many more replicas on other disks it should be perfectly safe to
>delete the 3 on /dev/dsk/c2t3d0s0
>without causing problems, correct? (metadb -f -d /dev/dsk/c2t3d0s0)
>
>Looking at dmesg, is the disk going or is the write error fatal because the 3
>replicas are "bad" (my feeling is the disk is going bad)?
>
>I will summarize.
>
>Regards,
>
>Michael J. Connolly
>Worldwide PLM/PDM Manager
>ITT Industries, Cannon
>617-969-3700 x8302
>
>
>************************************
>This email and any files transmitted with it are proprietary and intended
>solely for the use of the individual or entity to whom they are addressed. If
>you have received this email
>in error please notify the sender. Please note that any views or opinions
>presented in this email are solely those of the author and do not necessarily
>represent those of ITT Industries, Inc.
>The recipient should check this email and any attachments for the presence of
>viruses. ITT Industries accepts no liability for any damage caused by any
>virus transmitted by this
>email.
>************************************
>_______________________________________________
>SunHELP maillist  -  SunHELP at sunhelp.org
>http://www.sunhelp.org/mailman/listinfo/sunhelp