Datasets not mounting after reboot

When I boot my system, I need to issue afterwards a

zfs mount -a

Or else my datasets aren’t mounted. When I issue that command, there’s no error message, and all pools show no errors.

Note: I’m currently playing with the nightlies, but that used to work before (until reformatted the disks for a different layout), and it doesn’t look like standard behavior of mounting datasets upon book is a major construction site.

Any ideas? I mean, I could make a boot-time script, but given the appliance nature of TrueNAS that shouldn’t be required

I would try to export and reimport the pool from the UI first.

I kind of was hoping to avoid that, since it’s the system pool and its children (just one pool here, with various datasets).

I fear that will kill a variety of things I set up, like automatic snapshots etc. Or will these be retained?

What do you mean by system pool? There are

  • the boot pool
  • the storage pool with the system dataset

Regularly all your settings will be retained. You need to stop all services like SMB using datasets on that pool, first, though.

Nightlies are bleeding-edge. We’re changing a lot of under the hood ZFS stuff. If you encounter a bug then file bug reports (that’s how we get value out of people running nighties). Just make sure to provide enough information for it to be an actionable bug report.

The storage pool with the system dataset. The boot pool is on an 256GB eMMC stuck in an internal USB3.2 port…

So, all settings, like snapshot schedules, mounts, etc. are retained? OK, will try later. :crossed_fingers:

Well, I tried: no luck