Imported pool mounting in wrong location after upgrade (/mnt/mnt/spinpool)

TrueNAS General
,
1

When I installed 25.04.2.3 (my first ever install) I noticed that the pool I imported was mounted as /mnt/mnt/spinpool. I followed another post in these forums to fix that and it worked nicely across reboots. (properly mounting at /mnt/spinpool)

But after the upgrade to 25.04.2.4 the pool was again mounted at /mnt/mnt/spinpool instead of /mnt/spinpool.
I had to manually fix that again.

Is that expected? A bug? Some lingering config somewhere?
An how can I fix that?

P.S.: The post I followed to fix it initially was this one: Mountpoint /mnt/mnt/pool after import

1 Like
2

Thanks for starting the thread.

Can you describe your pool and datasets.

Are you sharing the pool directly… or a dataset?

3

The pool was created on FreeBSD 14.2 and then exported/imported into TrueNAS.

image
image997Ă—480 16.7 KB

Only a couple of the datasets are used by Samba (a home-share for various users, and a media share)

4

That was unfortunately bad advice.
The right way to manually import would have been to use the -R /mnt flag.

I am not sure what the best path out of the improper mount hole you’ve ended up in is.

5

well… since I’ve done the export/import dance twice now…
maybe I should do it a third time, but this time with the -R /mnt flag?

6

Hmm… spinpool comes from a FreeBSD manual setup, so I really don’t care about its name and I just have 2 samba shares at the moment that I can easily set up again. No apps yet or any other special things (I’m new to TrueNAS).

Assumption: On the FreeBSD system the mountpoint for spinpool was originally… /mnt/spinpool so that might have caused TrueNAS UI to get confused at import (which was done from the UI).

After reading up a bit, here’s my current thinking for a recovery strategy:

  1. export spinpool from the TrueNAS UI
    This should cleanly disconnect it.

  2. Then from the command line, as root:
    mkdir /someplace
    zpool import -R /someplace spinpool newpool
    zfs set mountpoint=/someplace newpool
    zfs destroy -r newpool/ix-apps
    zfs destroy -r newpool/.ix-virt
    zpool export newpool

  3. after checking newpool is no longer mounted, for good measure: rm -rf /someplace

  4. I should now have a clean newpool with all data intact
    (assumption/hope :wink: )

  5. Now import newpool from the UI which should take care of a clean import

How does that sound?

7

It makes sense at the zfs level.

At the TrueNAS level it is uncharted and untested territory…

The TrueNAS configuration database will not accurately reflect the status of the zpool. Its hard to predict the behavior.

So it might be better to do a fresh install of TrueNAS and then import the pool…

1 Like