You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: content/SCALE/GettingStarted/Migrate/MigratePrep.md
+11-5
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,7 @@ CORE Enterprise customers are encouraged to contact Support for assistance with
34
34
CORE systems at the latest 13.0 release can use the [iso upgrade](#migrating-using-an-iso-file-to-upgrade) method to migrate to SCALE.
35
35
36
36
2. Migrate [GELI-encrypted pools](https://www.truenas.com/docs/core/coretutorials/storage/pools/storageencryption/#geli-pool-migrations) to a non-GELI-encrypted pool before upgrading from CORE 12.0x or earlier releases!
37
+
If you do not migrate from GELI to ZFS encryption before upgrading to CORE 13.0-Ux or migrating to SCALE you permanently lose access to the data in the GELI encrypted pool(s).
37
38
38
39
3. Verify the root user is not locked.
39
40
Go to **Accounts > Users**, select the root user and click **Edit** to view current settings and confirm **Lock User** is not selected.
@@ -66,7 +67,12 @@ CORE Enterprise customers are encouraged to contact Support for assistance with
66
67
67
68
<inputtype="checkbox"> Data protection tasks - Write down or take screenshots of replication, periodic snapshot, cloud sync, or other task settings to reconfigure these in SCALE if you want to duplicate these tasks.
68
69
69
-
5. Write down or take screenshots of your network configuration information.
70
+
5. Remove all CORE SMB auxiliary parameter settings before migrating to SCALE.
71
+
As of 23.10 SCALE COBIA, the SMB **Auxiliary Parameters** option is no longer available in the UI.
72
+
Attempting to migrate with these settings can result in broken SMB shares post upgrade that require access to the CLI to fix.
73
+
We recommend removing these unsupported settings before migrating from CORE to SCALE.
74
+
75
+
6. Write down or take screenshots of your network configuration information.
70
76
Capture the global network settings, interfaces (LAGG, VLAN, bridge settings), static IP addresses, and aliases.
71
77
72
78
FreeBSD and Linux use different nomenclature for network interfaces, bridges, LAGGs, and VLANs.
@@ -79,14 +85,14 @@ CORE Enterprise customers are encouraged to contact Support for assistance with
79
85
If there are issues after a clean install of SCALE from an <file>iso</file> file or you are not using DHCP for network and interface configuration, use the information from your CORE settings to configure your SCALE network settings and to reconfigure your static IPs or aliases.
80
86
{{< include file="/static/includes/NetworkInstallRequirementsSCALE.md" >}}
81
87
82
-
6. Migrate the deprecated S3 MinIO service (if in use). See [services deprecated in SCALE](#migrating-from-deprecated-services).
88
+
7. Migrate the deprecated S3 MinIO service (if in use). See [services deprecated in SCALE](#migrating-from-deprecated-services).
83
89
This is a lengthy process depending on the amount of data stored while using the S3 service.
84
90
Read and follow instructions in [Migrating MinIO Data from CORE to SCALE](https://www.truenas.com/docs/solutions/miniocoretoscale/)!
85
91
Make sure S3 MinIO data is backed up as a precaution. The migration process from the S3 service requires first [migrating to the MinIO plugin in TrueNAS CORE](https://www.truenas.com/docs/core/13.0/coretutorials/jailspluginsvms/plugins/minioplugin/#migrating-from-s3-service-to-minio-plugin), migrating from CORE to SCALE, then installing the SCALE MinIO app and importing S3 data.
86
92
87
-
7. Back up any critical data.
93
+
8. Back up any critical data.
88
94
89
-
8. Download your [system configuration file](https://www.truenas.com/docs/core/coretutorials/systemconfiguration/usingconfigurationbackups/) and a [debug file](https://www.truenas.com/docs/core/uireference/system/advanced/).
95
+
9. Download your [system configuration file](https://www.truenas.com/docs/core/coretutorials/systemconfiguration/usingconfigurationbackups/) and a [debug file](https://www.truenas.com/docs/core/uireference/system/advanced/).
90
96
After updating to the latest publicly-available release of CORE and making any changes to CORE user accounts or any other settings download these files and keep them in a safe place and where you can access them if you need to revert to CORE with a clean install using the CORE <file>iso</file> file.
91
97
92
98
After completing the steps that apply to your CORE system listed above, download the [SCALE ISO file](https://www.truenas.com/download-tn-scale/) and save it to your computer.
@@ -180,4 +186,4 @@ To grant access to a specific user (and group) other than using the default admi
180
186
Note the UID and GID for this new user to enter in the application configuration screen.
181
187
182
188
After disabling the WebDAV service and clearing any existing share configurations from the **Shares > WebDAV** screen in Bluefin, install the **WebDAV** application to recreate your shares using the CORE service settings from your notes. Use the **webdav** user and group in control, and the UID and GID (**666**) in the application.
Copy file name to clipboardexpand all lines: content/SCALE/GettingStarted/SCALEReleaseNotes.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -49,8 +49,8 @@ More details are available from [Software Releases]({{< relref "/TrueNASUpgrades
49
49
* TrueNAS SCALE is an appliance built from specific Linux packages.
50
50
Attempting to update SCALE with `apt` or methods other than the SCALE web interface can result in a nonfunctional system.
51
51
52
-
* All auxiliary parameters can change between TrueNAS major versions due to security and development changes.
53
-
We recommend removing all auxiliary parameters from TrueNAS configurations before upgrading.
52
+
* All auxiliary parameters can experience changes between TrueNAS major versions due to security and development changes.
53
+
We recommend removing all auxiliary parameters from TrueNAS configurations before upgrading as these settings can result in SMB share failures after an upgrade.
54
54
55
55
* {{< include file="/static/includes/UpgradeClearCache.md" >}}
Copy file name to clipboardexpand all lines: content/SCALE/SCALETutorials/DataProtection/CloudSyncTasks/CloudSyncTaskGoogleDrive.md
+2
Original file line number
Diff line number
Diff line change
@@ -65,6 +65,8 @@ To add a cloud sync task, go to **Data Protection > Cloud Sync Tasks** and click
65
65
66
66
See **Using Scripting and Environment Variables** for more information on [environment variables]({{< relref "/SCALE/SCALETutorials/DataProtection/CloudSyncTasks/_index.md" >}}).
Copy file name to clipboardexpand all lines: content/SCALE/SCALETutorials/DataProtection/CreatingVMwareSnapshots.md
+2
Original file line number
Diff line number
Diff line change
@@ -88,6 +88,8 @@ Virtual machines must be running for TrueNAS to include them in VMWare snapshots
88
88
89
89
To configure TrueNAS SCALE to create VMWare snapshots, go to **Data Protection** and click the **VMware Snapshot Integration** button in the **Periodic Snapshot Tasks** widget to open the **VMWare Snapshots** screen.
90
90
91
+
Note that you can organize information in the columns of the table(s) below by clicking on each column title. This allows you to toggle the information between a descending an ascending order.
Copy file name to clipboardexpand all lines: content/SCALE/SCALETutorials/DataProtection/Replication/AdvancedReplication/ReplicationWithEncryptionSCALE.md
+2
Original file line number
Diff line number
Diff line change
@@ -108,6 +108,8 @@ This saves some time when creating multiple replication tasks between the same t
108
108
109
109
{{< include file="/static/includes/ReplicationScheduleAndRetentionSteps.md" >}}
Copy file name to clipboardexpand all lines: content/SCALE/SCALETutorials/DataProtection/Replication/LocalReplicationSCALE.md
+2
Original file line number
Diff line number
Diff line change
@@ -62,3 +62,5 @@ Saving changes to the configuration creates a new replication task without alter
62
62
To make it easier to find the snapshot, give it name easy for you to identify. For example, a replicated task named *dailyfull* for a full file system snapshot taken daily.
63
63
64
64
{{< include file="/static/includes/ReplicationScheduleAndRetentionSteps.md" >}}
Copy file name to clipboardexpand all lines: content/SCALE/SCALETutorials/DataProtection/SMARTTestsSCALE.md
+2
Original file line number
Diff line number
Diff line change
@@ -102,6 +102,8 @@ Start the S.M.A.R.T. service. Go to **System Settings > Services** and scroll do
102
102
If you have not configured the S.M.A.R.T. service yet, while the service is stopped, click <iclass="material-icons"aria-hidden="true"title="Configure">edit</i> to open the service configuration form. See [Services S.M.A.R.T. Screen]({{< relref "SMARTServicesScreen.md" >}}) for more information on service settings.
103
103
Click **Save** to save settings and return to the **Services** screen.
After creating and configuring the shares, connect to the mulit-protocol share using either SMB or NFS protocols from a variety of client operating systems including Windows, Apple, FreeBSD, and Linux/Unix systems.
Copy file name to clipboardexpand all lines: content/SCALE/SCALETutorials/Shares/SMB/AddSMBHomeShare.md
+35-6
Original file line number
Diff line number
Diff line change
@@ -7,14 +7,27 @@ tags:
7
7
- smb
8
8
---
9
9
10
+
{{< hint type=important title="Legacy Feature" >}}
11
+
SMB Home Shares are a legacy feature for organizations looking to maintain existing SMB configurations.
12
+
They are not recommended for new deployments.
13
+
14
+
Future TrueNAS SCALE releases can introduce instability or require configuration changes affecting this legacy feature.
15
+
{{< /hint >}}
16
+
10
17
## Setting Up SMB Home Shares
11
-
TrueNAS offers the **Use as Home Share** option, found in the **Add SMB** and **Edit SMB** screen **Advanced Options** settings in the **Other Options** section, for organizations or SMEs that want to use a single SMB share to provide a personal directory to every user account.
18
+
The **Use as Home Share** option, found in the **Add SMB** and **Edit SMB** screen **Advanced Options** settings in the **Other Options** section, is an available option for organizations or SMEs that want to use a single SMB share to provide a personal directory to every user account.
12
19
13
20
With home shares, each user is given a personal home directory when connecting to the share.
14
21
These home directories are not accessible by other users.
15
22
You can use only one share as the home share, but you can create as many non-home shares as you need or want.
16
23
17
-
Creating an SMB home share requires configuring the system storage and joining Active Directory.
24
+
<!-- Place holders for future tutorials/links below. Update with links to appropriate procedures as part of PD-1252 -->
25
+
Other options for configuring individual user directories include:
26
+
* Configure a single share on the TrueNAS and provision individual user directories on the client OS.
27
+
* Create a single SMB share and configure the ACL so that users can create individual directories on the share that inherit write access for the user and grant read access the administrator.
28
+
* Create an SMB share using the **Private SMB datasets and shares** preset that can create per-user datasets under the umbrella of a single share when users access the share.
29
+
30
+
Creating an SMB home share requires configuring the system storage and provisioning local users or joining Active Directory.
18
31
19
32
### Adding Local Share Users
20
33
Go to **Credentials > Local Users** and click **Add**.
@@ -26,7 +39,23 @@ By default, the user **Home Directory** title comes from the user account name a
26
39
27
40
If existing users require access to the home share, go to **Credentials > Local Users** and edit an existing account.
28
41
29
-
Adjust the user home directory to the appropriate dataset and give it a name to create their own directory.
42
+
Adjust the user home directory to the appropriate dataset and give it a name to create its own directory.
43
+
44
+
{{< hint type="important" title="Home Directory Known Impacts" >}}
45
+
{{< include file="/static/includes/24.04HomeDirectory.md" >}}
46
+
47
+
{{< expand "Why the change?" "v" >}}
48
+
TrueNAS uses the `pam_mkhomdir` PAM module in the pam_open_session configuration file to automatically create user home directories if they do not exist.
49
+
`pam_mkhomedir` returns `PAM_PERM_DENIED` if it fails to create a home directory for a user, which eventually turns into a pam_open_session() failure.
50
+
This does not impact other PAM API calls, for example, `pam_authenticate()`.
51
+
52
+
TrueNAS SCALE does not include the customized version of `pam_mkhomedir` used in TrueNAS CORE that specifically avoided trying to create the `/nonexistent` directory. This led to some circumstances where users could create the `/nonexistent` directory on SCALE versions before 24.04.
53
+
54
+
Starting in SCALE 24.04 (Dragonfish), the root filesystem of TrueNAS is read-only, which prevents `pam_mkhomdir` from creating the `/nonexistent` directory in cases where it previously did.
55
+
This results in a permissions error if `pam_open_session()` is called by an application for a user account that has **Home Directory** set to **/nonexistent**.
56
+
{{< /expand >}}
57
+
{{< /hint >}}
58
+
30
59
31
60
### Adding Share Users with Directory Services
32
61
@@ -62,17 +91,17 @@ Set the **Purpose** to **No presets**, then click **Advanced Options**.
62
91
Scroll down to **Other Options** and set **Use as Home Share**.
63
92
Click **Save**.
64
93
65
-
Enable the **SMB** service when prompted to make the share is available on your network.
94
+
Enable the **SMB** service when prompted to make the share available on your network.
66
95
67
96
After saving the dataset, set the permissions.
68
97
69
98
### Setting Dataset Permissions
70
-
After creating the share and dataset, you can edit permissions using either the **Edit** option on the **Permissions** widget for the dataset, or use the **Edit Filesystem ACL** option for the share on the **Windows (SMB) Share** widget to open the ACL edit screen for the share dataset.
99
+
After creating the share and dataset, you can edit permissions using either the **Edit** option on the **Permissions** widget for the dataset or use the **Edit Filesystem ACL** option for the share on the **Windows (SMB) Share** widget to open the ACL edit screen for the share dataset.
71
100
See [SMB Shares]({{< relref "ManageSMBShares.md" >}}) for more information on editing the share dataset permissions.
72
101
73
102
Click on the new dataset. Scroll down to the **Permissions** widget and click **Edit**.
74
103
75
-
Click the **Owner** dropdown and select the owner, the repeat for **Group**.
104
+
Click the **Owner** dropdown and select the owner, then repeat for **Group**.
76
105
Change the owning group to your Active Directory domain admins. Select **Apply Owner** and **Apply Group**.
77
106
78
107

Click **Add** to open the **Add Cron Job** configuration screen and create a new cron job. If you want to modify an existing cron job, click anywhere on the item to open the **Edit Cron Jobs** configuration screen populated with the settings for that cron job.
24
26
The **Add Cron Job** and **Edit Cron Job** configuration screens display the same settings.
0 commit comments