Solaris 10 X86 kernel patch 118844-30 ... probably bad

I installed the patch on some Dells. Seemed to run fine.
Actually, I installed 121127-01, 113000-07, and 118344-06
first since they were required by 118844-30.
Some problems have now turned up.
1. When you power cycle one of the patched machines they
refuse to boot with
Warning - The following files in / differ from the boot archive:
/boot/solaris/bootenv.rc
to continue booting .. #svc clear system/boot-archive
and then demand the root password.
2. Randomly, when you do a reboot, a patched machine will claim
that the hardware has changed and demand that you run
kdmconfig. Simply going in and out of kdmconfig, without
changes, does the job. Weird.
3. I went to patch the next machine and after the patch
install and reboot, it was a total brick, with the error
File not executable
Panic : No entry point in kernel/unix
Press any key to reboot
And, naturally, this patch cannot be backed out. For yucks
I tried the equivalent patches on a sparc. No problems. So
I think Sun effed up the GRUB stuff in the kernel patch

Ok ... I noticed that deep down in the README for the patch
they say to do a "reboot -r". Cute. We'll try that.
That seemed to go ok, but when I tried a power cycle, it
wouldn't boot, claiming
SMF database integrity check of /etc/svc/repository.db
failed making me run
/lib/svc/bin/restore_repository
which turned out to be a struggle.
My advice - stay FAR AWAY from this patch. At minumum,
it makes the power up boot process VERY delicate. Wait
for the -32 rev, which I predict will not be long in coming.
Thank you sun.

Similar Messages

Unable to boot the sytem after applying kernel patch 118844-27

We have an hp ProLiant DL380 Storage server connected to HP StorageWorks Moduler Smart Array 30 via SCSI. Solaris 03/05 was installed previously on this system with kernel 118844-20. When I queried and installed all required patches with 'smpatch add -i .. ' command, all patches applied and the system is rebooted. After reboot, the system kept restarting. I followed the instructions on Sun Alert document 102087, and installed grub using 01/06 1st CDROM. It installed successfully, but problem persisted. The systems started booting, but before printing 'Configuring devices' the system rebooted again. Providing -v option to the kernel, it lastly printed a PCI device id (/pci@....) and after 2-3 seconds rebooted again.
Finally I had to reinstall the solaris (this time 01/06). The disk was accessible after booting with CD ROM, and I was able to get cylinder numbers of disk, and I installed the new system to the root partition of the other live upgrade environment. The boot disk was partitioned under linux, it was three partitions, Solaris2 (50GB),Solaris(4GB),Linux(18GB). Installation medium told that the fdisk partition was invalid, and i repartitioned the whole disk again.
System up and running Solaris 10 01/06 now, but the strange thing is that, previously hard disk (both boot disk and disks on array) locations were identified as '/dev/rdsk/c0tx' but now, the system sees that hard disks at '/dev/c1tx' and CDROM at '/dev/c0t0'.
Now I want to ask tow questions:
* Could this disk number change made the system unbootable previously?
* May I safely apply patch 118844-28 to the system
-Thanks

Here's a similar topic https://bbs.archlinux.org/viewtopic.php?pid=536210 also if that doesn't work you should install vesa as it also says it's not found in your log.

Fresh solaris 10 x86 install patch update problems 119060-17 ...

