All my pools get mount to /mnt/mnt after update from SCALE 24.04.1.1 to 24.04.2.2

TrueNAS General
, ,
1

I haven’t found anyone else running into this and I can’t quite find where this is configured. I can ‘revert’ back to 1.1 and it works fine.

Before update:
/mnt/default/
/mnt/temp/

After update:
/mnt/mnt/default/
/mnt/mnt/temp/

1 Like
2

zpool get altroot

3

Before update:
NAME PROPERTY VALUE SOURCE
boot-pool altroot - default
default altroot - default
temp altroot - default

After update:
NAME PROPERTY VALUE SOURCE
boot-pool altroot - default
default altroot /mnt local
temp altroot /mnt local

4

Ironically, it is the “After update” that shows the correct values.

TrueNAS intentionally imports your storage pools with -R /mnt

Not sure what explains the “double” /mnt/

5

I also don’t get where that ‘other’ /mnt is coming from and what changed between 04.01.xx and 04.02.xx… Don’t see anything in the release notes…

6

I was able to fix the issue by just leaving out the first “mnt” as such:

zfs set mountpoint=/poolname poolname

zfs list now returns the mountpoint as /mnt/poolname and the pool is shown correctly in the ui for example the share tab

Hope this helps (allthough I have no clue, why this is happening in the first place)

2 Likes
7

That worked for me too, but it’s not the correct way, because now the .ix directories are inaccessible.
It seems that the ALTROOT is the (root) cause of the problem: before it was set to ‘default’, now it’s set to ‘/mnt’. This appears to get added to the original mountpoint which is ‘/mnt’, so you end up with ‘/mnt/mnt’ and that is causing all the problems.
I will have a go and see if I can reset the ‘ALTROOT’ to ‘default’ and that should be the end of it.

Just for clarification: this happened to me when upgrading from 24.10.1 to 24.10.2

1 Like
8

So that IS the issue: the mountpoint of the pool is set to /mnt and the -R /mnt is added and results in /mnt/mnt/ as the mountpoint.
Probably a bug.

1 Like
9

Did you submit a Bug Report?

10

Found this in the OpenZFS documentation:
" altroot: Alternate root directory . If set, this directory is prepended to any mount points within the pool.
(Emphasis mine) This perfectly explains the odd behavior.
Question is, how to ‘undo’ this?