Auto-update blog content from Obsidian: 2026-02-24 13:37:37
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 6s
Blog Deployment / Build (push) Has been skipped
Blog Deployment / Deploy-Staging (push) Successful in 9s
Blog Deployment / Merge (push) Successful in 7s
Blog Deployment / Deploy-Production (push) Successful in 9s
Blog Deployment / Test-Staging (push) Successful in 2s
Blog Deployment / Test-Production (push) Successful in 2s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 2s
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 6s
Blog Deployment / Build (push) Has been skipped
Blog Deployment / Deploy-Staging (push) Successful in 9s
Blog Deployment / Merge (push) Successful in 7s
Blog Deployment / Deploy-Production (push) Successful in 9s
Blog Deployment / Test-Staging (push) Successful in 2s
Blog Deployment / Test-Production (push) Successful in 2s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 2s
This commit is contained in:
@@ -99,7 +99,7 @@ During the installation I didn't choose to define a password for the user `truen
|
||||
Once the password is updated, I land on the dashbaord. The UI feels great at first glance:
|
||||

|
||||
|
||||
The first thing I do is to change the hostname to `granite` and check the box below to define the domain inherited from DHCP:
|
||||
I quickly explore the interface, the first thing I do is changing the hostname to `granite` and check the box below to define the domain inherited from DHCP:
|
||||

|
||||
|
||||
In the `General Settings`, I change the `Localization` settings. I set the Console Keyboard Map to `French (AZERTY)` and the Timezone to `Europe/Paris`.
|
||||
@@ -111,23 +111,40 @@ Finally I remove the admin role from `truenas_admin` and lock the account.
|
||||
|
||||
### Pool creation
|
||||
|
||||
{what is a pool?}
|
||||
In TrueNAS, a pool is a storage collection created by combining multiple disks into a unified ZFS‑managed space.
|
||||
|
||||
In the `Storage` page, I can find my `Disks`, where I can confirm TrueNAS can see my couple of NVMe drives:
|
||||

|
||||

|
||||
|
||||
Now back in the `Storage Dashboard`, I click the `Create Pool` button. I name the pool `storage`:
|
||||

|
||||
Back in the `Storage Dashboard`, I click the `Create Pool` button. I name the pool `storage` because I'm really inspired:
|
||||

|
||||
|
||||
Then I select the `Mirror` layout:
|
||||

|
||||

|
||||
|
||||
I explore quickly the optional options but none makes sense for my setup. At the end, before creating the pool, there is a Review section:
|
||||

|
||||
I explore quickly the optional configurations, but none makes sense for my setup. At the end, before creating the pool, there is a `Review` section:
|
||||

|
||||
|
||||
After hitting `Create Pool`, I'm warned that everything on the disks will be erased, which I have to confirm. Finally the pool is created.
|
||||
|
||||
### dataset config
|
||||
### Datasets creation
|
||||
|
||||
A dataset is a filesystem inside a pool. It can contains files, directories and child datasets of files, it can be shared using NFS and/or SMB. It allows you to independently manage permissions, compression, snapshots, and quotas for different sets of data within the same storage pool.
|
||||
|
||||
Let's now create my first dataset `files` to share files over the network, like ISOs, etc:
|
||||

|
||||
|
||||
Creating my first SMB dataset, TrueNAS prompts me to start and enable the SMB service:
|
||||

|
||||
|
||||
I create another dataset: `media`, and a child `photos`. I create a NFS share from the latter.
|
||||
|
||||
On my current NFS server, the files for the photos are owned by `root` (managed by *Immich*). Later I'll see how I can migrate towards a root-less version. For now I set, in `Advanced Options`, the `Maproot User` and `Maproot Group` to `root`. This is equivalent de the attribute `no_squash_root`, the local `root` of the client stays `root` on the server, not a best practice:
|
||||

|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### data protection
|
||||
|
||||
|
||||
Reference in New Issue
Block a user