Bill Shannon writes: > I saw another message about the "bootadm update-archive" command and > thought maybe that might be related. Can someone explain how that > command relates to boot environments?
It doesn't really relate to them. The archive is part of the GRUB booting process. GRUB is able to load an image of the system and start it running. That image contains a subset of the kernel components needed to get the file systems up and running so that we can read the rest of everything off of disk (or network or whereever the root file system actually comes from). Because it contains copies of some of the kernel parts, it needs to be kept in sync as the kernel itself is modified by upgrade and the like. Running "bootadm update-archive" (which is automatically invoked on certain commands, such as "reboot") causes the system to check the archive and regenerate it if any of the components have changed on disk. > I'm running in an old boot environment. (My newer boot environments > fail to boot, as described above.) Here's what I get: [...] > $ pfexec /usr/sbin/bootadm update-archive -vn > cannot find: /etc/cluster/nodeid: No such file or directory > changed /etc/devices/devid_cache That means that a new archive should be created. > Do any of those errors suggest a real problem? The errors it produces are meaningless. They relate to odd files that would be in the archive if present, but that aren't needed. > If I do the update-archive while running in this old boot environment, > what effect might it have on the ability of newer boot environments to > boot properly? None at all. Each boot environment has its own archive. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