Just yesterday, i installed a fresh Solaris 10 x86 onto some pc hardware. After getting solaris installed and issues with my network card, i downloaded and installed the free version of the update manager 1.0.x. Next, i proceeded to update all the general patches for the solaris 10 system. I started with the command 'pprosvc -i' from a terminal. It then proceeded to download and validate a bunch of patches successfully until it hit the following 3 patches:
119060-17 ---- X11 6.6.2_x86: Xsun patch
122213-10 ---- GNOME 2.6.0_x86: GNOME Desktop Patch
122912-02 ---- SunOS 5.10_x86: Apache 1.3 Patch
All 3 failed some kind of validation and then crashed the pprosvc program, at which point it exited with the following error:
122912-02 cannot be validated
119060-17 cannot be validated
122912-02 cannot be validated
Unexpected Failure: java.lang.Throwable: ERROR: Failed to validate the digital signature(s).
I also tried to use the GUI Update Manager to update, hoping the problem was isolated to pprosvc, but that problem was also in the GUI with a similar error message:
Error occurred...The detailed error message is: Unexpected Failure: java.lang.Throwable: ERROR: Failed to validate the digitial signature(s)
Anyone know why Sun's update patch process is so troublesome?
Getting Tired of Solaris Updates...
I should mention that this is the free solaris 10 x86 install and i don't have a service contract with Sun. If this problem persists, i don't think i'll get one, as i see only further problems after buying one.
tired and confused

Hi,
There is an issue with this that is currently being investigated. There is another thread that may shed some light on what is happening here;
http://forum.sun.com/jive/forum.jspa?forumID=316
Thread title is : Sun UC, Digitally Signed Patches Using New Verisign Certificates
In the short-term please ensure that the patch mentioned in it is installed.
To quote part of mentioned thread above:
"Once the Sun Update Connection client software is upgraded with patch 121118-06 (SPARC) or 121119-06 (x86/x64) or later revisions normal behavior will resume. "
If this fails to resolve your problem, would you be kind enough to post the output of the following command for analysis please;
# showrev -p | egrep -e '121454|121119|120336|121082|121564|122232|119789'
Sincerely,
Moderator.
Message was edited by:
ForumModerator

Kernel patch 118844-30 problem

I have an AMD-64 computer and when I try to install patch 118844-30 (and dependent patch for send mail), and restart, I get a million error messages at bootup, including "is syslogd running?". I had to reinstall the whole OS to get back to normal. Other updates worked fine.

Yes, I also experienced the same thing with 118844-30 and 118822-30. It seems other people are also having issues with 118855-xx. I simply bypassed these patches, after a painful rebuild, and now everything is OK, including all other recommended patches.

Solaris 10 x86 jumpstart patch problem

I'm trying to jumpstart and deploy the patch using the profile file(classfile). I does work well on the sparc however I seem to have an issue with x86. The line in profile file looks like this
patch patch_order nfs server1:/patch/10_x86
patch patch_order nfs server1:/patch/10_x86/10_x86_Recommended
The same directory "patch" is shared for sparc and x86 and all directory have the same permission.
Every time I jumpstart, I get this error message
Installing patches now
ERROR: Could not mount server1:/patch/10_x86 for patch install
ERROR: Could not mount server1:/patch/10_x86/10_x86_Recommended for patch install

The problem was caused by the ipfilter behavior - ignorance of interface alias. My ipnat rule was:
map aggr150031:1 ...
I have changed into:
map aggr150031 ...
and the things began to work.
Sorry for the noise.

Solaris patching on solaris 10 x86

just wondering if anyone can assist. i have just installed solaris 10 x86 recommended patches on a 16 disks server. where first 2 disks are mirrored called rpool, and remaining 14 disks are raid z called spool. upon installing the patches successfully and rebooting server, i am coming up with the following error:
NOTICE: Can not read the pool label from '/pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@0,0:a /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@1,0:a'
NOTICE: spa_import_rootpool: error 5, Inc. All rights reserved.
Cannot mount root on /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@0,0:a /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@1,0:a fstype zfs
panic[cpu0]/thread=fffffffffbc28820: vfs_mountroot: cannot mount root
fffffffffbc4b190 genunix:vfs_mountroot+323 ()
fffffffffbc4b1d0 genunix:main+a9 ()
fffffffffbc4b1e0 unix:_start+95 ()
skipping system dump - no dump device configured
rebooting...
It looks like the solaris 10 os cannot find zfs filesystem and keeps on rebooting in normal solaris os mode, but when I go to safe mode and type: zfs list, I can see zfs rpool (mirrored) file system and cannot see the zfs spool (raid z) file system, any ideas on how i can fix the boot problem and get zfs spool back in the safest way possible?...

