On Tue, 2010-05-04 at 10:36 -0500, Shawn Walker wrote:
> > What confuses me is that the update from b133 to b134 obviously worked
> > before--because I have a b134 image--but it doesn't now.
> 
> I'm on b135 myself and haven't seen this issue yet.
> 
> > I can't think of anything I did that changed anything on the disk or the
> > partition table, whatever that could be.  Or is this because I tried to
> > install b137 and that changed something?
> 
> What does your partition layout look like?  

Not sure how I can print the partition to show what you want to see.
Maybe this:

format> current
Current Disk = c12t0d0
<DEFAULT cyl 38910 alt 2 hd 255 sec 63>
/p...@0,0/pci10de,c...@b/d...@0,0

format> verify

Primary label contents:

Volume name = <        >
ascii name  = <DEFAULT cyl 38910 alt 2 hd 255 sec 63>
pcyl        = 38912
ncyl        = 38910
acyl        =    2
bcyl        =    0
nhead       =  255
nsect       =   63
Part      Tag    Flag     Cylinders         Size            Blocks
  0       root    wm       1 - 38909      298.06GB    (38909/0/0) 625073085
  1 unassigned    wm       0                0         (0/0/0)             0
  2     backup    wu       0 - 38909      298.07GB    (38910/0/0) 625089150
  3 unassigned    wm       0                0         (0/0/0)             0
  4 unassigned    wm       0                0         (0/0/0)             0
  5 unassigned    wm       0                0         (0/0/0)             0
  6 unassigned    wm       0                0         (0/0/0)             0
  7 unassigned    wm       0                0         (0/0/0)             0
  8       boot    wu       0 -     0        7.84MB    (1/0/0)         16065
  9 unassigned    wm       0                0         (0/0/0)             0

format> 

> How are you booting the 
> system? (rEFIt?)

No, I just installed OpenSolaris.

> 
> 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.

-- Christian

_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

Reply via email to