Have to export/import pool each reboot

Hello, I’m new to TrueNAS so forgive my ignorance if I don’t explain my problem well or if its supposed to work like this. My problem is that each time I reboot I need to export and then import my two pools. Both are offline on boot. I also need to then unlock the encrypted datasets but maybe that is another problem.

My questions are therefore:

  1. Is it normal that a pool in a mirrored set up needs to be exported and imported after each boot?
  2. Is there anything I can do about it?

My set up is:

OS Version:TrueNAS-SCALE-24.10.0 (upgraded from RC2)
Product:H170N-WIFI
Model:Intel(R) Core™ i5-6500T CPU @ 2.50GHz
Memory:16 GiB

Running on bare metal. Two pools:
Data VDEVs 1 x MIRROR | 2 wide | 9.1 TiB
Data VDEVs 1 x DISK | 1 wide | 931.51 GiB

No failed SMART tests on either.

Let me know if there are things I can try or share to help diagnose the issue.

On boot the pools are offline and I can’t import anything, the dropdown is empty:

Once I’ve exported the pool I can then import it and the dropdown is populated:

Screenshot 2024-11-06 142000

This next screenshot was taken after boot and before I added the extra drive and pool but you can see the Main pool has a guid (I problem I read about elsewhere):

If there is anything else that would help let me know and I’ll try it.

I recommend you post a bug report on this.
Also, update to 24.10.0.2.

2 Likes

I had a problem with similar. I created a pool and truenas woudn’t import it on the next boot. Even though everything works fine when “manually” importing it.

Here is what I noticed, maybe you have the same issue:

There is a error message in /var/log/middlewared.log:

[2024/11/08 21:29:25] (ERROR) PoolService.import_on_boot_impl():304 - Failed to import 'app' with guid: '7554823053285154468' with error: "cannot import '7554823053285154468': no such pool available\n"

The pool guid is correct, but zfs reports “no such pool available”.

Indeed in my case the pool was not listed when using “zpool import” on the commandline - it was however available for import using the GUI.

Using zfs import -d /dev/sda1 correctly shows the pool, so the issue seems to be with discovery of the pool. According to the documentation (man zpool-import) it uses libblkid for discovery.

Indeed, using the program blkid did not list the partition containing the pool. On my other truenas installation which doesn’t have any problems blkid will display things like partition label / guid / etc. Also the symlinks in in /etc/disk/by-partuuid were completely missing.

My suspicion was that the partition table (GPT) was wrong, maybe missing some attributes which causes it to not be properly discovered.

I went with the nuclear option and recreated the pool. No more issues after that.

Unless someone with this (or these) issue(s) posts a bug report, the chances of getting this fixed are slim at best.

1 Like

Thanks both. Another person with the same problem has logged this Jira ticket: TrueNAS - Issues - iXsystems TrueNAS Jira

I’ve uploaded a debug report so hopefully it can get fixed.