I finally figured it out. It seems that kernel patch 137138-09 was the culprit. It took me a while to test each kernel patch but I found out that if you have a mirrored volume or a virtual logical volume this will affect you. Also, after I did all this testing I finally found the sunsolve article referencing this patch. Seems you can install the patch, but you have to install 125556-01 first. Here's the article: http://sunsolve.sun.com/search/document.do?assetkey=1-66-246206-1

Patch 118844-28 fails to install on Ultra 20?

We're trying to run the standard updatemanager on our Ultra 20 running Solaris 10 x86. We've installed patches a number of times but we're hitting a wall with the recent kernel patch, 118844-28.
This patch shows up as needing to be applied in both the updatemanager gui as well as when we run smpatch analyze. The problem is that it doesn't seem like it will install even though the tools say that the installation procedure was successful. Specifically: we instruct the gui to install the patch, it goes off and looks like it's installing, it comes back and says that the installation is complete and successful and that we need to reboot the machine, we tell it to reboot the machine and it does. But when the machine comes back up the updatemanager (and smpatch) still says that this patch needs to be applied. And showrev says that we're still back at version 27. So it seems like it's properly applying the patch but then the patch isn't actually applied.
We tried to install the patch by hand with smpatch add in single user mode and we had a similar experience. The only exception being that the patch process complained that we had to have patch 117435-02 installed (which we do).
Has anybody seen this before? Has anybody gotten this patch to install on this hardware?

Yes, I agree with that fix- I just did it a little opposite:
# eeprom boot-device=/pci@0,0/pci-ide@11,1/ide@0/cmdk@0,0:a
which added an extra alias (permanently) to my 'BIOS' settings-
# eeprom | grep boot
bootpath=/pci@0,0/pci-ide@7/ide@0/cmdk@0,0:a
boot-device=/pci@0,0/pci-ide@7/ide@0/cmdk@0,0:a
I re-ran the 10 Rec. Cluster and it not only installed the kernel patch, but, a handful of other patches in the bundle too.
--David

Driver e1000g problem - patch 118844-30

Hi,
the situation is like this. I have fujitsu-siemens pc and Solaris 10 03/05 x86 installed. I wanted to patch it with latest recommended patch cluster. After that I was not able to get to default router and switch did not see my mac anymore. I looked in the patch cluster and removed patch by patch till the kernel patch 118844-30. I finished my todays troubleshooting with one big ZERO :-), but it works now a can sleep well. There was no error reported in log files, no smf failed, nothing. If anyone knows, where is the real problem or how to apply some work-around, it would be great.
Le

Yes, I also experienced the same thing with 118844-30 and 118822-30. It seems other people are also having issues with 118855-xx. I simply bypassed these patches, after a painful rebuild, and now everything is OK, including all other recommended patches.

Solaris boot problem after Patch cluster install

just wondering if anyone can assist. i have just installed solaris 10 x86 recommended patches on a 16 disks server. where first 2 disks are mirrored called rpool, and remaining 14 disks are raid z called spool. upon installing the patches successfully and rebooting server, i am coming up with the following error:
NOTICE: Can not read the pool label from '/pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@0,0:a /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@1,0:a'
NOTICE: spa_import_rootpool: error 5, Inc. All rights reserved.
Cannot mount root on /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@0,0:a /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@1,0:a fstype zfs
panic[cpu0]/thread=fffffffffbc28820: vfs_mountroot: cannot mount root
fffffffffbc4b190 genunix:vfs_mountroot+323 ()
fffffffffbc4b1d0 genunix:main+a9 ()
fffffffffbc4b1e0 unix:_start+95 ()
skipping system dump - no dump device configured
rebooting...
It looks like the solaris 10 os cannot find zfs filesystem and keeps on rebooting in normal solaris os mode, but when I go to safe mode and type: zfs list, I can see zfs rpool (mirrored) file system and cannot see the zfs spool (raid z) file system, any ideas on how i can fix the boot problem and get zfs spool back in the safest way possible?...

