10/22/09 SUN Alert Patch Cluster

I just applied the 10/22/09 SUN Alert Patch Cluster, and only 16 of the 176 patches were applied. Is this reasonable? I've been applying the most recent Alert patch cluster every three months for about 1-1/2 years.

continued.
I removed patch 138217-01 (svccfg & svcprop patch) and re-applied it.
Then, after booting into S-mode, I tried to continue with the broken patch 139555-08 (kernel).
It ends with
! root@jumpstart:/var/spool/patch # patchadd 139555-08
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Preparing checklist for non-global zone check...
Checking non-global zones...
This patch passes the non-global zone check.
139555-08
Summary for zones:
Zone oem
Rejected patches:
None.
Patches that passed the dependency check:
139555-08
Patching global zone
Adding patches...
Checking installed patches...
Executing prepatch script...
Installing patch packages...
Pkgadd failed. See /var/tmp/139555-08.log.21103 for details
Patchadd is terminating.
! root@jumpstart:/var/spool/patch #the logfile shows
! root@jumpstart:/var/spool/patch # vi /var/tmp/139555-08.log.21103
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
pkgadd: ERROR: couldn't lock in /var/run/.patchSafeMode/root/var/sadm/install (s
erver running?): Resource temporarily unavailable
Installation of <SUNWarc> failed (internal error).
No changes were made to the system.Help!
-- Nick

Similar Messages

Obtaining obsoleted Sun Alert patch Cluster

I need to build a Solaris 10 Sparc update 3 with Sun Alert Patch Cluster July 16 2007.
I cannot use a more recent Solaris instal version, nor can I use a more recent Sun Alert Patch Cluster version.
I cannot locate this specific Sun Alert Patch Cluster version for download from Sunsolve.
Can anyone advise if it is possible to obtain this Sun Alert Patch Cluster?

continued.
I removed patch 138217-01 (svccfg & svcprop patch) and re-applied it.
Then, after booting into S-mode, I tried to continue with the broken patch 139555-08 (kernel).
It ends with
! root@jumpstart:/var/spool/patch # patchadd 139555-08
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Preparing checklist for non-global zone check...
Checking non-global zones...
This patch passes the non-global zone check.
139555-08
Summary for zones:
Zone oem
Rejected patches:
None.
Patches that passed the dependency check:
139555-08
Patching global zone
Adding patches...
Checking installed patches...
Executing prepatch script...
Installing patch packages...
Pkgadd failed. See /var/tmp/139555-08.log.21103 for details
Patchadd is terminating.
! root@jumpstart:/var/spool/patch #the logfile shows
! root@jumpstart:/var/spool/patch # vi /var/tmp/139555-08.log.21103
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
pkgadd: ERROR: couldn't lock in /var/run/.patchSafeMode/root/var/sadm/install (s
erver running?): Resource temporarily unavailable
Installation of <SUNWarc> failed (internal error).
No changes were made to the system.Help!
-- Nick

How can install the latest SUN patch cluster on individual zones?

I have a global zone running Solaris 10 (11/06). I have a number of whole root zones running. I only want to apply the latest Sun Recommended patch cluster to a few of the individual local zones. Can this be done? How do I run install_cluster at the global and have it apply to only some of the local zones?
thanks in advance,
Brock

bgammel wrote:
I have a global zone running Solaris 10 (11/06). I have a number of whole root zones running. I only want to apply the latest Sun Recommended patch cluster to a few of the individual local zones. Can this be done? How do I run install_cluster at the global and have it apply to only some of the local zones?It really makes no sense to talk about a patch cluster this way. For some individual patches in the cluster, it may be possible for others not.
If a patch applies to the kernel, it makes no sense to apply to some zones and not others (or not the global zone). Otherwise you'd have files out of sync with the running kernel.
For other patches that are purely application-specific, it could be just fine. Something that patches 'sed' for instance should apply cleanly to a whole-root zone.
You'll need to read the notes for the individual patches.
Darren

How do I find the latest Critical Sun Solaris Patches on Oracle site

Hello
How do I find the latest critical Solaris Patches available to the users. I was searching the list on Oracle's site it's hard to determine which patch is critcal or not. When I type uname -a this is what returns Generic_142909-17.
Any help you could provide would be appreciated.

