Darren Reed wrote: > Now that those of us using Solaris/x86 have grub as our boot > manager, there's a new SMF thing - system/boot-archive. > > For a normal reboot/shutdown, this doesn't pose a problem. > > But if my system crashes (like it has been recently), on > reboot it stops with a message about clearing the state of > system/boot-archive. > > I'm also puzzled as to why it thinks this needs to be > rebuilt - since the last clean reboot, I've done nothing > to impact the local kernel files - well, nothing that > I'm aware of, unless compiling and reading email is > cause for reason here.
In addition to the static binaries from /kernel and /platform/i86pc/kernel there are some files in /etc that can change that are in the boot archive. /boot/solaris/filelist.ramdisk has the list of files that end up in the ramdisk. The /etc files are: etc/rtc_config etc/system etc/name_to_major etc/driver_aliases etc/name_to_sysnum etc/dacf.conf etc/driver_classes etc/path_to_inst etc/mach etc/devices/devid_cache etc/devices/mdi_scsi_vhci_cache etc/devices/mdi_ib_cache etc/cluster/nodeid I suspect it is probably either /etc/path_to_inst, because you have been hotplugging hardware. At least thats my experience with the boot archive getting out of date. The other possibility is that you actually have file system corruption in the crash and one of those /etc files is actually out of sync with the archive. -- Darren J Moffat
