These are the steps to upgrade a Netra t1 with two identical disks from solaris 9 to solaris 10, using liveupgrade with a
\nSolaris 10 image from a standard jumpstart directory. This procedure is good because it needs no downtime, and the
\nconfigurarion you have in your original system is preserved (\/etc,\/export\/home).
\nIf you have a jumpstart server, make a nfs share of the install directory for your new release, in this case
\nsolaris10. We have the solaris10 sparc jumpstart directory in a linux machine, so we edited the \/etc\/exports to
\ninclude:
\n\/200gb\/jumpstart (ro)
\nWhere \/200gb\/jumpstart\/sol10 contains:
\nbash-3.00# uname -a
\nLinux linuxy 2.4.31 #6 Sun Jun 5 19:04:47 PDT 2005 i686 unknown unknown GNU\/Linux
\nbash-3.00# ls -la \/200gb\/jumpstart\/sol10
\ntotal 491
\ndrwxr-xr-x 4 root root 432 2006-03-11 12:12 .
\ndrwxr-xr-x 4 root root 136 2006-08-23 09:14 ..
\n-r–r–r– 1 root root 93 2005-11-15 12:36 .cdtoc
\ndrwxr-xr-x 5 root root 184 2005-12-07 10:32 .install
\nlrwxrwxrwx 1 root root 33 2006-08-23 09:10 .install_config -> .\/Solaris_10\/Misc\/.install_config
\n-r–r–r– 1 root root 472 2006-03-11 12:12 .slicemapfile
\n-r–r–r– 1 root root 21 2005-11-15 12:36 .volume.inf
\n-r–r–r– 1 root root 23 2005-12-07 09:53 .volume.inf.2
\n-r–r–r– 1 root root 23 2005-12-07 09:53 .volume.inf.3
\n-r–r–r– 1 root root 23 2005-12-07 09:54 .volume.inf.4
\n-r–r–r– 1 root root 6604 2005-11-16 13:14 Copyright
\n-r–r–r– 1 root root 459760 2005-11-15 12:36 JDS-THIRDPARTYLICENSEREADME
\ndrwxr-xr-x 9 root root 232 2005-12-07 10:32 Solaris_10
\n-rwxr-xr-x 1 root root 257 2005-12-07 09:54 installer
\nBack at the Netra machine (the one to upgrade), verify what disks do we have
\nbash-2.05# uname -a
\nSunOS netra 5.9 Generic_118558-28 sun4u sparc SUNW,UltraSPARC-IIi-cEngine
\nbash-2.05# format <\/dev\/null
\nSearching for disks…done
\nAVAILABLE DISK SELECTIONS:
\n0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
\n\/pci@1f,0\/pci@1,1\/scsi@2\/sd@0,0
\n1. c0t1d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
\n\/pci@1f,0\/pci@1,1\/scsi@2\/sd@1,0
\nPartition the second disk identically as the first one.
\n231\/433
\nbash-2.05# \/usr\/sbin\/prtvtoc \/dev\/rdsk\/c0t0d0s2 | \/usr\/sbin\/fmthard -s – \/dev\/rdsk\/c0t1d0s2
\nIt is a requirement that if you upgrade a system from solaris 9 to solaris 10, you MUST install the live upgrade
\npakages for the target version in the old version. So, we install SUNWluu and SUNWlur getting it from the
\nsolaris10 install nfs export
\nbash-2.05# uname -a
\nSunOS netra 5.9 Generic_118558-28 sun4u sparc SUNW,UltraSPARC-IIi-cEngine
\nbash-2.0.5# mkdir \/jstart
\nbash-2.0.5# mount 172.16.1.50:\/200gb\/jumpstart \/jstart
\nbash-2.0.5# cd \/jstart\/sol10\/Solaris_10\/Product
\nbash-2.0.5# pkgadd -d . SUNWluu
\nbash-2.0.5# pkgadd -d . SUNWlur
\nWe now create the live upgrade environment for solaris10, along with the current solaris9 environment, in this
\ncase we only have \/, no \/opt,\/var,\/export\/home, so we only define that we have to copy \/.
\nbash-2.05# lucreate -c “sol9” -m \/:\/dev\/dsk\/c0t1d0s0:ufs -n “sol10”
\nDiscovering physical storage devices
\nDiscovering logical storage devices
\nCross referencing storage devices with boot environment configurations
\nDetermining types of file systems supported
\nValidating file system requests
\nPreparing logical storage devices
\nPreparing physical storage devices
\nConfiguring physical storage devices
\nConfiguring logical storage devices
\nAnalyzing system configuration.
\nNo name for current boot environment.
\nCurrent boot environment is named <sol9>.
\nCreating initial configuration for primary boot environment <sol9>.
\nThe device <\/dev\/dsk\/c0t0d0s0> is not a root device for any boot environment.
\nPBE configuration successful: PBE name <sol9> PBE Boot Device <\/dev\/dsk\/c0t0d0s0>.
\nComparing source boot environment <sol9> file systems with the file
\nsystem(s) you specified for the new boot environment. Determining which
\nfile systems should be in the new boot environment.
\nUpdating boot environment description database on all BEs.
\nSearching \/dev for possible boot environment filesystem devices
\nUpdating system configuration files.
\nThe device <\/dev\/dsk\/c0t1d0s0> is not a root device for any boot environment.
\nCreating configuration for boot environment <sol10>.
\nSource boot environment is <sol9>.
\nCreating boot environment <sol10>.
\nCreating file systems on boot environment <sol10>.
\nCreating <ufs> file system for <\/> on <\/dev\/dsk\/c0t1d0s0>.
\nMounting file systems for boot environment <sol10>.
\nCalculating required sizes of file systems for boot environment <sol10>.
\nPopulating file systems on boot environment <sol10>.
\nChecking selection integrity.
\nIntegrity check OK.
\nPopulating contents of mount point <\/>.
\n232\/433
\nCopying.
\nCreating shared file system mount points.
\nCreating compare databases for boot environment <sol10>.
\nCreating compare database for file system <\/>.
\nUpdating compare databases on boot environment <sol10>.
\nMaking boot environment <sol10> bootable.
\nPopulation of boot environment <sol10> successful.
\nCreation of boot environment <sol10> successful.
\nGo on and upgrade the sol10 boot environmet from the jumpstart image, nfs mounted, this step will install the
\nsolaris 10 packages needed over the solaris 9 image copied to c0t1d0
\nbash-2.05# luupgrade -u -n sol10 -s \/jstart\/sol10
\nValidating the contents of the media <\/jstart\/sol10>.
\nThe media is a standard Solaris media.
\nThe media contains an operating system upgrade image.
\nThe media contains <Solaris> version <10>.
\nConstructing upgrade profile to use.
\nLocating the operating system upgrade program.
\nChecking for existence of previously scheduled Live Upgrade requests.
\nCreating upgrade profile for BE <sol10>.
\nDetermining packages to install or upgrade for BE <sol10>.
\nPerforming the operating system upgrade of the BE <sol10>.
\nCAUTION: Interrupting this process may leave the boot environment unstable
\nor unbootable.
\nUpgrading Solaris: 100% completed
\nInstallation of the packages from this media is complete.
\nUpdating package information on boot environment <sol10>.
\nPackage information successfully updated on boot environment <sol10>.
\nAdding operating system patches to the BE <sol10>.
\nThe operating system patch installation is complete.
\nINFORMATION: The file <\/var\/sadm\/system\/logs\/upgrade_log> on boot
\nenvironment <sol10> contains a log of the upgrade operation.
\nINFORMATION: The file <\/var\/sadm\/system\/data\/upgrade_cleanup> on boot
\nenvironment <sol10> contains a log of cleanup operations required.
\nINFORMATION: Review the files listed above. Remember that all of the files
\nare located on boot environment <sol10>. Before you activate boot
\nenvironment <sol10>, determine if any additional system maintenance is
\nrequired or if additional media of the software distribution must be
\ninstalled.
\nThe Solaris upgrade of the boot environment <sol10> is complete.
\nNow we activate the solaris 10 boot environment:
\nbash-2.05# luactivate sol10
\nkraftek.html POSTS rescue rescued.html rescued.txt x y z
\nThe target boot environment has been activated. It will be used when you
\nreboot. NOTE: You MUST NOT USE the reboot, halt, or uadmin commands. You
\nMUST USE either the init or the shutdown command when you reboot. If you
\ndo not use either init or shutdown, the system will not boot using the
\ntarget BE.
\nkraftek.html POSTS rescue rescued.html rescued.txt x y z
\n233\/433
\nIn case of a failure while booting to the target BE, the following process
\nneeds to be followed to fallback to the currently working boot environment:
\n1. Enter the PROM monitor (ok prompt).
\n2. Change the boot device back to the original boot environment by typing:
\nsetenv boot-device disk:a
\n3. Boot to the original boot environment by typing:
\nboot
\nkraftek.html POSTS rescue rescued.html rescued.txt x y z
\nActivation of boot environment <sol10> successful.
\nBounce the system…
\nbash-2.05# init 6
\nINIT: New run level: 6
\nThe system is coming down. Please wait.
\nSystem services are now being stopped.
\nLive Upgrade: Deactivating current boot environment <sol9>.
\nLive Upgrade: Executing Stop procedures for boot environment <sol9>.
\nLive Upgrade: Current boot environment is <sol9>.
\nLive Upgrade: New boot environment will be <sol10>.
\nLive Upgrade: Activating boot environment <sol10>.
\nLive Upgrade: The boot device for boot environment <sol10> is
\n<\/dev\/dsk\/c0t1d0 s0>.
\nLive Upgrade: Activation of boot environment <sol10> completed.
\nThe system is down.
\nsyncing file systems… done
\nrebooting…
\nResetting …
\nNetra t1 (UltraSPARC-IIi 440MHz), No Keyboard
\nOpenBoot 3.10.27 ME, 256 MB memory installed, Serial #14270360.
\nEthernet address 8:0:20:d9:bf:98, Host ID: 80d9bf98.
\nExecuting last command: boot
\nBoot device: disk1:a File and args:
\nSunOS Release 5.10 Version Generic_118822-25 64-bit
\nCopyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
\nUse is subject to license terms.
\nWARNING: No major number for driver mpt in class scsi
\nHostname: netra
\nConfiguring devices.
\nLoading smf(5) service descriptions: 121\/121
\nAug 25 14:38:13 svc.startd[7]: svc:\/system\/mdmonitor:default: Method “\/lib\/svc\/method\/svc.
\nAug 25 14:38:14 svc.startd[7]: svc:\/system\/mdmonitor:default: Method “\/lib\/svc\/method\/svc.
\nAug 25 14:38:14 svc.startd[7]: svc:\/system\/mdmonitor:default: Method “\/lib\/svc\/method\/svc.
\n[ system\/mdmonitor:default failed (see ‘svcs -x’ for details) ]
\nThis system is configured with NFS version 4, which uses a domain
\nname that is automatically derived from the system’s name services.
\nThe derived domain name is sufficient for most configurations. In a
\nfew cases, mounts that cross different domains might cause files to
\nbe owned by “nobody” due to the lack of a common domain name.
\nDo you need to override the system’s default NFS version 4 domain
\nname (yes\/no) x y z [no] : no
\nFor more information about how the NFS version 4 default domain
\n234\/433
\nname is derived and its impact, refer to the man pages for nfs(4)
\nand nfsmapid(1m), and the System Administration Guide: Network
\nServices.
\nnetra console login: root
\nbash-3.00# uname -a
\nSunOS netra 5.10 Generic_118822-25 sun4u sparc SUNW,UltraSPARC-IIi-cEngine
\nSolaris 10 is now installed on the second disk.
\nTo bounce it back to our first disk on solaris 9, you can activate the boot environment and reboot.
\nbash-3.00# uname -a
\nSunOS netra 5.10 Generic_118822-25 sun4u sparc SUNW,UltraSPARC-IIi-cEngine
\nbash-3.00# luactivate sol9
\nbash-3.00# init 6
\nsolaris patchadd return codes
\n0. No error
\n1. Usage error
\n2. Attempt to apply a patch that’s already been applied
\n3. Effective UID is not root
\n4. Attempt to save original files failed
\n5. pkgadd failed
\n6. Patch is obsoleted
\n7. Invalid package directory
\n8. Attempting to patch a package that is not installed
\n9. Cannot access \/usr\/sbin\/pkgadd (client problem)
\n10. Package validation errors
\n11. Error adding patch to root template
\n12. Patch script terminated due to signal
\n13. Symbolic link included in patch
\n14. NOT USED
\n15. The prepatch script had a return code other than 0.
\n16. The postpatch script had a return code other than 0.
\n17. Mismatch of the -d option between a previous patch install and the current one.
\n18. Not enough space in the file systems that are targets of the patch.
\n19. $SOFTINFO\/INST_RELEASE file not found
\n20. A direct instance patch was required but not found
\n21. The required patches have not been installed on the manager
\n22. A progressive instance patch was required but not found
\n23. A restricted patch is already applied to the package
\n24. An incompatible patch is applied
\n25. A required patch is not applied
\n26. The user specified backout data can’t be found
\n27. The relative directory supplied can’t be found
\n28. A pkginfo file is corrupt or missing
\n235\/433
\n29. Bad patch ID format
\n30. Dryrun failure(s)
\n31. Path given for -C option is invalid
\n32. Must be running Solaris 2.6 or greater
\n33. Bad formatted patch file or patch file not found
\n34. Incorrect patch spool directory
\n35. Later revision already installed
\n236\/433<\/p>\n","protected":false},"excerpt":{"rendered":"
These are the steps to upgrade a Netra t1 with two identical disks from solaris 9 to solaris 10, using liveupgrade with a Solaris 10 image from a standard jumpstart directory. This procedure is good because it needs no downtime, and the configurarion you have in your original system is preserved (\/etc,\/export\/home). If you have […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-496","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"\/blog\/index.php\/wp-json\/wp\/v2\/posts\/496","targetHints":{"allow":["GET"]}}],"collection":[{"href":"\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=496"}],"version-history":[{"count":0,"href":"\/blog\/index.php\/wp-json\/wp\/v2\/posts\/496\/revisions"}],"wp:attachment":[{"href":"\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=496"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=496"},{"taxonomy":"post_tag","embeddable":true,"href":"\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=496"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}