Sorry, I wrote "Monthly" when I meant to write "Quarterly". Apologies for the confusion. My bad.
From - http://www.oracle.com/technetwork/topics/security/alerts-086861.html
They are released on the Tuesday closest to the 15th day of January, April, July and October. Starting 2011, the scheduled dates for the release of Critical Patch Updates will be on the Tuesday closest to the 17th day of January, April, July and October. The next four dates are:
* 19 April 2011
* 19 July 2011
* 18 October 2011
* 17 January 2012
The CPU for the Solaris Operating System is a rebranded snapshot of the Recommended OS Cluster. The rebranding involves only superficial changes to the patch cluster, with the actual patch content remaining unchanged. The patches contained in this patch cluster are considered the most important and highly recommended patches for Solaris 10. They provide the least amount of change required to address known security, data corruption and availability issues.
If there's a particular CVE Alert which you're vulnerable to or interested in, then the fix will be released within the patch that corresponds to the area of code the vulnerability affects. You can then apply that patch and it's requirements separate to the clusters. Next time you apply the cluster it will either install the latest rev of the patch or skip it if you have the latest installed already.
The Recommended Patch Cluster bundle is a much larger collection of patches and contains all the latest patches (at the time of release) which include Solaris updates, Security, and Sun Alert fixes. Note that we merged "Recommended Patch Cluster/Kernel Jumbo Patchset" and the "Sun Alert Patch Clusters" back in June 2010. See http://blogs.sun.com/patch/entry/merging_the_solaris_recommended_and for more information regarding what happened and why.
Of course there will be a large overlap between the "Recommended OS Cluster" and the "Critical Patch Updates" patchsets will be rolled in to the "Recommended OS Cluster" whenever it's cut and released.
There's a lot of information in the README files for each cluster so you may want to read those to understand the subtle differences.
Regards,
Steve

Patch cluster pass code - NEW from Sun just to inconvenience you

Wow. A few of the admins here, myself included, had to throw the latest patch cluster onto a few of our servers. Sun is now requiring a pass code as an argument! And they've hidden the pass code in the README with the excuse that it's to get you to read it.
Anyway, this "pass code" is "s10cluster". So, you have to run "./installcluster --s10cluster" to get the thing to install. {grumble} A pass code to install a cluster. Ridiculous.{grumble}
That said, some of the other changes they've made to the install script are very welcome.

