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>

Similar Messages

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

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

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.

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.

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

HT6114 Reboot loop after 10.9.2 upgrade

My 2009 (dual-quad) Mac Pro 4,1 is now stuck in a reboot loop after upgrading from 10.9.1 to 10.9.2.
//edit: I realized there wasn't a question: What is wrong with my computer and how do I fix it?
So far I have tried:
* Repairing the disk
* Repairing permissions
* Zapping the NVRAM/PRAM
* Resetting SMC
* Copying BootCache.playlist from a backup to /var/db
Other things to note about my setup:
In addition to the original hard drive, I installed a 4tb drive from which I have been working with since June. It is the 4tb drive that has 10.9.2 installed. The original 650gb still has 10.8.4 installed and all my original data pre-June.
Also installed is a VisionTek Radeon 7870 video card which powers my numerous monitors. I do not recall having to install anything extra, or modify any settings to get it to work. The only downside is you can't really see anything when booting.
In addition to the VisionTek card I also have one of the factory Geforce 120 cards installed. Using another monitor attached to that card I've been able to monitor the boot process using the command-v verbose output.
Of notable interest I get the dreaded "BootCache: unable to open /var/db/BootCache.playlist : 2" error, along with a few SMC errors. If these are important I can attach pictures taken of the boot process.
I am able to zap the NVRAM and boot the old 10.8.4 650gb drive. It loads fine. 10.9.2 will not boot into safe mode, but will boot into recovery mode.
As a final attempt to fix the BootCache error I copied it from a Time Machine backup into /var/db/ ensuring the correct permissions were set. After rebooting the file is deleted again.
I would greatly appreciate any help on this issue as this is my work computer. I do have full backups via Time Machine so I can reinstall, but I'm hoping there's another solution.

I just started a discussiion related to this topic in "Mac Pro."
https://discussions.apple.com/message/25019730#25019730
" I have a 2009 dual quad core Mac Pro (4.1) with an upgraded Radeon 7950 GPU. I use a 30" Apple Cinema display (DVI) and a 27" LED Cinema Display (Display Port). After updating to 10.9.2, the Mac would not boot, but went on a continuous re-boot cycle every 5-10 minutes without a flicker of life in either display. I unplugged both displays and the Mac booted. I could log in remotely from my laptop. I then attached the 30" Cinema Display into the DVI port and the Mac booted normally."
Dave

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.

Random iPhone crashes and reboot loop after iOS 7 upgrade

Hi all
Since I upgraded my iPhone to iOS 7, I suffer from random crashes/resets, where my iPhone reboots and enters a reboot loop (Apple logo, black screen, reboot, Apple logo, black screen, reboot, etc) that I can only exit by restoring the device (resetting doesn't help).
Some more information
a) The device: iPhone 4, 32 GB, has never been jailbroken, and has never shown any similar issues before.
b) The crashes/reboots: I haven't been able yet to find a pattern when and why they happen. I had reboots when searching for an app, when pluging in the wall charger, when entering the access code, and even when doing nothing at all (iPhone in my pocket). The only constant is the reboot loop after the crash.
c) What I tried so far: I restored the device several times, using normal restore (with the iTunes logo) and DFU mode (black screen). After that, I recovered from a recent backup (takes some hours), and everything is ok again - for some hours, until the next crash and reboot loop. I also set up the device as a new phone, and there it seems stable, so I exclude a hardware issue. I tried quite a few of the advices that I found when googling for reboot loops: reset all settings (this led to an another immediate crash and reboot loop), disable app background refresh, etc.
I've been using this device for my daily business. With the current instability (and the couple of hours it takes to bring it back to life again), it became more or less useless. I wish I could downgrade again (I know that I can't). My assumption is that either iOS 7, or some incompatible app or some corrupt setting is causing this situation. But I don't know how to proceed to isolate and eliminate the issue. I really would like to avoid setting up everything from scratch again.
Any advice is greatly appreciated!

All,
First of all, sorry for my half-finished post above. While typing, I was interrupted, and by reflex I hit CMD-S. Unfortunately, the stupid interface of Apple's support website interpreted that as a submit command. I tried to complete my text with the update function, but when finally hitting the submit button, I got an error message, and all my updated text was gone... No way to bring it back, and also no way to delete the half-baked posting. Quite frustrating.
Now, to complete what I started above:
In my case, the problem definitely had something to do with the springboard process (an iOS system 'app' that manages the iOS homescreens) and the watchdog process (another iOS system 'app' that monitors certain things on your phone and that can initiate a restart when it thinks the phone is frozen). In the folder '/Users/<your account>/Library/Logs/CrashReporter/MobileDevice/<your phone>' I could see what caused my crashes; they were all 'stack+SpringBoard' and the reason in these crash log files was 'Watchdog timeout'.
The following two forum posts helped me:
https://discussions.apple.com/thread/1676330?start=30&tstart=0
https://discussions.apple.com/message/20794982#20794982
I'm quite sure that my issues had to do with the 'application map' that is mentioned in the above posts. So far, Ive been thinking that it was just too large (as in the case of Andi1996 [second link above]), but jmbladen's observation seems not to support this. So, the absolute number might not the source of the problem, but I still assume that something went wrong with my application map during the upgrade from iOS6 to iOS7. I remember having stability problems before, as soon as all my 10 home screens were full of apps and newly downloaded apps would generate additional pages (only visible via iTunes). Considering that there are some fundamental changes to how we can organize apps within folders in iOS 7, it can well be that the springboard process just wasn't able to cope with my application map correctly within the 120 seconds before the watchdog process restarts the phone. My massive cleanup action must have fixed this somehow.
@jmbladen: I'm only using iCloud for the 'find my phone' functionality, so all the backup & recovery was done via iTunes from my local harddisk. And there was no temporal pattern for my crashes before. You might suffer from the same symptoms, but probably not because of the same cause.
My advice for anyone affected by random crashes and a reboot loop is to check out the directory with the CrashReporter logs mentioned above to find out what app or process causes the crash. If it's the springboard and watchdog problem, then you should try to clean up your home screens (from iTunes). Maybe the absolute number of apps is not that important, but make sure that you reduce the number of screens. And then sync and backup before you start using the phone again. In my case it helped.
Hope this helps someone else too.
P.S. Once you know the right keywords to search for, you find forum postings back to 2008 / iOS 2 describing exactly the same problem. This reboot loop is a very nasty issue, and it is hard to understand that Apple still hasn't been able to address this, or at least provide some better help on how to get out of it again.

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.

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.

