>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.
Yes, that happens. >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. Have you plugged in USB devices? Did the timezone change in the mean time? >My concern here is that we've needlessly added something >to our bootup that prevents the system from cleanly >reboot'ing after a panic. I'm at a loss as to whether >this is actually a bug/regression and if so, is it a >newboot or SMF one? > >Or is this just part of the newboot experience? It's a newboot thing but it's being worked; for critical systems, you should set the start method of boot-archove to ":true" Casper
