truenas · linzi-ix · Feb 4, 2025 · Feb 7, 2025 · Feb 7, 2025 · Feb 7, 2025
@@ -277,7 +277,7 @@ When a specific keyboard key or key combination is used, use the `<kbd>` HTML co
 Do not use the following in your articles:
 
 * The word *will*. It either does or does not do something. Use active voice and present tense when writing content.
-  For example, do not type "The system will reboot." Instead, use "The system reboots."
+  For example, do not type "The system will restart." Instead, use "The system restarts."
 
 * The word *may*. We all say it but we are not giving permission to do something, we are saying it *might* do something.
   You can also replace *may* with *can* or *should* if these words better describe the situation. Only use *may* when granting permission to do something.

@@ -28,7 +28,7 @@ Multiple measures can be taken to fix or prevent overheating issues.
 
 Follow these steps to adjust the BIOS fan settings for the Mini.
 
-1. Power on or reboot the system.
+1. Power on or restart the system.
 
 2. At the start of the boot process, press the <kbd>F2</kbd> or <kbd>Delete</kbd> key several times until the `BIOS Main menu` appears:
 

@@ -53,7 +53,7 @@ Align the new replacement node with the bay and slide it into the chassis until
 
 ![ZseriesNodeInstall](/images/Hardware/Legacy/ZseriesNodeInstall.png "Node Install")
 
-Reconnect the cables, referring to notes, labels, or photos for correct connection. Turn on the new node with the front power button. Use the console or web GUI to verify successful startup. On an HA system, select System –> Failover –> Sync to Peer. This forces a configuration sync from the active node to the standby node. The standby node will then reboot to load the new configuration.  Pack the old node into the shipping box from the new node for return to iXsystems.
+Reconnect the cables, referring to notes, labels, or photos for correct connection. Turn on the new node with the front power button. Use the console or web GUI to verify successful startup. On an HA system, select System –> Failover –> Sync to Peer. This forces a configuration sync from the active node to the standby node. The standby node will then restart to load the new configuration.  Pack the old node into the shipping box from the new node for return to iXsystems.
 
 The node replacement is now complete, and the new node is running. Contact [email protected] for any further questions about this article or the node replacement process.
 

@@ -6,7 +6,7 @@ aliases:
   - /hardware/notices/componentarticles/1300wpowersupply/
 ---
 
-The TrueNAS 1300W Power Supply Unit (PSU) with A05 firmware has a significant reliability issue that causes the PSU to overheat and forces a system reboot.
+The TrueNAS 1300W Power Supply Unit (PSU) with A05 firmware has a significant reliability issue that causes the PSU to overheat and forces a system restart.
 
 {{< hint type=note >}}
 The 1300W PSUs with A05 firmware are in all TrueNAS M40, M50, and R50 platforms shipped before April 11, 2022.

@@ -48,7 +48,7 @@ If a static address is desired, the following configuration methods are availabl
 **How do I perform firmware updates?**
 
 Remote management firmware can be upgraded using two methods: the firmware update in the maintenance menu of the web interface or a DOS utility run on the host. 
-The host must be rebooted after the update for the sensors to begin recording data again. 
+For the sensors to begin recording data again, restart the host after the update . 
 In most cases the update should be run without saving the existing configuration, though it can be saved if there is extensive network and user configuration already present that would take time to reconfigure.
 
 **What is the ipmitool and how do I get it?**
@@ -90,7 +90,7 @@ Servers can be grouped for speedy administration of multiple servers at once and
 
 In rare circumstances, remote management can malfunction and require a reset. 
 To reset remote management, log in to the web interface and select **Reset Controller** from the **Maintenance** menu. 
-Wait approximately two minutes before logging in to the web interface again. It might be necessary to reboot the host to allow the sensors to repopulate afterward.
+Wait approximately two minutes before logging in to the web interface again. It might be necessary to restart the host to allow the sensors to repopulate afterward.
 
 If the procedure above does not address the issue, remote management might need to be power-cycled by shutting down and unplugging the server for approximately 30 seconds, then reconnecting and powering up the server. This causes remote management to re-initialize itself upon the next boot.
 

@@ -32,11 +32,11 @@ A cache device failure does not affect the integrity of the pool, but it might i
 
 ### Persistent L2ARC in TrueNAS
 
-By default, the L2ARC cache empties when the system reboots.
-When Persistent L2ARC is enabled, a sysctl repopulates the cache device mapping during the reboot process.
-Persistent L2ARC preserves L2ARC performance even after a system reboot.
+By default, the L2ARC cache empties when the system restarts.
+When Persistent L2ARC is enabled, a sysctl repopulates the cache device mapping during the restarts process.
+Persistent L2ARC preserves L2ARC performance even after a system restarts.
 
