cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with internal FC disk replacement on SunFire 280R

kodaali
Level 3

Hello,

We replaced failed FC drive and all looks good at OS level. However, under veritas control it is showing as error and everytime we run vxdctl its generating new error devices. We cleaned up the device tree (both veritas and OS : removed disk from veritas, dmp, removed device using luxadm and physicall y removed disk, then devfsadm -Cv, inserted the drive, os detected, vxconfigd -k), still no luck. We followed instructions religiously from technote

Article URL http://www.symantec.com/docs/TECH73249


We are planning to reboot, however would like to check if anything i'm missing.

Thanks in Advance

Nagesh

 

 # echo | format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
       0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cf4cf914,0
       1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
          /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cf9f4da3,0
Specify disk (enter its number): Specify disk (enter its number):

# prtvtoc -s /dev/rdsk/c1t1d0s2
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       2      5    01          0  71127180  71127179
       3     15    01       2889      2889      5777
       4     14    01       5778  71121402  71127179
#

# vxdisk -e list
DEVICE       TYPE      DISK         GROUP        STATUS       OS_NATIVE_NAME
c1t0d0s2     auto      rootdisk      rootdg       online       c1t0d0s2
c1t1d0s2     auto      -             -            error        c1t1d0s2
c1t1d0s2     auto      -             -            error        c1t1d0s2
c1t1d0s2     auto      -             -            error        c1t1d0s2
-            -         rootmir      rootdg       removed was:c1t1d0s2
# 
1 ACCEPTED SOLUTION

Accepted Solutions

kodaali
Level 3

We left with no option and rebooted the machine. That fixed the issue.

View solution in original post

4 REPLIES 4

Gaurav_S
Moderator
Moderator
   VIP    Certified

what is OS & vxvm version you are using ?

# pkginfo -l VRTSvxvm

# uname -a

 

 

G

kodaali
Level 3

its 4.1 mp2 rp3 and solaris 8. (both are quiet old)

 $ modinfo | grep vx
 20 78016000 21ce29 273   1  vxio (VxVM 4.1_MP2_RP3 I/O driver)
 21 101fe548  35483 272   1  vxdmp (VxVM 4.1_MP2_RP3: DMP Driver)
 48 10338923   14a1 274   1  vxspec (VxVM 4.1_MP2_RP3 control/status)
281 7857b4ca    cb3 275   1  vxportal (VxFS 4.1_REV-MP2RP3a2 portal dr)
282 78584000 171d0d  18   1  vxfs (VxFS 4.1_REV-MP2RP3a2 SunOS 5.8)

$ pkginfo -l VRTSvxvm
   PKGINST:  VRTSvxvm
      NAME:  VERITAS Volume Manager, Binaries
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  4.1,REV=02.17.2005.21.28
   BASEDIR:  /
    VENDOR:  VERITAS Software
      DESC:  Virtual Disk Subsystem
    PSTAMP:  VERITAS-4.1_MP2_RP3.2:2007-12-03
  INSTDATE:  Feb 20 2010 00:39
   HOTLINE:  800-342-0652
     EMAIL:  support@veritas.com
    STATUS:  completely installed
     FILES:      848 installed pathnames
                  26 shared pathnames
                  18 linked files
                  98 directories
                 418 executables
              306838 blocks used (approx)

$ uname -a
SunOS test 5.8 Generic_117350-62 sun4u sparc SUNW,Sun-Fire-280R

$ cat /etc/release
                     Solaris 8 HW 5/03 s28s_hw2wos_06a SPARC
           Copyright 2003 Sun Microsystems, Inc.  All Rights Reserved.
                             Assembled 30 April 2003
$ 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

If these steps don't work, seems you have no choice but to do reconfiguration reboot:

1. mv /etc/vx/array.info /etc/vx/array.info.old
2. mv /etc/vx/disk.info /etc/vx/disk.info.old
3. rm /dev/vx/dmp/*
4. rm /dev/vx/rdmp/*
5. rm /dev/dsk/c#t#d#s# <------Remove all entries except for internal boot devices.
6. rm /dev/rdsk/c#t#d#s# <-------Remove all entries except for internal boot devices.
7. devfsadm -Cv
8. vxconfigd -k

kodaali
Level 3

We left with no option and rebooted the machine. That fixed the issue.