pk3 -> pk5 update, lsm problem help!

[Michael Schulte zur Sur]

BL,

thanks for your time. We had a technician at our workplace. Actually I am not to sure what all was done but I will have to request a statement because the patch was the cause for the disaster. We managed to boot to single user mode by replacing the LSM label on usr, disabled LSM in sysconfigtab. We could mount usr, restored /, /var and /usr but still had some problems with restoring the LSM label. After booting from CD the technician was able to restore the label and fix the problem.

Michael

[Venkatesh BL]

Glad to hear that the problem is finally resolved!

[Johan Brusche]

Glad it's working again.
Some observations ....
Via voldctl list, /etc/vol/volboot content tells us dsk6h was used to create rootdg.

Do you remember if dsfmgr was used to move
or interchange dsk6 with dsk0 ? Is dsk6 still there does it have also a partiton-h
with size 4096 ?
Any reference to LSM in cnx-partitions-h ?
cfr clu_bdmgr -d --> /dev/disk/dskn|simp::

What was the uptime, and was this rolling patch-install the first member reboot since then ? Maybe the problem was already there,
just waiting for a reboot to manifest itself.

Disklabels on disks containing root partitions are already locked at boot, you can change in-memory copies, but not on-disk.

__ Johan.

[Michael Schulte zur Sur]

Johan,

we did not use dsfmgr and this is not a cluster. It is a standalone machine. The simp partition is on dsk0. I have now heard by rumor that this is not supported. Can you confirm this? If so, why is there no check on this?

thanks,

Michael

[Venkatesh BL]

Which is not supported?. Can you elaborate?

[Michael Schulte zur Sur]

BL,

my colleague was told by HP, that patching a stand alone system while in multiuser mode is not supported.

Michael

[Johan Brusche]

That HP person made a quite restrictive interpretation of the "Warning" notice, that you will find also in your /var/adm/patch/log/session.log

To me it means: multi-user ie. "init state 3" is supported, with restrictions...

----quote----

*** Installation Warning ***

You have chosen to install patches onto this system while it is running in
Multi-User mode. Some patches may directly affect core operating system
operations. To ensure the proper operation of all applications, it is
strongly suggested that you install these patches while the system is in
Single-User mode. If this cannot be done, install these patches when the
system is as lightly loaded as possible (i.e. not running production
environments, no users logged on, etc.).

Do you wish to continue? (y/n) [y]: y

----end_quote----

The critical things are p.ex. the substitution of shared libraries. You can understand that applications like Oracle in production mode will shoke while in-use shared libraries are disappearing.

___ Johan.

[Michael Schulte zur Sur]

Johan,

that I would understand. But I stopped all applications before and there were no errors in the log.

Thanks,

Michael

[Venkatesh BL]

Michael,

This is strange to me. I am not sure why he said that its not supported. If that's the case, they could have removed that option completely (from patch installation).

[Michael Schulte zur Sur]

BL,

that would have been a wise course of action. Check if machine is a member of a cluster. If not, remove multiuser option.

greetings,

Michael