Sorry for spamming i just realized what do i make wrong after
3 hours of programig.
..({id'} has a missing @ mark :)

Management console problem after installing recommended patch cluster

Hello everyone.
I just got a new SUN 440 server, it didn't come with the solaris os installed and so I installed solaris 9 12/03 to it. The installation went fine and I could start the management console with no problems at all. Then I went to sunsolve.sun.com to download the latest recommended patch clusters for solaris 9 (this was yesterday Sept.-06-2006), I downloaded the file, checked it with md5sum, unzipped it, went to single user mode and ran the install_patch script. After the patch cluster finished installing I rebooted the server for the patches to take effect, I logged in, tried to run console management 2.1 and it starts OK but I cannot use any services it offers because it says (in the console events):
"Server Not Running: no solaris management console server was available on the specified server. Please ensure there is a Solaris Management Console server available on the specified host and that it is running"
When I click on "See Exception" I get (for a particular service that is... in this case com.sun.admin.fsmgr.client.VFsMgr - for managing file systems):
java.rmi.RemoteException: Server RMI is null:
at sun.com.management.viperimpl.client.ViperClient.lookupServer(ViperClient.java:376)and so on...
I already checked that the service is running on port 898 and it seems that there is no other app. using that same port. I also restarted the service using /etc/init.d.init stop/status/start but I get the same results.
I don't know solaris very much and don't know what else to do, please help.
Thanks in advance.

Well, I guess what you see isn't what you get.
Guess I'm used to the fact USENET just left things formatted the way they were :-O

How to backout a Recommended Patch cluster deployment in Solstice disksuite

Hello Admin's,
I am planning to use the following Plan of action for deploying the latest Solaris 8 Recommended Patch cluster on the production server's i support.My
concern is if the patching activity fails or the application and Oracle databases dont come up after deploying the patch cluster.How do i revert back to system to its original state using the submirror's which i have detached prior to patching the system :
1) Will shutdown the applications and the databases on the server:
2) Will capture the output of the following commands :
df -k
ifconfig -a
contents of the files /etc/passwd /etc/shadow /etc/vfstab /etc/system
metastat -p
netstat -rn
prtvtoc /dev/rdsk/c1t0d0s0
prtvtoc /dev/rdsk/c1t1d0s0
3) We bring the system to the ok prompt
4) We will try to boot the system from both the disk's which are part of the d10 metadevice for root filesystem
=======================================================================================
user1@myserver>pwd ; df -k / ; ls -lt | egrep '(c1t0d0s0|c1t1d0s0)' ; prtconf -vp | grep bootpath ; metastat d10
/dev/dsk
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 8258597 3435895 4740117 43% /
lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t0d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@0,0:a
lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t1d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@1,0:a
bootpath: '/pci@1c,600000/scsi@2/disk@0,0:a'
d10: Mirror
Submirror 0: d11
State: Okay
Submirror 1: d12
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 16779312 blocks
d11: Submirror of d10
State: Okay
Size: 16779312 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Okay
d12: Submirror of d10
State: Okay
Size: 16779312 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s0 0 No Okay
user1@myserver>
===================================================================================
ok nvalias backup_root <disk path>
Redefine the boot-device variable to reference both the primary and secondary submirrors, in the order in which you want to access them. For example:
ok printenv boot-device
boot-device= disk net
ok setenv boot-device disk backup_root net
boot-device= disk backup_root net
In the event of primary root disk failure, the system automatically boots from the secondary submirror. To test the secondary submirror, boot the system manually, as follows:
ok boot backup_root
user1@myserver>metadb -i
flags first blk block count
a m p luo 16 1034 /dev/dsk/c1t0d0s7
a p luo 1050 1034 /dev/dsk/c1t0d0s7
a p luo 2084 1034 /dev/dsk/c1t0d0s7
a p luo 16 1034 /dev/dsk/c1t1d0s7
a p luo 1050 1034 /dev/dsk/c1t1d0s7
a p luo 2084 1034 /dev/dsk/c1t1d0s7
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
user1@myserver>df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 8258597 3435896 4740116 43% /
/dev/md/dsk/d40 2053605 929873 1062124 47% /usr
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
/dev/md/dsk/d30 2053605 937231 1054766 48% /var
swap 2606008 24 2605984 1% /var/run
swap 6102504 3496520 2605984 58% /tmp
/dev/md/dsk/d60 13318206 8936244 4248780 68% /u01
/dev/md/dsk/d50 5161437 2916925 2192898 58% /opt
user1@myserver>metastat d40
d40: Mirror
Submirror 0: d41
State: Okay
Submirror 1: d42
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4194828 blocks
d41: Submirror of d40
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s4 0 No Okay
d42: Submirror of d40
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s4 0 No Okay
user1@myserver>metastat d30
d30: Mirror
Submirror 0: d31
State: Okay
Submirror 1: d32
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4194828 blocks
d31: Submirror of d30
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s3 0 No Okay
d32: Submirror of d30
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s3 0 No Okay
user1@myserver>metastat d50
d50: Mirror
Submirror 0: d51
State: Okay
Submirror 1: d52
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 10487070 blocks
d51: Submirror of d50
State: Okay
Size: 10487070 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s5 0 No Okay
d52: Submirror of d50
State: Okay
Size: 10487070 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s5 0 No Okay
user1@myserver>metastat -p
d10 -m d11 d12 1
d11 1 1 c1t0d0s0
d12 1 1 c1t1d0s0
d20 -m d21 d22 1
d21 1 1 c1t0d0s1
d22 1 1 c1t1d0s1
d30 -m d31 d32 1
d31 1 1 c1t0d0s3
d32 1 1 c1t1d0s3
d40 -m d41 d42 1
d41 1 1 c1t0d0s4
d42 1 1 c1t1d0s4
d50 -m d51 d52 1
d51 1 1 c1t0d0s5
d52 1 1 c1t1d0s5
d60 -m d61 d62 1
d61 1 1 c1t0d0s6
d62 1 1 c1t1d0s6
user1@myserver>pkginfo -l SUNWmdg
PKGINST: SUNWmdg
NAME: Solstice DiskSuite Tool
CATEGORY: system
ARCH: sparc
VERSION: 4.2.1,REV=1999.11.04.18.29
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: Solstice DiskSuite Tool
PSTAMP: 11/04/99-18:32:06
INSTDATE: Apr 16 2004 11:10
VSTOCK: 258-6252-11
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 150 installed pathnames
6 shared pathnames
19 directories
1 executables
7327 blocks used (approx)
user1@myserver>
=======================================================================================
5) After successfully testing the above we will bring the system to the single user mode
# reboot -- -s
6) Detach the following sub-mirrors :
# metadetach -f d10 d12
#metadetach -f d30 d32
#metadetach -f d40 d42
#metadetach -f d50 d52
# metastat =====> (to check if the submirror�s are successfully detached)
7) Applying patch on the server
After patch installation is complete will be rebooting the server to single user mode
# reboot -- -s
confirming if patch installation was successful (uname �a) .
8) Will be booting the server to the multiuser mode (init 3) and confirming with the database and the application teams if the
Applications/databases are working fine .Once confirmed successful will be reattaching the d12 submirror.
# metattach d12 d10
# metattach d30 d32
#metattach d40 d42
# metattach d50 d52
# metastat d10 =====> (to check the submirror is successfully reattached)
user1@myserver>uname -a ; cat /etc/release ; date
SunOS myserver 5.8 Generic_117350-04 sun4u sparc SUNW,Sun-Fire-V210
Solaris 8 HW 12/02 s28s_hw1wos_06a SPARC
Copyright 2002 Sun Microsystems, Inc. All Rights Reserved.
Assembled 12 December 2002
Mon Apr 14 17:10:09 BST 2008
-----------------------------------------------------------------------------------------------------------------------------

