How can I access a pool from freenas-boot after upgrade?

[NASbox]

I just did an upgrade from Freenas 11.3-U5 to Truenas 12.0-U5. I had a dataset freenas-boot/CUSTOM which I mounted as /CUSTOM under Freenas 11.3-U5.

After the upgrade if I attempt to access /CUSTOM from a root shell it appears as an empty directory, but before the upgrade it had many directories and files.

I know the data is stall there because when I attempt to list the dataset, I get the following:

Code:

# zfs list -t all -r freenas-boot/CUSTOM
NAME                                                       USED  AVAIL     REFER  MOUNTPOINT
freenas-boot/CUSTOM                                        170M  90.3G     81.7M  /CUSTOM
freenas-boot/CUSTOM@__MANUAL_PROTECT_2021-03-25_02.02.29    56K      -     81.7M  -
freenas-boot/CUSTOM@PREUPDATE                                8K      -     81.7M  -

I am assuming I need to do something to change the mount point, but I have no clue about how to do that. The complete listing seems to imply that it is correctly mounted. Any assistance is much appreciated.

Code:

NAME                                                                     USED  AVAIL     REFER  MOUNTPOINT
freenas-boot                                                            17.2G  90.3G      176K  none
freenas-boot/.system                                                     238M  90.3G     4.37M  legacy
freenas-boot/.system/configs-66c5ca0d9b594eb08a0e7191ec86e4a6            152M  90.3G      152M  legacy
freenas-boot/.system/configs-9d613bc4d69d4caa9ab03b2439285b53            136K  90.3G      136K  legacy
freenas-boot/.system/cores                                               136K  1024M      136K  legacy
freenas-boot/.system/rrd-66c5ca0d9b594eb08a0e7191ec86e4a6               56.5M  90.3G     56.5M  legacy
freenas-boot/.system/rrd-9d613bc4d69d4caa9ab03b2439285b53               3.85M  90.3G     3.85M  legacy
freenas-boot/.system/samba4                                             1.12M  90.3G      588K  legacy
freenas-boot/.system/samba4@update--2020-12-19-10-38--11.3-U4.1          360K      -      588K  -
freenas-boot/.system/samba4@update--2021-08-14-05-54--11.3-U5            168K      -      548K  -
freenas-boot/.system/services                                            144K  90.3G      144K  legacy
freenas-boot/.system/syslog-66c5ca0d9b594eb08a0e7191ec86e4a6            19.5M  90.3G     19.5M  legacy
freenas-boot/.system/syslog-9d613bc4d69d4caa9ab03b2439285b53             296K  90.3G      296K  legacy
freenas-boot/.system/webui                                               136K  90.3G      136K  legacy
freenas-boot/CUSTOM                                                      170M  90.3G     81.7M  /CUSTOM
freenas-boot/CUSTOM@PREUPDATE                                              8K      -     81.7M  -
freenas-boot/ROOT                                                       16.7G  90.3G      136K  none
freenas-boot/ROOT/11.0-U3                                                232K  90.3G      970M  /
freenas-boot/ROOT/11.0-U4                                                248K  90.3G      973M  /
freenas-boot/ROOT/11.1-RELEASE                                           424K  90.3G     1.08G  /
freenas-boot/ROOT/11.1-U4                                                452K  90.3G     1.09G  /
freenas-boot/ROOT/11.1-U5                                                452K  90.3G     1.10G  /
freenas-boot/ROOT/11.1-U6                                                572K  90.3G     1.10G  /
freenas-boot/ROOT/11.1-U6.3                                              440K  90.3G     1.04G  /
freenas-boot/ROOT/11.1-U7                                               9.32G  90.3G     1.07G  /
freenas-boot/ROOT/11.1-U7@2017-09-20-01:21:53                           4.05M      -      980M  -
freenas-boot/ROOT/11.1-U7@2017-09-19-23:36:41                           4.06M      -      980M  -
freenas-boot/ROOT/11.1-U7@2017-09-29-02:04:28                            969M      -      970M  -
freenas-boot/ROOT/11.1-U7@2017-12-15-20:16:16                            971M      -      973M  -
freenas-boot/ROOT/11.1-U7@2018-05-03-01:15:15                           1.08G      -     1.08G  -
freenas-boot/ROOT/11.1-U7@2018-06-18-15:51:46                           1.09G      -     1.09G  -
freenas-boot/ROOT/11.1-U7@2018-10-11-17:12:16                           1.09G      -     1.10G  -
freenas-boot/ROOT/11.1-U7@2019-01-16-03:04:16                           1.09G      -     1.10G  -
freenas-boot/ROOT/11.1-U7@2019-01-29-15:38:10                           1.04G      -     1.04G  -
freenas-boot/ROOT/11.2-U7                                                344K  90.3G     1.02G  /
freenas-boot/ROOT/11.2-U8                                                352K  90.3G     1.02G  /
freenas-boot/ROOT/11.3-U4.1                                              336K  90.3G     1.42G  /
freenas-boot/ROOT/11.3-U5                                                328K  90.3G     1.49G  /
freenas-boot/ROOT/FreeNAS-12.0-U5                                       7.40G  90.3G     1.62G  /
freenas-boot/ROOT/FreeNAS-12.0-U5@2019-11-28-16:20:43                   1017M      -     1018M  -
freenas-boot/ROOT/FreeNAS-12.0-U5@2020-04-09-04:04:54                   1.01G      -     1.02G  -
freenas-boot/ROOT/FreeNAS-12.0-U5@2020-09-15-02:17:11                   1.01G      -     1.02G  -
freenas-boot/ROOT/FreeNAS-12.0-U5@__MANUAL_PROTECT_2020-09-25_05.57.36  1.02M      -     1.42G  -
freenas-boot/ROOT/FreeNAS-12.0-U5@2020-12-19-05:37:00                   1.41M      -     1.42G  -
freenas-boot/ROOT/FreeNAS-12.0-U5@__MANUAL_PROTECT_2021-05-31_13.30.33  26.1M      -     1.46G  -
freenas-boot/ROOT/FreeNAS-12.0-U5@2021-08-14-01:52:46                   1.50M      -     1.49G  -
freenas-boot/ROOT/Initial-Install                                          8K  90.3G      980M  legacy
freenas-boot/ROOT/default                                                232K  90.3G      980M  legacy
freenas-boot/ROOT/default-20190917-081209                                360K  90.3G     1018M  legacy
freenas-boot/grub                                                       7.94M  90.3G     7.94M  legacy

 

