VxVM and Solaris 2.6

From: Greene, Marco (Marco.Greene@nexinnovations.com)
Date: Thu Feb 13 2003 - 09:43:09 EST


First some specifics. This is an E3000 running Solaris 2.6 and VxVM

pkginfo -l SUNWvxvm
   PKGINST: SUNWvxvm
      NAME: Sun StorEdge Volume Manager
  CATEGORY: system
      ARCH: sparc
   VERSION: 2.6,REV=2.5.3
    VENDOR: Sun Microsystems, Inc.
      DESC: Virtual Disk Subsystem
    PSTAMP: veritas-2.5.3c:27-apr-1998
  INSTDATE: Feb 18 2001 00:39
   HOTLINE: Please contact your local service provider
    STATUS: completely installed
     FILES: 225 installed pathnames
                11 shared pathnames
                 6 linked files
                37 directories
               122 executables
                 1 setuid/setgid executables
             24150 blocks used (approx)

This is the process that I used:
Rebooted the server to the alternate boot disk.
vxdiskadm - Remove disk for replacement
touch /reconfigure
Shutdown the server, replaced the bad disk with a good one
boot the server from the second disk
vxdctl enable
vxdiskadm - Replace failed or removed disk

While using vxdiskadm to replace the rootdisk, I am getting the
following error....

Continue with operation? [y,n,q,?] (default: y)
UNKNOWN ERROR WHILE WRITTING VTOC
UNKNOWN ERROR WHILE WRITTING VTOC
dd: /dev/rdsk/c2t0d0s0: open: I/O error

  Replacement of disk rootdisk in group rootdg with disk device
  c2t0d0 completed successfully.

Replace another disk? [y,n,q,?] (default: n)

*****
So with the error message, I think that I am OK because it also
indicated the rootdisk was replaced successfully, but then vxprint shows
me the following....notice the IOFAIL. This is a brand new disk and I
have had the same problem on other disks. From the OS point of view I
can format it and use it without problem, but within VxVM, I am having
some major issues.
*****

Disk group: rootdg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0
PUTIL0
dg rootdg rootdg - - - - -
-

dm disk01 c2t1d0s2 - 8378640 - - -
-
dm rootdisk c2t0d0s2 - 8378640 - - -
-

v home fsgen ENABLED 1060000 - ACTIVE ATT1
-
pl home-01 home ENABLED 1060000 - STALE ATT
-
sd rootdisk-08 home-01 ENABLED 1060000 0 - -
-
pl home-02 home ENABLED 1060560 - ACTIVE -
-
sd disk01-06 home-02 ENABLED 1060560 0 - -
-

v opt fsgen ENABLED 1740960 - ACTIVE -
-
pl opt-02 opt ENABLED 1740960 - ACTIVE -
-
sd disk01-05 opt-02 ENABLED 1740960 0 - -
-
pl opt-01 opt DISABLED 1740960 - RECOVER -
-
sd rootdisk-12 opt-01 ENABLED 1740960 0 - -
-

v oracle fsgen ENABLED 2336768 - ACTIVE -
-
pl oracle-01 oracle DISABLED 2337120 - RECOVER -
-
sd rootdisk-09 oracle-01 ENABLED 2337120 0 - -
-
pl oracle-02 oracle ENABLED 2337120 - ACTIVE -
-
sd disk01-07 oracle-02 ENABLED 2337120 0 - -
-

v rootvol root ENABLED 164160 - ACTIVE -
-
pl rootvol-02 rootvol ENABLED 164160 - ACTIVE -
-
sd disk01-01 rootvol-02 ENABLED 164160 0 - -
-
pl rootvol-01 rootvol DISABLED 164160 - IOFAIL -
-
sd rootdisk-11 rootvol-01 ENABLED 164160 0 - -
-

v swapvol swap ENABLED 1434240 - ACTIVE -
-
pl swapvol-02 swapvol ENABLED 1434240 - ACTIVE -
-
sd disk01-02 swapvol-02 ENABLED 1434240 0 - -
-
pl swapvol-01 swapvol DISABLED 1434240 - RECOVER -
-
sd rootdisk-10 swapvol-01 ENABLED 1434240 0 - -
-

v usr fsgen ENABLED 1127520 - ACTIVE -
-
pl usr-02 usr ENABLED 1127520 - ACTIVE -
-
sd disk01-03 usr-02 ENABLED 1127520 0 - -
-
pl usr-01 usr DISABLED 1127520 - IOFAIL -
-
sd rootdisk-14 usr-01 ENABLED 1127520 0 - -
-

v var fsgen ENABLED 514080 - ACTIVE -
-
pl var-02 var ENABLED 514080 - ACTIVE -
-
sd disk01-04 var-02 ENABLED 514080 0 - -
-
pl var-01 var DISABLED 514080 - RECOVER -
-
sd rootdisk-13 var-01 ENABLED 514080 0 - -
-

******
SCSI Inquiry shows the following for the replaced disk:
Vendor: SEAGATE
Product: ST34371W SUN4.2G
Revision: 3162

SCSI Inquiry show the following for the existing good disk:
Vendor: SEAGATE
Product: ST34371W SUN4.2G
Revision: 7462

Could it have something to do with the revision number on the drive?

Note, I know if I do it this way, upgrading is going to be a pain.
However, because of the software running on this server upgrading is not
an option. This server was previously upgraded from Solaris 2.5.1 but
that was way before I took over admin responsibilities for this box.

I am at a loss. Has anyone seen this before and know how to get around
it?

Thanks and will summarize.

Marco Greene, BEng
Infrastructure and Recovery Architect
NexInnovations Inc.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:25:48 EDT