-However, persistent L2ARC for large data pools can drastically slow the reboot process, degrading middleware and web interface performance.
+However, persistent L2ARC for large data pools can drastically slow the restarts process, degrading middleware and web interface performance.
 Because of this, we have disabled persistent L2ARC by default in TrueNAS, but you can manually activate it.
 
 ### Activating Persistent L2ARC
@@ -52,7 +52,7 @@ Make sure **Enabled** is selected and click **SUBMIT**.
 
 {{< expand "CLI Instructions" "v" >}}
 {{< hint type=important >}}
-TrueNAS does not write settings changed through the CLI to the configuration database. TrueNAS resets them on reboot.
+TrueNAS does not write settings changed through the CLI to the configuration database. TrueNAS resets them on restarts.
 {{< /hint >}}
 In a command line, enter `sysctl vfs.zfs.l2arc.rebuild_enabled=1`.
 When successful, the output reads: `vfs.zfs.l2arc.rebuild_enabled: 0 -> 1`

@@ -17,7 +17,7 @@ The data is then written to disk in a normal transaction group (TXG) which allow
 ZIL is often referred to as a *log* whose main purpose is data integrity.
 The ZIL exists to track in-progress, synchronous write operations.
 If the system crashes or loses power, the ZIL can replay the operation.
-While you lose a standard system cache on power failure, a ZIL persists through system reboots.
+While you lose a standard system cache on power failure, a ZIL persists through system restarts.
 
 By default, ZIL does not handle asynchronous writes.
 System memory handles these like any standard caching method.

@@ -86,9 +86,9 @@ This design means that the ZFS pool on the receiving end does not need to be ide
 ZFS boot environments allow you to recover from a failed upgrade.
 TrueNAS automatically takes a snapshot of the dataset the operating system resides on before upgrading or updating a system.
 TrueNAS automatically saves the boot environment to the GRUB boot loader.
-If the upgrade or configuration change fails, reboot and select the previous boot environment from the boot menu.
+If the upgrade or configuration change fails, restart and select the previous boot environment from the boot menu.
 Users can also create boot environments in TrueNAS as needed, such as before making configuration changes.
-This way, you can reboot the system into a snapshot of the system that did not include the new configuration changes.
+This way, you can restart the system into a snapshot of the system that did not include the new configuration changes.
 
 ### ZFS Write Cache
 

@@ -73,7 +73,7 @@ For network configuration options **1**, **2**, and **3**, we recommend using th
 
 * **8) Reboot**
 
-  Use to restart the system by powering down and then automatically powering on the system.
+  Restart the system by powering down and then automatically powering on the system.
 
 * **9) Shut down**
 
@@ -163,10 +163,10 @@ Immediately go to the **Credentials > Local User** screen, select the admin user
 **Caution!**
 Resetting the configuration deletes all settings and reverts TrueNAS to default settings.
 Before resetting the system, back up all data and encryption keys/passphrases!
-After the system resets and reboots, you can go to **Storage** and click **Import Pool** to re-import pools.
+After the system resets and restarts, you can go to **Storage** and click **Import Pool** to re-import pools.
 {{< /hint >}}
 
-Enter **5** in the Console Setup menu, then enter <kbd>y</kbd> to reset the system configuration. The system reboots and reverts to default settings.
+Enter **5** in the Console Setup menu, then enter <kbd>y</kbd> to reset the system configuration. The system restarts and reverts to default settings.
 
 ## Completing your System Setup
 After setting up network requirements, log into the web UI to complete your system setup by:

@@ -99,7 +99,7 @@ The sections that follow describe these steps in detail.
 This process of installing each controller sequentially has two methods:
 
 * Install and configure controller 1 up to the point where you are ready to sync to controller 2.
-  When complete, install controller 2 and reboot. After the console setup menu displays, switch back to controller 1 and sync to peer.
+  When complete, install controller 2 and restart. After the console setup menu displays, switch back to controller 1 and sync to peer.
   This synchronizes the completed configuration from controller 1 to controller 2 and keeps controller 1 designated as the primary controller.
 Or
 * Begin installing controller 2 immediately after installing controller 1. When controller 2 finishes installing, power it off and keep it powered down.
