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

Similar Messages

Problem: installing Recommend Patch Cluster: patch 140900-10 fails

I don't know if this is correct location for this thread (admin/moderator move as required).
We have a number of Solaris x86 hosts (ie 4) and I'm trying to get the patched and up to date.
I obtained the latest Recommended Patch Cluster (dated 28Sep2010).
I installed it on host A yesterday, 2 hours 9 mins, no problems.
I tried to install it on host B today, and that was just a critical failure.
Host B failed to install 140900-01, because the non global zones rejected the patch because dependancy 138218-01 wasn't installed in the non global zones.
Looking closer, it appears that 138218-01 is for global zone installation only; so it makes sense that the non global zones rejected it.
However, both hosts were in single user mode when installing the cluster and both hosts have non global zones.
140900-01 installed on host A with log:
| 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.
|
| 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.
|
|
| Installation of <SUNWcsu> was successful.
140900-1 failed on host B with this log:
| Validating patches...
|
| Loading patches installed on the system...
|
| Done!
|
| Loading patches requested to install.
|
| Done!
|
| Checking patches that you specified for installation.
|
| Done!
|
|
| Approved patches will be installed in this order:
|
| 140900-01
|
|
| Preparing checklist for non-global zone check...
|
| Checking non-global zones...
|
| Checking non-global zones...
|
| Restoring state for non-global zone X...
| Restoring state for non-global zone Y...
| Restoring state for non-global zone Z...
|
| This patch passes the non-global zone check.
|
| None.
|
|
| Summary for zones:
|
| Zone X
|
| Rejected patches:
| 140900-01
| Patches that passed the dependency check:
| None.
|
|
| Zone Y
|
| Rejected patches:
| 140900-01
| Patches that passed the dependency check:
| None.
|
|
| Zone Z
|
| Rejected patches:
| 140900-01
| Patches that passed the dependency check:
| None.
|
| Fatal failure occurred - impossible to install any patches.
| X: For patch 140900-01, required patch 138218-01 does not exist.
| Y: For patch 140900-01, required patch 138218-01 does not exist.
| Z: For patch 140900-01, required patch 138218-01 does not exist.
| Fatal failure occurred - impossible to install any patches.
| ----
| patchadd exit code : 1
| application of 140900-01 failed : unhandled subprocess exit status '1' (exit 1 b
| ranch)
| finish time : 2010.10.02 09:47:18
| FINISHED : application of 140900-01
It looks as if the patch strategy is completely different for the two hosts; both are solaris x86 (A is a V40z; B is a V20z).
Trying to use "-G" with patchadd crabs the patch is for global zones only and stops (ie it's almost as if it thinks installation is being attempted in a non global zone).
Without "-G" same behavior as patch cluster install attempt (no surprise there).
I have inherited this machines; I am told each of these machines were upgraded to Solaris 10u6 in June 2009.
Other than the 4-5 months it took oracle to get our update entitlement to us, we've had no problems.
I'm at a loss here, I don't see anyone else having this type of issue.
Can someone point the way...?
What am I missing...?

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

Problem install Recommended Patch cluster

Trying to install the Recommended patch cluster on Ultra 45s, on each one, the 40th patch, 120272-28, fails, and I don't understand why. Here's the snippet from the log:
STARTING : application of 120272-28
start time : 2010.11.30 08:41:42
# /usr/sbin/patchadd 120272-28
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
The following requested patches have packages not installed on the system
Package SUNWsmaS from directory SUNWsmaS in patch 120272-28 is not installed on the system. Changes for package SUNWsmaS will not be applied to the system.
Checking patches that you specified for installation.
Done!
The following requested patches will not be installed because
they are incompatible with patches already installed or with
other patches that you have specified for installation. In order to install these
requested patches you should resolve this incompatibility
by removing incompatible patches from requested-to-install set
or from the system.
0 Patch 120272-28 is declared as incompatible by IDR138540-01, which has already been installed on the system.
No patches to install.
patchadd exit code : 3
application of 120272-28 failed : unhandled subprocess exit status '3' (exit n branch)
finish time : 2010.11.30 08:41:42
FINISHED : application of 120272-28
I don't understand why it fails, rather than just being "skipped", as several other patches are. I assume the failure isn't coming from the fact that it's been declared incompatible, but rather the "unhandled subprocess exit status". How do I determine what that is?
Or, better yet, how do I tell the installcluster script to just not do that one?
Thanks!

did you try and removed the IDR? I.e: patchrm IDR138540-01 ?
.7/M.

BizTalk Administration Console problem after installing IBM iSeries Access

Hi,
We have a Biztalk Server 2010 environment on Windows Server 2008 R2 with SQL server on separate machine.
After installing IBM iSeries Access we get errors in Biztalk Administration Console, especially the Host Instance and Adapter information cannot be loaded.
Except for the errors in Adminsitration Console, the Biztalk installation seems to be working fine, so the integration processes doesn't seem to be affected.
We get the following error:
BizTalk Server cannot access SQL server. This could be due to one of the following reasons:
1. Access permissions have been denied to the current user. Either log on as a user that has been granted permissions to SQL and try again, or grant the current user permission to access SQL Server.
2. The SQL Server does not exist or an invalid database name has been specified. Check the name entered for the SQL Server and database to make sure they are correct as provided during SQL Server installation.
3. The SQL Server exists, but is not currently running. Use the Windows Service Control Manager or SQL Enterprise Manager to start SQL Server, and try again.
4. A SQL database file with the same name as the specified database already exists in the Microsoft SQL Server data folder.
Internal error from OLEDB provider: "The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception." (WinMgmt)
I tried to uninstall the IBM iSeries Access, but the problem remains.
This issue is related to this post
http://social.technet.microsoft.com/Forums/en-US/6f371f45-813c-48d8-80e3-bd94e00bf5dd
But this post seem to miss a solution.
Thanks fo your help with this!
BR
Samuel
SamueL J

Hi and thanks for your help!
The machine.config did it :)
According to this link there is a known issue with the IBM iSeries Access installation which removes the proper permissions from the machine.config and therefore Biztalk Administration Console stops working correctly.
http://www-01.ibm.com/support/docview.wss?uid=nas284158c400658982b86257611003c6d21
BR
Samuel
SamueL J

