diff --git a/content/Archive.md b/content/Archive.md index 8bb9204dda..65d8ada28d 100644 --- a/content/Archive.md +++ b/content/Archive.md @@ -92,7 +92,6 @@ Release Notes: * [2.0]({{< ref "/_includes/TCReleaseNotes/2.0.md" >}}) * [2.0-BETA]({{< ref "/_includes/TCReleaseNotes/2.0-Beta.md" >}}) - {{< /expand >}} {{< expand "TrueCommand 1.x" "v" >}} diff --git a/content/CORE/API/_index.md b/content/CORE/API/_index.md index ce3b0a73ac..0de4daf905 100644 --- a/content/CORE/API/_index.md +++ b/content/CORE/API/_index.md @@ -24,5 +24,3 @@ For convenience, static builds of the current 2.0 API documentation stored on th ## CORE Documentation Sections {{< include file="/_includes/COREDocsSections.md" >}} - -{{< taglist tag="coretopmenu" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/ChangingDefaultShell.md b/content/CORE/CORETutorials/ChangingDefaultShell.md index 0c69a86ae5..b085b356a9 100644 --- a/content/CORE/CORETutorials/ChangingDefaultShell.md +++ b/content/CORE/CORETutorials/ChangingDefaultShell.md @@ -7,7 +7,6 @@ tags: - coreshell --- - The default shell for a new installations is `zsh`. You can change the default shell in **Accounts > Users**. @@ -20,5 +19,3 @@ You can change the default shell in **Accounts > Users**. For more information on the web shell see [Shell]({{< relref "/CORE/UIReference/shell.md" >}}). For more information on using the keyboard and CLI commands in the Shell see [Using Shell]({{< relref "/CORE/CORETutorials/UsingShell.md" >}}). - -{{< taglist tag="coreshell" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/CommunityGuides/ACLPermissionsJails.md b/content/CORE/CORETutorials/CommunityGuides/ACLPermissionsJails.md index 7d6b7a0a42..18f95ac1f3 100644 --- a/content/CORE/CORETutorials/CommunityGuides/ACLPermissionsJails.md +++ b/content/CORE/CORETutorials/CommunityGuides/ACLPermissionsJails.md @@ -48,5 +48,3 @@ Flags: Inherit ![StoragePoolsPermissionsPlexPermissions](/images/CORE/Storage/StoragePoolsPermissionsPlexPermissions.png "Storage Pools Permissions Plex Permissions") If files already exist in the dataset, click the **Apply permissions recursively** checkbox and click **Save**. - -{{< taglist tag="corecommunityguides" vol="CORE" limit="5" title="Community Guides Articles" >}} diff --git a/content/CORE/CORETutorials/CommunityGuides/ETCHostsPersistence.md b/content/CORE/CORETutorials/CommunityGuides/ETCHostsPersistence.md index 7bfe897da6..dc945e9ec0 100644 --- a/content/CORE/CORETutorials/CommunityGuides/ETCHostsPersistence.md +++ b/content/CORE/CORETutorials/CommunityGuides/ETCHostsPersistence.md @@ -34,8 +34,6 @@ To speed up name resolution, add entries for commonly used hosts to the **hosts* To add an entry to the **hosts** file, use a browser to log in to your TrueNAS web interface and follow these steps: 1. Go to **Network > Global Configuration**. -3. Scroll down to the **Host name database** field and add an entry for the TrueNAS system in the format *IP_address space hostname*. -4. Click **Save**. +2. Scroll down to the **Host name database** field and add an entry for the TrueNAS system in the format *IP_address space hostname*. +3. Click **Save**. {{< /expand >}} - -{{< taglist tag="corecommunityguides" vol="CORE" limit="5" title="Community Guides Articles" >}} diff --git a/content/CORE/CORETutorials/CommunityGuides/LegacyReplication.md b/content/CORE/CORETutorials/CommunityGuides/LegacyReplication.md index 997415f197..d7cb7bc3c9 100644 --- a/content/CORE/CORETutorials/CommunityGuides/LegacyReplication.md +++ b/content/CORE/CORETutorials/CommunityGuides/LegacyReplication.md @@ -28,14 +28,12 @@ Creating a legacy replication requires creating an SSH connection to the remote 1. Go to **Tasks > Replication Tasks** and click **ADD**. 2. Select **Advanced Replication**. 3. Select **LEGACY** for the replication **Transport** method to reorganize the screen for the relevant options. - + ![ReplicationLegacyOptions](/images/CORE/Tasks/TasksReplicationLegacy.png "Legacy Replication Options") - + 4. Choose the SSH connection to a remote system that stores replicated snapshots. 5. Select the source datasets on the local system using the file browser or manually enter the dataset paths into the field. To also replicate snapshots of child datasets, set **Recursive**. 6. To choose the replication target, open the file browser and select the dataset to store snapshots. Entering a path to a new dataset creates that target dataset in the defined file path. 7. The remaining options allow defining how long to keep replicated snapshots, compressing data before replication, and setting a bandwidth limit on the transfer. - -{{< taglist tag="corecommunityguides" vol="CORE" limit="5" title="Community Guides Articles" >}} diff --git a/content/CORE/CORETutorials/CommunityGuides/LegacySMBACLs.md b/content/CORE/CORETutorials/CommunityGuides/LegacySMBACLs.md index 182b633764..3d5bdb9098 100644 --- a/content/CORE/CORETutorials/CommunityGuides/LegacySMBACLs.md +++ b/content/CORE/CORETutorials/CommunityGuides/LegacySMBACLs.md @@ -21,5 +21,3 @@ The complexity of the scenario depends on several factors: * Active Directory is in use. Depending on the specific authentication requirements, it can be necessary to create or import user and group accounts into FreeNAS/TrueNAS. - -{{< taglist tag="corecommunityguides" vol="CORE" limit="5" title="Community Guides Articles" >}} diff --git a/content/CORE/CORETutorials/CommunityGuides/OpenVPN.md b/content/CORE/CORETutorials/CommunityGuides/OpenVPN.md index 3bda061e3d..63958c6f5e 100644 --- a/content/CORE/CORETutorials/CommunityGuides/OpenVPN.md +++ b/content/CORE/CORETutorials/CommunityGuides/OpenVPN.md @@ -99,7 +99,7 @@ c0224e25d9ed3d2b562e94bed507fcac 1. Open **System > Certificate**. 2. Add a certificate. - + ![CertificateAdd](/images/UserProvided/CertificateAdd.png "Certificate Add") 3. Give it a name (example: `VPN`) and select **Import Certificate** as the Type. @@ -137,5 +137,3 @@ With a CA and Certificate created, we can configure the VPN connection next. Turn the OpenVPN client service on and off to see the difference. Logs of the OpenVPN client are in **/var/log/messages** and **/var/log/daemon**. - -{{< taglist tag="corecommunityguides" vol="CORE" limit="5" title="Community Guides Articles" >}} diff --git a/content/CORE/CORETutorials/DirectoryServices/ActiveDirectory.md b/content/CORE/CORETutorials/DirectoryServices/ActiveDirectory.md index 71a44e99a7..cb3ca61749 100644 --- a/content/CORE/CORETutorials/DirectoryServices/ActiveDirectory.md +++ b/content/CORE/CORETutorials/DirectoryServices/ActiveDirectory.md @@ -129,5 +129,3 @@ You can go to the **Shell** and enter various commands to get more details about * Test AD connection: `wbinfo -t`. A successful test shows a message similar to `checking the trust secret for domain YOURDOMAIN via RPC calls succeeded`. * User connection test to an SMB share: `smbclient '//127.0.0.1/smbshare -U AD01.LAB.IXSYSTEMS.COM\ixuser`, replacing `127.0.0.1` with your server address, `smbshare` with the SMB share name, `AD01.LAB.IXSYSTEMS.COM` with your trusted domain, and `ixuser` with the user account name for authentication testing. {{< /expand >}} - -{{< taglist tag="coredirectoryservices" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/DirectoryServices/Kerberos.md b/content/CORE/CORETutorials/DirectoryServices/Kerberos.md index 284b6254c0..dd0809287b 100644 --- a/content/CORE/CORETutorials/DirectoryServices/Kerberos.md +++ b/content/CORE/CORETutorials/DirectoryServices/Kerberos.md @@ -73,5 +73,3 @@ To instruct the Active Directory service to use the keytab, go to **Directory Se When using a keytab with Active Directory, **username** and **userpass** in the keytab should match the **Domain Account Name** and **Domain Account Password** fields in **Directory Services > Active Directory**. To instruct LDAP to use a principal from the keytab, go to **Directory Services > Active Directory**. Click **Advanced Options**, then select the installed keytab using the **Kerberos Principal** dropdown list. - -{{< taglist tag="corekerberos" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/DirectoryServices/LDAP.md b/content/CORE/CORETutorials/DirectoryServices/LDAP.md index 3f689ecf7e..3d85aea369 100644 --- a/content/CORE/CORETutorials/DirectoryServices/LDAP.md +++ b/content/CORE/CORETutorials/DirectoryServices/LDAP.md @@ -52,5 +52,3 @@ To configure LDAP certificate-based authentication for the LDAP provider to sign {{< hint type=important >}} [Samba 4.13.0](https://www.samba.org/samba/history/samba-4.13.0.html) deprecated **Samba Schema**. Select if SMB shares need LDAP authentication and the LDAP server is already configured with Samba attributes. If selected, specify the type of schema from the **Schema** dropdown list. {{< /hint >}} - -{{< taglist tag="coreldap" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/DirectoryServices/NIS.md b/content/CORE/CORETutorials/DirectoryServices/NIS.md index 645e3b32bd..426bd9dab7 100644 --- a/content/CORE/CORETutorials/DirectoryServices/NIS.md +++ b/content/CORE/CORETutorials/DirectoryServices/NIS.md @@ -37,5 +37,3 @@ Configure the remaining options as needed: Click **SAVE** to save configuration settings. Click **REBUILD DIRECTORY SERVICE CACHE** to resync the cache if it becomes out of sync. Or if fewer users than expected are available in the permissions editors. - -{{< taglist tag="corenis" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Getting Support.md b/content/CORE/CORETutorials/Getting Support.md index f254dc03ec..ba502e6269 100644 --- a/content/CORE/CORETutorials/Getting Support.md +++ b/content/CORE/CORETutorials/Getting Support.md @@ -12,14 +12,11 @@ tags: There are several options to get support for your TrueNAS installation. TrueNAS CORE users can engage with the TrueNAS community to answer questions and resolve issues. TrueNAS Enterprise hardware customers can also access the fast and effective support directly provided by iXsystems. - ## TrueNAS CORE {{< expand "" "v" >}} TrueNAS CORE users are welcome to report bugs and vote for or suggest new TrueNAS features in the project Jira instance. Have questions? We recommend searching through the software documentation and community resources for answers. - - ### Reporting a Bug If you encounter a bug or other issue while using TrueNAS, create a bug report in the [TrueNAS Jira Project](https://ixsystems.atlassian.net/projects/NAS/). @@ -120,5 +117,3 @@ Use the same email address submitted with the ticket when registering. ## Contacting iXsystems Support {{< include file="content/_includes/iXsystemsSupportContact.md" >}} - -{{< taglist tag="coresupport" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/JailsPluginsVMs/Jails/AccessingJailsUsingSSH.md b/content/CORE/CORETutorials/JailsPluginsVMs/Jails/AccessingJailsUsingSSH.md index 9225501bcd..f6c33991ea 100644 --- a/content/CORE/CORETutorials/JailsPluginsVMs/Jails/AccessingJailsUsingSSH.md +++ b/content/CORE/CORETutorials/JailsPluginsVMs/Jails/AccessingJailsUsingSSH.md @@ -121,5 +121,3 @@ Password: Every jail has its own user accounts and service configuration. These steps must be repeated for each jail that requires SSH access. - -{{< taglist tag="corejails" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/JailsPluginsVMs/Jails/CreatingJails.md b/content/CORE/CORETutorials/JailsPluginsVMs/Jails/CreatingJails.md index 898d0c8f36..9710d42880 100644 --- a/content/CORE/CORETutorials/JailsPluginsVMs/Jails/CreatingJails.md +++ b/content/CORE/CORETutorials/JailsPluginsVMs/Jails/CreatingJails.md @@ -162,5 +162,3 @@ These steps create a template jail: 7. Complete the jail creation wizard. {{< /expand >}} - -{{< taglist tag="corejails" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/JailsPluginsVMs/Jails/InstallingJailSoftware.md b/content/CORE/CORETutorials/JailsPluginsVMs/Jails/InstallingJailSoftware.md index 3f7754517d..928c72d2ce 100644 --- a/content/CORE/CORETutorials/JailsPluginsVMs/Jails/InstallingJailSoftware.md +++ b/content/CORE/CORETutorials/JailsPluginsVMs/Jails/InstallingJailSoftware.md @@ -222,5 +222,3 @@ The startup script also indicates if any additional parameters are available: # NAME_dir="/usr/local/etc/openvpn" # --cd directory ``` - -{{< taglist tag="corejails" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/JailsPluginsVMs/Jails/ManagingJails.md b/content/CORE/CORETutorials/JailsPluginsVMs/Jails/ManagingJails.md index 7c5e6c7e5f..dc6eeecd45 100644 --- a/content/CORE/CORETutorials/JailsPluginsVMs/Jails/ManagingJails.md +++ b/content/CORE/CORETutorials/JailsPluginsVMs/Jails/ManagingJails.md @@ -10,7 +10,6 @@ tags: {{< toc >}} - The **Jails** screen displays a list of jails installed on your system. ![Jails](/images/CORE/Jails/Jails.png "Jails List") @@ -41,5 +40,3 @@ For more information on jail options, see [Creating Jails]({{< relref "/CORE/COR To modify the IP address information for a jail, click the for the jail and then **EDIT** instead of issuing the networking commands directly from the command line of the jail. This ensures changes are saved and survive a jail or TrueNAS reboot. {{< /hint >}} - -{{< taglist tag="corejails" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/JailsPluginsVMs/Jails/SettingUpJailStorage.md b/content/CORE/CORETutorials/JailsPluginsVMs/Jails/SettingUpJailStorage.md index 8671bc0f11..5c351ee22c 100644 --- a/content/CORE/CORETutorials/JailsPluginsVMs/Jails/SettingUpJailStorage.md +++ b/content/CORE/CORETutorials/JailsPluginsVMs/Jails/SettingUpJailStorage.md @@ -8,7 +8,6 @@ tags: - corejailspluginsvm --- - Jails can be given access to an area of storage outside of the jail that is configured on the TrueNAS system. It is possible to give a FreeBSD jail access to an area of storage on the TrueNAS system. This is useful for applications or plugins that store large amounts of data or if an application in a jail needs access to data stored on the TrueNAS system. @@ -83,5 +82,3 @@ Files that are deleted from the **Destination** directory in the jail are also d However, removing the jail storage entry only removes the pointer. This leaves the data intact but no longer accessible to the jail. {{< /hint >}} - -{{< taglist tag="corejails" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/JailsPluginsVMs/Plugins/CreatingCustomPlugin.md b/content/CORE/CORETutorials/JailsPluginsVMs/Plugins/CreatingCustomPlugin.md index 46a4a779d6..58f244a92a 100644 --- a/content/CORE/CORETutorials/JailsPluginsVMs/Plugins/CreatingCustomPlugin.md +++ b/content/CORE/CORETutorials/JailsPluginsVMs/Plugins/CreatingCustomPlugin.md @@ -170,5 +170,3 @@ Remember to put a link to your newly created artifact repository in the comments This way a moderator can fork your repository and can make available in the community list of plugins. For guides on how to use Github, see [Github Guides](https://guides.github.com/). - -{{< taglist tag="corejailspluginsvm" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/JailsPluginsVMs/Plugins/ManagingPlugins.md b/content/CORE/CORETutorials/JailsPluginsVMs/Plugins/ManagingPlugins.md index 6e249ae53d..83abf32243 100644 --- a/content/CORE/CORETutorials/JailsPluginsVMs/Plugins/ManagingPlugins.md +++ b/content/CORE/CORETutorials/JailsPluginsVMs/Plugins/ManagingPlugins.md @@ -126,5 +126,3 @@ Confirm the plugin removal by typing in the name of the plugin jail and selectin Uninstalling can take a few moments while the plugin deletes from both **Plugins** and **Jails**. The plugin dataset also deletes from ***POOL*/iocage/jails/** and any jail snapshots from **Storage > Snapshots**. - -{{< taglist tag="coreplugins" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/JailsPluginsVMs/UpdateJailsPlugins.md b/content/CORE/CORETutorials/JailsPluginsVMs/UpdateJailsPlugins.md index 211e76ad48..a46e13dffa 100644 --- a/content/CORE/CORETutorials/JailsPluginsVMs/UpdateJailsPlugins.md +++ b/content/CORE/CORETutorials/JailsPluginsVMs/UpdateJailsPlugins.md @@ -67,5 +67,3 @@ The command checks if an update is available and prompts to proceed when the sof This example shows attempting to update the minio software but no update was available. ![MinioJailUpdateNone](/images/CORE/Jails/MinioJailUpdateNone.png "Minio Jail: no update available") - -{{< taglist tag="corejails" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/JailsPluginsVMs/VirtualMachines/CreatingBasicVM.md b/content/CORE/CORETutorials/JailsPluginsVMs/VirtualMachines/CreatingBasicVM.md index 8a341614ec..3acea22bc4 100644 --- a/content/CORE/CORETutorials/JailsPluginsVMs/VirtualMachines/CreatingBasicVM.md +++ b/content/CORE/CORETutorials/JailsPluginsVMs/VirtualMachines/CreatingBasicVM.md @@ -88,5 +88,3 @@ If the VM you created has no guest OS installed, the VM **State** toggle and }} - -{{< taglist tag="corejailspluginsvm" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/JailsPluginsVMs/VirtualMachines/SettingUpNPIV.md b/content/CORE/CORETutorials/JailsPluginsVMs/VirtualMachines/SettingUpNPIV.md index 2d52122ea7..49b40ff7b8 100644 --- a/content/CORE/CORETutorials/JailsPluginsVMs/VirtualMachines/SettingUpNPIV.md +++ b/content/CORE/CORETutorials/JailsPluginsVMs/VirtualMachines/SettingUpNPIV.md @@ -35,5 +35,3 @@ After the tunables are created, the configured number of virtual ports appears i They are also advertised to the switch so zoning can be configured on the switch. After associating a virtual port with a target, add it to the **Target** tab of [Reporting]({{< relref "/CORE/UIReference/ReportingGraphs.md" >}}) so you can view its bandwidth usage. - -{{< taglist tag="coreiscsi" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/ManagingTLSCiphers.md b/content/CORE/CORETutorials/ManagingTLSCiphers.md index 6057c7ca8b..611b6128ed 100644 --- a/content/CORE/CORETutorials/ManagingTLSCiphers.md +++ b/content/CORE/CORETutorials/ManagingTLSCiphers.md @@ -40,5 +40,3 @@ TLSv1.2 represented a major step forward in security effectiveness and resulted ### TLSv1.3 [TLSv1.3](https://www.rfc-editor.org/rfc/rfc8446.html) represents another major improvement to the protocol. TLSv1.3 removes legacy or insecure encryption algorithms, adds encryption for handshake messages, and separates authentication and key exchange concepts. - -{{< taglist tag="coreopenvpn" vol="CORE" limit="5" title="Related Articles">}} diff --git a/content/CORE/CORETutorials/Network/IPMI.md b/content/CORE/CORETutorials/Network/IPMI.md index 42da343e5e..dc2a81b0b8 100644 --- a/content/CORE/CORETutorials/Network/IPMI.md +++ b/content/CORE/CORETutorials/Network/IPMI.md @@ -34,7 +34,3 @@ Click **SAVE** to save the IPMI settings. Save the configuration. Access the IPMI interface using a web browser and the IP address specified in **Network > IPMI**. The management interface prompts for login credentials. Refer to your IPMI device documentation to learn the default administrator account credentials. Log in to the management interface. Here you can change the default administrative user name and create extra IPMI users. The appearance of the IPMI utility and the functions that are available vary by hardware. - -{{< taglist tag="coreipmi" vol="CORE" limit="5" >}} - -{{< taglist tag="corenetwork" vol="CORE" limit="5" title="Related Articles" >}} diff --git a/content/CORE/CORETutorials/Network/Interfaces/BridgeCreate.md b/content/CORE/CORETutorials/Network/Interfaces/BridgeCreate.md index 65955cfd84..9946ecd914 100644 --- a/content/CORE/CORETutorials/Network/Interfaces/BridgeCreate.md +++ b/content/CORE/CORETutorials/Network/Interfaces/BridgeCreate.md @@ -21,7 +21,3 @@ The next section is **Bridge Settings**. Use the dropdown list next to **Bridge See [Interfaces Screen]({{< relref "/CORE/UIReference/Network/InterfacesScreen.md" >}}) for more information on settings. {{< include file="/content/_includes/InterfaceOptions.md" markdown="true" >}} - -{{< taglist tag="corenetworkinterfaces" vol="CORE" limit="5" >}} - -{{< taglist tag="corejailspluginsvm" vol="CORE" limit="5" title="Related Articles" >}} diff --git a/content/CORE/CORETutorials/Network/Interfaces/EditingPhysicalInterface.md b/content/CORE/CORETutorials/Network/Interfaces/EditingPhysicalInterface.md index 423f53174c..8a78fe18fd 100644 --- a/content/CORE/CORETutorials/Network/Interfaces/EditingPhysicalInterface.md +++ b/content/CORE/CORETutorials/Network/Interfaces/EditingPhysicalInterface.md @@ -17,7 +17,7 @@ Be careful when configuring the network interface that controls the TrueNAS® we {{< /hint >}} **Network > Interfaces** lists all the physical [Network Interface Controllers (NICs)]({{< relref "/CORE/UIReference/Network/InterfacesScreen.md" >}}) connected -to your TrueNAS® system. +to your TrueNAS® system. ![NetworkInterfaces](/images/CORE/Network/NetworkInterfaces.png "Interfaces List") @@ -50,11 +50,8 @@ Users can either **SAVE CHANGES** or **REVERT CHANGES**. A user has the time the ![NetworkInterfaceEditSaveChanges](/images/CORE/Network/NetworkInterfaceEditSaveChanges.png "Network Interface Edit Save Changes ") - ![NetworkInterfaceSaveChangesOption](/images/CORE/Network/NetworkInterfaceSaveChangesOption.png "Network Interface Save Changes Option ") The system displays a dialog box to show that network interface changes are now permanent. ![NetworkInterfaceDialog](/images/CORE/Network/NetworkInterfaceDialogBox.png "Network Interface Dialog Box ") - -{{< taglist tag="corenetworkinterfaces" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Network/Interfaces/LAGGCreate.md b/content/CORE/CORETutorials/Network/Interfaces/LAGGCreate.md index 9ba3890a82..e743d5c2a2 100644 --- a/content/CORE/CORETutorials/Network/Interfaces/LAGGCreate.md +++ b/content/CORE/CORETutorials/Network/Interfaces/LAGGCreate.md @@ -46,7 +46,3 @@ Now define the **Lagg Interfaces** and review the remaining interface options. See [Interfaces Screen]({{< relref "/CORE/UIReference/Network/InterfacesScreen.md" >}}) for more information on settings. {{< include file="/content/_includes/InterfaceOptions.md" markdown="true" >}} - -{{< taglist tag="corenetworkinterfaces" vol="CORE" limit="5" >}} - -{{< taglist tag="corejailspluginsvm" vol="CORE" limit="5" title="Related Articles" >}} diff --git a/content/CORE/CORETutorials/Network/Interfaces/SettingStaticIP.md b/content/CORE/CORETutorials/Network/Interfaces/SettingStaticIP.md index 802c240dcf..bae446cdd4 100644 --- a/content/CORE/CORETutorials/Network/Interfaces/SettingStaticIP.md +++ b/content/CORE/CORETutorials/Network/Interfaces/SettingStaticIP.md @@ -124,5 +124,3 @@ This example shows adding static IPv4 addresses to interface *igb0*: {{< /expand >}} Saving interface configuration changes disrupts the web interface while system networking restarts. The new settings might need a system reboot to take effect. If the web interface is unavailable, this could also require a reboot. Check if the network interface you changed is the one utilized by the web interface. - -{{< taglist tag="corenetworkinterfaces" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Network/Interfaces/VLANCreate.md b/content/CORE/CORETutorials/Network/Interfaces/VLANCreate.md index df9204f3fc..5cd1304939 100644 --- a/content/CORE/CORETutorials/Network/Interfaces/VLANCreate.md +++ b/content/CORE/CORETutorials/Network/Interfaces/VLANCreate.md @@ -29,7 +29,3 @@ There are a few extra interface options to review after the VLAN options are set See [Interfaces Screen]({{< relref "/CORE/UIReference/Network/InterfacesScreen.md" >}}) for more information on settings. {{< include file="/content/_includes/InterfaceOptions.md" markdown="true" >}} - -{{< taglist tag="corenetworkinterfaces" vol="CORE" limit="5" >}} - -{{< taglist tag="corejailspluginsvm" vol="CORE" limit="5" title="Related Articles" >}} diff --git a/content/CORE/CORETutorials/Network/NetworkSummary.md b/content/CORE/CORETutorials/Network/NetworkSummary.md index 8be88ac1a1..b3334039e5 100644 --- a/content/CORE/CORETutorials/Network/NetworkSummary.md +++ b/content/CORE/CORETutorials/Network/NetworkSummary.md @@ -34,5 +34,3 @@ These areas are not editable. Define any Static Routes in **Network > [Static Routes]({{< relref "/CORE/CORETutorials/Network/StaticRoutes.md" >}})**. Out of Band Management is managed from **Network > [IPMI]({{< relref "/CORE/CORETutorials/Network/IPMI.md" >}})**. This option is visible only when TrueNAS detects the appropriate physical hardware. - -{{< taglist tag="corenetwork" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Network/StaticRoutes.md b/content/CORE/CORETutorials/Network/StaticRoutes.md index f42b0ebb9d..f19bb1a33c 100644 --- a/content/CORE/CORETutorials/Network/StaticRoutes.md +++ b/content/CORE/CORETutorials/Network/StaticRoutes.md @@ -20,5 +20,3 @@ When required, add a static route by going to **Network** > **Static Routes** an * Enter the IP address of the **Gateway**. * Enter any notes or identifiers describing the route in **Description**. - -{{< taglist tag="corenetwork" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Network/Wireguard.md b/content/CORE/CORETutorials/Network/Wireguard.md index 37e039755e..90af547636 100644 --- a/content/CORE/CORETutorials/Network/Wireguard.md +++ b/content/CORE/CORETutorials/Network/Wireguard.md @@ -66,5 +66,3 @@ There are [quickstart guides](https://www.wireguard.com/quickstart/) and [tutori Determine that you have a valid /root/wg0.conf. If so, rebooting the system brings up the WireGuard interface with a wg0 device in the output of `ifconfig`. ![wg0DeviceOutput](/images/CORE/System/wg0DeviceOutput.png "wg0 device output") - -{{< taglist tag="corenetwork" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Services/ConfigureDynamicDNS.md b/content/CORE/CORETutorials/Services/ConfigureDynamicDNS.md index 706d144024..f6b0ba25cf 100644 --- a/content/CORE/CORETutorials/Services/ConfigureDynamicDNS.md +++ b/content/CORE/CORETutorials/Services/ConfigureDynamicDNS.md @@ -17,5 +17,3 @@ Log in to the TrueNAS web interface and go to **Services > Dynamic DNS**. Your DDNS solution provides the required values for these fields. Start the DDNS service after choosing your **Provider** options and saving the settings. - -{{< taglist tag="coreddns" vol="CORE" limit="5" >}} \ No newline at end of file diff --git a/content/CORE/CORETutorials/Services/ConfigureUPS.md b/content/CORE/CORETutorials/Services/ConfigureUPS.md index 15587047ab..7e96d9a61c 100644 --- a/content/CORE/CORETutorials/Services/ConfigureUPS.md +++ b/content/CORE/CORETutorials/Services/ConfigureUPS.md @@ -41,5 +41,3 @@ This primary system makes UPS status available on the network for other computer The secondary computers receive UPS status data from the primary computer. The secondary computers receive power from the UPS. See the [NUT User Manual](https://networkupstools.org/docs/user-manual.chunked/index.html) and [NUT User Manual Pages](https://networkupstools.org/docs/man/index.html#User_man). {{< /expand >}} - -{{< taglist tag="coreups" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Services/ConfiguringFTP.md b/content/CORE/CORETutorials/Services/ConfiguringFTP.md index c4fbe982c4..cc19ea34cb 100644 --- a/content/CORE/CORETutorials/Services/ConfiguringFTP.md +++ b/content/CORE/CORETutorials/Services/ConfiguringFTP.md @@ -6,7 +6,6 @@ tags: - coreftp --- - ## FTP Connections FTP connections cannot share connections with other accounts, such as SMB connections. FTP connections need a new dataset and local user account. @@ -60,5 +59,3 @@ The default directory is the same as the user /home directory. After connecting, you can create directories and upload or download files. ![FilezillaFTPConnect](/images/CORE/FilezillaFTPConnect.png "Filezilla FTP Connection") - -{{< taglist tag="coreftp" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Services/ConfiguringLLDP.md b/content/CORE/CORETutorials/Services/ConfiguringLLDP.md index fe21cec19b..74a7673317 100644 --- a/content/CORE/CORETutorials/Services/ConfiguringLLDP.md +++ b/content/CORE/CORETutorials/Services/ConfiguringLLDP.md @@ -11,7 +11,7 @@ Network devices use the [Link Layer Discovery Protocol (LLDP)](https://tools.iet TrueNAS uses the [ladvd](https://github.com/sspans/ladvd) LLDP implementation. LLDP service is often used in a local network environment with managed switches. Configuring and starting the LLDP service allows the TrueNAS system to advertise itself on the network. -To configure LLDP, go to the **Services** page, find the **LLDP** entry, and click the icon. +To configure LLDP, go to the **Services** page, find the **LLDP** entry, and click the icon. ![ServicesLLDPOptions](/images/CORE/Services/ServicesLLDPOptions.png "LLDP Service Options") @@ -20,5 +20,3 @@ Select **Interface Description** and enter a **Country Code**. The location of t Click **SAVE** to save the current selections and return to the **Services** screen. Click the toggle on the **Services** screen to turn the LLDP service on. The toggle turns blue when it is running. - -{{< taglist tag="corelldp" vol="CORE" limit="5" >}} \ No newline at end of file diff --git a/content/CORE/CORETutorials/Services/ConfiguringOpenVPN.md b/content/CORE/CORETutorials/Services/ConfiguringOpenVPN.md index 2677aea932..17634bca19 100644 --- a/content/CORE/CORETutorials/Services/ConfiguringOpenVPN.md +++ b/content/CORE/CORETutorials/Services/ConfiguringOpenVPN.md @@ -17,13 +17,14 @@ A virtual private network (VPN) is an extension of a private network over public Public key infrastructure (PKI) must be in place before configuring TrueNAS as either an OpenVPN server or client. PKI utilizes [certificates]({{< relref "/CORE/UIReference/System/Certificates.md" >}}) and [certificate authorities]({{< relref "CAs.md" >}}) created in or imported to TrueNAS. {{< expand "What does this do?" "v" >}} -TrueNAS authenticates with clients or servers by confirming network credentials. These must be signed by a valid master certificate authority (CA). +TrueNAS authenticates with clients or servers by confirming network credentials. These must be signed by a valid master certificate authority (CA). To read more about the required PKI for OpenVPN, see the [OpenVPN PKI Overview](https://community.openvpn.net/openvpn/wiki/HOWTO?__cf_chl_jschl_tk__=92022277e38bff707b1684f49a2af61f5eb4c632-1605712222-0-AQxKxUAlHKMcfHHNdSMOLL25Lr3e8icKHu3CgjMFRe6GXS1Z72EgXMieNrGaBdWa0m3R5CEZcxwGdwhgaRO392FTivdOQis5Pa2Bm-4jEzydUBTqhx_F4XWN7ujVee5CUxG6AoyOet91SaWM-siqV0_d0ppGnSsfwX9HFOmKuAnJexAjqpofUlP6xjru4Qujw72uR-yUT3fuFDMyukAAtEAP_zPXtewdS_kcSC5eSdf-RC6V8T_QZ2UT6GfqxxSr5shwe0rFkNinTCOKLk_67UIU2zEkpuiQ8C7p3ysh1DS_ONAzR2pfwdgetKm3HiBJ38C86956W6D8-mpOulfP26E#Overview). {{< /expand >}} ## Configuring OpenVPN: Process Overview The general process to configure OpenVPN (server or client) on TrueNAS is to: + * Select the networking credentials * Set the connection detail * Choose any additional security or protocol options @@ -46,7 +47,7 @@ The **Device Type** must match with the OpenVPN server **Device Type**. Enabled by default, it allows the OpenVPN client and server to run at the same time. Review the [Security Options](#security-options) and select settings that meet your network security requirements. -Determine if the OpenVPN server is using TLS Encryption. If so, copy the static TLS encryption key and paste into the **TLS Crypt Auth** field. +Determine if the OpenVPN server is using TLS Encryption. If so, copy the static TLS encryption key and paste into the **TLS Crypt Auth** field. ### OpenVPN Server @@ -93,8 +94,8 @@ See [OpenVPN Screens]({{< relref "/CORE/UIReference/Services/OpenVPNScreen.md" > Connecting to a private network still sends data over less secure public resources. OpenVPN includes several security features that are optional. These optional security features help protect the data sent into or out of the private network. -* **Authentication Algorithm**: This is used to validate packets that are sent over the network connection. Your network environment might require a specific algorithm. **SHA1 HMAC** is a good standard algorithm to use if a particular algorithm is not required. -* **Cipher**: This is an algorithm to encrypt data packets sent through the connection. While not required, choosing a cipher can increase connection security. Verify the required ciphers for your networking environment. If there are no specific cipher requirements, **AES-256-GCM** is a good default choice. +* **Authentication Algorithm**: This is used to validate packets that are sent over the network connection. Your network environment might require a specific algorithm. **SHA1 HMAC** is a good standard algorithm to use if a particular algorithm is not required. +* **Cipher**: This is an algorithm to encrypt data packets sent through the connection. While not required, choosing a cipher can increase connection security. Verify the required ciphers for your networking environment. If there are no specific cipher requirements, **AES-256-GCM** is a good default choice. * **TLS Encryption**: Selecting **TLS Crypt Auth Enabled** encrypts all TLS handshake messages. This adds another layer of security. OpenVPN server and clients share a required static key. ## Service Activation @@ -104,7 +105,3 @@ Start the service by clicking the related toggle in **Services**. To check the current state of the service, hover over the toggle. **Start Automatically**: Selecting this option starts the OpenVPN service whenever TrueNAS completes booting. The network and data pools must be running. - -{{< taglist tag="coreopenvpn" vol="CORE" limit="5" >}} - -{{< taglist tag="coretlsciphers" vol="CORE" limit="5" title="Related TLS Articles">}} diff --git a/content/CORE/CORETutorials/Services/ConfiguringRsync.md b/content/CORE/CORETutorials/Services/ConfiguringRsync.md index 3fe3648920..c8697415ec 100644 --- a/content/CORE/CORETutorials/Services/ConfiguringRsync.md +++ b/content/CORE/CORETutorials/Services/ConfiguringRsync.md @@ -55,5 +55,3 @@ To create a new module, click **ADD**. {{< hint type=note >}} When a **Hosts Allow** list is defined, only the IPs and hostnames on the list are able to connect to the module. {{< /hint >}} - -{{< taglist tag="corersync" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Services/ConfiguringS3.md b/content/CORE/CORETutorials/Services/ConfiguringS3.md index 4b6c7273ec..7ffe073d9c 100644 --- a/content/CORE/CORETutorials/Services/ConfiguringS3.md +++ b/content/CORE/CORETutorials/Services/ConfiguringS3.md @@ -45,5 +45,3 @@ MinIO manages files as objects. These objects cannot mix with other dataset file Configure the rest of the options as needed in your environment. Make sure to start the service after saving any changes. - -{{< taglist tag="cores3" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Services/ConfiguringSFTP.md b/content/CORE/CORETutorials/Services/ConfiguringSFTP.md index bab5ad5e24..1f82bd9268 100644 --- a/content/CORE/CORETutorials/Services/ConfiguringSFTP.md +++ b/content/CORE/CORETutorials/Services/ConfiguringSFTP.md @@ -8,7 +8,6 @@ tags: - coressh --- - ## Configuring SFTP Service SSH File Transfer Protocol (SFTP), is available by enabling SSH remote access to the TrueNAS system. @@ -20,8 +19,8 @@ Go to **Services**, find the **SSH** entry, and click the }}) for information on SSH screen settings. ### SFTP Connections @@ -39,7 +38,7 @@ This example uses FileZilla. Using FileZilla, enter `SFTP://TrueNAS IP`, `username`, `password`, and port `22` to connect. Where `TrueNAS IP` is the IP address for your system, and `username` and `password` are those you use to connect to the FTP client. Or enter `SFTP://'TrueNAS IP'`, `'username'`, `'password'`, and port `22` to connect. {{< hint type=important >}} -Chroot is not 100% secure, but SFTP does not have chroot locking. +Chroot is not 100% secure, but SFTP does not have chroot locking. The lack of chroot allows users to move up to the root directory. They can view internal system information. If this level of access is a concern, FTP with TLS may be the more secure choice. {{< /hint >}} @@ -59,7 +58,7 @@ Select the networking options for either DHCP or a static IP and confirm to crea After the jail is created, click the expand icon **>** on the right-hand side of the jail to open it. Click **START** and open **SHELL**. -Create a user in the jail. +Create a user in the jail. Enter command `adduser`. Follow the prompts. Include the password and home directory location. When complete, the jail asks to confirm the credentials. @@ -75,5 +74,3 @@ Using an FTP client, such as FileZilla, log in with the jail IP address and user ![FilezillaJailConnectSFTP](/images/CORE/FilezillaJailConnectSFTP.png "Filezilla SFTP Connect to TrueNAS Jail") {{< /expand >}} - -{{< taglist tag="coressh" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Services/ConfiguringSMART.md b/content/CORE/CORETutorials/Services/ConfiguringSMART.md index ff85ebfec5..f9487e32f8 100644 --- a/content/CORE/CORETutorials/Services/ConfiguringSMART.md +++ b/content/CORE/CORETutorials/Services/ConfiguringSMART.md @@ -34,5 +34,3 @@ Start the service by clicking the related toggle in **Services**. To check the current state of the service, hover over the toggle. Selecting **Start Automatically** starts the service whenever TrueNAS completes booting. The network and data pools must be running. - -{{< taglist tag="coresmart" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Services/ConfiguringSNMP.md b/content/CORE/CORETutorials/Services/ConfiguringSNMP.md index ddffee99f1..4b36e92a9a 100644 --- a/content/CORE/CORETutorials/Services/ConfiguringSNMP.md +++ b/content/CORE/CORETutorials/Services/ConfiguringSNMP.md @@ -23,5 +23,3 @@ Locate available Management Information Bases (MIBs). Go to /usr/local/sha Here is a sample of the directory contents: ![ServicesSNMPMibSample](/images/CORE/Services/ServicesSNMPMibSample.png "Services SNMP Mib Sample") - -{{< taglist tag="coresnmp" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Services/ConfiguringSSH.md b/content/CORE/CORETutorials/Services/ConfiguringSSH.md index ebc660c5c4..2cdcc34a3b 100644 --- a/content/CORE/CORETutorials/Services/ConfiguringSSH.md +++ b/content/CORE/CORETutorials/Services/ConfiguringSSH.md @@ -63,5 +63,3 @@ Repeat for each user that needs restricted SSH access. Test the configuration from another system. Run the `sftp`, `ssh`, and `scp` commands as that user account. `sftp` and `scp` work but `ssh` fails. {{< /expand >}} - -{{< taglist tag="coressh" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Services/ConfiguringTFTP.md b/content/CORE/CORETutorials/Services/ConfiguringTFTP.md index 1ebefe25c0..ef3186f0df 100644 --- a/content/CORE/CORETutorials/Services/ConfiguringTFTP.md +++ b/content/CORE/CORETutorials/Services/ConfiguringTFTP.md @@ -8,7 +8,6 @@ tags: - coresftp --- - ## Setting Up TFTP The Trivial File Transfer Protocol (TFTP) is a light-weight version of FTP. It is often used in a local environment. It can transfer configuration or boot files between machines, such as routers. @@ -21,5 +20,3 @@ If the system has minimal usage requirements, start the service. Starting the TF ![ServicesTFTPOptions](/images/CORE/Services/ServicesTFTPOptions.png "TFTP Service Options") Use the **TFTP** screen to configure the system for SFTP. - -{{< taglist tag="coretftp" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Services/FTPTFTP.md b/content/CORE/CORETutorials/Services/FTPTFTP.md index 56fd02a985..8301e772e9 100644 --- a/content/CORE/CORETutorials/Services/FTPTFTP.md +++ b/content/CORE/CORETutorials/Services/FTPTFTP.md @@ -15,5 +15,3 @@ The additional SSH options provide secure config file transfer methods. Trivial Options for configuring **FTP**, **SSH**, and **TFTP** are in the system **Services**. Click the to configure the related service. - -{{< taglist tag="coreftp" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Services/S3forMinIO.md b/content/CORE/CORETutorials/Services/S3forMinIO.md index 4cee6b13a1..023520a6b7 100644 --- a/content/CORE/CORETutorials/Services/S3forMinIO.md +++ b/content/CORE/CORETutorials/Services/S3forMinIO.md @@ -21,7 +21,7 @@ To test access to the MinIO Browser, select **Enable Browser**. Open a web brows Different methods are used for connecting to and using MinIO: -{{< expand "s3cmd" >}} +{{< expand "s3cmd" >}} Linux or macOS users must have the [s3cmd](https://s3tools.org/s3cmd) service installed before beginning this setup. On Windows, users can also refer to [S3Express](https://www.s3express.com/) for a similar command line experience. @@ -31,14 +31,14 @@ The `s3cmd --configure` command is available for Ubuntu or other Linux distribut {{< /hint >}} Enter the specified access key and the secret key. -Under the **S3 Endpoint**, enter the TrueNAS IP address followed by TCP port, and reply **N** to the DNS-style bucket+hostname. +Under the **S3 Endpoint**, enter the TrueNAS IP address followed by TCP port, and reply **N** to the DNS-style bucket+hostname. Save the file. On Linux, the default is in the home directory \~/.s3cfg. If the connection has any issues, open .s3cfg again to troubleshoot. In Ubuntu, use command `nano .s3cfg` or `vi .s3cfg` or `gedit .s3cfg` depending on the preferred text editor. -For other operating systems, .s3cfg file location and editing tools may vary. +For other operating systems, .s3cfg file location and editing tools may vary. Scroll down to the host_bucket area. Make sure the %(bucket)s. portion is removed. The IP address should point to the *IP_address:TCP_port* for the system. @@ -64,7 +64,7 @@ On Windows PCs, the S3 Browser is another convenient way to connect to the MinIO To set it up, first [install the S3 Browser](https://s3-browser.en.uptodown.com/windows). -After installation completes, add a new account. +After installation completes, add a new account. ![AmazonS3NewAccount](/images/CORE/AmazonS3NewAccount.png "S3 Browser: New Account") @@ -78,6 +78,3 @@ It is possible to access, create new buckets, or upload files to created buckets ![AmazonS3Browser](/images/CORE/AmazonS3Browser.png "S3 Browser") {{< /expand >}} - -{{< taglist tag="cores3" vol="CORE" limit="5" >}} - \ No newline at end of file diff --git a/content/CORE/CORETutorials/SettingUIPreferences.md b/content/CORE/CORETutorials/SettingUIPreferences.md index c1d1f6db32..217f36b5a4 100644 --- a/content/CORE/CORETutorials/SettingUIPreferences.md +++ b/content/CORE/CORETutorials/SettingUIPreferences.md @@ -33,5 +33,3 @@ To create a custom theme, click **CREATE NEW THEME**. 4. Color selections display in the **Preview**. The **Preview** updates to reflect your current choices. You can turn this feature off. Click the **PREVIEW** tab then click the **Global Preview** toggle. This allows you to compare these selections with the currently active theme. 5. Go to the **GENERAL** tab and choose the primary, accent, and topbar colors for the theme. The color selections you made in the **COLORS** tab determine the options shown here. 6. Name and label the theme. Click **SUBMIT** to save it and add it to the options on the **Preferences** page. - -{{< taglist tag="coreinterfacepref" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SettingUpUsersAndGroups.md b/content/CORE/CORETutorials/SettingUpUsersAndGroups.md index facf82ed71..5be893fa7c 100644 --- a/content/CORE/CORETutorials/SettingUpUsersAndGroups.md +++ b/content/CORE/CORETutorials/SettingUpUsersAndGroups.md @@ -159,5 +159,3 @@ To manage group membership, go to **Accounts > Groups**, click the . Select multiple users by holding CTRL while clicking each entry. - -{{< taglist tag="users" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Sharing/AFPShare.md b/content/CORE/CORETutorials/Sharing/AFPShare.md index b7fdff7a27..23111b3385 100644 --- a/content/CORE/CORETutorials/Sharing/AFPShare.md +++ b/content/CORE/CORETutorials/Sharing/AFPShare.md @@ -67,5 +67,3 @@ Enter `afp://{IPofTrueNASsystem}` and click **Connect**. For example, entering `afp://192.168.2.2` connects to the TrueNAS AFP share at 192.168.2.2. ![Apple AFP Connect](/images/CORE/AppleAFPConnect.png "Apple AFP Connect") - -{{< taglist tag="coreafp" vol="CORE" limit="5" >}} \ No newline at end of file diff --git a/content/CORE/CORETutorials/Sharing/NFSShare.md b/content/CORE/CORETutorials/Sharing/NFSShare.md index 80ca8a7f14..17a6088674 100644 --- a/content/CORE/CORETutorials/Sharing/NFSShare.md +++ b/content/CORE/CORETutorials/Sharing/NFSShare.md @@ -85,5 +85,3 @@ Go to **Advanced Options** and change the **Access** settings. {{< hint type=important >}} ESXI 6.7 or later is required for read/write functionality with NFSv4 shares. {{< /hint >}} - -{{< taglist tag="corenfs" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Sharing/SMB/HomeShare.md b/content/CORE/CORETutorials/Sharing/SMB/HomeShare.md index ac669b3262..e0c22e425e 100644 --- a/content/CORE/CORETutorials/Sharing/SMB/HomeShare.md +++ b/content/CORE/CORETutorials/Sharing/SMB/HomeShare.md @@ -68,5 +68,3 @@ If existing users require access to the home share, go to **Accounts > Users** a Adjust the user home directory to the appropriate dataset and give it a name to create their own directory. After the user accounts have been added and permissions configured, users can log in to the share and see a folder matching their user name. - -{{< taglist tag="coresmb" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Sharing/SMB/ManagingSMBShares.md b/content/CORE/CORETutorials/Sharing/SMB/ManagingSMBShares.md index 3a5d772786..b5a7596691 100644 --- a/content/CORE/CORETutorials/Sharing/SMB/ManagingSMBShares.md +++ b/content/CORE/CORETutorials/Sharing/SMB/ManagingSMBShares.md @@ -88,11 +88,8 @@ Has three entries: {{< /nest-expand >}} {{< /expand >}} - ### Adding ACL Entries (ACEs) To define permissions for a specific user account or group, click **ADD ACL ITEM**. Open the **Who** dropdown list, select **User** or **Group**, and select a specific user or group account. Define the settings for the account. Define the permissions to apply to that account. For example, to allow the *tmoore* user permission to view dataset contents but not make changes, define the **ACL Type** as **Allow**. Define **Permissions** for this user as **Read**. ![ExampleACE](/images/CORE/Storage/StoragePoolsEditACLExample.png "Sample ACE") - -{{< taglist tag="coresmb" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Sharing/SMB/SMBShare.md b/content/CORE/CORETutorials/Sharing/SMB/SMBShare.md index ae7e3b0d19..df88520262 100644 --- a/content/CORE/CORETutorials/Sharing/SMB/SMBShare.md +++ b/content/CORE/CORETutorials/Sharing/SMB/SMBShare.md @@ -165,5 +165,3 @@ Mount the volume. `sudo mount_smbfs -I computer_name\share_name /mnt/smb_share`. {{< /nest-expand >}} {{< /expand >}} - -{{< taglist tag="coresmb" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Sharing/SMB/ShadowCopies.md b/content/CORE/CORETutorials/Sharing/SMB/ShadowCopies.md index 7e77cdb213..479f203ecb 100644 --- a/content/CORE/CORETutorials/Sharing/SMB/ShadowCopies.md +++ b/content/CORE/CORETutorials/Sharing/SMB/ShadowCopies.md @@ -37,5 +37,3 @@ To work around this issue, edit the Windows registry. Use **Regedit** and go to The **DWORD AllowInsecureGuestAuth** is an incorrect value: **0x00000000**. Change this value to **0x00000001** (Hexadecimal 1) to allow adjusting the settings in gpedit.msc. You can apply this to a fleet of Windows machines with a Group Policy Update. {{< /expand >}} - -{{< taglist tag="coresmb" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Sharing/WebDAVShare.md b/content/CORE/CORETutorials/Sharing/WebDAVShare.md index 13d2241618..14947fcbf9 100644 --- a/content/CORE/CORETutorials/Sharing/WebDAVShare.md +++ b/content/CORE/CORETutorials/Sharing/WebDAVShare.md @@ -67,5 +67,3 @@ Example: *https://10.2.1.1:8081/newdataset* When the **Authentication** WebDAV service option is configured to either **Basic** or **Digest**, a user name and password is required. Enter the user name **webdav** and the password defined in the WebDAV service. - -{{< taglist tag="corewebdav" vol="CORE" limit="5" >}} \ No newline at end of file diff --git a/content/CORE/CORETutorials/Sharing/iSCSI/AddingiSCSIShare.md b/content/CORE/CORETutorials/Sharing/iSCSI/AddingiSCSIShare.md index 6e5d7b49b8..3d6cb9b7e7 100644 --- a/content/CORE/CORETutorials/Sharing/iSCSI/AddingiSCSIShare.md +++ b/content/CORE/CORETutorials/Sharing/iSCSI/AddingiSCSIShare.md @@ -19,27 +19,27 @@ Go to **Sharing > Block Shares (iSCSI)**. You can either set one up manually or ![SharingISCSIWizardDevice](/images/CORE/Sharing/SharingISCSIWizardDevice.png "iSCSI Wizard: Block Device") -On **Create or Choose Block Device**: +On **Create or Choose Block Device**: -1. Enter a name for the iSCSI share. It can only contain lowercase alphanumeric characters plus a dot (.), dash (-), or colon (:). We recommend keeping the name short or at most 63 characters. +1. Enter a name for the iSCSI share. It can only contain lowercase alphanumeric characters plus a dot (.), dash (-), or colon (:). We recommend keeping the name short or at most 63 characters. 2. Choose the **Extent Type**. * If the **Extent Type** is **Device**, select the Zvol to share from the **Device** menu. - + * If the **Extent Type** is **File**, select the path to the extent and indicate the file size. 3. Select the type of platform to use for the share. For example, if using the share from an updated Linux OS, choose **Modern OS**. 4. Click **Next**. The **Portals** screen displays. -5. Select an existing portal or click **Create New** to add a portal. - - If you create a new portal, you must select a discovery authentication method. - +5. Select an existing portal or click **Create New** to add a portal. + + If you create a new portal, you must select a discovery authentication method. + a. Select either **CHAP** or **MUTUAL CHAP** in the **Discovery Authentication Method** field. - b. Select either **None** or **Create New** in the **Discovery Authentication Group** field. **Create New** displays additional configuration fields. + b. Select either **None** or **Create New** in the **Discovery Authentication Group** field. **Create New** displays additional configuration fields. If you select **None** you can leave **Discovery Authentication Group** empty. c. Enter a number in the **Group ID** field to identify the group. @@ -48,13 +48,13 @@ On **Create or Choose Block Device**: e. Enter a password of 12 to 16 characters in the **Secret** field and again in **Secret (Confirm)**. - f. Select the IP address(es) to use. If adding more than one IP address, click **ADD** and then select the IP address. + f. Select the IP address(es) to use. If adding more than one IP address, click **ADD** and then select the IP address. Use **0.0.0.0.** to listen on all IPv4 or **::** to listen on all IPv6 IP addresses. G. Select the TCP port number to use if different from the default. H. Click Next to display the **Initiator** screen. - + 6. Enter the initiator information to use. Decide which initiators or networks can use the iSCSI share. Leave the list empty to allow all initiators or networks, or add entries to the list to limit access to those systems. Use the keyboard Enter between each entry. Click **Next** to display the **Confirm Options** screen. 7. Confirm the settings you entered. To change any setting click **BACK** until you see the screen where you want to make changes. @@ -66,30 +66,30 @@ On **Create or Choose Block Device**: To add or edit an existing iSCSI share, use the seven tab to access the various iSCSI configuration screens. 1. Configure the share global configuration settings. Click the **Target Global Configuration** tab. - + ![SharingISCSIManualTargetGlobalConfig](/images/CORE/Sharing/SharingISCSIManualTargetGlobalConfig.png "iSCSI Target Global Configuration") 2. Configure the portal settings. Click on the **Portals** tab. - + ![SharingISCSIManualPortals](/images/CORE/Sharing/SharingISCSIManualPortals.png "iSCSI Portal") To add a new portal, click **ADD** and enter the basic and IP address information. - + To edit an existing portal, click next to the portal and select **Edit**. ![SharingISCSIManualPortalsForm](/images/CORE/Sharing/SharingISCSIManualPortalsForm.png "iSCSI Portals Form") - + 3. Configure the initiator settings (not required). Click on the **Initiators Groups** tab. Both the **Add** and **Edit** forms have the same settings fields. - - ![iSCSIAddInitiators](/images/CORE/Sharing/iSCSIAddInitiators.png "iSCSI Add Initiators") - - Use **ADD** to display the **Initiators Add** configuration screen. + + ![iSCSIAddInitiators](/images/CORE/Sharing/iSCSIAddInitiators.png "iSCSI Add Initiators") + + Use **ADD** to display the **Initiators Add** configuration screen. Either leave **Allow All Initiators** checked or configure your own allowed initiators and authorized networks. - - Click the icon for the initiator group and select **Edit** to display the **Initiator Group Edit** configuration screen. + + Click the icon for the initiator group and select **Edit** to display the **Initiator Group Edit** configuration screen. 4. Configure authorized access networks. Click the **Authorized Access** tab. - + ![SharingISCSIManualAuthorizedAccessForm](/images/CORE/Sharing/SharingISCSIManualAuthorizedAccessForm.png "iSCSI Authorized Access Form") Click **ADD** to add a new authorized access network. Fill out the group, user and peer user information. @@ -97,7 +97,7 @@ To add or edit an existing iSCSI share, use the seven tab to access the various Click next to the authorized access network and select **Edit**. 5. Configure targets. Click the **Targets** tab. - + ![SharingISCSIManualTargetsForm](/images/CORE/Sharing/SharingISCSIManualTargetsForm.png "iSCSI Targets Form") To add a new target, click **ADD** and enter the basic and iSCSI group information. @@ -105,15 +105,15 @@ To add or edit an existing iSCSI share, use the seven tab to access the various To edit an existing target, click next to it and select **Edit**. 6. Configure extents. Click the **Extents** tab. - + ![SharingISCSIManualExtentsForm](/images/CORE/Sharing/SharingISCSIManualExtentsForm.png "iSCSI Extents Form") To add a new extent, click **ADD** and enter the basic, type, and compatibility information. - + To edit an existing extent, click next to it and select **Edit**. 7. Configure any associated targets. Click on the **Associated Targets** tab. - + ![SharingISCSIManualAssociatedTargetsForm](/images/CORE/Sharing/SharingISCSIManualAssociatedTargetsForm.png "iSCSI Associated Targets Form") To add a new associated target, click **ADD** and fill out the information. @@ -129,5 +129,3 @@ To set it to start automatically when TrueNAS boots up, select the **Start Autom ![ServicesISCSIEnable](/images/CORE/Services/ServicesISCSIEnable.png "Starting the iSCSI Service") Click on the returns to the options in **Sharing > iSCSI**. - -{{< taglist tag="coreiscsi" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Sharing/iSCSI/IncreasingiSCSIAvailableStorage.md b/content/CORE/CORETutorials/Sharing/iSCSI/IncreasingiSCSIAvailableStorage.md index 76f02ba6e7..e853f1c721 100644 --- a/content/CORE/CORETutorials/Sharing/iSCSI/IncreasingiSCSIAvailableStorage.md +++ b/content/CORE/CORETutorials/Sharing/iSCSI/IncreasingiSCSIAvailableStorage.md @@ -13,7 +13,7 @@ tags: TrueNAS lets users expand Zvol and file-based LUNs to increase the available storage that the iSCSI shares. -### Expanding Zvol LUNs +### Expanding Zvol LUNs To expand a Zvol LUN, go to **Storage > Pools** and click the next to the Zvol LUN, then select **Edit Zvol**. @@ -24,14 +24,14 @@ Enter a new size in the **Size for this zvol** field, then click **SAVE**. ![ExpandingZvolLUNSize](/images/CORE/Storage/ExpandingZvolLUNSize.png "Change the Zvol Size") {{< hint type=tip >}} -To prevent data loss, the web interface does not allow users to reduce the Zvol size. +To prevent data loss, the web interface does not allow users to reduce the Zvol size. TrueNAS also does not allow users to increase the Zvol size past 80% of the pool size. {{< /hint >}} -### Expanding a File-Based LUN +### Expanding a File-Based LUN -To expand a file-based LUN, you need to know the path to the file. To find the path, go to **Sharing > Block Shares (iSCSI)** and click the **Extents** tab. -Click the next to the file-based LUN and select **Edit**. +To expand a file-based LUN, you need to know the path to the file. To find the path, go to **Sharing > Block Shares (iSCSI)** and click the **Extents** tab. +Click the next to the file-based LUN and select **Edit**. ![ExpandingFileLUNPath](/images/CORE/Storage/ExpandingFileLUNPath.png "Copy the Path to the File") @@ -44,5 +44,3 @@ Go to **Shell** and input command `truncate -s +[size] [path to file]` where *[s An example of the command could look like this: `truncate -s +2g /mnt/Shares/Dataset1/FileLun/FileLUN` Lastly, go back to the extent in **Sharing > Block Shares (iSCSI)** and make sure the **Filesize** is set to **0** so that the share uses the actual file size. - -{{< taglist tag="coreiscsi" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Sharing/iSCSI/SettingUpFibreChannel.md b/content/CORE/CORETutorials/Sharing/iSCSI/SettingUpFibreChannel.md index aba3de5a60..06d6986700 100644 --- a/content/CORE/CORETutorials/Sharing/iSCSI/SettingUpFibreChannel.md +++ b/content/CORE/CORETutorials/Sharing/iSCSI/SettingUpFibreChannel.md @@ -16,67 +16,64 @@ Fibre Channel is a TrueNAS Enterprise feature. Only TrueNAS systems licensed for ![Sharing ISCSI Fibre Channel Ports](/images/CORE/Sharing/SharingISCSIFibreChannelPorts.png "Sharing ISCSI Fibre Channel Ports") {{< /hint >}} -## Setting up a Fibre Channel ISCSI Share +## Setting up a Fibre Channel ISCSI Share {{< hint type=note >}} -This procedure uses an example to illustrate each step. +This procedure uses an example to illustrate each step. {{< /hint >}} - -1. Add a zvol to use for the share. +1. Add a zvol to use for the share. a. Go to **Storage > Pools**. - - b. Find an existing pool, click   and **Add zvol** to create a new zvol. - + + b. Find an existing pool, click   and **Add zvol** to create a new zvol. + ![StoragePoolsZvolFibreEnterprise](/images/CORE/Storage/StoragePoolsZvolFibreEnterprise.png "Creating a Zvol for Fibre Channel") 2. Configure these iSCSI tabs in **Sharing > Block Shares (iSCSI)**: - + {{< hint type=note >}} **Initiators** and **Authorized Access** screens only apply to iSCSI and can be ignored when configuring Fibre Channel. {{< /hint >}} - + a. **Portals**. Check for the **0.0.0.0:3260** IP and port number. If it doesn't exist, click **Add** and add this portal. - b. **Targets**. Click **Add** to set up a new target. Enter the values for your uses case in the **Target Name**, **Target Alias**, and **Portal Group**. + b. **Targets**. Click **Add** to set up a new target. Enter the values for your uses case in the **Target Name**, **Target Alias**, and **Portal Group**. Select the **Target Mode** option from **iSCSI**, **Fibre Channel** or **Both**. The **Initiator Group ID** selects which existing initiator group has access to the target. - - Options for the **Authentication Method** are **None**, **CHAP**, or **Mutual CHAP**. - + + Options for the **Authentication Method** are **None**, **CHAP**, or **Mutual CHAP**. + Set **Authentication Group Number** to either none or an integer. This value represents the number of existing authorized accesses. - + ![Sharing ISCSI Targets Add Fibre](/images/CORE/Sharing/SharingISCSITargetsAddFibre.png "ISCSI Targets: Fibre") - + The **Target** [Reporting]({{< relref "/CORE/UIReference/ReportingGraphs.md" >}}) tab provides Fibre Channel port bandwidth graphs. - + c. **Extents**. Click **Add** to create a new extent. - + ![ISCSIExtentsAddFibre](/images/CORE/Sharing/ISCSIExtentsAddFibre.png "ISCSI Extents Add Fibre") - d. **Associated Targets**. Click **Add** to add a new associated target. - - Select values for **Target** and **Extent**. + d. **Associated Targets**. Click **Add** to add a new associated target. + + Select values for **Target** and **Extent**. The LUN ID is a value between 0 and 1023. Some initiators expect a value below 256. Leave this field blank to automatically assign the next available ID. - + ![ISCSIAssocTargetAddFibre](/images/CORE/Sharing/ISCSIAssocTargetAddFibre.png "ISCSI Assoc Target: Add Fibre") 3. Set **Fibre Channel Ports**. - a. Click to expand the option for the port you want to select. - + a. Click to expand the option for the port you want to select. + b. Select the **Mode** as either **Initiators** or **Targets**. The **Targets** dropdown field displays on the right side of the screen. - + c. Select the target from the list. A list of **Connected Initiators displays below the **Targets** dropdown list field. - + ![Sharing ISCSI Targets Add Fibre](/images/CORE/Sharing/SharingISCSITargetsAddFibre.png "ISCSI Targets: Fibre") d. Select the initiator you want to use and then click **Save**. 4. Start the iSCSI service. Go to **Services** and click the **iSCSI** toggle until the **Running** status message displays. - -{{< taglist tag="coreiscsi" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Sharing/iSCSI/UsingiSCSIShare.md b/content/CORE/CORETutorials/Sharing/iSCSI/UsingiSCSIShare.md index ff3b3975cc..21e8683619 100644 --- a/content/CORE/CORETutorials/Sharing/iSCSI/UsingiSCSIShare.md +++ b/content/CORE/CORETutorials/Sharing/iSCSI/UsingiSCSIShare.md @@ -129,5 +129,3 @@ Finally, go to **This PC** or **My Computer** in File Explorer. The new iSCSI vo ![WindowsiSCSIVolumeLocation](/images/CORE/WindowsiSCSIVolumeLocation.png "Windows iSCSI Volume Location") {{< /expand >}} - -{{< taglist tag="coreiscsi" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Storage/Disks/DiskReplace.md b/content/CORE/CORETutorials/Storage/Disks/DiskReplace.md index 10b0b62de0..ee08bdeae9 100644 --- a/content/CORE/CORETutorials/Storage/Disks/DiskReplace.md +++ b/content/CORE/CORETutorials/Storage/Disks/DiskReplace.md @@ -87,7 +87,3 @@ For pools with large amounts of data, resilvering can take a long time. When the resilver completes, the pool status screen updates to show the new disk, and the pool status returns to **Online**. {{< trueimage src="/images/CORE/Storage/StoragePoolsStatusReplaceComplete.png" alt="Replacement Complete" id="Pool Status disk replacement complete" >}} - -{{< taglist tag="corerecovery" vol="CORE" limit="5" >}} - -{{< taglist tag="storage" vol="CORE" limit="5" title= "Related Storage Articles" >}} diff --git a/content/CORE/CORETutorials/Storage/Disks/DiskWipe.md b/content/CORE/CORETutorials/Storage/Disks/DiskWipe.md index f58adec038..b408528f40 100644 --- a/content/CORE/CORETutorials/Storage/Disks/DiskWipe.md +++ b/content/CORE/CORETutorials/Storage/Disks/DiskWipe.md @@ -45,7 +45,3 @@ When satisfied the disk can be wiped, select **Confirm** and click **CONTINUE**. A dialog shows the disk wipe progress. See [Disks Screens]({{< relref "DisksScreens.md" >}}) for more information on Disks screen settings. - -{{< taglist tag="corerecovery" vol="CORE" limit="5" >}} - -{{< taglist tag="storage" vol="CORE" limit="5" title= "Related Storage Articles" >}} diff --git a/content/CORE/CORETutorials/Storage/ImportDisk.md b/content/CORE/CORETutorials/Storage/ImportDisk.md index 7a9d6bff08..4361cf0b62 100644 --- a/content/CORE/CORETutorials/Storage/ImportDisk.md +++ b/content/CORE/CORETutorials/Storage/ImportDisk.md @@ -38,7 +38,3 @@ A dialog allows viewing or downloading the disk import log. Use the same import procedure to restart the task. Choose the same entry in **Destination Path** as the interrupted import for TrueNAS to scan the destination for previously imported files and resume importing any remaining files. {{< /expand >}} - -{{< taglist tag="storage" vol="CORE" limit="5" >}} - -{{< taglist tag="coredataset" vol="CORE" limit="5" title="Related Articles" >}} diff --git a/content/CORE/CORETutorials/Storage/Pools/Datasets.md b/content/CORE/CORETutorials/Storage/Pools/Datasets.md index 652f5d932a..8be63d3934 100644 --- a/content/CORE/CORETutorials/Storage/Pools/Datasets.md +++ b/content/CORE/CORETutorials/Storage/Pools/Datasets.md @@ -34,7 +34,6 @@ To quickly create a dataset with the default options, enter a name for the datas The **Name and Options** fields is required to create the dataset. Datasets typically inherit most of these settings from the root or parent dataset, only a dataset name is required before clicking **SUBMIT**. - See [Dataset Screens]({{< relref "/CORE/UIReference/Storage/Pools/DatasetsScreen.md" >}}) for more information on basic and advanced settings. By default, datasets inherit the **Encryption Options** from the root or parent dataset. @@ -115,6 +114,3 @@ To edit group quotas in bulk, click **Actions** and select **Set Quotas (Bulk)** {{< trueimage src="/images/CORE/Storage/StoragePoolsDatasetActionsGroupQuotasBulkEdit.png" alt="Group Quotas: Bulk Edit" id="Bulk Edit" >}} The same options for single groups are presented, along with choosing groups for these new quota rules. - -{{< taglist tag="coredataset" vol="CORE" limit="5" >}} -{{< taglist tag="corepool" vol="CORE" limit="5" title="Related Storage Pool Articles" >}} diff --git a/content/CORE/CORETutorials/Storage/Pools/FusionPool.md b/content/CORE/CORETutorials/Storage/Pools/FusionPool.md index 350ee558c5..c61e409ce2 100644 --- a/content/CORE/CORETutorials/Storage/Pools/FusionPool.md +++ b/content/CORE/CORETutorials/Storage/Pools/FusionPool.md @@ -8,9 +8,6 @@ tags: - corepools --- - {{< include file="/_includes/FusionPools.md" >}} See [Managing Pools]({{< relref "/CORE/CORETutorials/Storage/Pools/ManagingPools.md" >}}). - -{{< taglist tag="corepools" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Storage/Pools/ManagingPools.md b/content/CORE/CORETutorials/Storage/Pools/ManagingPools.md index 4ea3890e7f..864542ca24 100644 --- a/content/CORE/CORETutorials/Storage/Pools/ManagingPools.md +++ b/content/CORE/CORETutorials/Storage/Pools/ManagingPools.md @@ -97,5 +97,3 @@ It is not necessary to stop any sharing services to upgrade the pool. However, it is best to upgrade when the pool is not in heavy use. The upgrade process suspends I/O for a short period, but is nearly instantaneous on a quiet pool. {{< /expand >}} - -{{< taglist tag="storage" vol="CORE" limit="5" title="Related Storage Articles" >}} diff --git a/content/CORE/CORETutorials/Storage/Pools/Permissions.md b/content/CORE/CORETutorials/Storage/Pools/Permissions.md index baff05f28d..4fc95f43fc 100644 --- a/content/CORE/CORETutorials/Storage/Pools/Permissions.md +++ b/content/CORE/CORETutorials/Storage/Pools/Permissions.md @@ -142,7 +142,3 @@ Advanced flags offer finer control for applying an ACE to new files or directori * **No Propagate Inherit** (`n`): The ACE can only be inherited once. * **Inherit Only** (`i`): Remove the ACE from permission checks but allow it to be inherited by new files or subdirectories. Inherit Only is removed from these new objects. * **Inherited** (`I`): set when the ACE has been inherited from another dataset. - -{{< taglist tag="coredataset" vol="CORE" limit="5" >}} - -{{< taglist tag="storage" vol="CORE" limit="5" title="Related Storage Articles" >}} diff --git a/content/CORE/CORETutorials/Storage/Pools/PoolCreate.md b/content/CORE/CORETutorials/Storage/Pools/PoolCreate.md index bdac4e6220..4be067461b 100644 --- a/content/CORE/CORETutorials/Storage/Pools/PoolCreate.md +++ b/content/CORE/CORETutorials/Storage/Pools/PoolCreate.md @@ -148,6 +148,3 @@ For example, if two disks are added, TrueNAS automatically configures the vdev a {{< trueimage src="/images/CORE/Storage/StoragePoolsAddCreateMirror.png" alt="Mirrored Vdev" id="Mirrored Vdev" >}} To change the vdev layout, open the **Data VDevs** list and select the desired layout. - -{{< taglist tag="corepool" vol="CORE" limit="5" title="Related Pool Articles" >}} -{{< taglist tag="coredataset" vol="CORE" limit="5" title="Related Dataset Articles" >}} diff --git a/content/CORE/CORETutorials/Storage/Pools/PoolImport.md b/content/CORE/CORETutorials/Storage/Pools/PoolImport.md index d42135d347..ae6739673b 100644 --- a/content/CORE/CORETutorials/Storage/Pools/PoolImport.md +++ b/content/CORE/CORETutorials/Storage/Pools/PoolImport.md @@ -102,5 +102,3 @@ Do *not* select **Destroy data on this pool?**. Now import the pool again. During the import, add the encryption keys as described previously. {{< /expand >}} - -{{< taglist tag="storage" vol="CORE" limit="5" title="Related Storage Articles" >}} diff --git a/content/CORE/CORETutorials/Storage/Pools/SLOGOverprovision.md b/content/CORE/CORETutorials/Storage/Pools/SLOGOverprovision.md index 757e90b431..9915ae63ea 100644 --- a/content/CORE/CORETutorials/Storage/Pools/SLOGOverprovision.md +++ b/content/CORE/CORETutorials/Storage/Pools/SLOGOverprovision.md @@ -45,5 +45,3 @@ The command to over-provision an SSD is `disk_resize {DEVICE} {SIZE}`, where *{D Example: `disk_resize ada5 16GB`. When no size is specified, it reverts the provision back the full size of the device. {{< /expand >}} - -{{< taglist tag="storage" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Storage/Pools/StorageEncryption.md b/content/CORE/CORETutorials/Storage/Pools/StorageEncryption.md index 12bf32aa39..de1d519324 100644 --- a/content/CORE/CORETutorials/Storage/Pools/StorageEncryption.md +++ b/content/CORE/CORETutorials/Storage/Pools/StorageEncryption.md @@ -196,8 +196,7 @@ To not encrypt the dataset on the remote side so it does not require a key to un 4. Click **SUBMIT**. {{< /expand >}} - -{{< hint type=note >}} +{{< hint type=tip >}} This does not affect TrueNAS Enterprise installs with [KMIP]({{< relref "/CORE/UIReference/System/KMIP.md" >}}). {{< /hint >}} @@ -286,6 +285,3 @@ Legend: Back up your key file immediately! 7. Repeat this process for every dataset in the pool that you need to migrate. {{< /expand >}} - -{{< taglist tag="coredataset" vol="CORE" limit="5" title="Related Dataset Articles" >}} -{{< taglist tag="corepool" vol="CORE" limit="5" title="Related Pool Articles" >}} diff --git a/content/CORE/CORETutorials/Storage/Pools/Zvols.md b/content/CORE/CORETutorials/Storage/Pools/Zvols.md index 925a7f3273..19300d5ecb 100644 --- a/content/CORE/CORETutorials/Storage/Pools/Zvols.md +++ b/content/CORE/CORETutorials/Storage/Pools/Zvols.md @@ -74,5 +74,3 @@ When a clone is promoted, the original volume becomes a clone of the clone, maki Otherwise, a clone cannot be deleted while the original volume exists. When the zvol is created with [encryption]({{< relref "/CORE/CORETutorials/Storage/Pools/StorageEncryption.md" >}}) enabled, additional **Encryption Actions** are displayed. - -{{< taglist tag="storage" vol="CORE" limit="5" title="Related Storage Articles" >}} diff --git a/content/CORE/CORETutorials/Storage/SED.md b/content/CORE/CORETutorials/Storage/SED.md index 000e7ac6d1..c7f8416012 100644 --- a/content/CORE/CORETutorials/Storage/SED.md +++ b/content/CORE/CORETutorials/Storage/SED.md @@ -232,5 +232,3 @@ If it fails use: `sedutil-cli --PSIDrevert /dev/` {{< /nest-expand >}} {{< /expand >}} - -{{< taglist tag="storage" vol="CORE" limit="5" title="Related Storage Articles" >}} diff --git a/content/CORE/CORETutorials/Storage/Snapshots.md b/content/CORE/CORETutorials/Storage/Snapshots.md index ed26930a24..baadb1852d 100644 --- a/content/CORE/CORETutorials/Storage/Snapshots.md +++ b/content/CORE/CORETutorials/Storage/Snapshots.md @@ -85,13 +85,13 @@ Rollback is a dangerous operation that causes any configured replication tasks t Replications use the existing snapshot when doing an incremental backup, and rolling back can put the snapshots out of order. To restore the data within a snapshot, the recommended steps are: -1. Clone the desired snapshot. +1. Clone the desired snapshot. -2. Share the clone with the share type or service running on the TrueNAS system. +2. Share the clone with the share type or service running on the TrueNAS system. -3. Allow users to recover their needed data. +3. Allow users to recover their needed data. -4. Delete the clone from **Storage > Pools**. +4. Delete the clone from **Storage > Pools**. This approach does not destroy any on-disk data and has no impact on replication. {{< /hint >}} @@ -110,6 +110,3 @@ Clicking **Yes** reverts all dataset files to the state they were in at the time A user with permission to access the hidden file can view and explore all snapshots for a dataset from the **Shell** or the **Sharing** screen using services like **SMB**, **NFS**, and **SFTP**. {{< include file="/_includes/BrowsingSnapshotCollections2.md" >}} - -{{< taglist tag="coresnapshots" vol="CORE" limit="5" >}} - diff --git a/content/CORE/CORETutorials/Storage/VMware-Snapshots.md b/content/CORE/CORETutorials/Storage/VMware-Snapshots.md index fcd502dd08..e106d1c3f2 100644 --- a/content/CORE/CORETutorials/Storage/VMware-Snapshots.md +++ b/content/CORE/CORETutorials/Storage/VMware-Snapshots.md @@ -35,5 +35,3 @@ After entering the **Hostname**, **Username**, and **Password**, click **FETCH D TrueNAS connects to the VMware host after clicking *FETCH DATASTORES*. The **ZFS Filesystem** and **Datastore** drop-down menus populate from the VMware host response. Choosing a datastore also selects any previously mapped dataset. - -{{< taglist tag="coresnapshots" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/ConfiguringACMEDNS.md b/content/CORE/CORETutorials/SystemConfiguration/ConfiguringACMEDNS.md index 1791d2b19c..f8f9a18d7b 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/ConfiguringACMEDNS.md +++ b/content/CORE/CORETutorials/SystemConfiguration/ConfiguringACMEDNS.md @@ -47,5 +47,3 @@ To create a new ACME certificate, go to **System > Certificates**, click }} diff --git a/content/CORE/CORETutorials/SystemConfiguration/ConfiguringFailover.md b/content/CORE/CORETutorials/SystemConfiguration/ConfiguringFailover.md index 77c49d0f05..0580aee57b 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/ConfiguringFailover.md +++ b/content/CORE/CORETutorials/SystemConfiguration/ConfiguringFailover.md @@ -86,5 +86,3 @@ To have the system wait to failover during a network timeout, replace *0* with a Do not sync the TrueNAS configuration unless directed by an iXsystems Support Engineer! TrueNAS automatically synchronizes the system configuration. The manual sync options are only for dangerous or high-risk troubleshooting situations. {{< /hint >}} - -{{< taglist tag="corefailover" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/ConfiguringKMIP.md b/content/CORE/CORETutorials/SystemConfiguration/ConfiguringKMIP.md index bb1a1ec83d..43be9d2418 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/ConfiguringKMIP.md +++ b/content/CORE/CORETutorials/SystemConfiguration/ConfiguringKMIP.md @@ -64,5 +64,3 @@ Refresh the **KMIP** screen to show the current **KMIP Key Status**. ![SystemKMIPKeyStatus](/images/CORE/System/SystemKMIPKeyStatus.png "Example Key Synced") If you want to cancel a pending key synchronization, set *Force Clear* and click *SAVE*. - -{{< taglist tag="corekmip" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/ConfiguringSSHConnections.md b/content/CORE/CORETutorials/SystemConfiguration/ConfiguringSSHConnections.md index b6c27c523a..a8c951259e 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/ConfiguringSSHConnections.md +++ b/content/CORE/CORETutorials/SystemConfiguration/ConfiguringSSHConnections.md @@ -71,7 +71,3 @@ Log back into the local TrueNAS system and go to **System > SSH Connections**. A ![SystemSSHConnectionsAddManual](/images/CORE/System/SystemSSHConnectionsAddManual.png "SSH Connections: Manual Options") Select the private key from the SSH keypair you used when you transferred the public key on the remote NAS. - -{{< taglist tag="coressh" vol="CORE" limit="5" >}} - -{{< taglist tag="corereplication" vol="CORE" limit="5" title="Related Replication Articles" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/ConfiguringTunables.md b/content/CORE/CORETutorials/SystemConfiguration/ConfiguringTunables.md index 2192ddb6b3..b245b3b948 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/ConfiguringTunables.md +++ b/content/CORE/CORETutorials/SystemConfiguration/ConfiguringTunables.md @@ -72,5 +72,3 @@ You cannot manually tune any setting the autotuner controlls. To permanently change a value set by autotune, change the description of the tunable. For example, changing the description to "*manual override*" prevents autotune from reverting the tunable back to the autotune default value. {{< /expand >}} - -{{< taglist tag="coretunables" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/ConfiguringtheSystemEmail.md b/content/CORE/CORETutorials/SystemConfiguration/ConfiguringtheSystemEmail.md index fa82fe03a5..171d6dc93c 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/ConfiguringtheSystemEmail.md +++ b/content/CORE/CORETutorials/SystemConfiguration/ConfiguringtheSystemEmail.md @@ -29,5 +29,3 @@ Next, select a **Send Mail Method** and fill out the remaining fields (SMTP) or Click **SEND TEST MAIL** to verify the configured email settings are working. If the test email fails, double-check that the root user **Email** field is correctly configured. - -{{< taglist tag="coreemail" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/CreatingAlerts.md b/content/CORE/CORETutorials/SystemConfiguration/CreatingAlerts.md index 09cab8f2e2..e0d694df80 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/CreatingAlerts.md +++ b/content/CORE/CORETutorials/SystemConfiguration/CreatingAlerts.md @@ -33,5 +33,3 @@ Customize each alert **Warning Level** and **Frequency** using the drop-down men Changing any of these options affects every configured alert service. Click **SAVE** before leaving the page. - -{{< taglist tag="corecreatealerts" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/CreatingCAsandCertificates/CreatingCertificateAuthorities.md b/content/CORE/CORETutorials/SystemConfiguration/CreatingCAsandCertificates/CreatingCertificateAuthorities.md index 069626fa11..89a0e505ef 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/CreatingCAsandCertificates/CreatingCertificateAuthorities.md +++ b/content/CORE/CORETutorials/SystemConfiguration/CreatingCAsandCertificates/CreatingCertificateAuthorities.md @@ -113,5 +113,3 @@ Before deleting a CA, verify it is not used by another service such as S3, FTP, Also, before you can delete a CA, you need to delete certificates issued by the CA or those relying on the CA. If you receive an error that mentions foreign keys reference, ensure the certificates on your system do not use the CA you want to delete. - -{{< taglist tag="corecertificates" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/CreatingCAsandCertificates/CreatingCertificates.md b/content/CORE/CORETutorials/SystemConfiguration/CreatingCAsandCertificates/CreatingCertificates.md index f94d193d35..b8ab52a3a5 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/CreatingCAsandCertificates/CreatingCertificates.md +++ b/content/CORE/CORETutorials/SystemConfiguration/CreatingCAsandCertificates/CreatingCertificates.md @@ -182,5 +182,3 @@ To import a certificate signing request (CSR): 4. Enter and confirm the Private Key **Passphrase**. 5. Click **Submit**. - -{{< taglist tag="corecertificates" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/ManagingBootEnvironments.md b/content/CORE/CORETutorials/SystemConfiguration/ManagingBootEnvironments.md index a29b11e44a..fe6aacc6bc 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/ManagingBootEnvironments.md +++ b/content/CORE/CORETutorials/SystemConfiguration/ManagingBootEnvironments.md @@ -85,5 +85,3 @@ Click **Boot Pool Status** to see the status of each boot-pool device, including ### Scrub the Boot Pool Click **Scrub Boot Pool** to perform a manual (data integrity check) of the operating system device. - -{{< taglist tag="coreboot" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/MirroringtheBootPool.md b/content/CORE/CORETutorials/SystemConfiguration/MirroringtheBootPool.md index 992015f7b4..4bf05211ed 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/MirroringtheBootPool.md +++ b/content/CORE/CORETutorials/SystemConfiguration/MirroringtheBootPool.md @@ -39,5 +39,3 @@ When you select **Use all disk space**, TrueNAS uses the entire capacity of the If the original operating system device fails and is detached, the boot mirror changes to consist of just the newer device and grows to whatever capacity it provides. However, new devices added to this mirror must now be as large as the new capacity. {{< /expand >}} - -{{< taglist tag="coreboot" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/SettingtheSystemDataset.md b/content/CORE/CORETutorials/SystemConfiguration/SettingtheSystemDataset.md index 2e07275bd8..5e97080fb4 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/SettingtheSystemDataset.md +++ b/content/CORE/CORETutorials/SystemConfiguration/SettingtheSystemDataset.md @@ -44,5 +44,3 @@ You cannot move the system dataset to a passphrase-encrypted or read-only pool. {{< /hint >}} If a user changes the pool storing the system dataset later, TrueNAS migrates the existing data in the system dataset to the new location. - -{{< taglist tag="coredataset" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/UsingConfigurationBackups.md b/content/CORE/CORETutorials/SystemConfiguration/UsingConfigurationBackups.md index e262549f14..1b8e4a47b3 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/UsingConfigurationBackups.md +++ b/content/CORE/CORETutorials/SystemConfiguration/UsingConfigurationBackups.md @@ -77,5 +77,3 @@ After resetting the system configuration, the system restarts, and you must set Users can restore configurations by going to **System > General** and clicking **UPLOAD CONFIG**. When uploading a config, you can select any previously saved config files for their system. - -{{< taglist tag="coreconfigbackup" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/UsingTwoFactorAuthentication.md b/content/CORE/CORETutorials/SystemConfiguration/UsingTwoFactorAuthentication.md index 3e38046876..3b06b9b605 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/UsingTwoFactorAuthentication.md +++ b/content/CORE/CORETutorials/SystemConfiguration/UsingTwoFactorAuthentication.md @@ -55,5 +55,3 @@ Set **Log in as Root with Password** and click **SAVE**. Toggle the **SSH** serv Open a Command Prompt or Terminal and SSH into TrueNAS using the system hostname or IP address, *root* account username and password, and the 2FA code from the mobile device. {{< /expand >}} - -{{< taglist tag="core2fa" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/SystemConfiguration/ViewingEnclosures.md b/content/CORE/CORETutorials/SystemConfiguration/ViewingEnclosures.md index a78ba7a258..16bdfe1001 100644 --- a/content/CORE/CORETutorials/SystemConfiguration/ViewingEnclosures.md +++ b/content/CORE/CORETutorials/SystemConfiguration/ViewingEnclosures.md @@ -37,5 +37,3 @@ In the **Disks** tab, select a disk on the enclosure image and click **IDENTIFY {{< hint type=note >}} The TrueNAS Mini Series models do not support drive light identification. {{< /hint >}} - -{{< taglist tag="corehardware" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Tasks/CreatingCloudSyncTasks.md b/content/CORE/CORETutorials/Tasks/CreatingCloudSyncTasks.md index a694ef53bc..b4f57805d7 100644 --- a/content/CORE/CORETutorials/Tasks/CreatingCloudSyncTasks.md +++ b/content/CORE/CORETutorials/Tasks/CreatingCloudSyncTasks.md @@ -143,7 +143,3 @@ Give the new task a **Description** and define the path to a storage location fo TrueNAS saves the restored cloud sync task as another entry in **Tasks > Cloud Sync Tasks**. If the restore destination dataset is the same as the original source dataset, the restored files might have their ownership altered to _root_. If _root_ did not create the original files and they need a different owner, you can recursively reset ACL Permissions of the restored dataset through the GUI or by running `chown` from the CLI. - -{{< taglist tag="corecloudsynctasks" vol="CORE" limit="5" >}} - -{{< taglist tag="coredatabackuptasks" vol="CORE" limit="5" title="Related Data Backup Articles" >}} diff --git a/content/CORE/CORETutorials/Tasks/CreatingCronJobs.md b/content/CORE/CORETutorials/Tasks/CreatingCronJobs.md index c6d401e41c..c5e7a6457c 100644 --- a/content/CORE/CORETutorials/Tasks/CreatingCronJobs.md +++ b/content/CORE/CORETutorials/Tasks/CreatingCronJobs.md @@ -47,7 +47,3 @@ Go to **Tasks > Cron Jobs** and click the ne Clicking **RUN NOW** immediately starts the job **Command**, separately from any **Schedule**. **EDIT** changes any setting available during task creation. **DELETE** removes the cron job from TrueNAS. Once you delete a cron job, you cannot restore the job configuration. - -{{< taglist tag="corecronjobs" vol="CORE" limit="5" >}} - -{{< taglist tag="coresystemleveltasks" vol="CORE" limit="5" title="Related System Level Tasks" >}} diff --git a/content/CORE/CORETutorials/Tasks/CreatingInitShutdownScripts.md b/content/CORE/CORETutorials/Tasks/CreatingInitShutdownScripts.md index a5f7f6c748..587688dc25 100644 --- a/content/CORE/CORETutorials/Tasks/CreatingInitShutdownScripts.md +++ b/content/CORE/CORETutorials/Tasks/CreatingInitShutdownScripts.md @@ -54,7 +54,3 @@ All init/shutdown scripts are run with `sh`. All saved Init/Shutdown tasks are in **Tasks > Init/Shutdown Scripts**. Click (Options) next to a task to **EDIT** or **DELETE** that task. - -{{< taglist tag="coreinitshutdownscripts" vol="CORE" limit="5" >}} - -{{< taglist tag="coresystemleveltasks" vol="CORE" limit="5" title="Related System Level Tasks Articles" >}} diff --git a/content/CORE/CORETutorials/Tasks/CreatingPeriodicSnapshotTasks.md b/content/CORE/CORETutorials/Tasks/CreatingPeriodicSnapshotTasks.md index 1a5be01a2f..109264b0d7 100644 --- a/content/CORE/CORETutorials/Tasks/CreatingPeriodicSnapshotTasks.md +++ b/content/CORE/CORETutorials/Tasks/CreatingPeriodicSnapshotTasks.md @@ -78,7 +78,3 @@ Click **SUBMIT** to save the task in **Tasks > Periodic Snapshot Tasks**. You can find any snapshots from this task in **Storage > Snapshots**. To check the log for a saved snapshot schedule, go to **Tasks > Periodic Snapshot Tasks** and click the task **State**. - -{{< taglist tag="coresnapshots" vol="CORE" limit="5" >}} - -{{< taglist tag="corezfstasks" vol="CORE" limit="5" title="Related ZFS Tasks Articles">}} diff --git a/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/AdvancedReplication.md b/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/AdvancedReplication.md index d91b01883a..e37169877b 100644 --- a/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/AdvancedReplication.md +++ b/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/AdvancedReplication.md @@ -144,7 +144,3 @@ Setting the **Schedule** checkbox allows scheduling the replication to run at a Setting **Only Replicate Snapshots Matching Schedule** restricts the replication to only replicate those snapshots created at the same time as the replication schedule. ![TasksReplicationAddAdvancedSchedule](/images/CORE/Tasks/TasksReplicationAddAdvancedSchedule.png "Advanced Replication: Schedule") - -{{< taglist tag="corereplication" vol="CORE" limit="5" >}} - -{{< taglist tag="coressh" vol="CORE" limit="5" title="Related SSH Articles" >}} diff --git a/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/LocalReplication.md b/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/LocalReplication.md index cfd966da30..d02209514f 100644 --- a/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/LocalReplication.md +++ b/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/LocalReplication.md @@ -80,5 +80,3 @@ Clicking the task state shows the replication log with an option to download it To confirm that snapshots replicated, go to **Storage > Snapshots** and verify the destination dataset has new snapshots with correct timestamps. ![TasksReplicationTasksLocalSnapshots](/images/CORE/Tasks/TasksReplicationTasksLocalSnapshots.png "Finding Replicated Snapshots") - -{{< taglist tag="corereplication" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/RemoteReplication.md b/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/RemoteReplication.md index 3a9af79b09..0c4426fe29 100644 --- a/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/RemoteReplication.md +++ b/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/RemoteReplication.md @@ -77,9 +77,8 @@ Adding a name to the end of the path creates a new dataset in that location. ![TasksReplicationTasksAddRemoteDest](/images/CORE/Tasks/TasksReplicationTasksAddRemoteDest.png "Replication with Remote Destination") - ![TasksReplicationTasksAddRemoteDestEncrypt](/images/CORE/Tasks/remote_rep_encrypt.png "Remote Destination Encryption Options") - + **Encryption**: To use encryption when replicating data, check the Encryption box. * *Encryption Key Format* allows the user to choose between a Hex (base 16 numeral) or Passphrase (alphanumeric) style encryption key. * *Store Encryption key in Sending TrueNAS database* allows the user to either store the Encryption key in the sending TrueNAS database (box checked) or choose a temporary location for the encryption key to decrypt replicated data (box unchecked). @@ -98,9 +97,6 @@ NETCAT uses common port settings, but these can be overridden by switching to th TrueNAS suggests a name based on the selected sources and destination, but you can overwrite it with a custom name. - -## Schedule and Lifetime - Adding a schedule automates the task to run according to your chosen times. You can choose between several preset schedules or create a custom schedule for when the replication runs. Choosing to run the replication once runs the replication immediately after saving the task, but you must manually trigger any additional replications. @@ -119,7 +115,3 @@ Later replications run faster, as only the subsequent changes to snapshots repli Clicking the task state opens the log for that task. ![TasksReplicationTasksRemoteLogs](/images/CORE/Tasks/TasksReplicationTasksRemoteLogs.png "Remote Replication Log") - -{{< taglist tag="corereplication" vol="CORE" limit="5" >}} - -{{< taglist tag="coressh" vol="CORE" limit="5" title="Related SSH Articles" >}} diff --git a/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/TroubleshootingTips.md b/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/TroubleshootingTips.md index 999d9bd6ea..5e8a309ba1 100644 --- a/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/TroubleshootingTips.md +++ b/content/CORE/CORETutorials/Tasks/CreatingReplicationTasks/TroubleshootingTips.md @@ -57,5 +57,3 @@ See [**Alert Settings**]({{< relref "CORE/UIReference/System/AlertSettings.md" > **Question**: If a site changes a lot of data at once and the internet bandwidth is not enough to finish sending the snapshot before the next one begins, do the replication jobs run one after the other and not stomp on each other? **Answer**: Yes. - -{{< taglist tag="corereplication" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Tasks/CreatingRsyncTasks.md b/content/CORE/CORETutorials/Tasks/CreatingRsyncTasks.md index a22133c4af..8b7359915f 100644 --- a/content/CORE/CORETutorials/Tasks/CreatingRsyncTasks.md +++ b/content/CORE/CORETutorials/Tasks/CreatingRsyncTasks.md @@ -125,7 +125,3 @@ You can still run the rsync task by going to **Tasks > Rsync Tasks** and clickin The rsync task does not work when the related system service is off. To turn the rsync service on, go to **Services** and click the **rsync** toggle button. The toggle button turns blue when the service is on. See [Configuring Rsync]({{< relref "ConfiguringRsync.md" >}}) for more information on rsync configuration and module creation. - -{{< taglist tag="corersync" vol="CORE" limit="5" >}} - -{{< taglist tag="coredatabackuptasks" vol="CORE" limit="5" title="Related Data Backup Articles" >}} diff --git a/content/CORE/CORETutorials/Tasks/CreatingScrubTasks.md b/content/CORE/CORETutorials/Tasks/CreatingScrubTasks.md index f6885fe968..b6e531e5d3 100644 --- a/content/CORE/CORETutorials/Tasks/CreatingScrubTasks.md +++ b/content/CORE/CORETutorials/Tasks/CreatingScrubTasks.md @@ -25,5 +25,3 @@ To create a scrub task for a pool, go to **Tasks > Scrub Tasks** and click **ADD ![TasksScrubTasksAdd](/images/CORE/Tasks/TasksScrubTasksAdd.png "Creating a new Scrub Task") Select a **Pool**, enter the **Threshold** (in days), and give the scrub a description. Assign a **Schedule** and click **SUBMIT**. - -{{< taglist tag="corescrub" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Tasks/GoogleDriveSync.md b/content/CORE/CORETutorials/Tasks/GoogleDriveSync.md index 8e179f6911..bde45a8bc8 100644 --- a/content/CORE/CORETutorials/Tasks/GoogleDriveSync.md +++ b/content/CORE/CORETutorials/Tasks/GoogleDriveSync.md @@ -85,5 +85,3 @@ Once the sync reports **SUCCESS**, you can verify it by opening the folder on an ## Working with Google-Created Content {{< include file="content/_includes/GoogleDriveBadPermissions.md" >}} - -{{< taglist tag="corecloudsynctasks" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Tasks/RunningSMARTTests.md b/content/CORE/CORETutorials/Tasks/RunningSMARTTests.md index 5eab72d147..1c6b703f3e 100644 --- a/content/CORE/CORETutorials/Tasks/RunningSMARTTests.md +++ b/content/CORE/CORETutorials/Tasks/RunningSMARTTests.md @@ -91,7 +91,3 @@ You must [enable S.M.A.R.T. service]({{< relref "CORE/CORETutorials/Services/Con Disable the S.M.A.R.T. service when using a RAID disk controller. The controller monitors S.M.A.R.T. separately and marks disks as a **Predictive Failure** on a test failure. {{< /expand >}} - -{{< taglist tag="coresmart" vol="CORE" limit="5" >}} - -{{< taglist tag="coresystemleveltasks" vol="CORE" limit="5" title="Related System Level Tasks Articles" >}} diff --git a/content/CORE/CORETutorials/Tasks/UsingAdvancedScheduler.md b/content/CORE/CORETutorials/Tasks/UsingAdvancedScheduler.md index 875ccfbcba..d204537d1b 100644 --- a/content/CORE/CORETutorials/Tasks/UsingAdvancedScheduler.md +++ b/content/CORE/CORETutorials/Tasks/UsingAdvancedScheduler.md @@ -96,5 +96,3 @@ With these options, you can create flexible schedules similar to these examples: {{< /expand >}} - -{{< taglist tag="coreadvancedscheduler" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/Tasks/UsingResilverPriority.md b/content/CORE/CORETutorials/Tasks/UsingResilverPriority.md index 28bbd276fa..f9cfcf2a88 100644 --- a/content/CORE/CORETutorials/Tasks/UsingResilverPriority.md +++ b/content/CORE/CORETutorials/Tasks/UsingResilverPriority.md @@ -24,7 +24,3 @@ Set **Enabled**, then use the drop-down menus to select a **Begin** and **End** A resilver process running during the time frame defined between "Begin Time" and "End Time" will likely work faster. We advise you avoid putting the system under any intensive activity or heavy loads (replications, SMB transfers, NFS transfers, Rsync transfers, S.M.A.R.T. tests, pool scrubs, etc) during a resilver process. {{< /hint >}} - -{{< taglist tag="coreresilverpriority" vol="CORE" limit="5" >}} - -{{< taglist tag="corezfstasks" vol="CORE" limit="5" title="Related ZFS Tasks Articles">}} diff --git a/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingCORE.md b/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingCORE.md index d8d5945726..b3a62cb505 100644 --- a/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingCORE.md +++ b/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingCORE.md @@ -158,5 +158,3 @@ When an update is in progress, the web interface shows an animated }} diff --git a/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingENTERPRISE.md b/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingENTERPRISE.md index 3e5172c4c4..6cc4ebec01 100644 --- a/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingENTERPRISE.md +++ b/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingENTERPRISE.md @@ -122,5 +122,3 @@ Enterprise customers should contact iX Support for assistance updating their Tru * Log into the system. * Click **Continue** in the **Pending Upgrade** dialog box. The standby controller reboots completing the upgrade. {{< /expand >}} - -{{< taglist tag="coreha" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingSoftwareforaMajorVersion.md b/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingSoftwareforaMajorVersion.md index 371fd54d14..0a32924212 100644 --- a/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingSoftwareforaMajorVersion.md +++ b/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingSoftwareforaMajorVersion.md @@ -123,5 +123,3 @@ The conversion happens during the reboot `Applying database schema changes` line The conversion can take a long time to finish, sometimes fifteen minutes or more, and can cause the system to reboot again. The system boots normally afterwards. If database errors display but the web interface is accessible, log in, go to **System > General**, and use the **UPLOAD CONFIG** button to upload the configuration backup you downloaded before starting the upgrade. - -{{< taglist tag="coreupdate" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/UsingShell.md b/content/CORE/CORETutorials/UsingShell.md index 4786cf8e32..51ec2d4e74 100644 --- a/content/CORE/CORETutorials/UsingShell.md +++ b/content/CORE/CORETutorials/UsingShell.md @@ -9,7 +9,6 @@ tags: {{< toc >}} - The web interface has a web shell that makes it convenient to run command line tools from the web browser as the root user. ![UIShell](/images/CORE/Shell/UIShell.png "TrueNAS Shell") @@ -58,5 +57,3 @@ Click **Reconnect** to start a new session. The CLI `tmux` command provides the ability to detach shell sessions and then reattach to them later. Commands continue to run in a detached session. - -{{< taglist tag="coreshell" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/UsingTaskManager.md b/content/CORE/CORETutorials/UsingTaskManager.md index e9d18b1ad0..ca6f2dfa1b 100644 --- a/content/CORE/CORETutorials/UsingTaskManager.md +++ b/content/CORE/CORETutorials/UsingTaskManager.md @@ -20,5 +20,3 @@ If a task fails, the error status shows. Tasks with log file output have a **View Logs** button to show the log files. Click **CLOSE** or anywhere outside the **Task Manager** dialog to close it, or press Esc. - -{{< taglist tag="coretopmenu" vol="CORE" limit="5" >}} diff --git a/content/CORE/CORETutorials/_index.md b/content/CORE/CORETutorials/_index.md index 4b3473c16d..9622325deb 100644 --- a/content/CORE/CORETutorials/_index.md +++ b/content/CORE/CORETutorials/_index.md @@ -15,4 +15,3 @@ Welcome to TrueNAS CORE tutorials! ## Table of Contents {{< children depth="1" description="true" >}} - diff --git a/content/CORE/GettingStarted/Applications.md b/content/CORE/GettingStarted/Applications.md index 81ed793888..b37b22ac2b 100644 --- a/content/CORE/GettingStarted/Applications.md +++ b/content/CORE/GettingStarted/Applications.md @@ -217,7 +217,3 @@ This example shows using an Ubuntu .iso: {{< /tab >}} {{< /tabs >}} - -{{< taglist tag="coregettingstarted" vol="CORE" limit="5" >}} - -{{< taglist tag="coreplugins" vol="CORE" limit="5" title="Related Plugins Articles" >}} diff --git a/content/CORE/GettingStarted/COREHardwareGuide.md b/content/CORE/GettingStarted/COREHardwareGuide.md index 85ff8c740f..62b9341b8e 100644 --- a/content/CORE/GettingStarted/COREHardwareGuide.md +++ b/content/CORE/GettingStarted/COREHardwareGuide.md @@ -10,5 +10,3 @@ tags: --- {{< include file="/_includes/TNHardwareGuide.md" >}} - -{{< taglist tag="coregettingstarted" vol="CORE" limit="5" >}} diff --git a/content/CORE/GettingStarted/ConsoleSetupMenu.md b/content/CORE/GettingStarted/ConsoleSetupMenu.md index 3234dc363e..92aec69ef4 100644 --- a/content/CORE/GettingStarted/ConsoleSetupMenu.md +++ b/content/CORE/GettingStarted/ConsoleSetupMenu.md @@ -82,5 +82,3 @@ Restarting network: ok The web user interface is at http://192.168.1.108 ``` - -{{< taglist tag="coregettingstarted" vol="CORE" limit="5" >}} diff --git a/content/CORE/GettingStarted/DataBackups.md b/content/CORE/GettingStarted/DataBackups.md index b9d6630570..5d8f893eae 100644 --- a/content/CORE/GettingStarted/DataBackups.md +++ b/content/CORE/GettingStarted/DataBackups.md @@ -96,5 +96,3 @@ TrueNAS is now accessible and configured to store, share, and back up your data! If you need to expand the system capabilities, see the remaining article about additional [Applications]({{< relref "Applications.md" >}}). When you're ready to fine-tune the system configuration or learn more about the advanced features, see the remaining sections in the TrueNAS CORE and Enterprise section. These sections are organized in order of appearance in the TrueNAS interface, with additional topics for [3rd party solutions]({{< relref "/Solutions/_index.md" >}}), [API reference guide]({{< relref "/CORE/API/_index.md" >}}), and [community recommendations]({{< ref "/CORE/CORETutorials/CommunityGuides/_index.md" >}}). - -{{< taglist tag="coregettingstarted" vol="CORE" limit="5" >}} diff --git a/content/CORE/GettingStarted/Install.md b/content/CORE/GettingStarted/Install.md index 50f1bb0aa9..1f26791d90 100644 --- a/content/CORE/GettingStarted/Install.md +++ b/content/CORE/GettingStarted/Install.md @@ -319,5 +319,3 @@ Click *Add* and create a new tunable with the *Variable* `if_vmx_load`, *Value* Congratulations, TrueNAS is now installed! The next step is to [log in to the web interface]({{< relref "/CORE/GettingStarted/LoggingIn.md" >}}) using the administrative account credentials and begin configuring the system. - -{{< taglist tag="coregettingstarted" vol="CORE" limit="5" >}} diff --git a/content/CORE/GettingStarted/LoggingIn.md b/content/CORE/GettingStarted/LoggingIn.md index 331af3ef50..8182b24b55 100644 --- a/content/CORE/GettingStarted/LoggingIn.md +++ b/content/CORE/GettingStarted/LoggingIn.md @@ -145,5 +145,3 @@ For users with compatible TrueNAS Hardware, clicking the system image goes to th The **Dashboard** provides access to all TrueNAS management options. Now that you can access the TrueNAS web interface and see all the management options, it's time to begin [storing data]({{< relref "StoringData.md" >}})! - -{{< taglist tag="coregettingstarted" vol="CORE" limit="5" >}} diff --git a/content/CORE/GettingStarted/SharingStorage.md b/content/CORE/GettingStarted/SharingStorage.md index b32022d582..029d22fe63 100644 --- a/content/CORE/GettingStarted/SharingStorage.md +++ b/content/CORE/GettingStarted/SharingStorage.md @@ -111,5 +111,3 @@ A simple configuration is beyond the scope of this getting started guide, but de With simple sharing done, TrueNAS is now installed, accessible, and capable to receive or share data over your network. Now it is time to protect the TrueNAS storage by setting up [data backups]({{< relref "DataBackups.md" >}}). - -{{< taglist tag="coregettingstarted" vol="CORE" limit="5" >}} diff --git a/content/CORE/GettingStarted/StoringData.md b/content/CORE/GettingStarted/StoringData.md index 65b1341ac0..52d6e77513 100644 --- a/content/CORE/GettingStarted/StoringData.md +++ b/content/CORE/GettingStarted/StoringData.md @@ -64,7 +64,3 @@ Users create datasets and zvols as part of configuring specific data-sharing sit Organize the pool with additional datasets or zvols according to your access and data-sharing requirements before moving any data into the pool. When you finish building and organizing your TrueNAS pools, move on to configuring how the system [shares data]({{< relref "SharingStorage.md" >}}) - -{{< taglist tag="corestoredata" vol="CORE" limit="5" >}} - -{{< taglist tag="coregettingstarted" vol="CORE" limit="5" title="Getting Started Articles" >}} diff --git a/content/CORE/GettingStarted/UserAgreements/COREEULA.md b/content/CORE/GettingStarted/UserAgreements/COREEULA.md index 79cc8c44b0..953778bd7e 100644 --- a/content/CORE/GettingStarted/UserAgreements/COREEULA.md +++ b/content/CORE/GettingStarted/UserAgreements/COREEULA.md @@ -58,23 +58,13 @@ The TrueNAS CORE software includes Open Source components and some proprietary e 4.4 United States Government End Users - For any TrueNAS CORE Software licensed directly or indirectly on behalf of a unit or agency of the United States Government, this paragraph applies. Company’s proprietary software embodied in the Product: (a) was developed at private expense and is in all respects Company’s proprietary information; (b) was not developed with government funds; (c) is Company’s trade secret for all purposes of the Freedom of Information Act; (d) is a commercial item and thus, pursuant to Section 12.212 of the Federal Acquisition Regulations (FAR) and DFAR Supplement Section 227.7202, Government’s use, duplication or disclosure of such software is subject to the restrictions set forth by the Company and Licensee shall receive only those rights with respect to the Product as are granted to all other end users. - 4.5 Title - iXsystems retains all rights, titles, and interest in TrueNAS CORE Software and all related copyrights, trade secrets, patents, trademarks, and any other intellectual and industrial property and proprietary rights, including registrations, applications, registration keys, renewals, and extensions of such rights. Contact Information - If You have any questions about this Agreement, or if You want to contact iXsystems for any reason, please email legal@ixsystems.com. - - 4.6 Maintenance and Support - You may be entitled to support services from iXsystems after purchasing a Product or a support contract. iXsystems will provide these support services based on the length of time of the purchased support contract. This maintenance and support is only valid for the length of time that You have purchased with Your Product. iXsystems may from time to time and at their sole discretion vary the terms and conditions of the maintenance and support agreement based on different business environmental and personnel factors. Any variations will be notified via email and the support portal. For more information on our Maintenance and Support contract, refer to https://www.ixsystems.com/support/. - - - 4.7 Force Majeure - iXsystems will not be deemed to be in default of any of the provisions of this Agreement or be liable for any delay or failure in performance due to Force Majeure, which shall include without limitation acts of God, earthquake, weather conditions, labor disputes, changes in law, regulation or government policy, riots, war, fire, epidemics, acts or omissions of vendors or suppliers, equipment failures, transportation difficulties, malicious or criminal acts of third parties, or other occurrences which are beyond iXsystems’ reasonable control. - - 4.8 Termination - iXsystems may cease any and all support, services, or maintenance under this Agreement without prior notice, or liability, and for any reason whatsoever, without limitation, if any of the terms and conditions of this Agreement are breached. Other provisions of this Agreement will survive termination including, without limitation, ownership provisions, warranty disclaimers, indemnity, and limitations of liability. - 4.9 Open Source Software Components - iXsystems uses Open Source Software components in the development of the TrueNAS CORE Software. Open Source Software components that are used in the TrueNAS CORE Software are composed of separate components each having their own trademarks, copyrights, and license conditions. - 4.10 Assignment - Licensee shall not assign or otherwise transfer any of its rights, or delegate or otherwise transfer any of its obligations or performance, under this Agreement, in each case whether voluntarily, involuntarily, by operation of law, or otherwise, without iXsystems’ prior written consent. No delegation or other transfer will relieve Licensee of any of its obligations or performance under this Agreement. Any purported assignment, delegation, or transfer in violation of this Section is void. iXsystems may freely assign or otherwise transfer all or any of its rights, or delegate or otherwise transfer all or any of its obligations or performance, under this Agreement without Licensee's consent. This Agreement is binding upon and inures to the benefit of the parties hereto and their respective permitted successors and assigns. ### 5.0 Export Control Regulations diff --git a/content/CORE/UIReference/Accounts/Groups.md b/content/CORE/UIReference/Accounts/Groups.md index 43dd5866ce..abfb621a8f 100644 --- a/content/CORE/UIReference/Accounts/Groups.md +++ b/content/CORE/UIReference/Accounts/Groups.md @@ -46,5 +46,3 @@ The **Groups** screen lets you create and manage UNIX-style groups. | **Samba Authentication** | Allows group to be used for Samba permissions and authentication. | | **Allow Duplicate GIDs** | Allows more than one group to have the same group ID. | {{< /truetable >}} - -{{< taglist tag="coregroups" vol="CORE" limit="5" >}} diff --git a/content/CORE/UIReference/Accounts/Users.md b/content/CORE/UIReference/Accounts/Users.md index 25a958f4ac..1508066134 100644 --- a/content/CORE/UIReference/Accounts/Users.md +++ b/content/CORE/UIReference/Accounts/Users.md @@ -81,5 +81,3 @@ The **Users** screen lets you create and manage user accounts. | Microsoft Account | Allows Windows authentication methods. | | Samba Authentication | Lets users authenticate to Samba shares. | {{< /truetable >}} - -{{< taglist tag="users" vol="CORE" limit="5" >}} diff --git a/content/CORE/UIReference/Accounts/_index.md b/content/CORE/UIReference/Accounts/_index.md index 2d76c9c5df..badb2c0f23 100644 --- a/content/CORE/UIReference/Accounts/_index.md +++ b/content/CORE/UIReference/Accounts/_index.md @@ -9,5 +9,3 @@ related: false This section has articles documenting the TrueNAS local User and Group screens. {{< children depth="2" description="true" >}} - -{{< taglist tag="coreaccountstutorials" vol="CORE" limit="5" >}} diff --git a/content/CORE/UIReference/DirectoryServices/ADScreen.md b/content/CORE/UIReference/DirectoryServices/ADScreen.md index baa0bbf75f..c75fa4a982 100644 --- a/content/CORE/UIReference/DirectoryServices/ADScreen.md +++ b/content/CORE/UIReference/DirectoryServices/ADScreen.md @@ -60,5 +60,3 @@ Click **BASIC OPTIONS** to return to the **Active Directory** display of basic o Click **EDIT IDMAP** to navigate to the **Directory Services > Idmap** screen. Click **REBUILD DIRECTORY SERVICE CACHE** to resync the cache if it becomes out of sync. Or if fewer users than expected are available in the permissions editors. - -{{< taglist tag="coread" vol="CORE" limit="5" >}} diff --git a/content/CORE/UIReference/DirectoryServices/IdmapScreen.md b/content/CORE/UIReference/DirectoryServices/IdmapScreen.md index ab6023342e..1e50b30191 100644 --- a/content/CORE/UIReference/DirectoryServices/IdmapScreen.md +++ b/content/CORE/UIReference/DirectoryServices/IdmapScreen.md @@ -35,7 +35,3 @@ Click the