Pool.dataset.sync_db_keys || failed to create mountpoint: Read-only file system Import was successful, but unable to mount some datasets#

TrueNAS General
,
1

Everything was working correctly, it was a reboot, it took a long time, I saw the log and they crossed it out! This error appears, leaving the system completely useless when it starts, luckily I had a backup of the configuration from two days ago and I will try to reinstall the system

Any other suggestions?

image

20240428_010214
20240428_0102141920×3413 504 KB

image

image

2

Can you start from the top?

  • What are you trying to do?
  • What did you already try?
  • System information?
  • Is ZFS encryption being used?
  • What is this pool?
  • Rotate images the correct orientation.
3

I don’t even know how it happened, I restarted the system and a Raidz1 stopped being recognized in the mount, I tried to mount it, unmount it, I did all kinds of commands and nothing, it appeared in the dataset but not in the storage, it appeared to import but it didn’t matter

Touching what I did was change the assembly
And right now at the end I mount it by removing the readonly=off and I am copying the data to delete the pool and copy it again correctly

4

I mean this with no disrespect, but can you understand how someone not in your position might have difficulty following along, let alone providing troubleshooting steps?

So everything’s “working correctly” now?

5

I don’t even know how it happened, I restarted the system and a Raidz1 stopped being recognized in the mount, I tried to mount it, unmount it, I did all kinds of commands and nothing, it appeared in the dataset but not in the storage, it appeared to import but it didn’t matter

Touching what I did was change the assembly
And right now at the end I mount it by removing the readonly=off and I am copying the data to delete the pool and copy it again correctly

Here I leave all the threads that I was getting and testing to inform me of the error and I think that in the end in the last one I found the solution

http s://www. truenas .com/community/threads/unable-to-import-the-storage-pool-on-truenas-after-cut-power.115098/

http s://www. truenas .com/community/threads/zfs-pool-eror-checksum-and-gui-stuck.115163/

http s://www. truenas .com/community/threads/unable-to-view-or-mount-storage-pool-after-power-outage.83315/

http s://www. truenas .com/community/threads/unable-to-import-pool-after-version-upgrade.115158/

http s://www. truenas .com/community/threads/zfs-pool-corrupted.98445/

http s://www. truenas .com/community/threads/how-to-export-import-pools-from-cli-in-truenas-core.98309/

http s://docs. oracle .com/cd/E19253-01/819-5461/gazuf/index.html

http s://www. truenas .com/community/threads/unable-to-mount-full-zpool.45893/page-2

https://forum .proxmox .com/threads/zfs-pools-not-mounting-correctly.76810/

https:// davejansen .com/truenas-fix-cannot-mount-directory-failed-to-create-mountpoint/

6

“zfs readonly=on …” can be a problem, especially when the dataset has never been mounted before.
Usually, one the parent dataset with the readonly=on flag is the reason why the mountpoint fails because ZFS/FreeBSD needs to be able to write or edit the moutpoint details. At least this is rough understanding.

7

Can you elaborate as I suspect you are destroying a perfectly good pool.