Same problem here with actual recomended patch set.
NOTICE: Can not read the pool label from '/pci@0,0/pci10de,375@f/pci1000,3150@0/sd@0,0:a /pci@0,0/pci10de,375@f/pci1000,3150@0/sd@1,0:a'
NOTICE: spa_import_rootpool: error 5
Cannot mount root on /pci@0,0/pci10de,375@f/pci1000,3150@0/sd@0,0:a /pci@0,0/pci10de,375@f/pci1000,3150@0/sd@1,0:a fstype zfs
panic[cpu0]/thread=fffffffffbc28820: vfs_mountroot: cannot mount root
fffffffffbc4b190 genunix:vfs_mountroot+323 ()
fffffffffbc4b1d0 genunix:main+a9 ()
fffffffffbc4b1e0 unix:_start+95 ()
What the hell happened to the bootsektor or the pool or what ever?

Last kernel patch for Solaris 10 x86 screwed up my kernel

Hi,
The last kernel patch for Solaris 10 x86 (sorry I can�t remember the patch id, but the revision is 30), available from Sun Update Manager screwed up my system.
The system is still booting but in maintenance mode: smf can't start because of repository corrupted. Given instructions to restore the repository does not work because / filesystem is mounted read-only...
As I am not a solaris expert, I will reinstall it from CD. I hope I won't loose the filesystem.
I was used to blindly trust Sun solaris patches, that was a mistake.
Laurent.

i dont know why but still i do get default log in into the single mode
after startup
Requesting maintenance mode
(See /lib/svc/share/README for aditional information. )
Root password for system maintenance (control-d to bypass):i did removed the patch installed before so now
SunOS jorgito 5.10 Generic_118844-26 i86pc i386 i86pcand finaly i do have milestone like this
bash-3.00$ svcprop restarter | grep mile
options/milestone astring svc:/milestone/multi-user:default
dont know what to do else, also tried to synchronize boot-archive from solaris failsafe ...

Kernel patch updation for solaris 10 x86

I have Solaris 10 06/06 installed on x86 machine which is using svm and clustered with another node. The kernel revision is 118855-19 from the uname -a output. I am looking for the kernel patch updation and I heard 118855-36 is the latest one. Shall I go ahead with this patch and what r the dependency patches for this.
If anyone done this please guide me..

Patch 118855-36 is the latest kernel patch for Solaris 10 on x86 and its dependencies are:
113000-01 117435-02 118344-14 119043-09 119255-14 121264-01 122035-01 123840-01 (or greater)
Whether you should go ahead and install the patch is up to you, if possible try it out on a test box first. For better advice on this matter, I would suggest posting in the Solaris 10 forum as this forum is for the Sun Update Connection, Patch Manager & PatchPro toolsets.

Kernel patch update for solaris 10 x86

I have Solaris 10 06/06 installed on x86 machine which is using svm and clustered with another node. The kernel revision is 118855-19 from the uname -a output. I am looking for the kernel patch updation and I heard 118855-36 is the latest one. Shall I go ahead with this patch and what r the dependency patches for this.
If anyone done this please suggest and guide me..

For Solaris 10 x86 the latest offered with smpatch is 125101-07 and yes it may be recommended to patch. Then again you said clustered with sun cluster? You may want to check the documentation and if your machines aren't facing the internet you may wait for 7/07 to hit the street and do an upgrade.

Applied Kernel Patch to Solaris 10 on v40z, no longer auto boots

I recently updated the patches on a v40z machine including a kernel patch. After rebooting, the machine would no longer automatically boot to Solaris. Instead it would just wait for user input at the Grub bootloader screen. Anyone experienced this or have a solution?
I believe the patch in question is 118855-19
# bootadm list-menu
The location for the active GRUB menu is: /boot/grub/menu.lst
default 0
timeout 10
0 Solaris 10 6/06 s10x_u2wos_09a X86
1 Solaris failsafe

