#1152 closed System Defect (fixed)

internal error: failed to initialize ZFS library

Reported by: q/pa Owned by:
Priority: critical Milestone:
Component: System Configuration Version: 10.0-RELEASE
Keywords: ZFS, BE, snapshot Cc: trac-bugs@…



When trying to boot another BE snapshot from the GRUB menu than the one set as default I get the message

mounting local file systems:
internal error: failed to initialize ZFS library

I had no problems to boot older BE snapshots until today but I did not alter any settings. Can this be related to the fact that I mixed the use of the CLI beadm commands and the GUI Boot Manager in the past? Can a BE show up damaged after a few days and function normally before? See also https://trac.pcbsd.org/ticket/1138, where I describe the GUI showing the wrong BE as the default one.

The actual BE I am using right now was created with the GUI. I hope this one does not break to soon so that I might be of help with additional information.

The PCBSD Disk Manager also does not work anymore. Although I do not know whether this is related to the new Control Panel or a broken GRUB (or whatever got broken).

Change History (1)

comment:1 Changed 14 months ago by kris

  • Resolution set to fixed
  • Status changed from new to closed

We put some fixes into creating / destroying BE's in the past few days. I'm not sure why this is broken, but it sounds like its not specifically a BE create / delete issue, rather that the BE you are using got its FreeBSD world horked up somehow...

If you can duplicate please let us know.

Note: See TracTickets for help on using tickets.