Sowmini.Varadhan at Sun.COM wrote: >> hg pull >> setup setenv.sh >> ran nightly setenv.sh >> made copy of existing b81 / into new fs, mounted as /a >> bfu /path/to/archives /a
Did you run acr to make sure the name_to_major file gets its conflicts resolved properly? >> bootadm update-archive -R /a >> umount /a >> edit grub >> reboot >> >> I glanced through the files that it complained as having a conflict >> due to local modifications), but nothing stood out (it was stuff like >> me setting 2a as the the default crypt algo, etc). Might there be >> specific files that could be related to a postattach failure I should >> examine in closer detail (just to cover all bases). You should never have to look at the conflicts if you run the "acr" command. If you're bfu'ing an alternate root, "acr /a" from the bfu prompt should have done the trick. Also, you don't need to run bootadm update-archive by hand, bfu does that for you. My hunch is that a major number is out of whack or missing. Are there any messages on the console regarding why the postattach failed? -Seb