Recommended patch sets are and to the best of my knowledge have always been regenerated twice a month.
I think your thinking of maintenance releases. When they generate a new CD image which can be used to do an upgrade install.
They try to generate those every 6 months, but the schedule often slips.
The two most recent were sol10 11/06 and sol10 8/07.

Non priviledged commands fail after patch cluster install

For several years, to allow users to access system functions for higher clock resolutions in their
applications, we have made the following mods to two files (per Sun recommendations):
In the /etc/system file, add lines:
* 10 ms clock resolution*
set higher_tick = 1*
In /etc/user_attr, add:
dssuser::::type=normal;defaultpriv=proc_clock_highres,file_link_any,proc_info,proc_session,proc_fork,proc_exec
Everything was fine until I installed the latest patch cluster (from 2-14-2011) on our Netra 210. No issues installing the cluster. Upon reboot, the dssuser cannot do some simple things, like use ftp or ping. Messages like this:
ping: unknown host
ftp: socket: Permission denied.
The root user has no problems using any of these commands. As soon as I comment out the dssuser line from the /etc/user_attr file, everything works as expected. But we need the highres clock settings for our applications. I am unfamiliar with the workings and intent of the entries in user_attr so any help would be most appreciated.
Mark

The problem is that after patch implementation, the special privileges for any user defined in the /etc/user_attr file were modified to append the string "!net_privaddr" specifically denying use of common commands ping and ftp for example. The output of ppriv:
$ ppriv $$
14870: -sh
flags = <none>
E: basic,proc_clock_highres,!net_privaddr
I: basic,proc_clock_highres,!net_privaddr
P: basic,proc_clock_highres,!net_privaddr
L: all
I had to add the keyword net_privaddr in the user_attr file like:
dssuser::::type=normal;defaultpriv=proc_clock_highres,file_link_any,proc_info,proc_session,proc_fork,proc_exec,net_privaddr
to get past this problem. A bug or what?

Latest patch cluster idated march 14 nstalled on solaris10

I installed the latest patch cluster on my solaris10 system and afterwards the Solaris Management console would not work. I kept getting the error that the server was not running. I followed the limited trouble-shooting guidelines for stopping and starting the service but still did not work. After reviwing the patch cluster I discoved there was a patch that updated smc. There was no special instructions for this patch. I removed the patch and the smc worked find. Has anyone had any problems with patch 121308-12.

Patch 119313-19(SPARC), 119314-20(x86) will resolve your problem.
But these patch are NOT included in the recommanded pathces.
You need to join Sun's SunSolve or Sun's standard support.

Patch cluster 3/26/10 will hose X4500 disk management task in multiuser

