Solved ZFS/GELI Reboot Failure

spmzt

spmzt

Hi,
In a fresh installed FreeBSD 13 with ZFS/GELI, When I reboot or power on the system, I get the following error after entering the storage password.
Code: 
GELI Passphrase for disk0p4:

Calculating GELI Decryption Key for disk0p4: 2224665 iterations...
....
zio_read error: 45
zio_read error: 45
zio_read error: 45
zio_read error: 45
...
ZFS: i/o error - all block copies unavailable
zio_read error: 45
ZFS: i/o error - all block copies unavailable
ERROR: error loading module 'config' from file ''/boot/lua/config.lua':
E        /boot/lua/config.lua:1: malformed number near '8q'.
E
E
Type '?'...
OK
But when I specifically choose the boot option from the UEFI, it turns on without any problems.
Any idea?
 
After a successful boot:

efibootmgr -v
zpool status
geom part show
freebsd-version -kru
uname -aKU

Please share the outputs from those commands.

Can you describe the hardware?

Hard disk drive? And so on. Thanks.
 
grahamperrin said:
After a successful boot:

efibootmgr -v
zpool status
geom part show
freebsd-version -kru
uname -aKU

Please share the outputs from those commands.

Can you describe the hardware?

Hard disk drive? And so on. Thanks.
Click to expand...
Code: 
~# efibootmgr -v                                                                                                                                                                                                   1 ↵ 
Boot to FW : false
BootCurrent: 0010
Timeout    : 0 seconds
BootOrder  : 0010, 000B, 000F, 0013, 000E, 000A, 000C, 0014, 0000, 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008, 0009, 0011, 000D
+Boot0010* FreeBSD HD(1,GPT,becdd594-67d2-11ec-9fef-dc4a3e6975b1,0x28,0x82000)/File(\efi\freebsd\loader.efi)
                      ada0p1:/efi/freebsd/loader.efi /boot/efi//efi/freebsd/loader.efi
 Boot000B* Generic USB3.0-CRW 29203008282014000 PciRoot(0x0)/Pci(0x14,0x0)/USB(0x17,0x0)
 Boot000F* hp DVDRW DU8A6SH  PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x2,0x0,0x0)
 Boot0013* ST500DM002-1BD142  PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x1,0x0,0x0)
 Boot000E* HUAWEI :  BBS(CDROM,HUAWEI : ,0x500)/PciRoot(0x0)/Pci(0x14,0x0)
 Boot000A* hp DVDRW DU8A6SH :  BBS(CDROM,hp DVDRW DU8A6SH : ,0x400)/PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x2,0x0,0x0)
 Boot000C* CT240BX500SSD1 :  BBS(HD,CT240BX500SSD1 : ,0x400)/PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x0,0x0,0x0)
 Boot0014* ST500DM002-1BD142 :  BBS(HD,ST500DM002-1BD142 : ,0x400)/PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x1,0x0,0x0)
 Boot0000  Startup Menu Fv(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)
 Boot0001  System Information Fv(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)
 Boot0002  Bios Setup Fv(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)
 Boot0003  3rd Party Option ROM Management Fv(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)
 Boot0004  System Diagnostics Fv(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)
 Boot0005  System Diagnostics Fv(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)
 Boot0006  System Diagnostics Fv(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)
 Boot0007  System Diagnostics Fv(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)
 Boot0008  Boot Menu Fv(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)
 Boot0009  HP Recovery Fv(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)
 Boot0011  Network Boot Fv(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)
 Boot000D  HUAWEI PciRoot(0x0)/Pci(0x14,0x0)/USB(0xa,0x1)

# zpool status
  pool: zroot
 state: ONLINE
config:

        NAME          STATE     READ WRITE CKSUM
        zroot         ONLINE       0     0     0
          ada0p4.eli  ONLINE       0     0     0
          ada1p4.eli  ONLINE       0     0     0

# geom part show
=>       40  468862048  ada0  GPT  (224G)
         40     532480     1  efi  (260M)
     532520       1024     2  freebsd-boot  (512K)
     533544        984        - free -  (492K)
     534528    4194304     3  freebsd-swap  (2.0G)
    4728832  464132096     4  freebsd-zfs  (221G)
  468860928       1160        - free -  (580K)

=>       40  976773088  ada1  GPT  (466G)
         40     532480     1  efi  (260M)
     532520       1024     2  freebsd-boot  (512K)
     533544        984        - free -  (492K)
     534528    4194304     3  freebsd-swap  (2.0G)
    4728832  972044288     4  freebsd-zfs  (464G)
  976773120          8        - free -  (4.0K)

# freebsd-version -kru
13.0-RELEASE
13.0-RELEASE
13.0-RELEASE

# uname -aKU
FreeBSD hostname 13.0-RELEASE FreeBSD 13.0-RELEASE #0 releng/13.0-n244733-ea31abc261f: Fri Apr  9 02:00:00 UTC 2021     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64 1300139 1300139
 
Is that two separate installations of FreeBSD (one per disk), both encrypted but with different encryption keys?

Code: 
# freebsd-version -kru
13.0-RELEASE
13.0-RELEASE
13.0-RELEASE
Click to expand...

Outdated, so (when you can) update the system. I don't expect it to resolve the boot issue; just standard advice.
 
grahamperrin said:
Is that two separate installations of FreeBSD (one per disk), both encrypted but with different encryption keys?



Outdated, so (when you can) update the system. I don't expect it to resolve the boot issue; just standard advice.
Click to expand...
No. During installation (bsdinstall), I just added my two drives as stripe to zfs and enabled encryption.
 
Can you share the diskinfo ada0 ? My first assumption would be you've native 4k sector on those disks; you can't legacy boot from those disks.
 
_martin said:
Can you share the diskinfo ada0 ? My first assumption would be you've native 4k sector on those disks; you can't legacy boot from those disks.
Click to expand...
# diskinfo ada0 ada1
ada0 512 240057409536 468862128 0 0 465141 16 63
ada1 512 500107862016 976773168 4096 0 969021 16 63
 
It's not it then, sector size is reported as 512 (the ada1 is 512e).
I first thought you have those disks in mirror. It took me few times to read the output to see you're concating them together. Is this desired ?

Anyway I tried this in my VM. If I had only a small 20G disk all was ok. When I concated 1TB disk to it I got these errors. As if 1TB was just too much for it to handle.
 
You must log in or register to reply here.
Back
Top