I tested a backup BE and the boot froze while looking for the NTP server. I checked the beadm man page and I had created the BE using the active BE as the source for the cloning. So I rebooted, selected the backup BE, jumped back to the first screen, selected 'boot single user' and it booted to the backup BE fine. But when I then tried to create another BE using 'beadm create -e' and the now-inactive good BE the cloning failed because ZFS couldn't read the something-or-other/entropy file.
I didn't see anything in the man page for switches not to include things so I'm at a loss here. Just grateful I found this now while the normal BE is fine. This is full disk encryption during initial install on a ZFS 2-disk mirror with a hot spare. How can I get around this?
thanks.
I didn't see anything in the man page for switches not to include things so I'm at a loss here. Just grateful I found this now while the normal BE is fine. This is full disk encryption during initial install on a ZFS 2-disk mirror with a hot spare. How can I get around this?
thanks.