Hello all,

After having had "all the fun of the fair" with getting pkg image-update 
to successfully update my 2008.05 installation, I am now left with an 
unbootable "up"graded BE.

Basically what seems to be happening is that on reboot of the updated 
BE, it tries to load the root filesystem from /ramdisk:a and tells me 
that it is not a bootable device.

I looked through the code on cvs.opensolaris.org and thru kmdb, and as 
far as I can see, on 2008.05 and updated nv_90, rootfs.bo_fstype and 
bo_name both start off life as "ufs" and "/ramdisk:a" respectively. But 
when I successfully boot 2008.05, rootfs.bo_fstype becomes "zfs" and 
rootfs.bo_name becomes "root/RPOOL/opensolaris" as you would expect. 
However when I try to boot the updated nv_90, and am unceremoniously 
dumped into kmdb, my rootfs.bo_fstype is correctly set to "zfs", but my 
rootfs.bo_name is still at "/ramdisk:a"; which causes the panic. Looks 
like the latter is not being populated correctly, for some reason.

I guess that there may well be a straightforward answer to this, but I 
can't spot it yet; and similarly can't spot anything on 
defect.opensolaris.org.

This is a vanilla 2008.05 install (well, except for the endless faffing 
around with defective IPS) on a Fujitsu Siemens Amilo pi2515 running 
2008.05 in a VirtualBox 1.6.0 machine. I doubt that any of these facts 
will be of significance though.

Any thoughts/help gratefully received.

Thanks and regards... Sean.


Reply via email to