We're updating our x86 systems to kernel patch 142901-05 to resolve a probe-based IP-multipathing issue. We successfully applied it to one x4200 system. However, applying the same patch to another similar machine resulted in failure, as well as on an x4240. All systems are at the same patch level, except for this kernel patch.
--- WARNING: The following files in / differ from the boot archive: The recommended action is to reboot to the failsafe archive to correct the above inconsistency. To accomplish this, on a GRUB-based platform, reboot and select the "Solaris failsafe" option from the boot menu. On an OBP-based platform, reboot then type "boot -F failsafe". Then follow the prompts to update the boot archive. Alternatively, to continue booting at your own risk, you may clear the service by running: "svcadm clear system/boot-archive" --- Note that no differing files are listed. No problem... reboot to failsafe, and run "bootadm update-archive", right? Unfortunately not; the subsequent reboot into multi-user results in the same message. Nor does "svcadm clear boot-archive"; multiple services fail to start, and many commands seg fault. We've tried installing in multiple ways, with no difference in outcome. * install from multi-user * init from multi-user to single-user and install * boot to single-user and install We can remove the patch from failsafe, and Solaris boots. The shutdown immediately after installing the patch results in: --- /var is a separate mount point and isn't found under /var/run/.patch_root_loopbackmnt/ making /var/tmp under /var/run/.patch_root_loopbackmnt/ Creating boot_archive for /var/run/.patch_root_loopbackmnt updating /var/run/.patch_root_loopbackmnt/platform/i86pc/boot_archive chksum: input file "/main-pool/boot/grub/menu.lst": No such file or directory bootadm: error generating checksum of GRUB menu --- Has anyone else successfully deployed 142901-05? Any ideas what we're doing wrong? Many thanks, --Scott Severtson