MB.ACT light OFF --- after Solaris 9 recommended patch cluster applied

After applying the recommended patch cluster to several SunFire V210s/V240s the "system ready" or "activity" light on the front panel no longer illuminates. The systems come up fine and are fully functional, just no light.
While this has absolutely no impact on usability it is a bit disconcerting for the folks in the server room when glancing at the rack and not seeing the typical green light.
I first noticed the problem in mid 2007 and have tried patch clusters as recent as last month, but the light remains out.
One interesting discovery is that if I reset (hard) the ALOM module the light comes back on. However, if the system is subsequently rebooted for any reason the light does not come back on...
If anyone can shed some light on the issue I would greatly appreciate it!
-Sap

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

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>

Installing new patch cluster after os is hardened with Jass 4.2

hi, i have a Solaris 10 system that's hardened with Jass 4.2. what is the correct way/best practice to apply the latest recommended patch cluster?
will applying the latest recommended patch cluster 'un harden' the system?
thanks.

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

Sun Update Manager not working after applying latest patches

I just applied the latest patches using the Sun Update Manager GUI but now it doesn't work. After logging in to the GUI as root I get a message telling me an unknown error occurred and I see the following on my terminal:
java.lang.NullPointerException
at com.sun.swup.client.engine.solaris.SolarisUpdateCollection.invalidateCachedData(SolarisUpdateCollection.java:783)
at com.sun.swup.client.ui.UpdateFrame$LoadDataWorker.construct(UpdateFrame.java:256)
at com.sun.swup.client.ui.foundation.swing.SwingWorker$2.run(SwingWorker.java:109)
at java.lang.Thread.run(Thread.java:595)
Any hints?

I just installed the latest 9 recommended patch cluster and I am getting the same problem. Although I am not even able to login as root. I enter the login name root and then it blinks and comes back to the login screen. Any help would be greatly appreciated.

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.

Can't detect my build-in touchpad after installing grub patch

Hi
I have installed on my HP Compaq nx8220 solaris 10 01/06 and I had a problem with USB that was solved by installing the pathces required for installing recomanded patch cluster.The problem is that after installing those patches and respecting the README files from every patch my touchpad is not recognise anymore.The mouse should be found in /devices/isa/i8042\@1\,60/mouse\@0.
Can anyone help me

Hi
I have installed on my HP Compaq nx8220 solaris 10 01/06 and I had a problem with USB that was solved by installing the pathces required for installing recomanded patch cluster.The problem is that after installing those patches and respecting the README files from every patch my touchpad is not recognise anymore.The mouse should be found in /devices/isa/i8042\@1\,60/mouse\@0.
Can anyone help me

Install Recommended Path Cluster Fails

When I try to install the patch cluster on a new install I get two kinds of failures depending on what I am trying to do.
I am installing on a 2900 and the Solaris 2.10 (3/05)
If I use the nosave option then I get a failure code of 45
If I don't use the nosave option I get this:
ld.so.1: zonename: fatal: relocation error: file /sbin/zonename: symbol zonecfg_is_scratch: referenced symbol not found
Can someone tell me what is going on?