I just want to warn user about the potential problem that you will encounter if you have a SUN X4500 system.
After applying patch cluster 3/26/10 on a SUN X4500 (thumper), now I can not do many disk management tasks in multiuser mode, such as
format
zpool create
and possibly many more commands (involving disk devices) would just hang.
Drop it to single user mode, however, you CAN still do these management task. I had to create zpool in single user mode
zfs create pool/zfsset still works in multiuser mode.
Thank you for your attention.

I'm having exactly the same problem on an x4500 server running OpenSolaris snv_127. We suffered a disk failure (c7t0d0), so I resilvered one of the pools onto a spare drive, which succeeded:
# zpool history data
<snip>
2010-04-20.14:45:08 zpool offline data c7t0d0
2010-04-20.14:58:19 zpool replace -f data c7t0d0 c7t1d0
# zpool status data
pool: data
state: ONLINE
scrub: resilver completed after 43h58m with 0 errors on Thu Apr 22 10:56:50 2010
config:
NAME STATE READ WRITE CKSUM
data ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
c11t1d0 ONLINE 0 0 0
c10t1d0 ONLINE 0 0 0
c13t1d0 ONLINE 0 0 0
c12t0d0 ONLINE 0 0 0
c8t1d0 ONLINE 0 0 0
c12t1d0 ONLINE 0 0 0
c10t0d0 ONLINE 0 0 0
c10t7d0 ONLINE 0 0 0
c12t2d0 ONLINE 0 0 0
c8t0d0 ONLINE 0 0 0
c7t1d0 ONLINE 0 0 0 381G resilvered
As you can see, the drive c7t0d0 has been successfully replaced and no longer appears in any zpool:
# zpool status | grep c7t0d0
# iostat -En | grep c7t0d0
c7t0d0 Soft Errors: 2 Hard Errors: 4 Transport Errors: 0
# cfgadm -l | grep c7t0d0
sata1/0::dsk/c7t0d0 disk connected configured ok
However when I attempt to unconfigure the sata port in preperation for replacing the drive, it doesn't work:
# cfgadm -c unconfigure sata1/0
Unconfigure the device at: /devices/pci@0,0/pci1022,7458@1/pci11ab,11ab@1:0
This operation will suspend activity on the SATA device
Continue (yes/no)? yes
cfgadm: Hardware specific failure: Failed to unconfig device at ap_id: /devices/pci@0,0/pci1022,7458@1/pci11ab,11ab@1:0
Also just pulling out the drive doesn't work, you end up with an unusable unconfigured port:
# cfgadm -l | grep unusable
sata6/0 disk connected unconfigured unusable
It's highly frustrating, because it means to replace disks we'll have to shut this server down. Not ideal!
I'm fairly certain this used to work fine.
If anyone has a solution, I'm all ears. I'm going to update this box to snv_130 soon (mainly to get the new zfs resilvering code) but I'm not hopeful about this bug/issue.
Regards,
Alasdair

GLOBAL ZONE stuck in shutting_down after applying latest patch cluster