SOLVED:
Disabled ECC in the bios (though Windows and Gentoo Linux show now trouble whatsoever with my ECC memory, solaris doesn't like it)

Kernel patch 127128-11 renders my x86 system unbootable - what to do?

Just installed some patches with smpatch as usual, kernel patch 127128-11 among them. I then dropped to single user mode to finish the installation, rebooted and... nothing. I get the SunOS copyright notice, and then nothing but a flashing cursor... I waited for half an hour, but nothing happened, no disk activity, keyboard not responding, nothing.
I had to reset the stupid machine...
This happened on old(ish) HP Vectra SFF.
What I can do now? What are my options? (And please DON'T say: "reinstall everything"!!!)
I have used Linux for 7-8 years, but Solaris is pretty new for me, this installation is some 2 months old (Sun Solaris 10 - 8/07 - x86)

I remember I ever tried a tool that you need to run in order to put your computer on the list.
Well it suddenly crashed and I didn't try it again.The certification tool: http://www.sun.com/bigadmin/hcl/hcts/
At Sun they know very well which systems I'm running Solaris on.
This data is sent when you register to apply for updates.They don't use your registration info to list a system as certified to run Solaris10. See link above.
I have to admit I never added any patches by going into single user mode.I install in single user per instructions in patch README. I have rarely had issues installing patches this way.
Reading back this thread I see that this patch was part of the Solaris 10 5/08 version
and since I recently upgraded to this version and everything is working fine,
I don't think there is an issue. Neither do I think that there is an issue with 127128-11 patch, which is why I mentioned that OPs machine was not on HCL. It's an issue with OPs hardware, not the new kernel. So, what is that 'fix' disabling so that Solaris will run on unsupported hardware?
I haven't tried OpenSolaris yet. What do you think of it so far?

Keyboard messed up on Solaris 10 x86 after applying patch update

I have run into a keyboard problem on my Solaris 10 desktop. The keyboard is messed up. When I type �root� then it echoes as �eiir�. It is a Solaris 10 x86 system with PS/2 keyboard. The keyboard layout is US-English and type is generic 104 keys. The keyboard works fine in text mode but gets messed up as soon as the graphical login screen comes up.
The output for �eeprom kbd-type� is �kbd-type=US-English(104-Key)�.
The output for �kbd -l� is
�type=6
layout=33 (0x21)
delay(ms)=500
rate(ms)=40�.
Running command �showrev -p | grep 118966� shows �
Patch: 118966-11 Obsoletes: Requires: Incompatibles: Packages: SUNWxorg-xkb, SUNWxorg-server, SUNWxorg-doc, SUNWxorg-graphics-ddx
Patch: 118966-21 Obsoletes: Requires: 118860-01 Incompatibles: Packages: SUNWxorg-xkb, SUNWxorg-server, SUNWxorg-cfg, SUNWxorg-doc, SUNWxorg-graphics-ddx, SUNWxorg-client-programs
The file /var/dt/Xerrors contains the following error �
The XKEYBOARD keymap compiler (xkbcomp) reports:
Error: No Symbols named "ralt_switch_multikey" in the include file "level3"
Exiting
Abandoning symbols file "basic"
Error: Num_Lock added to symbol map for multiple modifiers
Using Mod3, ignoring Mod2.
Abandoning symbols file "default"
My keyboard was working fine till around a couple of days back and messed up after performing updates with Sun Update Manager. The patch 118966-21 was installed during that update and so was patch 118844-30. I have not tried uninstalling either of these patches to see if that fixes the problem. Should I?
Please help!!! Thanks�

Problem solved... me the n00b...
After reading the log in /var/dt/Xerrors more closely this time I found that it was trying to load module "Keyboard" for the device "Keyboard1" and was not able to find that module. The log was also suggesting that this module is deprecated and I should use "kbd" instead... Made the changes in xorg.conf and things are good now...

Solaris 10 X86 kernel patch 118844-30 ... probably bad

Similar Messages

Maybe you are looking for