I had the same error yesterday, but only in a zone, not the global one.
Here is how I solved my problem:
FROM THE LOCAL ZONE:
# ldd /sbin/zonename
libzonecfg.so.1 => /usr/lib/libzonecfg.so.1
libc.so.1 => /lib/libc.so.1
libsocket.so.1 => /lib/libsocket.so.1
libnsl.so.1 => /lib/libnsl.so.1
libxml2.so.2 => /usr/lib/libxml2.so.2
libmp.so.2 => /lib/libmp.so.2
libmd5.so.1 => /lib/libmd5.so.1
libscf.so.1 => /lib/libscf.so.1
libpthread.so.1 => /lib/libpthread.so.1
libz.so.1 => /usr/lib/libz.so.1
libm.so.2 => /lib/libm.so.2
libdoor.so.1 => /lib/libdoor.so.1
libuutil.so.1 => /lib/libuutil.so.1
/platform/SUNW,Sun-Fire-V240/lib/libc_psr.so.1
/platform/SUNW,Sun-Fire-V240/lib/libmd5_psr.so.1
I noticed 2 .so files the were local to the zone (in /usr). Since the "zonename" command worked fine in the global zone, I suspected corrupted librairies.
FROM THE GLOBAL ZONE:
bash-3.00# diff /usr/lib/libzonecfg.so.1 /mnt/ms012/root/usr/lib/libzonecfg.so.
1
Binary files /usr/lib/libzonecfg.so.1 and /mnt/ms012/root/usr/lib/libzonecfg.so.1 differ
So here is my problem. I just took the .so file from the global zone to the local one.
bash-3.00# cp /usr/lib/libzonecfg.so.1 /mnt/ms012/root/usr/lib
bash-3.00# zlogin ms012
[Connected to zone 'ms012' pts/1]
Last login: Tue Jan 22 10:33:33 on pts/1
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
*# zonename*
ms012
Voil�! the zonename command works fine again. After that, I did a clear on all services tagged in maintenance state in svcs -a.

I see that i have a problem after installing my new hard drive on my macbook pro mid 2009 version. I put a new hard drive, with all of my information from my old drive installed on it, into the computer. but now have the blinking question mark folder

i see that i have a problem after installing my new hard drive on my macbook pro mid 2009 version. I put a new hard drive, with all of my information from my old drive installed on it, into the computer. but now have the blinking question mark folder. I see that it means that it isn't reading the new hard drive.
did i miss a step between transferring all of my information from my old hard drive to the new hard drive and installing the new hard drive into the computer. I believe that i installed properly. it was quite easy.
thanks for your help

It means there is no bootable system on the drive. If you still have access to the old drive, then I suggest you boot from it then clone it to the new internal drive. Use OPTION boot to boot from the Recovery HD on the old drive:
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
     1. Select Disk Utility from the main menu then press the Continue
         button.
     2. Select the destination volume from the left side list.
     3. Click on the Restore tab in the DU main window.
     4. Select the destination volume from the left side list and drag it
         to the Destination entry field.
     5. Select the source volume from the left side list and drag it to
         the Source entry field.
     6. Double-check you got it right, then click on the Restore button.
Source means the external old drive. Destination means the new internal drive.

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.

Patch manager for sol9 missing some recommended patches

I just tried cross checking a machine that was completely up to date according to patch manager with the Sol 9 recommended patch set.
The recommended patch set included the following patches that patch manager doesnt appear to distribute.
114049, 111711, 111712, 119211.
I would have thought anything that was important enough to be included in the recommended patch set was worth distributing through patch manager.
In particular, 114049 and 119211 appear to have security implications.

Hi Robert,
This forum is for Sun update Connection problems on Solaris 10 only.
I cannot give you reply as to why Patch manager for sol9 missing is some recommended patches. I will email an internal email alias and try to find out.
Regards,
Scott

A lot of problems after installing Windows XP using Boot Camp on a Mac Book

I have been having a lot of problems after installing Windows XP Home Edition (2002).
For one, after installing Windows using Boot Camp with Mac OS X 10.5.1, I opened Windows on my Mac Book, inserted the Mac OS X Disk 1 as in the instructions and got the message: +"This package requires a newer version of the Windows installer. Do you want to update the version of the Windows Installer on your system?"+ When I clicked Yes (I had NO idea what it meant at the time), I got the message: "The required resource 'UPDATE' is missing" and the Installer quit.
How do I fix this problem?
Another problem I have is that there is no sound on the Windows XP, yet it works perfectly on Mac OS X. Is there any way to fix this problem?
A third problem I have is that I can't wirelessly connect to the internet using Window XP, yet I can on Mac OS X. I have no idea on how to fix this, and it's really messing with me. D:<
D: There are way too many problems, and I have a feeling there will be a lot more later on. Help....
~Twilight

---I'm moving this topic to the Boot Camp forums.
-Twilight

Management console problem after installing recommended patch cluster

Similar Messages

Maybe you are looking for