[NugentS]

Did you hack the partitions on the boot media to allow you to store a dataset on the bootpool?

 

[NASbox]

Did you hack the partitions on the boot media to allow you to store a dataset on the bootpool?

Yes, I can't remember how long ago, but I created a CUSTOM data set that has all my maintenance scripts etc. Back in the day it was on a separate USB drive, but when I upgraded to an SSD, I put it on the boot drive (so that I would have access even if my storage pool was not mounted).

If I have to I can recreate it from a backup, but I'd like to figure out how to correct it properly because all the data is on the drive. It's just a matter of moving the dataset.

 

[Patrick M. Hausen]

So it's just a dataset and not a separate pool. It still exists and there seems to be 170M of data on it.
Could you show us the output of mount?

 

[NASbox]

DELETED - Original content repeated below with missing info included.

 

[Patrick M. Hausen]

I've included the relevant output from mount

So where is it?

 

[NASbox]

So it's just a dataset and not a separate pool. It still exists and there seems to be 170M of data on it.
Could you show us the output of mount?

Thanks for the reply @Patrick M. Hausen - Yes it is a dataset with no child datasets. I've included the relevant output from mount (I deleted many lines related to the main storage pool that are not relevant to the issue). Based on the output I'm having a hard time understanding what exactly is happening. In the past I've just recreated the dataset on top of each update (and I suspect there are a bunch of old copies in all the old snapshots, but I'd like to actually learn something so I know what I'm doing and fix this properly.

Code:

FN#>mount
freenas-boot/ROOT/FreeNAS-12.0-U5 on / (zfs, local, noatime, nfsv4acls)
devfs on /dev (devfs, local, multilabel)
tmpfs on /etc (tmpfs, local)
tmpfs on /mnt (tmpfs, local)
tmpfs on /var (tmpfs, local)
fdescfs on /dev/fd (fdescfs)
TANK on /mnt/TANK (zfs, local, noatime, nfsv4acls)
[Many Lines relating to TANK Deleted for Clarity]
freenas-boot/.system on /var/db/system (zfs, local, noatime, nfsv4acls)
freenas-boot/.system/cores on /var/db/system/cores (zfs, local, noatime, nfsv4acls)
freenas-boot/.system/samba4 on /var/db/system/samba4 (zfs, local, noatime, nfsv4acls)
freenas-boot/.system/syslog-66c5ca0d9b594eb08a0e7191ec86e4a6 on /var/db/system/syslog-66c5ca0d9b594eb08a0e7191ec86e4a6 (zfs, local, noatime, nfsv4acls)
freenas-boot/.system/rrd-66c5ca0d9b594eb08a0e7191ec86e4a6 on /var/db/system/rrd-66c5ca0d9b594eb08a0e7191ec86e4a6 (zfs, local, noatime, nfsv4acls)
freenas-boot/.system/configs-66c5ca0d9b594eb08a0e7191ec86e4a6 on /var/db/system/configs-66c5ca0d9b594eb08a0e7191ec86e4a6 (zfs, local, noatime, nfsv4acls)
freenas-boot/.system/webui on /var/db/system/webui (zfs, local, noatime, nfsv4acls)
freenas-boot/.system/services on /var/db/system/services (zfs, local, noatime, nfsv4acls)
devfs on /mnt/TANK/iocage/jails/syncthing/root/dev (devfs, local, multilabel)
fdescfs on /mnt/TANK/iocage/jails/syncthing/root/dev/fd (fdescfs)

Any assistance is much appreciated.

 

[Patrick M. Hausen]

So it is simply not mounted. That's why I asked.

zfs set mountpoint=/mnt/CUSTOM freenas-boot/CUSTOM
zfs mount freenas-boot/CUSTOM

should do the trick. If it does, then copy your data to a dataset on TANK and promise to never do it again.
The boot pool belongs to FreeNAS/TrueNAS. Don't mess with it.

 

[NASbox]

So it is simply not mounted. That's why I asked.

zfs set mountpoint=/mnt/CUSTOM freenas-boot/CUSTOM
zfs mount freenas-boot/CUSTOM

should do the trick. If it does, then copy your data to a dataset on TANK and promise to never do it again.
The boot pool belongs to FreeNAS/TrueNAS. Don't mess with it.

Thanks @Patrick M. Hausen that was it. I confused MOUNTPOINT in the dataset with actually being mounted.

I'm back in business. I actually mounted at / instead of /mnt since the contents of this pool are only for use by scripts that I run from the shell, and I want to make sure that I have access to this dataset if for some reason my pool is broken/unmounted. I don't want this area accessed by shares, and as much as possible I want to keep it separate from FreeNAS/TrueNAS. If you have a better suggestion as to how I can accomplish this, please let me know.

I think I've been doing it since about 11.0, and I either managed to figure it out myself (or more likely recreated it from scratch). I do regularly make a backup of this dataset to TANK, and I always do so before an upgrade. Thanks so much for making sure I didn't have to restore from it!