Solaris upgrade with Veritas filesystem

[terrywashington]

I have been tasked with upgrading an E450 from Solaris 2.6 to 2.8. The root disk and four partitions are controlled by Veritas Volume Manager 3.1. I have no experience with Veritas but am familiar with Disksuite. I have been going through the docs left by the previous admin and found that the upgrade should be rather straight forward. It looks like I will run upgrade_start, upgrade the system and run upgrade_finish. I am concerned as the server is showing errors when I run vxdisk list. The output is below. Is it safe to attempt an upgrade in this condition? Also if the disks are mirrored shouldn’t they be partitioned identically? I know that is the case in Disksuite. I have included the results of vxlist disk, df –k and format below. Any input would be greatly appreciated. Thanks.

# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 sliced rootdisk rootdg online
c0t1d0s2 sliced - - error
c0t2d0s2 sliced - - error
c0t3d0s2 sliced - - error
c2t0d0s2 sliced - - error
c2t1d0s2 sliced - - error
c2t2d0s2 sliced - - online invalid
c2t3d0s2 sliced homedir02 homedir online
c3t0d0s2 sliced - - error
c3t1d0s2 sliced - - error
c3t2d0s2 sliced - - error
c3t3d0s2 sliced - - error
c4t0d0s2 sliced - - error
c4t1d0s2 sliced - - error
c4t2d0s2 sliced - - error
c4t3d0s2 sliced homedir01 homedir online
c5t0d0s2 sliced devp01 devp online
c5t1d0s2 sliced devp02 devp online
c5t2d0s2 sliced devp05 devp online
c5t3d0s2 sliced devp03 devp online
c5t4d0s2 sliced devp06 devp online
c5t5d0s2 sliced devp04 devp online
c5t8d0s2 sliced devp07 devp online
c5t9d0s2 sliced devp08 devp online
# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/rootvol 1986439 1533125 393721 80% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
/dev/vx/dsk/opt 6169915 4482077 1626139 74% /opt
swap 600064 11328 588736 2% /tmp
/dev/dsk/c0t2d0s2 8705501 4529969 4088477 53% /databases
/dev/dsk/c0t3d0s2 8705501 6386419 2232027 75% /disk3
/dev/md/dsk/d1 69630637 39629451 29304880 58% /disk1
/dev/dsk/c4t0d0s2 17413250 5469848 11769270 32% /disk2
/dev/dsk/c4t1d0s2 17413250 1174050 16065068 7% /export/oldhome
/dev/dsk/c4t2d0s2 17413250 10092464 7146654 59% /newdisk1
/dev/vx/dsk/devp/vol01
100013145 78660646 20352368 80% /morganadm
/dev/vx/dsk/homedir/timeiq
479982 22368 452815 5% /disk5
/dev/vx/dsk/homedir/home01
24380812 21415448 2721556 89% /export/home
/dev/vx/dsk/devp/vol02
66678240 58794795 7216663 90% /disk6
/export/home/fsmadmin
24380812 21415448 2721556 89% /home/fsmadmin

# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/pci@1f,4000/scsi@3/sd@0,0
1. c0t1d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/pci@1f,4000/scsi@3/sd@1,0
2. c0t2d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/pci@1f,4000/scsi@3/sd@2,0
3. c0t3d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/pci@1f,4000/scsi@3/sd@3,0
4. c2t0d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/pci@6,4000/scsi@4/sd@0,0
5. c2t1d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/pci@6,4000/scsi@4/sd@1,0
6. c2t2d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/pci@6,4000/scsi@4/sd@2,0
7. c2t3d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/pci@6,4000/scsi@4/sd@3,0
8. c3t0d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/pci@6,4000/scsi@4,1/sd@0,0
9. c3t1d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/pci@6,4000/scsi@4,1/sd@1,0
10. c3t2d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/pci@6,4000/scsi@4,1/sd@2,0
11. c3t3d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/pci@6,4000/scsi@4,1/sd@3,0
12. c4t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
/pci@6,4000/scsi@3/sd@0,0
13. c4t1d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
/pci@6,4000/scsi@3/sd@1,0
14. c4t2d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
/pci@6,4000/scsi@3/sd@2,0
15. c4t3d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
/pci@6,4000/scsi@3/sd@3,0
16. c5t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@6,4000/scsi@2/sd@0,0
17. c5t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@6,4000/scsi@2/sd@1,0
18. c5t2d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@6,4000/scsi@2/sd@2,0
19. c5t3d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@6,4000/scsi@2/sd@3,0
20. c5t4d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@6,4000/scsi@2/sd@4,0
21. c5t5d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@6,4000/scsi@2/sd@5,0
22. c5t8d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@6,4000/scsi@2/sd@8,0
23. c5t9d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@6,4000/scsi@2/sd@9,0
Specify disk (enter its number):

 

[crowe]

I would start by checking how many disks are REALLY in the system. (open the door on the 450). I dont think a 450 supports 23 disks, although it does support quite a few. It could be that these are dangling disk devices from previous disks. Once the number of disks is established, you will want to clean up the old ones, and make the old (not really there) disks unknown to VxVM.

crowe

 

[julianbarnett]

Looks like you probably have 16 out of a possible 20 disks in the E450 itself. The remaining ones 8 x 36Gbs on channel 5 I'm guessing are in an external unit (A1000, D1000). You have a rather odd layout in that you have some disks under SDS, some under no disk management and others under Veritas. My guess is that this system has, how can I put it ...evolved. To get a real understanding of how your system is laid out you would also need to post the metastat output and a vxprint -hrt listing.

The disks showing error are not really in error - just not under Veritas control. Your homedir diskgroup seems to be a simple Veritas concat or stripe of a 9G (c2t3) and 18G (c4t3) drive. fmsadm looks like a automounted directory in the /export/home directory. The SDS disk d1 appears to be a stripe or concat of 8 9G disks (c0t1, c2t0-c2t2, c3t0-c3t3) I'm assuming one is c2t2 hence the invalid status from Veritas. The rest of the devices on the devp diskgroup may be RAID5 - difficult to tell.

You should be able to upgrade but your system appears to have no resilience on the internal disks. You would be better off getting a good understanding of the layout of the disks and addressing some of the issues before undertaking an upgrade.

Julian

 

[terrywashington]

Thanks for the info.

 

[Samirjha]

Hi,

I am upgrading from solaris 2.5.1 to solaris 5.8. I have got veritas 3.0.3 installed on which I have data disks.
When the upgrade is completed, the server is not able to boot, it says that incompatible kernel for vxvmboot. Is there any specific way for this kind of upgrade or what other options can I try. Any inputs will be greatly appreciated.

thx in advance

 

[rgaskill1]

Hi,
There is some useful stuff on OS upgrades on sunsolve, go to sunsolve.sun.com and search for infodocs 14189 and 48.

Regards