Hi,
after installing the latest patch cluster, my zones on the system are not accessable
root@typhoon # zoneadm list -civ
ID NAME STATUS PATH BRAND IP
0 global shutting_down / native shared
- typhoon-log installed /local/zone/typhoon-log native shared
- typhoon-ftp installed /local/zone/typhoon-ftp native shared
- typhoon-rndrepos installed /local/zone/typhoon-rndrepos native shared
- typhoon-drpreview installed /local/zone/typhoon-test native shared
- typhoon-ossec installed /local/zone/typhoon-ossec native shared
- typhoon-drjboss installed /local/zone/typhoon-drjboss native shared
- typhoon-webdata installed /datapool/web/zones/webdata native shared
- typhoon-webzone installed /datapool/web/zones/typhoon-webzone native shared
# uname -a
SunOS typhoon 5.10 Generic_139556-08 i86pc i386 i86pc
there is one service reporting in maintenane
# svcs -xv
svc:/system/filesystem/volfs:default (Volume Management filesystem)
State: maintenance since Wed Jul 15 20:04:07 2009
Reason: Restarting too quickly.
See: http://sun.com/msg/SMF-8000-L5
See: man -M /usr/man -s 7FS volfs
See: /var/svc/log/system-filesystem-volfs:default.log
Impact: This service is not running.
I tried stopping and starting the vold, but without any effect
the / is on a zfs pool
# zpool list
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
datapool 576G 105G 471G 18% ONLINE -
datapool2 148G 111G 37.0G 74% ONLINE -
rpool 120G 37.1G 82.9G 30% ONLINE -
root@typhoon # zpool status
pool: datapool
state: ONLINE
scrub: scrub completed after 0h31m with 0 errors on Thu Jul 16 02:31:53 2009
config:
NAME STATE READ WRITE CKSUM
datapool ONLINE 0 0 0
mirror ONLINE 0 0 0
c2d1s3 ONLINE 0 0 0
c1d1s3 ONLINE 0 0 0
errors: No known data errors
pool: datapool2
state: ONLINE
scrub: scrub completed after 1h53m with 0 errors on Wed Jul 15 23:53:06 2009
config:
NAME STATE READ WRITE CKSUM
datapool2 ONLINE 0 0 0
mirror ONLINE 0 0 0
c2d0s0 ONLINE 0 0 0
c1d0s3 ONLINE 0 0 0
errors: No known data errors
pool: rpool
state: ONLINE
scrub: scrub completed after 0h26m with 0 errors on Thu Jul 16 06:20:39 2009
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror ONLINE 0 0 0
c1d1s0 ONLINE 0 0 0
c2d1s0 ONLINE 0 0 0
errors: No known data errors
root@typhoon #
# tail /var/svc/log/system-filesystem-volfs:default.log
[ Jul 16 08:03:11 Method "start" exited with status 0 ]
Thu Jul 16 08:03:11 2009 fatal: mounting of "/vol" failed
[ Jul 16 08:03:11 Stopping because all processes in service exited. ]
[ Jul 16 08:03:11 Executing stop method (:kill) ]
[ Jul 16 08:03:11 Executing start method ("/lib/svc/method/svc-volfs start") ]
[ Jul 16 08:03:11 Method "start" exited with status 0 ]
Thu Jul 16 08:03:11 2009 fatal: mounting of "/vol" failed
[ Jul 16 08:03:11 Stopping because all processes in service exited. ]
[ Jul 16 08:03:11 Executing stop method (:kill) ]
[ Jul 16 08:03:11 Restarting too quickly, changing state to maintenance ]
please advise, (this was on test run before implemention this patch cluster on the production server).
And I need to get a solution, to get my zone back running and then decide what to do with this patch cluster
thx
Edited by: Denis@SDN on Jul 16, 2009 1:06 AM

