On Tue, 2010-05-04 at 11:18 -0500, Shawn Walker wrote: > >> How are you booting the > >> system? (rEFIt?) > > > > No, I just installed OpenSolaris. > > Ah, only OS then?
Yes. > > ... > >> Only bug I see possibly related is 6929493 (in the sense that changes > >> for the bug may have triggered this issue possibly). > > > > A few days ago I noticed that the new boot environment is actually there > > and can be booted despite the ZFS error. I installed b138 today and it > > works, but I get this error on updating. > > So, there are some ZFS bugs that seem related, although some of them are > supposedly already fixed and I'm not certain that others relate: > > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6740164 > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6860320 > > Did you recently attach or import any zpools? I don't think so. The only thing I did was: http://mail.opensolaris.org/pipermail/laptop-discuss/2009-November/008131.html But I did that around 132 or 133 and at least I did one image-update after that, which worked. > > Also, when you originally installed the OS, did you completely erase the > drive before installing? I can't remember, but I guess no. > > I've run into problems in the past where fixes or changes have caused > the OS to check partition headers and other areas for signatures that > were leftover by other disk utilities and gave me grief. > > So, to be clear, sometime after you updated to b134, you could no longer > update to any other builds because it gave you a message like this? > > be_get_uuid: failed to get uuid property from BE root dataset user > ... > set_bootfs: failed to set bootfs property for pool rpool: property > 'bootfs' not supported on EFI labeled devices > be_activate: failed to set bootfs pool property for > rpool/ROOT/opensolaris-135 Exactly. -- Christian _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