@@ -117,7 +117,7 @@ These steps are nearly identical to the section above but controller 2 is either
    Apply the HA license, sign the EULA, and [complete the UI configuration](#configuring-settings-in-the-scale-ui) to the point where you are ready to sync to peer on controller 1, but do not sync yet.
 5. Power up controller 2 and wait for it to complete the boot process.
 6. Log into controller 1, go to **System > Failover**, and click **Sync to Peer**.
-   This synchronizes controller 2 with controller 1 and reboots controller 2. Controller 2 becomes the standby controller when it finishes rebooting.
+   This synchronizes controller 2 with controller 1 and restarts controller 2. Controller 2 becomes the standby controller when it finishes restarting.
 
 ### Downloading the TrueNAS Install File
 
@@ -151,9 +151,9 @@ Use this process to install the <file>iso</file> file on both controller 1 and c
 
 3. Return to the **Remote Control > iKVM/HTML5** window opened in step 2. Either use your keyboard or open the keyboard in the window then:
 
-   a. Type **8** to reboot controller 1 (also repeat for controller 2), and type **y** to confirm and reboot.
+   a. Type **8** to restart controller 1 (also repeat for controller 2), and type **y** to confirm and restart.
 
-   b. As the system reboots, be prepared to hit the <kbd>F11</kbd> key when you first see the **TrueNAS Open Storage** splash screen.
+   b. As the system restarts, be prepared to hit the <kbd>F11</kbd> key when you first see the **TrueNAS Open Storage** splash screen.
       Alternatively, you can start clicking on the **F11** key on the online keyboard until you see the TrueNAS Installer screen.
 
    c. Select the **UEFI: ATEN Virtual CDROM** device from the boot list. The bootstrap loader begins. When it ends the TrueNAS installer opens.
@@ -171,7 +171,7 @@ Also have your TrueNAS system configuration file and data backups handy, so you
 6. Select **OK** after the **The TrueNAS installation on <nvme0n1> succeeded** displays. The Console setup menu screen displays.
 
 7. Enter **3** to **Reboot System** and immediately return to the IPMI **Virtual Media > CD-ROM image** screen to click **Unmount**. Click **Save**.
-   If you fail to unmount the <file>iso</file> image before the system completes the reboot, the bootstrap install continues in a boot loop.
+   If you fail to unmount the <file>iso</file> image before the system completes the restart, the bootstrap install continues in a boot loop.
 
 TrueNAS is now installed on controller 1 and repeated for controller 2 starting with [Using IPMI to Install the ISO on a Controller](#using-ipmi-to-install-the-iso-on-a-controller).
 
@@ -265,7 +265,7 @@ For more information on how to import a pool [click here]({{< relref "ImportPool
 1. Turn the failover service back on. Go to **System > Services** locate the **Failover** service and click edit.
 
 2. Select **Disable Failover** to clear the checkmark and turn failover back on, then click **Save**.
-   The system might reboot. Use IPMI to monitor the status of controller 2 and wait until the controller is back up and running.
+   The system might restart. Use IPMI to monitor the status of controller 2 and wait until the controller is back up and running.
 
 3. Log out of the controller 1 UI, and log in using the VIP address.
 
@@ -285,7 +285,7 @@ Take note of this information.
 ### Troubleshooting HA Installation
 
 If controller 2 comes online as the primary and controller 1 as the standby, you installed and configured the controllers incorrectly.
-1. Go to **System > Failover**, clear the **Default TrueNAS Controller** option, and click **Save**. The system reboots and fails over to the current standby controller (in this case, to controller 1).
+1. Go to **System > Failover**, clear the **Default TrueNAS Controller** option, and click **Save**. The system restarts and fails over to the current standby controller (in this case, to controller 1).
 
 2. Log back into the UI with the VIP address. Go to **System > Failover** and select **Default TrueNAS Controller** to make controller 1 the primary controller.
 

@@ -134,7 +134,7 @@ Before you begin:
 
 With the installer added to a device (CD or USB), you can now install TrueNAS onto the desired system using the TrueNAS installer.
 
-Insert the install media and reboot or boot the system.
+Insert the install media and restart or boot the system.
 At the motherboard splash screen, use the hotkey defined by your motherboard manufacturer to boot into the motherboard UEFI/BIOS.
 
 Choose to boot in **UEFI mode** or **legacy CSM/BIOS mode**.
@@ -143,7 +143,7 @@ For Intel chipsets manufactured in 2020 or later, UEFI is likely the only option
 
 If your system supports SecureBoot, and you have not disabled it or set it to **Other OS**, do it now, so you can boot the install media.
 
-Select the install device as the boot drive, exit, and reboot the system.
+Select the install device as the boot drive, exit, and restart the system.
 If the USB stick is not shown as a boot option, try a different USB slot.
 Slots available for boot differs by hardware. For optimal performance, consider using NVMe S.M.A.R.T. tests to ensure the reliability of your storage devices before installation.
 
@@ -158,7 +158,7 @@ After the system boots into the installer, follow these steps.
 {{< expand "TrueNAS Installer Instructions" "v" >}}
 {{< include file="/static/includes/SCALEInstallerProcedure.md" >}}
 
-After following the steps to install, reboot the system and remove the install media.
+After following the steps to install, restart the system and remove the install media.
 
 {{< expand "Troubleshooting" "v">}}
 If the system does not boot into TrueNAS, there are several things you can check to resolve the situation:
@@ -218,9 +218,9 @@ The procedure for creating a TrueNAS VM is the same for most hypervisors.
 
 2. Boot the VM and install TrueNAS as usual.
 
-3. After the installation completes, shut down the VM instead of rebooting, and disconnect the CD/DVD from the VM before rebooting the VM.
+3. After the installation completes, shut down the VM instead of restarting, and disconnect the CD/DVD from the VM before restarting the VM.
 
-4. After rebooting into TrueNAS, install VM tools if applicable for your VM, and if they exist for Debian 11, or ensure they loaded on boot.
+4. After restarting into TrueNAS, install VM tools if applicable for your VM, and if they exist for Debian 11, or ensure they loaded on boot.
 {{< /expand >}}
 
 #### Installing Using VMWare Player 15.5

@@ -61,7 +61,7 @@ This method is only available for non-Enterprise community systems.
 4. When the latest update for that chosen TrueNAS release is loaded, click **Apply Pending Update** or **Download Updates** to begin the update process documented in [Updating TrueNAS]({{< relref "UpdateSCALE.md#performing-an-automatic-update" >}}).
    It is strongly recommended to download the system configuration backup prior to starting the update.
 
-5. After the system installs the update and reboots, log in and review the system configuration to ensure the migration was successful.
+5. After the system installs the update and restarts, log in and review the system configuration to ensure the migration was successful.
 
 ### Manual Update
 Some TrueNAS 13.0 or 13.3 releases can migrate using the UI **Upgrade** function using a TrueNAS 24.04 update file downloaded from the website.
@@ -93,19 +93,19 @@ If this process fails, retry using the iso file method above.
 
    Then click **APPLY UPDATE**.
 
-7. After the update completes, reboot the system if it does not reboot automatically.
+7. After the update completes, restart the system if it does not restart automatically.
 
-   {{< trueimage src="/images/SCALE/SystemSettings/SidegradeRestart.png" alt="Reboot to Finish" id="Reboot to Finish" >}}
+   {{< trueimage src="/images/SCALE/SystemSettings/SidegradeRestart.png" alt="Restart to Finish" id="Restart to Finish" >}}
 
-After TrueNAS reboots, you might need to [use the Console Setup menu to configure the primary networking interfaces]({{< relref "ConsoleSetupMenuScale.md" >}}) to enable GUI accessibility.
+After TrueNAS restarts, to enable GUI accessibility, you might need to use the [Console Setup menu]({{< relref "ConsoleSetupMenuScale.md" >}}) to configure the primary networking interfaces.
 
 After gaining access to the UI, sign in with the admin user credentials created during installation.
 
 Go to **System > General Settings** and [upload the system config file](/scale/scaletutorials/systemsettings/general/managesysconfigscale/#uploading-the-file).
 This migrates your settings, imports your pools, shares, etc.
-The system reboots to apply the uploaded configuration.
+The system restarts to apply the uploaded configuration.
 
-After TrueNAS reboots, sign in with the root user credentials from the previous configuration.
+After TrueNAS restarts, sign in with the root user credentials from the previous configuration.
 Uploading the config file deletes the **truenas_admin** user account created during a clean install and therefore requires you to [recreate an administrative user](#recreating-the-admin-user-account).
 
 After uploading the config file, review each area of the UI previously configured to validate pools imported and settings migrated correctly. Begin with your network settings.

@@ -100,7 +100,7 @@ Saved schedules appear in the **S.M.A.R.T. Tests** window.
 S.M.A.R.T. tests can offline disks! Avoid scheduling S.M.A.R.T. tests simultaneously with scrub or other data protection tasks.
 {{< /hint >}}
 
-Start the S.M.A.R.T. service. Go to **System > Services** and scroll down to the **S.M.A.R.T.** service. If not running, click the toggle to turn the service on. Select **Start Automatically** to have this service start after after the system reboots.
+Start the S.M.A.R.T. service. Go to **System > Services** and scroll down to the **S.M.A.R.T.** service. If not running, click the toggle to turn the service on. Select **Start Automatically** to have this service start after after the system restarts.
 
 ![SMARTSystemServicesSCALE](/images/SCALE/SystemSettings/SMARTSystemServicesSCALE.png "System Services S.M.A.R.T. Test")