On 11/03/2010 12:07, Rob McMahon wrote:
Thanks for the suggestions, but I think this is my own fault. I
think I've shot myself in the foot by enabling compression on rpool.
Replying to myself in case anyone else gets themselves in this position.
What worked for me was to burn a new 134
On 10/03/2010 19:40, alan pae wrote:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6932552
http://opensolaris.org/jive/thread.jspa?threadID=125486tstart=0
http://opensolaris.org/jive/thread.jspa?threadID=125445tstart=0
alan
Thanks for the suggestions, but I think this is my
Thanks for the suggestions, but I think this is my own fault. I think
I've shot myself in the foot by enabling compression on rpool.
So: `root (TAB'
gives you a nice clue about how to proceed, it says there's a ZFS
filesystem at partition 2.
`findroot (pool_rpool, 2, a)'
succeeds, and finds
I'm sure this should be a FAQ, but I'm having trouble finding the answer.
Yesterday I upgraded my laptop from 133 to 134. The upgrade went
without a hitch, and the fast reboot gave me a working system. I then
shut it down, feeling all confident, but now when I try to boot it I
just get to
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6932552
http://opensolaris.org/jive/thread.jspa?threadID=125486tstart=0
http://opensolaris.org/jive/thread.jspa?threadID=125445tstart=0
alan
--
This message posted from opensolaris.org
___
