lsdev
command? Does that show anything? # gpart show
or # zpool import
?Shouldn't be much of an issue, but then again I'm not well experienced with UEFI.
But when you said it doesn't boot, what exactly does or doesn't happen? I mean, do you get the boot menu at all? If so; what happens if you hit escape (to get the ok> prompt) and then issue thelsdev
command? Does that show anything?
I'm not much of a fan of the memstick environment (because it provides few tools to work with) but if you boot using a rescue environment (my choice would be the disc1 ISO image) then what happens if you run# gpart show
or# zpool import
?
If those last 2 commands actually show reasonable output then this situation might be easily solvable by editing loader.conf again.
gpart show
shows reasonable output. zpool import
outputs no pools available to import
. zpool list
shows HEALTH->UNAVAIL for both bootpool and zroot zpool
commands work. [I]no ZFS pools[/I]
. zpool status
says status: [I]One or more devices could not be opened. There are insufficient replicas for the pools to continue functioning.[/I]
action: [I]Attach the missing device and online it using 'zpool online'[/I]
NAME STATE READ WRITE CKSUM
bootpool UNAVAIL 0 0 0
12798312938724987234 UNAVAIL 0 0 0 was /dev/ada0p2
I'm not much of a fan of the memstick environment (because it provides few tools to work with) but if you boot using a rescue environment (my choice would be the disc1 ISO image)
SHELL
and Live CD
, as far as rescue options go?Not that much, it mostly boils down to having more tools and information (manual pages) at your disposal. So if you're doing a rescue operation you'll also have full network support at your disposal.By the way, what is the difference between choosing aSHELL
andLive CD
, as far as rescue options go?
So it stopped working after you changed something in loader.conf? What did you change?
Unfortunately no. My problem is that I have very little experience with UEFI and from what I do know that setup also provides the whole BIOS for a PC. Which makes it hard to determine a cause. I could imagine this caused by either a mismatched or not working drivers, or something more drastic such as a possible pool corruption.Thanks for the answers, appreciate it. Trying to learn ZFS. Any on-topic advice? I would like to try any approach, and get to the bottom of this problem, short of re-installing the system.
Please explain what you have been doing about encryption. Your comments sound like the harddisk itself is encrypted (that exists, they're called SED or self-encrypting drives), and the harddisk needs to be unlocked. You'll need to tell us what is going on.The other thinking path is: do I need both BIOS encrpytion and geli encryption? Do they collide? How does ZFS behave if you start a live memstick without unlocking the hard disk?
ada0
1 EFI 200M
- free 1M
2 freebsd-zfs 2G
3 freebsd-swap 6G
4 freebsd-zfs the rest of G's
- free 4K (the bsdinstall option 4K per sector was selected)
gpart
to show the partition table on your disk. If that works, and gives reasonable answers, then the BIOS hardware encryption has been correctly unlocked. Next step: Find the partition that is supposed to be the ZFS volume in the gpart
output, and run the command zdb -l
on it (example: "zdb -l /dev/adaXpY", for suitable values of X and Y, probably ada0p2 judging from your old ). That should show that this partition contains a ZFS volume, and will tell you many details about it. If that completely fails, then perhaps the partition or disk is still encrypted. Here is for fun the start of the zdb
output for one of my partitions, to give you a flavor (it goes on for >100 lines):# zdb -l /dev/ada3p9
--------------------------------------------
LABEL 0
--------------------------------------------
version: 5000
name: 'macbackup'
state: 0
txg: 6035078
pool_guid: 8337558203742914770
hostid: 4194647577
hostname: 'house.lr.los-gatos.ca.us'
top_guid: 16009679047817592512
guid: 16009679047817592512
vdev_children: 1
vdev_tree:
type: 'disk'
id: 0
guid: 16009679047817592512
path: '/dev/gpt/hd16_macbackup'
...