TrueNAS Scale: Stuck on boot for 15min exception in import_on_boot

We cannot reproduce this and cannot sink more time into investigating what may possibly be related to this unsupported configuration you have created.

Hello @Kenan Isgör,

There seems to be a misconfiguration in the boot device setup. By default, the system dataset is located in the boot pool but it can be moved to a storage pool (different disk) if configured. But the attached logs show that the system dataset is on a separate pool but somehow it is residing on the same disk with the boot pool, which indicates that SCALE is installed on a partitioned disk or there might be some custom configuration. The SCALE needs to own the whole boot disk to operate correctly.

Moreover, I have tested the a scenario by creating a docker application from scratch on one storage pool and reboot worked just fine after its replication to another storage pool.

Hi there,

just reproduced the problem again (timeout ZFS import @boot).

System: 22.02-RELEASE

Changed and tested:

• Unset pool for ix-applications

• Completely deleted ix-applications dataset inkl. snapshots

• Replication of system dataset completely removed from backup dataset

• Set pool for ix-applications again to dataset system and installed docker applications from scratch (Observation: before, ix-application had sub-datasets for each subdirectory except "backup" directory, now it is only one dataset "ix-applications", but after replication of system dataset to backup dataset there are different snapshots per subdirectory again, e.g. "backup/snapshots/system/ix-applications/docker@auto-xx, ...ix-applications/release@auto-xx, etc.)

• Done again replication of system dataset incl. ix-applications dataset to backup dataset

• Reboot timed out at import of ZFS pools

• Debug saved and attached in private section

No timeout occurs when replication of system dataset is destroyed in backup dataset (as before).

Please advise if you need another session. Thanks!

... and also the replication of system/ix-applications/docker is the problem. if deleted the boot runs through fine.

Issue persists also in RELEASE version