I guess that is what is done during the shutdown ?
The symptom is the same :
bootadm update-archive -f
updating /platform/i86pc/amd64/boot_archive
updating /platform/i86pc/boot_archive
mount: /dev/lofi/2 is not this fstype
mount: /dev/lofi/1 is not this fstype
umount: warning: /tmp/create_ramdisk
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 wrote:
> Yes I can, I tried the upgrade several times and each time with the sa
I've upgraded a few boxes from earlier versions myself without too much issues,
so really, I don't know what may be causing this. Will a reinstall of the rpool
make a big problem?
roy
- Original Message -
> Yes I can, I tried the upgrade several times and each time with the
> same the r
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 Si
> 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 presen
