Hi,
After applying patch 137137-09 in multi-user on two Solaris 10 (Sparc)
boxes, one of them refused to boot with following message:
----------------------
{0} ok boot
...
Rebooting with command: boot
Boot device: /[EMAIL PROTECTED],600000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0:a
File and args:
Boot load failed.
The file just loaded does not appear to be executable.
----------------------
We had to apply a bootblock recovery procedure to be able to boot again.
(see http://sunsolve.sun.com/search/document.do?assetkey=1-62-206110-1)
We could see where the problem lies on an equivalent test system while
applying the patch in single-user:
----------------------
...
Patch 137137-09 has been successfully installed.
See /var/run/.patchSafeMode/root/var/sadm/patch/137137-09/log for details
Executing postpatch script...
Detected SVM root.
Installing bootblk on /dev/rdsk//dev/dsk/c6t20000014C35012F5d0s0
/dev/rdsk//dev/dsk/c6t20000014C35012F5d0s0: Not a character device
Installing bootblk on /dev/rdsk//dev/dsk/c6t20000004CF6F4E64d0s0
/dev/rdsk//dev/dsk/c6t20000004CF6F4E64d0s0: Not a character device
...
----------------------
The installboot argument is broken if you have Solaris I/O multipathing
enabled (MPxIO) AND your system disks are fiber channel devices. (In
that case short device names are replaced by STMS long device names.
Example: c1t0d0 becomes c6t20000004CF6F4E64d0.)
The postpatch script works as expected if you have standard short names.
To fix without using a bootblock recovery procedure
---------------------------------------------------
After applying the patch in single-user, you can run following command
on every disk boot devices listed by the postpatch script:
# /usr/sbin/installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk
/dev/rdsk/c6t20000014C35012F5d0s0
# /usr/sbin/installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk
/dev/rdsk/c6t20000004CF6F4E64d0s0
# reboot
Hope this helps.
Dominique
