My only guess is the existing boot archives are invalid. dmesg while running update-archive should confirm this.
To replace them, try bootadm update-archive -f -Albert On Thu, Mar 10, 2011 at 5:39 PM, Didier Carlier <did...@lafalise.org> wrote: > Yes I can, I tried the upgrade several times and each time with the same the > result. > At first I thought it was the upgrade to OpenIndiana which was the problem > but no, the problem is with the upgrade to svn_134, or more exactly the "init > 6" of svn_134. > > Didier > > > =On 10 Mar 2011, at 23:09, Roy Sigurd Karlsbakk wrote: > >>> Any hint greatly appreciated... >> >> Can you reboot into the old BE? If so, retry. If not, something bad is >> happening... >> >> Vennlige hilsener / Best regards >> >> roy >> -- >> Roy Sigurd Karlsbakk >> (+47) 97542685 >> r...@karlsbakk.net >> http://blogg.karlsbakk.net/ >> -- >> I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det >> er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av >> idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate >> og relevante synonymer på norsk. >> >> _______________________________________________ >> OpenIndiana-discuss mailing list >> OpenIndiana-discuss@openindiana.org >> http://openindiana.org/mailman/listinfo/openindiana-discuss > > > _______________________________________________ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > _______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
