Install Solaris 10

SmartAntz · January 24, 2010, 11:31pm

Hi all,

Currently I wish to upgrade a server from Solaris 8 to Solaris 10.
This server cannot access to internet. and will upgrade to Solaris 10 for testing purpose.
the data before that no need to backup. =)

My question is what is the proper way to upgrade the OS version?
is it just need to boot cdrom and direct install ?

below is the current server details:

root@leo # uname -a
SunOS leo 5.8 Generic_117350-46 sun4u sparc SUNW,Sun-Fire-V490

root@leo # df -k
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/vx/dsk/bootdg/rootvol
                     116961355 11976577 103815165    11%    /
/proc                      0       0       0     0%    /proc
mnttab                     0       0       0     0%    /etc/mnttab
fd                         0       0       0     0%    /dev/fd
swap                 31232560      24 31232536     1%    /var/run
dmpfs                31232536       0 31232536     0%    /dev/vx/dmp
dmpfs                31232536       0 31232536     0%    /dev/vx/rdmp
swap                 31232864     328 31232536     1%    /tmp

root@leo # format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c6a73c58,0
       1. c1t1d0 <SEAGATE-ST314670FSUN146G-0354 cyl 14087 alt 2 hd 24 sec 848>
          /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c6a75d1b,0
       2. c2t8d1 <EMC-SYMMETRIX-5567 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,1
       3. c2t8d2 <EMC-SYMMETRIX-5567 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,2
       4. c2t8d3 <EMC-SYMMETRIX-5567 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,3
       5. c2t8d4 <EMC-SYMMETRIX-5567 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,4
       6. c2t8d5 <EMC-SYMMETRIX-5567 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,5
       7. c2t8d6 <EMC-SYMMETRIX-5567 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,6
       8. c2t8d7 <EMC-SYMMETRIX-5567 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,7
       9. c2t8d8 <EMC-SYMMETRIX-5567 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,8
      10. c2t8d30 <EMC-SYMMETRIX-5566 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,1e
      11. c2t8d31 <EMC-SYMMETRIX-5566 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,1f
      12. c2t8d32 <EMC-SYMMETRIX-5566 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,20
      13. c2t8d33 <EMC-SYMMETRIX-5566 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,21
      14. c2t8d34 <EMC-SYMMETRIX-5566 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,22
      15. c2t8d35 <EMC-SYMMETRIX-5566 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,23
      16. c2t8d36 <EMC-SYMMETRIX-5566 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,24
      17. c2t8d37 <EMC-SYMMETRIX-5566 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,25
      18. c2t8d38 <EMC-SYMMETRIX-5566 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,26
      19. c2t8d39 <EMC-SYMMETRIX-5567 cyl 18412 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,27
      20. c2t8d240 <EMC-SYMMETRIX-5566 cyl 4 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,f0
      21. c2t8d241 <EMC-SYMMETRIX-5566 cyl 4 alt 2 hd 15 sec 64>
          /pci@8,600000/QLGC,qla@1/sd@8,f1

#device         device          mount           FS      fsck    mount   mount
#to mount       to fsck         point           type    pass    at boot options
#
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr          ufs     1       yes     -
fd      -       /dev/fd fd      -       no      -
/proc   -       /proc   proc    -       no      -
/dev/vx/dsk/bootdg/swapvol      -       -       swap    -       no      -
/dev/vx/dsk/bootdg/rootvol      /dev/vx/rdsk/bootdg/rootvol     /       ufs
1       no      -
swap    -       /tmp    tmpfs   -       yes     -
#NOTE: volume rootvol (/) encapsulated partition c1t0d0s0
#NOTE: volume swapvol (swap) encapsulated partition c1t0d0s1

What information i need to gather before upgrade ?
Kindly advise =)

incredible · January 25, 2010, 1:12am

Have a backup first (maybe using flash archive)
Break the OS mirror and change it to raw device. Ensure both disks are bootable by themselves.
Download latest Solaris 10 dvd image and burn.
Boot the system from ok> prompt to boot cdrom and follow through the installation process. When it prompts for the type, choose "Upgrade Install"
That's it.
Check your apps after bootup. Mine was successful.
If you find problem in yours, then recover it from your backup disk and use your Solaris 8:)

SmartAntz · January 25, 2010, 1:23am

how to check the mirror information Solaris 8?
coz when me run the metastat to check, it give me the error

root@leo # metastat
metastat: not found

incredible · January 25, 2010, 6:16am

which metastat
or find / -name metastat -print

brusell · January 25, 2010, 9:43am

Guys, on output from /etc/vfstab you can see that this server is using Veritas file system.

incredible · January 25, 2010, 10:27am

So what? :rolleyes:
That's where I asking the OP to change the filesystem to raw device (to take out of VxVM control) and then do the upgrade.
If successful, he can install VxVM again and encapsulate the root disks..

SmartAntz · January 25, 2010, 7:33pm

Hmn.. the result not so good..