Sound familiar?
[http://opensolaris.org/jive/thread.jspa?threadID=105001&tstart=0]
This guy killed a process as workaround
[http://alittlestupid.com/2009/07/04/solaris-zone-stuck-in-shutting_down-state/]
We patched some SPARC systems recently and no issues though that's little consolation to you x86 admins.

SPARC10 not booting after 2.5.1 Recommended Patch Cluster Install

Hi everyone,
Just finished installing the "latest" patch cluster on my ancient SPARC10, and now it doesn't boot. Here's what I see:
ok boot /iommu/sbus/espdma@f,400000/esp@f,800000/sd@0,0
screen not found.
Can't open input device.
Keyboard not present. Using tty for input and output.
SPARCstation 10 (1 X 390Z55), No Keyboard
ROM Rev. 2.25, 112 MB memory installed, Serial #6332710.
Ethernet address 8:0:20:12:7f:99, Host ID: 7260a126.
Rebooting with command: /iommu/sbus/espdma@f,400000/esp@f,800000/sd@0,0
Boot device: /iommu/sbus/espdma@f,400000/esp@f,800000/sd@0,0 File and args:
not found: abort_enable
not found: abort_enable
not found: tod_validate
not found: tod_fault_reset
krtld: error during initial load/link phase
Memory Address not Aligned
Type help for more information
ok
At first I thought I had a RAM problem. I've swapped RAM, but that didn't make it boot. I then thought I had a system board problem. I've swapped that as well, and still no dice. I wish I'd have kept the list of patches that successfully installed like my gut told me to, but I didn't. Searching Google and the Sun websites didn't turn up any fixes to the problem, so I'm hoping I can find help here.
Did the patches clobber something the machine needs to boot? I believe the OS disks are mirrored, and I've tried booting off each submirror, but the result is the same.
If I can avoid booting off of CD-ROM, that would be ideal since I don't have an external CD-ROM available to boot from.
Thanks for any help!

Ouch !
Haven't seen that one in years !
It's your choice of that ancient Operating Environment, combined with a cpu faster than 419MHz.
I hope you still have the extra OECD disk that was packed with that system when it was first shipped from Sun.
Otherwise you may just be out of luck with using Solaris 2.5.1
Here's a link at a non-Sun 3rd party web site to SRDB document *20576*
http://www.sunshack.org/data/sh/2.1/infoserver.central/data/syshbk/collections/intsrdb/20576.html
Perhaps MAAL and haroldb can contribute their thoughts on this.

Solaris reboot loop after recommended patch cluster

Hi,
I have a problem with my solaris 10 x86 install on my intel notebook. after installing the latest recommended patch cluster and the necessary reboot my latop stays in a loop.
one of the last lines I was able to see:
panic[cpu0]/thread=fec1d660: boot_mapin():No pp for pfnum=20fff
fec33b4c genunix:main+1b ()
skipping system dump - ....
rebooting...
any ideas ?
cu+thx

This horrible patch caught me out too. I found this and it fixed my problem.
http://weblog.erenkrantz.com/weblog/software/solaris
<snip>
[...at the Solaris boot prompt; enable kmdb, debugging, and single-user
so that you can remove the patch and reboot...]
boot -kds
[...wait for it to boot...]
physmax:w
:c
[...you'll see 'stop on write of'...]
physmax/X
[...you'll see something like the following line:
physmax: bff7f
this is a hex number; add one; so if you see bff7f,
your next line will need to be bff80...]
physxmax/W bff80
:c
[...system will boot and go into single user mode...
now, go toss those patches...]
patchrm 118844-19 120662-03 118345-12 118376-04 \
118565-03 118886-01 119076-10 118813-01 \
118881-02 120082-07 119851-02
shutdown -i6 -y -g0 "sun should test their patches"
</snip>

Solaris 10 SPARC Recommended Patch Cluster for 2008 quarter 3 version

Dear All,
Could any one please guide me, where I can download "Solaris 10 SPARC Recommended Patch Cluster" for 2008 quarter 3 version.
I have checked in sunsolve.sun.com, I'm able to find only the latest release.
please guide me.
Thanks and regards,
veera

Ok,
Here's a cute little formula to try using your systems parameters to gain some "head's-up" on an expected or estimated time to complete the patch run.
You will need a few things to prepare.
Number of "real" CPU's (not hyperthreads)
Speed of each CPU as a whole number i.e 2.87Ghz = 2,867
the total number of patches from the cluster i.e. Sept 15th = 381 (Solaris 10)
Network factor if using NFS = 2.5
local cluster file factor = 1.5
Patch cluster on CDROM factor = 3.25
Now, combine all of those elements in this equation:
{ ( #1 * #2 ) / #3 * factor(#4 or #5 or #6) }
This will yield a number in minutes of patch run time. Then all you will need to add is the standard boot up time to get the total of all patching and reboot.
Of course you could write a script to extract all of this information and feed it to "bc -l" to get a quick figure.
Example, on one of my Solaris 10 boxes with the information filled in to the equation:
#> echo "((4*2660)/381)*1.5"|bc -l
#> 41.88976377952755905511
It actually took 44.2 minutes to complete the patching of this box plus another 12 minutes to reboot. But all in all a pretty fair estimate I think.

Recommended patch cluster release

Hello,
How often is the Recommended Patch cluster released?
A Couple of years ago, i was told at a Sun event during a session, that changes has been made en the way patch cluster was created, and that the patch clusters was created 4 times a year, to make it more streamlike, instead of creating patchclusters once in a while, when enough patches has been created. I need to know if it still works the way, that patch cluster are created 4 times a year, it is to be used with patch procedures and recommendations.
Best regards
Yngve Berthelsen

Recommended patch sets are and to the best of my knowledge have always been regenerated twice a month.
I think your thinking of maintenance releases. When they generate a new CD image which can be used to do an upgrade install.
They try to generate those every 6 months, but the schedule often slips.
The two most recent were sol10 11/06 and sol10 8/07.

10/22/09 SUN Alert Patch Cluster

Similar Messages

Maybe you are looking for