PRS-T1 stuck in infinite reboot loop after failed firmware update

Hi,
I tried to update the firmware, but failed when updating to version 1.0.07.05070. Tried to 2 times. The first time it failed I simply tried again. The second time, it took a lot longer to reach the failed to update message, but it did cause the ereader to reboot.
Now, it's stuck in an infinite reboot loop on the "Opening book" page. The progress bar on that page stays completely empty, lasts for about 30 seconds, and reboots again. This will go one until the battery is dead or indefinitely if plugged in.
I have tried pressing the Home + Menu buttons, but they seem to have no effect.
Please advise if there is anything I can try to revive it?
Thanks in advanced.
David
Solved!
Go to Solution.

Kiroken,
Here is what I have observed:
- After a hard boot (reset + power button during 3+ seconds), if I don't do anything, it will reboot every ~30seconds.
- If I press and hold the Home and Menu buttons, no effect. The same as if I didn't press anything.
- If I press the Forward + Back buttons (2 & 4), it does not reboot after 30 seconds. Instead, the orange light on the power button blink every ~2-3 seconds.
- Any other key combinations that I have tried have no effect.
I have tried with and without several rescue sdcard. No difference. No improvement. In every case, the computer never sees the reader. If plugged into the power outlet, it seems like the battery charges alright. It does not appear to charge if plugged into USB port.
That's all I know. If I can't fix it, I might be forced to turn it into a coaster or maybe a cutting board for the kitchen.
David

Tour in Reboot Loop after Installing new Messenger

Hi all,
A couple of weeks ago I got a message saying there was a new version of messenger available, so of course I upgraded. After install it wanted a reboot so I did, but the phone never came back. It would start to boot for a couple of minutes but never make it to the desktop. I tried a battery pull with no change.
I ended up reloading the OS (latest Verizon 4.7 release) and all my apps and the phone was fine.
Today I got a message saying, of course, "a new version of messenger is available..." so guess what I did?!?! Yep, and bricked the phone again, it's just in a reboot loop. No error messages, it just constantly reboots without ever making it to the desktop.
I did some searching but haven't found much on this exact problem. Anybody have any ideas? I guess for now I will just avoid the new messenger as I don't really use it that much, but it would be nice if it worked.
TIA

You don't have to have it (the 5.0.0.57 version of BBMessenger) loaded, if you used it much you would see the advantages.
But, If you don't use it, don't worry.
I think there is likely some third party app conflcting with you, but that is another whole long drawn out search .
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

IPod touch 4g 6.1.6 stuck in reboot loop after trying to restore

My ipod touch 4g has a really bad battery and only works if you have it plugged in and charging, but I've never had this problem before. I unplugged it from where it was charging and it died, of course. But when I plugged it into my computer to sync it, it started an endless reboot loop with the apple logo. I tried putting it into dfu mode and restoring it, I've tried doing it on three other macs, and the I've let the battery drain since it dies when I unplug it. Still dont know what the problem is. I cant take it to apple cause I dont have apple care on it and they cant help because the battery doesnt work anyway. Help is much appriciated.

See if y misse anything here:
- iOS: Not responding or does not turn on
- Also try DFU mode after try recovery mode
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
- If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
- Try another cable
- Try on another computer
- If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order. You do not need AppleCare and it is free.
Apple Retail Store - Genius Bar

Reboot loop after software update

My phone is also in constant reboot loop since the update. I tried deleting app after app with no luck. What is going on? Is there anything I can do? I also have tried the master reset, I highlighted recovery pressed the volume up and it went into reboot loop mode again. Any suggestions??

I know its frustrating to have a phone that is rebooting constantly Jimlpn. I'm sorry the steps provided in the other thread did not work. Is your phone damaged? Replacing the phone may be the next step. You can also take your phone to a corporate store location for a hands on evaluation. Is your phone under the 1year manufactures warranty and do you have insurance?
KinquanaH_VZW

Solaris reboot loop after recommended patch cluster

Similar Messages

Maybe you are looking for