Hi
I've got a problem with a Sun E3500 running Solaris 2.6 and Veritas. I'm not sure which version of Veritas it is, but when I run vxserial -p it returns release level 22, whichever that is. Can you tell I'm not a Solaris bod???
Now, I know this is a very old server, and I'd forgotten it was still running prod jobs, but now I'm stuck with it.
Anyway, I got an automated page out for a fault with this server, simply saying media failure. I've run a dmesg and found a few references of:
*****
WARNING: /sbus@2,0/QLGC,isp@2,10000/sd@c,0 (sd26):
Error for Command: load/start/stop Error Level: Retryable
Requested Block: 0 Error Block: 0
Vendor: IBM Serial Number: 011714D21
Sense Key: Not Ready
ASC: 0x4 (LUN not ready), ASCQ: 0x0, FRU: 0x0
*****
I've then run a vxprint -Ath and got:
*****
dg rootdg default default 0 976896389.1025.cwspr06
dm disk01 c0t2d0s2 sliced 4711 35363560 FAILING
dm disk03 c1t5d0s2 sliced 4711 35363560 -
dm disk05 - - - - NODEVICE
dm disk06 c0t1d0s2 sliced 3590 17678493 -
dm rootdisk c0t0d0s2 sliced 3590 17682083 -
*****
Looking further down the vxprint output I can see no references to any filesystem using disk01, but I can see that disk05 has the submirrors for /usr and /var.
From there, I've done a read test using format on what it reports is a failing disk - c0t2d0s2 - and got no errors.
So 2 questions:
Firstly, if an analyze/read test reports no problems, what can be causing Veritas to think there is one?
Secondly, it also states a disk05 has NODEVICE. How do I find out what this should have been? A vxlist all doesn't refer to it at all?
Thanks in advance.
I've got a problem with a Sun E3500 running Solaris 2.6 and Veritas. I'm not sure which version of Veritas it is, but when I run vxserial -p it returns release level 22, whichever that is. Can you tell I'm not a Solaris bod???
Now, I know this is a very old server, and I'd forgotten it was still running prod jobs, but now I'm stuck with it.
Anyway, I got an automated page out for a fault with this server, simply saying media failure. I've run a dmesg and found a few references of:
*****
WARNING: /sbus@2,0/QLGC,isp@2,10000/sd@c,0 (sd26):
Error for Command: load/start/stop Error Level: Retryable
Requested Block: 0 Error Block: 0
Vendor: IBM Serial Number: 011714D21
Sense Key: Not Ready
ASC: 0x4 (LUN not ready), ASCQ: 0x0, FRU: 0x0
*****
I've then run a vxprint -Ath and got:
*****
dg rootdg default default 0 976896389.1025.cwspr06
dm disk01 c0t2d0s2 sliced 4711 35363560 FAILING
dm disk03 c1t5d0s2 sliced 4711 35363560 -
dm disk05 - - - - NODEVICE
dm disk06 c0t1d0s2 sliced 3590 17678493 -
dm rootdisk c0t0d0s2 sliced 3590 17682083 -
*****
Looking further down the vxprint output I can see no references to any filesystem using disk01, but I can see that disk05 has the submirrors for /usr and /var.
From there, I've done a read test using format on what it reports is a failing disk - c0t2d0s2 - and got no errors.
So 2 questions:
Firstly, if an analyze/read test reports no problems, what can be causing Veritas to think there is one?
Secondly, it also states a disk05 has NODEVICE. How do I find out what this should have been? A vxlist all doesn't refer to it at all?
Thanks in advance.