Unable to mount zfs pool [resolved]

Support
1

Hey folks, I have a NVME from another system that I’m trying to mount up via external usb connection and its giving me this error…
“Error mounting /dev/sdc2 at /run/media/jason/boot-pool: Filesystem type zfs_member not configured in kernel.”

[optiplex5260 ~]# uname -a 
Linux optiplex5260 5.15.89-1-MANJARO #1 SMP PREEMPT Wed Jan 18 20:37:11 UTC 2023 x86_64 GNU/Linux

[optiplex5260 ~]# pacman -Qe | grep zfs
linux515-zfs 2.1.7-9
zfs-dkms 2.1.7-1
zfs-utils 2.1.7-1
[optiplex5260 ~]# 

[optiplex5260 ~]# lsmod | grep zfs
zfs                  4014080  0
zunicode              335872  1 zfs
zzstd                 585728  1 zfs
zlua                  192512  1 zfs
zavl                   16384  1 zfs
icp                   323584  1 zfs
zcommon               106496  2 zfs,icp
znvpair               114688  2 zfs,zcommon
spl                   118784  6 zfs,icp,zzstd,znvpair,zcommon,zavl
[optiplex5260 ~]#

[optiplex5260 ~]# zpool import  boot-pool
[optiplex5260 ~]# zpool list
NAME        SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
boot-pool  95.5G  1.16G  94.3G        -     15.5G     0%     1%  1.00x    ONLINE  -
[optiplex5260 ~]# zfs list
NAME                                                         USED  AVAIL     REFER  MOUNTPOINT
boot-pool                                                   1.16G  91.4G       24K  /mnt/zfs
boot-pool/.system                                           1.52M  91.4G       26K  legacy
boot-pool/.system/configs-7bdf26d378f44463a02df9c5bc4d0ea3    24K  91.4G       24K  legacy
boot-pool/.system/cores                                       24K  1024M       24K  legacy
boot-pool/.system/rrd-7bdf26d378f44463a02df9c5bc4d0ea3      1.28M  91.4G     1.28M  legacy
boot-pool/.system/samba4                                      45K  91.4G       45K  legacy
boot-pool/.system/services                                    24K  91.4G       24K  legacy
boot-pool/.system/syslog-7bdf26d378f44463a02df9c5bc4d0ea3     83K  91.4G       83K  legacy
boot-pool/.system/webui                                       24K  91.4G       24K  legacy
boot-pool/ROOT                                              1.16G  91.4G       24K  /mnt/zfs/ROOT
boot-pool/ROOT/Initial-Install                                 1K  91.4G     1.16G  legacy
boot-pool/ROOT/default                                      1.16G  91.4G     1.16G  legacy
[optiplex5260 ~]#

I believe I have all the right things loaded to support ZFS. Any suggestions on how to get this mounted correctly?

-db

2

I see the output of zfs list showed ok.

What is the output:

$ zfs get canmount boot-pool
$ zfs get mountpoint boot-pool
$ zfs get mounted boot-pool

You do not need to install linux515-zfs, because zfs-dkms and zfs-utils were installed.

3

thanks for taking the time to respond Zesko,

[optiplex5260 Downloads]# zfs get canmount boot-pool
NAME       PROPERTY  VALUE     SOURCE
boot-pool  canmount  off       local
[optiplex5260 Downloads]# zfs get mountpoint  boot-pool
NAME       PROPERTY    VALUE       SOURCE
boot-pool  mountpoint  /mnt/zfs    local
[optiplex5260 Downloads]# zfs get mounted  boot-pool
NAME       PROPERTY  VALUE    SOURCE
boot-pool  mounted   no       -
[optiplex5260 Downloads]#
4

That looks like the same issue.

Maybe the zfs 2.1.7 and other zfs legacy version from the other system are incompatible.

You can ask @dalto or @mbod in EOS forum if they can help.

Edit:

Did you take this NVME out of the other system’s RAID, but its old ZFS configuration would not match non-RAID on your system when mounted? I guess this NVME is part of “zfs_member” (RAID)

5

You are using a kernel with zfs modules and then loading zfs-dkms on top of that. I would try removing zfs-dkms

6

so I removed that dmks package, set the pool as mountable and rebooted and now it seems like it mounts

zfs get mounted  boot-pool
NAME       PROPERTY  VALUE    SOURCE
boot-pool  mounted   yes      -
[optiplex5260 ~]# df -h | grep zfs
boot-pool        92G  128K   92G   1% /mnt/zfs
[optiplex5260 ~]# ls /mnt/zfs/
[optiplex5260 ~]#

but there is nothing under that mount point?

i see this as well

[optiplex5260 ~]# zfs list 
NAME                                                         USED  AVAIL     REFER  MOUNTPOINT
boot-pool                                                   1.16G  91.4G       24K  /mnt/zfs
boot-pool/.system                                           1.52M  91.4G       26K  legacy
boot-pool/.system/configs-7bdf26d378f44463a02df9c5bc4d0ea3    24K  91.4G       24K  legacy
boot-pool/.system/cores                                       24K  1024M       24K  legacy
boot-pool/.system/rrd-7bdf26d378f44463a02df9c5bc4d0ea3      1.28M  91.4G     1.28M  legacy
boot-pool/.system/samba4                                      45K  91.4G       45K  legacy
boot-pool/.system/services                                    24K  91.4G       24K  legacy
boot-pool/.system/syslog-7bdf26d378f44463a02df9c5bc4d0ea3     83K  91.4G       83K  legacy
boot-pool/.system/webui                                       24K  91.4G       24K  legacy
boot-pool/ROOT                                              1.16G  91.4G       24K  /mnt/zfs/ROOT
boot-pool/ROOT/Initial-Install                                 1K  91.4G     1.16G  legacy
boot-pool/ROOT/default                                      1.16G  91.4G     1.16G  legacy

and maybe the data Im looking for is in boot-pool/ROOT ?
I was able to get that mounted as well.

[optiplex5260 ROOT]# df -h | grep zfs
boot-pool        92G  128K   92G   1% /mnt/zfs
boot-pool/ROOT   92G  128K   92G   1% /mnt/zfs/ROOT

but there is still nothing under that mount ?

[optiplex5260 ROOT]# ls -al /mnt/zfs/ROOT/
total 1
drwxr-xr-x 2 root root 2 Mar 26 2021 .
drwxr-xr-x 3 root root 3 Feb 4 09:10 …
[optiplex5260 ROOT]#


how can I get to the old filesystems on this nvme?

-db
7

Check if your data is in the dataset boot-pool/ROOT/default

8

it was! thanks!

as a side note… I was trying to recover an nvme that I used to have in my desktop that wouldnt boot anymore… I mounted up this nvme thinking it was my previous Linux install, but it turns out it was a freebsd install after I looked at the filesystems!