root@leo # which metastat
no metastat in /usr/sbin /usr/bin /usr/ccs/bin /usr/openwin/bin /usr/dt/bin /usr/platform/SUNW,Sun-Fire-V490/sbin /opt/sun/bin /etc/vx/bin /opt/VRTS/bin /etc/vx/bin /opt/VRTSob/bin /opt/VRTSvlic/bin /opt/SUNWexplo/bin /opt/CTEact/bin
root@leo # find / -name metastat -print
root@leo #

what are the step i should do now? :o

TonyFullerMalv · January 25, 2010, 8:26pm

You evidently do not have disk mirroring using disksuite, if you were /etc/vfstab entries for local disks would be /dev/md. Your system is using Veritas (now owned by Symantec) Volume Manager for its mirroring hence your disks are mounted /dev/vx as pointed out by Incredible. You need to undo the mirroring and return the /etc/vfstab back normal /dev/dsk mounts before upgrading. Suggest checking on the Symantec web site on how to do this if you do not know.

SmartAntz · January 25, 2010, 9:48pm

Since this is my first time touch on the Veritas.
Hope you all kindly advise me, if got any wrong or mistake. =)
and hope can guide me step by step. =)

Below is the veritas disk listing

root@leo # vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c1t0d0s2     auto:sliced     rootdg01     rootdg       online
c1t1d0s2     auto:sliced     rootdg02     rootdg       online
c2t8d1s2     auto:sliced     -            -            online
c2t8d2s2     auto:sliced     -            -            online
c2t8d3s2     auto:sliced     -            -            online
c2t8d4s2     auto:sliced     -            -            online
c2t8d5s2     auto:sliced     -            -            online
c2t8d6s2     auto:sliced     -            -            online
c2t8d7s2     auto:sliced     -            -            online
c2t8d8s2     auto:sliced     -            -            online
c2t8d30s2    auto:sliced     -            -            online
c2t8d31s2    auto:sliced     -            -            online
c2t8d32s2    auto:sliced     -            -            online
c2t8d33s2    auto:sliced     -            -            online
c2t8d34s2    auto:sliced     -            -            online
c2t8d35s2    auto:sliced     -            -            online
c2t8d36s2    auto:sliced     -            -            online
c2t8d37s2    auto:sliced     -            -            online
c2t8d38s2    auto:sliced     -            -            online
c2t8d39s2    auto:none       -            -            online invalid

root@leo #  vxprint
Disk group: rootdg

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

dm rootdg01     c1t0d0s2     -        286698623 -       -        -       -
dm rootdg02     c1t1d0s2     -        286657920 -       -        -       -

sd rootdg01Priv -            ENABLED  40703    -        -        -       PRIVATE

v  rootvol      root         ENABLED  237528192 -       ACTIVE   -       -
pl rootvol-01   rootvol      ENABLED  237528192 -       ACTIVE   -       -
sd rootdg01-B0  rootvol-01   ENABLED  1        0        -        -       Block0
sd rootdg01-02  rootvol-01   ENABLED  237528191 1       -        -       -
pl rootvol-02   rootvol      ENABLED  237528192 -       ACTIVE   -       -
sd rootdg02-01  rootvol-02   ENABLED  237528192 0       -        -       -

v  swapvol      swap         ENABLED  49129728 -        ACTIVE   -       -
pl swapvol-01   swapvol      ENABLED  49129728 -        ACTIVE   -       -
sd rootdg01-01  swapvol-01   ENABLED  49129728 0        -        -       -
pl swapvol-02   swapvol      ENABLED  49129728 -        ACTIVE   -       -
sd rootdg02-02  swapvol-02   ENABLED  49129728 0        -        -       -
root@leo #

brusell · January 27, 2010, 6:24am

OK, and some explanation, why to use Veritas when you have SVM as a native part of Solaris 10 for free???
I suppose that SVM is very good piece of software, so I don't see any reason why don't use it.

incredible · January 27, 2010, 7:02am

Hi Brusell,
I don't think you understand what Im saying. I think there's some communication break-down here.

TonyFullerMalv · January 27, 2010, 4:42pm

I was on a Veritas SVM course where they recommend you use SVM for the system disks and VxVm for the data disks.

I would use SVM for the root/system disks after the upgrade rather than use VxVm.

Incredible was not saying you *had* to use VxVm he was just stating what you would have to do to reinstate the system back the way it was before the upgrade.

dpc.ucore.info · January 28, 2010, 9:32am

When the VxVM breaks it is much trickier to get it back working if you're unable to access / partition easily. That is why it is more common to use SVM for / . And / usage pattern is usually very stable through the system lifetime and once set up it rather not change. That's why you don't need fancy features of VxVM.

SmartAntz · February 9, 2010, 3:06am

for double confirm, when i wish to upgrade the solaris from 8 to 10,
is a must to break the Veritas?

incredible · February 9, 2010, 5:33am

Yes, YOU HAVE TO BREAK THE OS MIRROR

dpc.ucore.info · February 9, 2010, 10:58am

Post deleted. Sorry.