diff --git a/docs/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx b/docs/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx index 9ad37a2a441..545d9071c37 100644 --- a/docs/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx +++ b/docs/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx @@ -20,7 +20,7 @@ You can enhance the Dashboard with plugins from [Community Applications](../../u ### 2. Main -The **Main** screen enables efficient management of your Unraid storage and disk operations. You can configure your %%array|array%%, %%cache pools|cache-pool%%, and flash devices, as well as manage USB storage and unassigned devices, including remote shares. It displays key information about each storage device, such as health, capacity, and file systems. +The **Main** screen enables efficient management of your Unraid storage and disk operations. You can configure your %%array|array%%, %%cache pools|cache-pool%%, and boot devices, as well as manage USB storage and unassigned devices, including remote shares. It displays key information about each storage device, such as health, capacity, and file systems. ![Main tab](/img/maintab.png) At the bottom, the Array Operation section provides maintenance options to keep your %%array|array%% running smoothly. diff --git a/docs/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx b/docs/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx index a5d34a776a8..24707e3a5da 100644 --- a/docs/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx +++ b/docs/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx @@ -9,15 +9,15 @@ Congratulations on your initial setup! Now, it's time to explore a few more important aspects that will enhance your server's functionality and security. -## Back up your flash device +## Back up your boot device -Always back up your Unraid flash device after making significant configuration changes. Regular backups are *highly* recommended. +Always back up your Unraid boot device after making significant configuration changes. Regular backups are *highly* recommended. -To back up your flash device, go to the **Main** tab, select the device, and click on **Flash Backup**. +To back up your boot device, go to the **Main** tab, select the device, and click on **Boot Device Backup**. :::warning -Store backups outside the Unraid %%array|array%% for easy access if the %%array|array%% isn't operational. [Learn more about flash device management here](../../system-administration/maintain-and-update/changing-the-flash-device.mdx). +Store backups outside the Unraid %%array|array%% for easy access if the %%array|array%% isn't operational. [Learn more about boot-device management here](../../system-administration/maintain-and-update/changing-the-flash-device.mdx). ::: diff --git a/docs/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx b/docs/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx index a954ee6e75d..dc1be25667d 100644 --- a/docs/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx +++ b/docs/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx @@ -15,7 +15,7 @@ If you're struggling with any part of the Unraid installation, be sure to check ## Assign Parity and Data disks -You’ll use the **Main** tab in the Unraid %%WebGUI|web-gui%% to assign and review devices, including %%array|array%% and pool assignments along with any unassigned devices and your boot device (the **USB flash device**). +You’ll use the **Main** tab in the Unraid %%WebGUI|web-gui%% to assign and review devices, including %%array|array%% and pool assignments along with any unassigned devices and your boot device (USB flash by default). ![Configuring array](/img/configuringarray1.png) @@ -29,7 +29,7 @@ Unraid OS uses drives for various purposes: - **Pool Devices:** High-performance drives used primarily as a **cache**, storing files temporarily to enhance performance before transferring them to the %%array|array%%. -- **Boot Device:** The USB flash device containing Unraid OS, which starts your server. +- **Boot Device:** The device containing Unraid OS (USB flash by default), which starts your server.
Disk assignment recommendations diff --git a/docs/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx b/docs/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx index f888a604caf..9ea41b26ae1 100644 --- a/docs/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx +++ b/docs/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx @@ -308,7 +308,7 @@ Configure how notifications appear in your browser: - **Auto-close (seconds)**: How long notifications stay visible before automatically closing - **Date format**: Choose your preferred date format for notification timestamps - **Time format**: Choose between *12 hours* or *24 hours* time display -- **Store notifications to flash**: Save notification history to your USB flash device (requires flash storage space) +- **Store notifications to boot drive**: Save notification history to your boot device (requires available storage space on the boot device) #### Notification types diff --git a/docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx b/docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx index 7a8e10d7c10..5ed63453eb3 100644 --- a/docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx +++ b/docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx @@ -9,7 +9,7 @@ After booting Unraid OS for the first time, you'll use the %%WebGUI|web-gui%% to :::info[Localize] -It may be easier for users to follow this guide after configuring their language settings. Check out [Multi-language support](../../using-unraid-to/customize-your-experience/multi-language-support.mdx) to make the %%WebGUI|web-gui%% more accessible in your preferred language. +It may be easier for users to follow this guide after configuring their language settings. Check out [Multi-language support](../../using-unraid-to/customize-your-experience/multi-language-support.mdx) to make the %%WebGUI|web-gui%% more accessible in your preferred language. ::: @@ -33,12 +33,12 @@ When you access the %%WebGUI|web-gui%% for the first time, you'll be prompted to Make sure your password is: - Unique -- At least 8 characters long. (Although, best practice recommends 12+ for the most secure passwords!) +- At least 8 characters long. (Although, best practice recommends 12+ for the most secure passwords!) - A mix of letters, numbers, and special characters We recommend using a password manager for secure storage. -
+
![Set root password](/img/Set_root_password.png)
@@ -48,19 +48,75 @@ If you forget your root password, you can reset it following the [Reset your pas ::: +## Onboarding + +:::note[Unraid 7.3 and later] + +The onboarding wizard below applies to Unraid 7.3 and later. + +::: + +1. Press **Get Started** to launch the onboarding wizard. If you prefer to configure manually, select **Skip Setup**. + +
+ ![Step 1: Welcome to Unraid](/img/onboarding_step1.png) +
+ + To relaunch the wizard later, go to **_Settings → Onboarding Wizard_**. + +2. Configure your server settings, including server name and description, time zone, language, and optional SSH and theme preferences. Then click **Next**. + +
+ ![Step 2: Configure Settings](/img/onboarding_step2.png) +
+ +3. Choose your boot option: + - For **flash boot**, keep the default USB/flash boot configuration and click **Next**. + +
+ ![Step 3: Flash Boot](/img/onboarding_step3a.png) +
+ - For **internal boot**, choose single or mirrored boot mode, select the + device(s), and set the space reserved for the boot partition. Then click + **Next**. + +
+ ![Step 3: Internal Boot](/img/onboarding_step3b.png) +
+ +4. Optionally choose whether to preinstall key plugins, then click **Next**. + +
+ ![Step 4: Plugins](/img/onboarding_step4.png) +
+ +5. Review the summary, then click **Confirm & Apply**. + +
+ ![Step 5: Summary](/img/onboarding_step5.png) +
+ +6. On the **Next Steps** screen, review the recommended follow-up actions, then click: + - **Go to Dashboard** if you chose flash boot + - **Reboot** if you chose internal boot + +
+ ![Step 6: Next Steps](/img/onboarding_step6.png) +
+ ## Register your license key -After setting your root password, log in to your Unraid.net account to obtain a license key: +Log in to your Unraid.net account to obtain a license key: 1. In the %%WebGUI|web-gui%%, go to the **Get Started** section. -
+
![Get started](/img/Upc_get_started.png)
2. Sign in or create an account, after which a trial key will be installed automatically. -
+
![Install trial key](/img/Upc_install_trial_key.png)
@@ -68,7 +124,7 @@ After setting your root password, log in to your Unraid.net account to obtain a :::important -For details on your license, visit ***Tools → Registration*** in the %%WebGUI|web-gui%%. +For details on your license, visit **_Tools → Registration_** in the %%WebGUI|web-gui%%. ::: @@ -79,35 +135,35 @@ Before deploying Unraid OS, it's important to verify your system's BIOS and stor
Click to expand our BIOS and Storage Controller checklist - Proper BIOS and storage controller configuration is vital for a stable Unraid OS deployment. Use this checklist before your first boot. +Proper BIOS and storage controller configuration is vital for a stable Unraid OS deployment. Use this checklist before your first boot. - ### Basic Settings +### Basic Settings - ✅ Set the USB flash drive as the primary boot device.\ - ✅ Configure the storage controller to **%%AHCI|ahci%%** mode with SATA connections.\ - ✅ Set the controller to **%%HBA mode|hba-mode%%** (not **%%RAID|raid%%**).\ - ✅ Disable **Secure Boot** as it is not supported by Unraid OS. +✅ Set the USB flash drive as the primary boot device.\ + ✅ Configure the storage controller to **%%AHCI|ahci%%** mode with SATA connections.\ + ✅ Set the controller to **%%HBA mode|hba-mode%%** (not **%%RAID|raid%%**).\ + ✅ Disable **Secure Boot** as it is not supported by Unraid OS. - ### Advanced Settings +### Advanced Settings - ✅ Enable **%%hardware virtualization|hvm%%** features (e.g., **%%Intel VT-x|intel-vt-x%%** or **%%AMD-V|amd-v%%**) for **%%virtual machines (VMs)|vm%%**.\ - ✅ Enable **%%IOMMU|iommu%%** support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs. +✅ Enable **%%hardware virtualization|hvm%%** features (e.g., **%%Intel VT-x|intel-vt-x%%** or **%%AMD-V|amd-v%%**) for **%%virtual machines (VMs)|vm%%**.\ + ✅ Enable **%%IOMMU|iommu%%** support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs. - ### Troubleshooting Tips +### Troubleshooting Tips - If Unraid OS does not boot, try: +If Unraid OS does not boot, try: - ✅ Adjusting the boot order to: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\ - ✅ Disabling USB 2.0/3.0 support.\ - ✅ Toggling any Fast Boot features.\ - ✅ Toggling USB keyboard support. +✅ Adjusting the boot order to: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\ + ✅ Disabling USB 2.0/3.0 support.\ + ✅ Toggling any Fast Boot features.\ + ✅ Toggling USB keyboard support. - For further assistance, visit the [Unraid general support forum](https://forums.unraid.net/). +For further assistance, visit the [Unraid general support forum](https://forums.unraid.net/). - :::important - Many motherboards limit boot device selection to 12 hard drives. If your USB flash drive is recognized as a hard drive, you may not be able to boot from it after installing 12 physical hard drives. Configure the BIOS to treat the flash drive as a removable device whenever possible. +:::important +Many motherboards limit boot device selection to 12 hard drives. If your USB flash drive is recognized as a hard drive, you may not be able to boot from it after installing 12 physical hard drives. Configure the BIOS to treat the flash drive as a removable device whenever possible. - If using an add-on HBA, you may be able to disable INT 13h support to prevent its connected drives from appearing in the bootable devices list, helping to stay within the 12-drive limit. - ::: +If using an add-on HBA, you may be able to disable INT 13h support to prevent its connected drives from appearing in the bootable devices list, helping to stay within the 12-drive limit. +:::
diff --git a/docs/unraid-os/getting-started/what-is-unraid.mdx b/docs/unraid-os/getting-started/what-is-unraid.mdx index 9f0232a74dd..c2f35614476 100644 --- a/docs/unraid-os/getting-started/what-is-unraid.mdx +++ b/docs/unraid-os/getting-started/what-is-unraid.mdx @@ -7,7 +7,7 @@ sidebar_label: What is Unraid? Unraid is an embedded operating system designed to give you complete control over your hardware. It functions as a robust network-attached storage (NAS) system, an %%application server|application-server%%, and a host for %%virtual machines (VMs)|vm%%. -Unraid installs on a USB flash drive and boots from it, loading into a root RAM file system. It uses a modern Linux kernel with updated hardware drivers, allowing it to run on nearly any 64-bit x86\_64 system while maintaining a minimal memory footprint. All configuration data for the operating system is stored on the flash drive and loads simultaneously with the operating system. +Unraid installs on a USB flash drive and boots from it, loading into a root RAM file system. It uses a modern Linux kernel with updated hardware drivers, allowing it to run on nearly any 64-bit x86\_64 system while maintaining a minimal memory footprint. All configuration data for the operating system is stored on the boot drive and loads simultaneously with the operating system. Unraid features a [user-friendly web interface](./explore-the-user-interface/tour-the-web-gui.mdx) for easy management. It offers basic controls for common tasks and advanced settings for experienced users. While it defaults to settings that suit most people, it also allows customization. This blend of simplicity and flexibility helps you store, protect, share, and enjoy your content effectively. diff --git a/docs/unraid-os/release-notes/7.3.0.md b/docs/unraid-os/release-notes/7.3.0.md new file mode 100644 index 00000000000..7d42f189fb3 --- /dev/null +++ b/docs/unraid-os/release-notes/7.3.0.md @@ -0,0 +1,231 @@ +# Version 7.3.0-beta.1 2026-03-17 + +This release includes internal boot support, related licensing and onboarding improvements, storage and ZFS enhancements, and a broad set of bug fixes and usability improvements. + +## Upgrading + +For step-by-step instructions, see [Upgrading Unraid](../../unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx). Questions about your [license](../../unraid-os/troubleshooting/licensing-faq.mdx#license-types--features)? + +### Known issues + +For other known issues, see the [7.2.4 release notes](7.2.4.md#known-issues). + +### Rolling back + +Once you enable internal boot or switch to TPM-based licensing, you cannot roll back to an earlier release. + +If you upgrade ZFS pool features, earlier Unraid releases may not be able to import those pools. + +If rolling back earlier than 7.2.4, also see the [7.2.4 release notes](7.2.4.md#rolling-back). + +## Changes vs. [7.2.4](7.2.4.md) + +### Onboarding and internal boot + +New users automatically start in the onboarding wizard, where they choose language, time zone, theme, and activation code settings before selecting a boot option, including internal boot. + +Existing users can go to **_Settings → Onboarding Wizard_** to review settings and migrate to internal boot. + +For details, see [Onboarding](../getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx#onboarding). + +### Licensing + +All new and replacement keys use TPM-based licensing when possible because it is more reliable than flash-based licensing. + +To proactively switch to TPM-based licensing, see [How can I move from flash-based licensing to TPM-based licensing](../troubleshooting/licensing-faq.mdx#tpm). + +#### Other licensing + +- Improvement: Improve handling of missing key file states + +### Storage + +- New: Show corrupted files in ZFS pool status +- New: Add user-facing control for ZFS ARC max size on **_Settings → Disk Settings → Tunable (zfs_arc_max)_** +- Improvement: Improve visibility into pool and drive health information +- Improvement: Improve duplicate drive detection and related messaging +- Fix: Resolve formatting-related crashes and segfaults in affected array and boot-pool scenarios +- Fix: Prevent drives from spinning down during parity copy as part of parity swap +- Fix: Correct mover availability when emptying an array disk with no pool assigned +- Fix: Correct ZFS pools waking once every 24 hours in affected cases + +### WebGUI + +- Improvement: Update many user-facing strings from “Flash” to “Boot” +- Improvement: Improve organization of boot-related settings +- Fix: Correct RAM display parsing after dmidecode unit label changes +- Fix: Correct time zone label and identifier issues in affected regions +- Fix: Correct Docker page tab behavior regression +- Fix: Correct Docker port mapping display for localhost-only bindings +- Fix: Correct strict proxy connectivity checks when using HTTP proxies that block CONNECT on port 80 +- Fix: Correct rc.crond status typo +- Fix: Auto-restart SSH daemon after network recovery +- Fix: Correct Discord notification formatting issues +- Fix: Correct interface parsing when `ip addr` output includes peer information + +### File Manager + +- Improvement: Improve File Manager UI and overall performance +- Improvement: Improve same-filesystem move operations +- Improvement: Improve upload behavior +- Fix: Correct path handling issues involving `/sub/` in file paths +- Fix: Correct scrollbar interaction issues during copy or move operations +- Fix: Correct handling of double quotes in directory names +- Fix: Correct move and rename edge cases +- Fix: Preserve empty directories during affected rename operations + +### Virtualization + +- Improvement: Improve System Devices visibility and VM template workflows +- Improvement: Improve custom VNC port validation and defaults +- Fix: Prevent VMs created from user-defined templates from inheriting the source VM MAC address +- Fix: Correct VM snapshot commit cleanup not updating snapshot metadata correctly +- Fix: Correct libvirt startup issues encountered during testing + +## Misc + +- New: Add **_Settings → Tailscale_** stub page for easier plugin discovery +- Fix: Correct custom image case model handling on the login page +- Fix: Remove outdated ReiserFS warnings and stale references + +### Unraid API + +- dynamix.unraid.net 4.30.0 - [see changes](https://github.com/unraid/api/releases) + +### Linux kernel + +- version 6.18.18-Unraid + +### Base distro updates + +- aaa_libraries: version 15.1 +- at-spi2-core: version 2.58.3 +- bash: version 5.3.009 +- bash-completion: version 2.17.0 +- bind: version 9.20.20 +- brotli: version 1.2.0 +- btrfs-progs: version 6.19 +- ca-certificates: version 20260212 +- cifs-utils: version 7.5 +- coreutils: version 9.10 +- cryptsetup: version 2.8.4 +- curl: version 8.18.0 +- dmidecode: version 3.7 +- dnsmasq: version 2.92 +- docker: version 29.3.0-x86_64-1_LT +- dynamix.unraid.net: version 4.30.0 +- efibootmgr: version 18 +- efivar: version 20201015_cff88dd +- elfutils: version 0.194 +- elogind: version 255.22 +- etc: version 15.1 +- ethtool: version 6.19 +- exfatprogs: version 1.3.1 +- file: version 5.47 +- freeglut: version 3.8.0 +- freetype: version 2.14.2 +- gawk: version 5.4.0 +- gdk-pixbuf2: version 2.44.5 +- gettext: version 1.0 +- gettext-tools: version 1.0 +- git: version 2.53.0 +- glew: version 2.3.1 +- glib2: version 2.86.4 +- glibc-zoneinfo: version 2026a +- gnutls: version 3.8.12 +- grub: version 2.14 +- harfbuzz: version 13.0.0 +- icu4c: version 78.2 +- iotop-c: version 1.30 +- iperf3: version 3.20 +- iproute2: version 6.19.0 +- iptables: version 1.8.13 +- jansson: version 2.15.0 +- krb5: version 1.22.2 +- less: version 692 +- libarchive: version 3.8.5 +- libcap-ng: version 0.9.1 +- libdeflate: version 1.25 +- libdisplay-info: version 0.3.0 +- libdrm: version 2.4.131 +- libevdev: version 1.13.6 +- libfontenc: version 1.1.9 +- libgcrypt: version 1.12.1 +- libgpg-error: version 1.59 +- libjpeg-turbo: version 3.1.3 +- libnetfilter_conntrack: version 1.1.1 +- libnftnl: version 1.3.1 +- libnl3: version 3.12.0 +- libnvme: version 1.16.1 +- libpcap: version 1.10.6 +- libpng: version 1.6.55 +- libtasn1: version 4.21.0 +- libunistring: version 1.4.2 +- liburing: version 2.14 +- libvirt: version 11.10.0-x86_64-1cf_LT +- libvirt-php: version 0.5.8_abf2ec0-x86_64-1_LT +- libX11: version 1.8.13 +- libx86: version 1.1.1 +- libXcomposite: version 0.4.7 +- libXdamage: version 1.1.7 +- libXext: version 1.3.7 +- libXinerama: version 1.1.6 +- libxkbcommon: version 1.13.1 +- libxkbfile: version 1.2.0 +- libxml2: version 2.15.2 +- libXmu: version 1.3.1 +- libXpm: version 3.5.18 +- libXrandr: version 1.5.5 +- libxslt: version 1.1.45 +- libXxf86dga: version 1.1.7 +- libXxf86vm: version 1.1.7 +- lmdb: version 0.9.35 +- lsof: version 4.99.6 +- lvm2: version 2.03.38 +- mcelog: version 210 +- mesa: version 26.0.1 +- nano: version 8.7.1 +- ncurses: version 6.6 +- nfs-utils: version 2.8.5 +- nghttp2: version 1.68.0 +- nghttp3: version 1.15.0 +- noto-fonts-ttf: version 2026.03.01 +- ntp: version 4.2.8p18 +- nvme-cli: version 2.16 +- openssl: version 3.5.5 +- ovmf-stable: version 202508 +- p11-kit: version 0.26.2 +- pam: version 1.7.2 +- pango: version 1.57.0 +- pcre2: version 10.47 +- php: version 8.4.15-x86_64-1_LT +- pkgtools: version 15.1 +- procps-ng: version 4.0.6 +- qemu: version 10.1.2-x86_64-1cf_LT +- rclone: version 1.72.0-x86_64-1_SBo_LT +- readline: version 8.3.003 +- shadow: version 4.19.4 +- spirv-llvm-translator: version 20260218_56778655 +- sqlite: version 3.51.2 +- sysstat: version 12.7.9 +- talloc: version 2.4.4 +- tdb: version 1.4.15 +- telnet: version 0.17 +- tpm2-tools: version 5.7 +- tpm2-tss: version 4.1.3 +- userspace-rcu: version 0.15.6 +- util-linux: version 2.41.3 +- virglrenderer: version 1.2.0 +- virtiofsd: version 1.13.2 +- wireguard-tools: version 1.0.20260223 +- wireless-regdb: version 2026.02.04 +- xauth: version 1.1.5 +- xfsprogs: version 6.18.0 +- xkbcomp: version 1.5.0 +- xkeyboard-config: version 2.47 +- xkill: version 1.0.7 +- xorg-server: version 21.1.21 +- xterm: version 407 +- xz: version 5.8.2 +- zfs: version 2.4.1_6.18.18_Unraid-x86_64-1_LT +- zlib: version 1.3.2 diff --git a/docs/unraid-os/system-administration/advanced-tools/command-line-interface.mdx b/docs/unraid-os/system-administration/advanced-tools/command-line-interface.mdx index 9215c8a3166..647de112ae1 100644 --- a/docs/unraid-os/system-administration/advanced-tools/command-line-interface.mdx +++ b/docs/unraid-os/system-administration/advanced-tools/command-line-interface.mdx @@ -89,7 +89,7 @@ smartctl -t long /dev/sdX smartctl -a /dev/sdX > /boot/smart_report.txt ``` -This saves the report to your Unraid flash drive for later review or sharing on the [forums](https://forums.unraid.net/). +This saves the report to your Unraid boot drive for later review or sharing on the [forums](https://forums.unraid.net/).
@@ -102,7 +102,7 @@ This script allows for comprehensive surface-level performance testing with visu This used to be a script you would download from the Unraid forums. DiskSpeed is available now in a more refined package: -Install DiskSpeed from [Community Applications](../../using-unraid-to/run-docker-containers/community-applications.mdx) (**_Apps tab_**) by searching for "DiskSpeed", or visit the [GitHub repository](https://github.com/jbartlett777/DiskSpeed) for manual installation instructions. +Install DiskSpeed from [Community Applications](../../using-unraid-to/run-docker-containers/community-applications.mdx) (***Apps tab***) by searching for "DiskSpeed", or visit the [GitHub repository](https://github.com/jbartlett777/DiskSpeed) for manual installation instructions. diff --git a/docs/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx b/docs/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx index 82880422d89..13d80f337ce 100644 --- a/docs/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx +++ b/docs/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx @@ -82,7 +82,7 @@ The plugin manages most sleep configuration options. :::caution[Persistence] WoL settings configured manually are **not persistent** across reboots by default. To make them permanent: - 1. Create a `go` file on your flash drive at `/boot/config/go`. + 1. Create a `go` file on your boot drive at `/boot/config/go`. 2. Add this line: diff --git a/docs/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx b/docs/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx index ec201db96dc..6b186143ba0 100644 --- a/docs/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx +++ b/docs/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx @@ -1,8 +1,8 @@ -1. Go to the **Main** tab and select your flash device. -2. Under **Flash device settings**, click **FLASH BACKUP** to download a zipped backup to your computer. +1. Go to the **Main** tab and select your boot device. +2. In the **Boot Device** tab, click **Boot Device Backup** to download a zipped backup to your computer.
![Flash Backup](/img/flashbackup.png)
-Alternatively, use [Unraid Connect flash backup](../../../../unraid-connect/automated-flash-backup.mdx) for automated flash backups. +Alternatively, use [Unraid Connect automated backup](../../../../unraid-connect/automated-flash-backup.mdx) for automated boot-device backups. diff --git a/docs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx b/docs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx index 5d2ae0e1536..d2cabc1f0d3 100644 --- a/docs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx +++ b/docs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx @@ -18,13 +18,13 @@ Upgrading Unraid OS ensures that you have the latest features, security updates, :::note[Prerequisites] -Before you start upgrading, make sure to create a complete backup of your USB flash device. For more details, refer to [Backing up your flash device](../maintain-and-update/changing-the-flash-device.mdx#backing-up-your-flash-device). +Before you start upgrading, make sure to create a complete backup of your boot device. For more details, refer to [Backing up your boot device](../maintain-and-update/changing-the-flash-device.mdx#backing-up-your-flash-device). ::: :::tip[Best practices before upgrading] -1. **Make a backup** of your flash drive and any important data. +1. **Make a backup** of your boot device and any important data. 2. **Read the Release Notes** for the version you plan to install. 3. **Update all plugins** to their latest versions. 4. **Optionally, stop the array** before proceeding. @@ -137,11 +137,11 @@ Before downgrading, be sure to read the release notes for the version you are do If you have access to the WebGUI, you can go to **Tools → Downgrade OS.** This option allows you to downgrade to your previously installed version without downloading a zip file from the Version History page. -If you don't see the option to downgrade under **Tools → Downgrade OS**, use the manual method described below. This usually means that the files for the previous version are not on your flash drive. +If you don't see the option to downgrade under **Tools → Downgrade OS**, use the manual method described below. This usually means that the files for the previous version are not on your boot device. ### Manual downgrade or upgrade -Manual downgrades are only needed if you can't access the %%WebGUI|web-gui%% or if the downgrade option isn't available. Before proceeding, it's important to back up your USB flash device. For more details, see [Backing up your flash device](../maintain-and-update/changing-the-flash-device.mdx#backing-up-your-flash-device). +Manual downgrades are only needed if you can't access the %%WebGUI|web-gui%% or if the downgrade option isn't available. Before proceeding, it's important to back up your boot device. For more details, see [Backing up your boot device](../maintain-and-update/changing-the-flash-device.mdx#backing-up-your-flash-device). diff --git a/docs/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx b/docs/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx similarity index 62% rename from docs/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx rename to docs/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx index c9135403508..86f9aead6b8 100644 --- a/docs/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx +++ b/docs/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx @@ -1,15 +1,15 @@ --- sidebar_position: 2 -sidebar_label: Securing your flash drive +sidebar_label: Securing your boot device --- -# Securing your flash drive +# Securing your boot device -The flash drive is essential to your Unraid server, as it stores all configuration data, licensing, and system settings. Due to its importance, it’s crucial to keep its contents secure and accessible at all times. +The boot device is essential to your Unraid server, as it stores all configuration data, licensing, and system settings. Due to its importance, it is crucial to keep its contents secure and accessible at all times. ## Backups -Having a recent backup of your flash drive ensures you can quickly recover from hardware failures, accidental changes, or data corruption. Be sure to create backups in the following situations: +Having a recent backup of your boot device ensures you can quickly recover from hardware failures, accidental changes, or data corruption. Be sure to create backups in the following situations: - Before upgrading Unraid or installing plugins - After adding or removing drives @@ -17,19 +17,27 @@ Having a recent backup of your flash drive ensures you can quickly recover from - Before making any major configuration changes - Periodically, as part of your regular maintenance routine -To back up your flash drive using the Unraid %%WebGUI|web-gui%%, follow these steps: +To back up your boot device using the Unraid %%WebGUI|web-gui%%, follow these steps: -1. Select your flash drive from the **Main** tab. -2. In the **Flash Device Settings**, click **Flash Backup**. +1. Select your boot device from the **Main** tab. +2. In the **Boot Device** tab, click **Boot Device Backup**. -
+
![Select the Flash backup button](/img/flashbackup.png)
-3. Unraid will create a ZIP file containing the flash drive's contents. +3. Unraid will create a ZIP file containing the boot device's contents. 4. Save this ZIP file to a secure location outside your Unraid server (like a separate PC, NAS, or cloud storage). -If you need to recreate your flash drive, use this backup with the [USB Creator tool](https://unraid.net/download). +If you need to recreate your boot device, use this backup with the [USB Creator tool](https://unraid.net/download). :::tip @@ -41,16 +49,16 @@ Consider keeping a screenshot of your [disk assignments](../../getting-started/s ## Network access -You can control whether your flash drive is accessible over the network, similar to other shares in Unraid. However, network access should be restricted since the flash drive contains sensitive configuration and licensing data. Consider the following: +You can control whether your boot device is accessible over the network, similar to other shares in Unraid. However, network access should be restricted since the boot device contains sensitive configuration and licensing data. Consider the following: -- **Network visibility:** Decide if your flash drive should be visible or hidden on your network. +- **Network visibility:** Decide if your boot device should be visible or hidden on your network. - **Access rights:** If network access is enabled, set permissions to limit who can view or modify its contents. :::important[Reducing security risks] -- **Disable sharing:** Set the flash drive's %%SMB|samba%% export to **No** to prevent network access entirely. -- **Restrict access:** If you must share the flash drive, set security to **Private** and grant access only to trusted users with strong passwords. -- **Avoid public access:** Never leave the flash drive share set to **Public** or **Secure** with guest write access. +- **Disable sharing:** Set the boot device's %%SMB|samba%% export to **No** to prevent network access entirely. +- **Restrict access:** If you must share the boot device, set security to **Private** and grant access only to trusted users with strong passwords. +- **Avoid public access:** Never leave the `flash` share set to **Public** or **Secure** with guest write access. These steps help prevent unauthorized changes or exposure of critical files. @@ -60,9 +68,9 @@ These steps help prevent unauthorized changes or exposure of critical files. ## Permissions -To enhance system security, files on the flash drive can no longer be given execute permission. This change prevents malicious or unintended code from running directly off the flash drive, reducing the risk of exploitation or accidental system modification. +To enhance system security, files on the boot device can no longer be given execute permission. This change prevents malicious or unintended code from running directly off the boot device, reducing the risk of exploitation or accidental system modification. -If you have custom scripts or programs stored on the flash drive, follow these steps: +If you have custom scripts or programs stored on the boot device, follow these steps: 1. **Copy scripts to an executable location:** - Use `/usr/local/bin` if you want the scripts on the default system path. diff --git a/docs/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx b/docs/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx index 21ea6e566f5..57364725ae6 100644 --- a/docs/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx +++ b/docs/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx @@ -152,9 +152,9 @@ While passwordless access to shares is convenient, it can also put your data at ### Avoid exposing the flash share - or make it private -The Unraid flash device contains critical system and configuration files. While it may be convenient to expose the flash share over %%SMB|samba%% for advanced configuration, this introduces significant risk if left public. +The Unraid boot device contains critical system and configuration files. While it may be convenient to expose the **flash** share over %%SMB|samba%% for advanced configuration, this introduces significant risk if left public. -- Only expose the flash share if absolutely necessary and set it to **Private**. +- Only expose the **flash** share if absolutely necessary and set it to **Private**. - Require a username and strong password for access. - Remove or disable the share when not in use to reduce risk. diff --git a/docs/unraid-os/system-administration/secure-your-server/wireguard.mdx b/docs/unraid-os/system-administration/secure-your-server/wireguard.mdx index d8cb6502e8c..0c2b9bcd1b7 100644 --- a/docs/unraid-os/system-administration/secure-your-server/wireguard.mdx +++ b/docs/unraid-os/system-administration/secure-your-server/wireguard.mdx @@ -248,7 +248,7 @@ WireGuard is designed to be unobtrusive - if something isn’t working, it won If you lose access to the Unraid %%WebGUI|web-gui%% and need to disable %%WireGuard|wireguard%% auto-start - - Delete `/boot/config/wireguard/autostart` from your flash drive and reboot. + - Delete `/boot/config/wireguard/autostart` from your boot drive and reboot. diff --git a/docs/unraid-os/troubleshooting/common-issues/data-recovery.mdx b/docs/unraid-os/troubleshooting/common-issues/data-recovery.mdx index 4f3c32a7e88..a6f086873b8 100644 --- a/docs/unraid-os/troubleshooting/common-issues/data-recovery.mdx +++ b/docs/unraid-os/troubleshooting/common-issues/data-recovery.mdx @@ -26,7 +26,7 @@ Even though Unraid offers protection against various hardware failures, having r - **Multiple backup copies:** Stick to the 3-2-1 rule: keep at least three copies of your data on two different media types, with one copy stored offsite or in the cloud. This minimizes risk from physical disasters like fire or theft. - **Backup frequency:** Schedule regular backups to reduce the chances of data loss. - **Ransomware protection:** At least one backup copy should be offline or inaccessible to protect against potential corruption. -- **Backup tools:** For Unraid 7.0 and above, it's recommended to use [Unraid Connect](../../../unraid-connect/overview-and-setup.mdx) for automated backups of your flash and configuration to the cloud. Additional popular backup solutions include: +- **Backup tools:** For Unraid 7.0 and above, it's recommended to use [Unraid Connect](../../../unraid-connect/overview-and-setup.mdx) for automated backups of your boot device and configuration to the cloud. Additional popular backup solutions include: - **[Duplicati](https://unraid-production-481d40bf.preview.craft.cloud/community/apps?q=Duplicati#r:~:text=of%202%20Apps-,duplicati,-Backup%2C%20Cloud):** A versatile, open-source backup tool that offers deduplication and encryption, supporting cloud, local, USB, and remote destinations. - **[rclone](https://unraid-production-481d40bf.preview.craft.cloud/community/apps?q=rclone#r:~:text=various%20cloud%20services.-,rclone,-Waseh%27s%20Repository):** A robust solution for syncing and backing up cloud storage providers. - **[rsync](https://rsync.samba.org/):** An efficient option for local or remote backups. @@ -36,7 +36,7 @@ Users should assess their risk tolerance and backup needs, but utilizing cloud i :::tip[Modern backup strategy] -With Unraid 7.0 and up, enable [Unraid Connect](../../../unraid-connect/overview-and-setup.mdx) for automated cloud backups of your flash device and configuration. Consider using Duplicati, rclone, or similar tools for important files and shares to create scheduled backups to local, remote, or cloud destinations. Always test your restore process to ensure your backups will work when needed. +With Unraid 7.0 and up, enable [Unraid Connect](../../../unraid-connect/overview-and-setup.mdx) for automated cloud backups of your boot device and configuration. Consider using Duplicati, rclone, or similar tools for important files and shares to create scheduled backups to local, remote, or cloud destinations. Always test your restore process to ensure your backups will work when needed. ::: @@ -222,7 +222,7 @@ If these repair attempts do not resolve the issue or if you encounter errors you ## Lost array configuration -Losing your %%array|array%% configuration can be stressful, but it doesn't mean your data is gone. The %%array|array%% configuration file (located at `config/super.dat` on your flash device) tells Unraid how your drives are assigned and which ones serve as %%parity|parity%%. If you've lost your flash drive or don’t have a recent backup, you can recover your %%array|array%% by carefully reassigning the drives. +Losing your %%array|array%% configuration can be stressful, but it doesn't mean your data is gone. The %%array|array%% configuration file (located at `config/super.dat` on your boot device) tells Unraid how your drives are assigned and which ones serve as %%parity|parity%%. If you've lost your boot device or don’t have a recent backup, you can recover your %%array|array%% by carefully reassigning the drives. Here’s what to do if you find yourself in this situation: diff --git a/docs/unraid-os/troubleshooting/common-issues/docker-troubleshooting.mdx b/docs/unraid-os/troubleshooting/common-issues/docker-troubleshooting.mdx index 3040de7c091..d73fdce8060 100644 --- a/docs/unraid-os/troubleshooting/common-issues/docker-troubleshooting.mdx +++ b/docs/unraid-os/troubleshooting/common-issues/docker-troubleshooting.mdx @@ -34,7 +34,7 @@ Now you’re ready to reinstall your containers using their saved settings. ## Reinstalling Docker applications -Unraid automatically saves a template for each installed container on your flash drive. These templates store your configuration, making it easy to restore containers after recreating the Docker image file. +Unraid automatically saves a template for each installed container on your boot device. These templates store your configuration, making it easy to restore containers after recreating the Docker image file. To reinstall your containers: diff --git a/docs/unraid-os/troubleshooting/common-issues/partials/unclean-shutdowns/flash-drive-failure.mdx b/docs/unraid-os/troubleshooting/common-issues/partials/unclean-shutdowns/flash-drive-failure.mdx index 0492adbde38..83bc3c5f305 100644 --- a/docs/unraid-os/troubleshooting/common-issues/partials/unclean-shutdowns/flash-drive-failure.mdx +++ b/docs/unraid-os/troubleshooting/common-issues/partials/unclean-shutdowns/flash-drive-failure.mdx @@ -1 +1 @@ -The %%array|array%% status is stored on your USB flash device. If the flash drive becomes unavailable or enters a read-only state, Unraid cannot update the shutdown status, even if the %%array|array%% stops correctly. This results in an unclean shutdown being detected at the next boot. +The %%array|array%% status is stored on your boot device. If the boot device becomes unavailable or enters a read-only state, Unraid cannot update the shutdown status, even if the %%array|array%% stops correctly. This results in an unclean shutdown being detected at the next boot. diff --git a/docs/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx b/docs/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx index 79b42645ad6..22129dfdf30 100644 --- a/docs/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx +++ b/docs/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx @@ -18,8 +18,8 @@ Taking some proactive steps can help you avoid or identify unclean shutdowns: - **Use a UPS:** Keep your server connected to an Uninterruptible Power Supply (UPS) and set it up to initiate a controlled shutdown when battery power runs low. - **Attempt a graceful shutdown:** If your server is unresponsive, briefly press the power button to trigger a safe shutdown. Do not hold the button down, as this will force a hard power off and lead to an unclean shutdown. -- **Enable persistent logging:** Go to **_Settings → Syslog Server_** to activate logging that persists after a reboot. See [Persistent logs (Syslog server)](../diagnostics/capture-diagnostics-and-logs.mdx#persistent-logs-syslog-server) for more details. -- **Attach diagnostics for support:** If an unclean shutdown occurs, Unraid will attempt to save diagnostics to `/log/diagnostics.zip` on your flash device. Attach this file to forum posts when you seek help. +- **Enable persistent logging:** Go to ***Settings → Syslog Server*** to activate logging that persists after a reboot. See [Persistent logs (Syslog server)](../diagnostics/capture-diagnostics-and-logs.mdx#persistent-logs-syslog-server) for more details. +- **Attach diagnostics for support:** If an unclean shutdown occurs, Unraid will attempt to save diagnostics to `/log/diagnostics.zip` on your boot device. Attach this file to forum posts when you seek help. ::: @@ -28,7 +28,7 @@ Taking some proactive steps can help you avoid or identify unclean shutdowns: A well-configured UPS is your best defense against unclean shutdowns caused by power loss. - **Connect the UPS via USB** to your Unraid server. -- **Enable UPS support** in **_Settings → UPS Settings_**. +- **Enable UPS support** in ***Settings → UPS Settings***. - **Configure shutdown timeouts:** Set the UPS to trigger a controlled shutdown before the battery runs low. Adjust the "Battery runtime left" or "Battery charge level" thresholds to provide enough time for Unraid to [stop the %%array|array%%](../../using-unraid-to/manage-storage/array/overview.mdx#startstop-the-array) and power down safely. - **Test your configuration:** Simulate a power loss to ensure the UPS and Unraid respond correctly. @@ -50,9 +50,9 @@ Unraid supports most UPS units using the %%apcupsd Protocol|apcupsd%% protocol ( ::: -### Flash drive failure +### Boot device failure -The %%array|array%% status is stored on your USB flash device. If the flash drive becomes unavailable or enters a read-only state, Unraid cannot update the shutdown status, even if the %%array|array%% stops correctly. This results in an unclean shutdown being detected at the next boot. +The %%array|array%% status is stored on your boot device. If the boot device becomes unavailable or enters a read-only state, Unraid cannot update the shutdown status, even if the %%array|array%% stops correctly. This results in an unclean shutdown being detected at the next boot. ### Open terminal sessions @@ -172,9 +172,9 @@ In this section, we’ll cover how to configure timeouts for various systems and | Setting | Default | When to increase | Where to configure | | ----------------------------- | ------- | ------------------------------------------------- | ---------------------------------------------------- | -| %%VM\|vm%% shutdown timeout | 60s | 300s if not using hibernation and VMs crash | **_Settings → VM Manager → VM Shutdown (Advanced)_** | -| Docker container stop timeout | 10s | 30s if any containers are crashing when stopped | **_Settings → Docker (Advanced)_** | -| General shutdown timeout | 90s | 180s if you get unclean shutdowns, 300s+ with VMs | **_Settings → Disk Settings → Shutdown time-out_** | +| %%VM\|vm%% shutdown timeout | 60s | 300s if not using hibernation and VMs crash | ***Settings → VM Manager → VM Shutdown (Advanced)*** | +| Docker container stop timeout | 10s | 30s if any containers are crashing when stopped | ***Settings → Docker (Advanced)*** | +| General shutdown timeout | 90s | 180s if you get unclean shutdowns, 300s+ with VMs | ***Settings → Disk Settings → Shutdown time-out*** | :::tip[When to increase timeouts] @@ -223,7 +223,7 @@ This section provides in-depth information about configuring timeouts for differ #### VM timeouts -Configure VM shutdown timeouts in **_Settings → VM Manager → VM Shutdown_** (enable Advanced view). +Configure VM shutdown timeouts in ***Settings → VM Manager → VM Shutdown*** (enable Advanced view). **How it works:** @@ -252,7 +252,7 @@ Without hibernation and %%QEMU|qemu%% %%Guest Agent|guest-agent%%, there isn't a #### Docker timeouts -Configure Docker container stop timeouts in **_Settings → Docker_** (enable Advanced view). +Configure Docker container stop timeouts in ***Settings → Docker*** (enable Advanced view). **How it works:** @@ -271,7 +271,7 @@ Configure Docker container stop timeouts in **_Settings → Docker_** (enable Ad #### General timeouts -Configure the general shutdown timeout in **_Settings → Disk Settings → Shutdown time-out_**. +Configure the general shutdown timeout in ***Settings → Disk Settings → Shutdown time-out***. **UPS considerations (most critical factor):** diff --git a/docs/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx b/docs/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx index 2f332453d99..b6b4d64cfe4 100644 --- a/docs/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx +++ b/docs/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx @@ -53,7 +53,7 @@ Attach the single diagnostics zip file when posting on forums - avoid uploading By default, diagnostics are automatically anonymized. If you enable %%Mover|mover%% logging under ***Settings → Scheduler → Mover Settings***, the %%syslog|syslog%% will include details about files the %%Mover|mover%% processes. It's best to allow %%Mover|mover%% logging only when troubleshooting specific %%Mover|mover%%-related issues, as it may reveal file paths and names. -When your system shuts down gracefully, the session log is saved automatically to the flash drive. You can access it after rebooting by going to ***Tools → Syslog → syslog-previous***. This log is also included in diagnostics on the next boot. However, if the system crashes, the system log will be lost. In these cases, enabling %%syslog|syslog%% mirroring to the flash or using a remote %%syslog server|syslog-server%% is recommended to preserve logs for troubleshooting. +When your system shuts down gracefully, the session log is saved automatically to the boot device. You can access it after rebooting by going to ***Tools → Syslog → syslog-previous***. This log is also included in diagnostics on the next boot. However, if the system crashes, the system log will be lost. In these cases, enabling %%syslog|syslog%% mirroring to the boot device or using a remote %%syslog server|syslog-server%% is recommended to preserve logs for troubleshooting. --- @@ -147,9 +147,9 @@ Go to ***Settings → Syslog Server*** to set up persistent logging. Each method | Method | Pros | Cons | Best for | | ----------------------------- | ------------------------------------------------------------------------------ | ----------------------------------------- | ------------------------------------------- | -| **Mirror to flash** | Captures boot process events | Can wear out flash drive quickly | Short-term diagnostics (a few days) | +| **Mirror syslog to boot drive** | Captures boot process events | Can wear out the boot device quickly | Short-term diagnostics (a few days) | | **Remote %%syslog\|syslog%%** | Logs are stored on another device | Needs a separate always-on server | Long-term monitoring (weeks to months) | -| **Local %%syslog\|syslog%%** | Keeps logs on the %%array\|array%% or %%cache\|cache%%, reducing wear on flash | Less accessible if there's a system crash | Continuous logging without external devices | +| **Local %%syslog\|syslog%%** | Keeps logs on the %%array\|array%% or %%cache\|cache%%, reducing wear on the boot device | Less accessible if there's a system crash | Continuous logging without external devices | :::tip @@ -160,7 +160,7 @@ For detailed configuration help, check the **Help** icon in the WebGUI toolbar. ### Enabling the syslog server - + diff --git a/docs/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdx b/docs/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdx index ef66f8d1e44..b9eee82130f 100644 --- a/docs/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdx +++ b/docs/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdx @@ -5,7 +5,7 @@ To create a persistent, reliable copy of your Unraid %%syslog|syslog%% on your s - **Local %%syslog|syslog%% folder**: Use a cache-only or preferred share (best for SSDs). - **Rotation settings**: Adjust the file size and number limits. 3. For best results and to ensure all %%syslog|syslog%% data (including boot events) is captured, set the **Remote %%syslog server|syslog-server%%** field to your server's own IP address (the "Loopback method"), or the %%syslog|syslog%% will not be saved to the set share. - - This ensures %%syslog|syslog%% events are both stored locally and persist across reboots, without writing to the flash drive. + - This ensures %%syslog|syslog%% events are both stored locally and persist across reboots, without writing to the boot device. 4. Click **Apply**. - Logs will be saved to the share you specified. diff --git a/docs/unraid-os/troubleshooting/diagnostics/partials/syslog-server/mirror.mdx b/docs/unraid-os/troubleshooting/diagnostics/partials/syslog-server/mirror.mdx index 30171b7c59b..0165ddb65ae 100644 --- a/docs/unraid-os/troubleshooting/diagnostics/partials/syslog-server/mirror.mdx +++ b/docs/unraid-os/troubleshooting/diagnostics/partials/syslog-server/mirror.mdx @@ -1,17 +1,17 @@ -1. Select **Yes** under **Mirror to flash**. -2. Click **Apply**. Logs will be saved to `/boot/logs/syslog` on your flash drive +1. Select **Yes** under **Mirror syslog to boot drive**. +2. Click **Apply**. Logs will be saved to `/boot/logs/syslog` on your boot device On the next reboot, this file will be renamed to `/boot/logs/syslog-previous`. You can view this file through **Tools → Syslog → syslog-previous**, and it will also be included (anonymized) in diagnostics.

How it works

-- By default, Unraid copies the %%syslog|syslog%% to the flash drive during every graceful shutdown. This is managed through the "copy %%syslog|syslog%% to flash on shutdown" setting, which is enabled by default. -- If you're troubleshooting crashes, you can enable "Mirror to flash." This will write the %%syslog|syslog%% to both `/var/log/syslog` and `/boot/logs/syslog` in real time. If a crash happens, any %%syslog|syslog%% entries recorded to flash before the crash will be preserved. +- By default, Unraid copies the %%syslog|syslog%% to the boot device during every graceful shutdown. This is managed through the "Copy %%syslog|syslog%% to boot drive on shutdown" setting, which is enabled by default. +- If you're troubleshooting crashes, you can enable "Mirror syslog to boot drive." This will write the %%syslog|syslog%% to both `/var/log/syslog` and `/boot/logs/syslog` in real time. If a crash happens, any %%syslog|syslog%% entries recorded to the boot device before the crash will be preserved. Both methods result in the creation of a `/boot/logs/syslog-previous` file after the next boot, which you can access via the %%syslog|syslog%% viewer and will be included in diagnostics. :::caution -The **Copy %%syslog|syslog%% to flash on shutdown** setting is safe for your flash drive. However, enabling **Mirror to flash** can lead to excessive writes if left on for an extended period. For long-term logging needs, consider using a local or remote %%syslog server|syslog-server%% instead. +The **Copy %%syslog|syslog%% to boot drive on shutdown** setting is safe for your boot device. However, enabling **Mirror syslog to boot drive** can lead to excessive writes if left on for an extended period. For long-term logging needs, consider using a local or remote %%syslog server|syslog-server%% instead. ::: diff --git a/docs/unraid-os/troubleshooting/faq.mdx b/docs/unraid-os/troubleshooting/faq.mdx index c6b89588f88..1630756346a 100644 --- a/docs/unraid-os/troubleshooting/faq.mdx +++ b/docs/unraid-os/troubleshooting/faq.mdx @@ -126,6 +126,7 @@ Replace `X` with the correct drive letter (e.g., sda, sdb, sdc) ::: + 8. Continue with the normal Unraid setup and configuration.
@@ -134,7 +135,7 @@ Replace `X` with the correct drive letter (e.g., sda, sdb, sdc) ### How do I change the hostname of my server? -To change your Unraid server's hostname, navigate the %%WebGUI|web-gui%% to **_Settings → System Settings → Identification_**. +To change your Unraid server's hostname, navigate the %%WebGUI|web-gui%% to ***Settings → System Settings → Identification***. **Effects of changing your hostname:** @@ -251,8 +252,8 @@ Before starting the conversion process, put your %%array|array%% into **Maintena Conversion process
-1. Ensure you have a valid %%parity|parity%% and a current backup of your flash drive. -2. Enter **Maintenance Mode** from the **_Main_** tab. +1. Ensure you have a valid %%parity|parity%% and a current backup of your boot device. +2. Enter **Maintenance Mode** from the ***Main*** tab. 3. Replace and rebuild your %%parity|parity%% drive first. 4. Swap out each data drive one at a time, rebuilding the %%array|array%% after each replacement. 5. The new drive will be formatted with the appropriate partitioning style based on its size: @@ -269,7 +270,7 @@ This process keeps your data safe while changing the partitioning style. - **Larger than 2TB**: Always uses GPT partitioning - Starting with Unraid OS 6.9, partition 1 starts at 32KiB for rotational devices and 1MiB for non-rotational devices, regardless of the partition style. - -- Always [back up your flash drive](../system-administration/secure-your-server/secure-your-flash-drive.mdx#backups) before starting this conversion process. + -- Always [back up your boot device](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) before starting this conversion process. ::: @@ -338,7 +339,7 @@ When using the USB flash creator, select the option to enable %%UEFI|uefi%% boot #### Option 2: After booting in Legacy Mode -In the %%WebGUI|web-gui%%, head to the Flash Device **_Settings → Flash Device_** page. +In the %%WebGUI|web-gui%%, head to the Flash Device ***Settings → Flash Device*** page. Enable %%UEFI|uefi%% boot mode and reboot your server. diff --git a/docs/unraid-os/troubleshooting/licensing-faq.mdx b/docs/unraid-os/troubleshooting/licensing-faq.mdx index 134e671bfae..4f17f550054 100644 --- a/docs/unraid-os/troubleshooting/licensing-faq.mdx +++ b/docs/unraid-os/troubleshooting/licensing-faq.mdx @@ -67,11 +67,11 @@ You can upgrade your license at any time from within the %%WebGUI|web-gui%% (*** **Annual extension fee** (Starter & Unleashed only): $36 USD -1 Attached storage devices refers to the total number of drives you may attach before starting the %%array|array%% (does not include the USB flash boot device).\ +1 Attached storage devices include all devices present before array start, except one eMMC device and one USB device.\ 2 "Unlimited" means you are not limited by the license, but by hardware and OS constraints. Additional storage devices can be used for %%VMs|vm%%, unassigned devices, or other Unraid features.\* -### How do I manually install my license keyfile to my USB flash device? {#manual-keyfile-install} +### How do I manually install my license keyfile to my boot device? {#manual-keyfile-install} #### Install via WebGUI download @@ -88,13 +88,41 @@ You can upgrade your license at any time from within the %%WebGUI|web-gui%% (*** #### Install via USB flash drive -1. Ensure you have a recent backup of your USB drive. Use [Unraid Connect](../../unraid-connect/overview-and-setup.mdx) (recommended) or the local backup option at ***Main → Flash → Flash Backup***. +This does not apply if you have configured internal boot. + +1. Ensure you have a recent backup of your USB drive. Use [Unraid Connect](../../unraid-connect/overview-and-setup.mdx) (recommended) or the local backup option at ***Main → Boot Device → Boot Device Backup***. 2. Shut down your Unraid server and remove the USB flash device. 3. Insert the USB flash into another computer. 4. Open the USB drive and copy your `.key` file into the `/config` folder. *Make sure this is the only `.key` file present - delete any others.* 5. Safely eject the USB flash device, reinstall it in your server, and reboot. +### How can I move from flash-based licensing to TPM-based licensing? {#tpm} + +:::note[Unraid 7.3 and later] + +TPM-based licensing is available in Unraid 7.3 and later. + +::: + +All new and replacement keys use TPM-based licensing when possible because it is more reliable than flash-based licensing. + +To proactively switch to TPM-based licensing, navigate to ***Tools → Registration*** and click **Move License to TPM**. You are taken to the Unraid Account website, where you can approve the transfer. + +If the **Move License to TPM** button isn't available, Unraid could not detect your TPM 2.0 device. It may be disabled in your BIOS. Check settings related to **Trusted Computing**, and leave **Secure Boot** disabled. + +### What are the benefits of moving to TPM-based licensing? {#tpm-benefits} + +USB flash devices are becoming less reliable. TPM-based licensing means your license remains valid even if you change boot devices. + +### What if I get a new motherboard? {#tpm-new-motherboard} + +You can transfer a TPM-based license to a new motherboard, similar to transferring a flash-based license to a new USB device. In this case, only the original license is blacklisted, not the entire motherboard. + +### What if my motherboard does not have a TPM device? {#tpm-missing} + +Moving to TPM-based licensing is not a hard requirement, but many older motherboards include a header where a TPM add-on device can be installed. These devices are inexpensive and widely available. + ### How can I determine my registration type? {#registration-type} Navigate to ***Tools → Registration*** in the %%WebGUI|web-gui%%. Here, you can find your current license type and registration details. @@ -140,15 +168,15 @@ Here are the current limits:
| License Tier | %%Parity\|parity%%-Protected %%Array\|array%% | Named Pools | Devices per Pool | Total Attached Storage Devices | -| ------------ | --------------------------------------------- | ----------- | ---------------- | --------------------- | -| Starter | Up to 6 (including parity) | Up to 6 | Up to 6 | Up to 6¹ | -| Unleashed | Up to 30 (28 data + 2 %%parity\|parity%%) | Up to 34 | Up to 200 | Unlimited² | -| Lifetime | Up to 30 (28 data + 2 %%parity\|parity%%) | Up to 34 | Up to 200 | Unlimited² | +| ------------ | --------------------------------------------- | ----------- | ---------------- | ------------------------------ | +| Starter | Up to 6 (including parity) | Up to 6 | Up to 6 | Up to 6¹ | +| Unleashed | Up to 30 (28 data + 2 %%parity\|parity%%) | Up to 34 | Up to 200 | Unlimited² | +| Lifetime | Up to 30 (28 data + 2 %%parity\|parity%%) | Up to 34 | Up to 200 | Unlimited² |
-1 Attached storage devices refers to the total number of drives you may attach before starting the %%array|array%% (does not include the USB flash boot device).\ +1 Attached storage devices include all devices present before %%array|array%% start, except one eMMC device and one USB device.\ 2 "Unlimited" means you are not limited by the license, but by hardware and OS constraints. Additional storage devices can be used for %%VMs|vm%%, unassigned devices, or other Unraid features.\* @@ -172,7 +200,7 @@ The first transfer can be done at any time, while subsequent transfers are allow :::tip -Routinely back up your USB device using [Unraid Connect](../../unraid-connect/overview-and-setup.mdx) to simplify recovery and avoid data loss. +Routinely back up your boot device using [Unraid Connect](../../unraid-connect/overview-and-setup.mdx) to simplify recovery and avoid data loss. ::: diff --git a/docs/unraid-os/troubleshooting/partials/licensing-faq/manual-keyfile-offline.mdx b/docs/unraid-os/troubleshooting/partials/licensing-faq/manual-keyfile-offline.mdx index 5d54cad138c..79ab3582ce9 100644 --- a/docs/unraid-os/troubleshooting/partials/licensing-faq/manual-keyfile-offline.mdx +++ b/docs/unraid-os/troubleshooting/partials/licensing-faq/manual-keyfile-offline.mdx @@ -1,4 +1,4 @@ -1. Ensure you have a recent backup of your USB drive. Use [Unraid Connect](../../../../unraid-connect/overview-and-setup.mdx) (recommended) or the local backup option at ***Main → Flash → Flash Backup***. +1. Ensure you have a recent backup of your USB drive. Use [Unraid Connect](../../../../unraid-connect/overview-and-setup.mdx) (recommended) or the local backup option at ***Main → Boot Device → Boot Device Backup***. 2. Shut down your Unraid server and remove the USB flash device. 3. Insert the USB flash into another computer. 4. Open the USB drive and copy your `.key` file into the `/config` folder. diff --git a/docs/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx b/docs/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx index f746d2f2f3c..323edb8c25c 100644 --- a/docs/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx +++ b/docs/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx @@ -17,7 +17,7 @@ Regularly checking your Unraid array is crucial for maintaining data integrity a ## Checking array devices -You can initiate a check using the **Check** button under **_Array Operations_**. Depending on your array's configuration, this button allows you to conduct either a %%parity check|parity-check%% or a %%read check|read-check%%. +You can initiate a check using the **Check** button under ***Array Operations***. Depending on your array's configuration, this button allows you to conduct either a %%parity check|parity-check%% or a %%read check|read-check%%.
-For convenience, you can schedule these checks to run automatically at intervals that suit you by navigating to **_Settings → Scheduler_**. It's advisable to perform automated, correcting checks on a monthly or quarterly basis to ensure the ongoing health of your data and fix any sync errors found. +For convenience, you can schedule these checks to run automatically at intervals that suit you by navigating to ***Settings → Scheduler***. It's advisable to perform automated, correcting checks on a monthly or quarterly basis to ensure the ongoing health of your data and fix any sync errors found. ### Parity checks @@ -44,9 +44,9 @@ For convenience, you can schedule these checks to run automatically at intervals ### Check history -Whenever the system performs a %%parity check|parity-check%% or a %%read check|read-check%%, it keeps a record of what happened. You can view these details easily by clicking the **History** button found under **_Array Operations_** in the interface. +Whenever the system performs a %%parity check|parity-check%% or a %%read check|read-check%%, it keeps a record of what happened. You can view these details easily by clicking the **History** button found under ***Array Operations*** in the interface. -For those who want to dive deeper, all these records are saved in a text file located in the `config` directory on your Unraid USB flash device. +For those who want to dive deeper, all these records are saved in a text file located in the `config` directory on your Unraid boot device. ## Spinning disks down or up @@ -128,7 +128,7 @@ Do not use **New Config** if your goal is to rebuild a disk. Performing a New Co To reverse a reset: -1. Access your flash device over the network (SMB). +1. Access your boot device over the network (SMB). 2. Open the `config` folder. 3. Rename `super.old` to `super.dat`. 4. Reboot your server to restore the prior configuration. @@ -149,7 +149,7 @@ Remember that the status reports don't include %%SMART|smart%% data. %%SMART rep ## Troubleshooting array start failures -If your array won't start, follow these steps to identify and fix common problems. Look for error messages under **_Main → Array Operation_**. +If your array won't start, follow these steps to identify and fix common problems. Look for error messages under ***Main → Array Operation***. ### Missing disks diff --git a/docs/unraid-os/using-unraid-to/manage-storage/shares.mdx b/docs/unraid-os/using-unraid-to/manage-storage/shares.mdx index 0ae5e6efeec..282ecb688e7 100644 --- a/docs/unraid-os/using-unraid-to/manage-storage/shares.mdx +++ b/docs/unraid-os/using-unraid-to/manage-storage/shares.mdx @@ -494,7 +494,7 @@ Once you enable them, you'll notice disk shares in the Unraid GUI under a sectio :::important -The Unraid flash device, which stores your Unraid settings, is not treated as a disk share. If you want it to be accessible over the network, you can set it up as a share named 'flash'. This device is mounted at `/boot` in Linux. +The Unraid boot device, which stores your Unraid settings, is not treated as a disk share. If you want it to be accessible over the network, you can set it up as a share named 'flash'. This device is mounted at `/boot` in Linux. For security, it's best to keep your shares in *Private* mode and only grant access to trusted users. diff --git a/docs/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx b/docs/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx index 4759c279c0f..31a7a7ff421 100644 --- a/docs/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx +++ b/docs/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx @@ -52,7 +52,7 @@ To install the Community Applications plugin: :::tip -Before installing, consider backing up your flash drive to protect your configuration. See [Secure your flash drive](../../system-administration/secure-your-server/secure-your-flash-drive.mdx) for backup guidance. +Before installing, consider backing up your boot device to protect your configuration. See [Secure your boot device](../../system-administration/secure-your-server/secure-your-boot-drive.mdx) for backup guidance. ::: diff --git a/docs/unraid-os/using-unraid-to/run-docker-containers/overview.mdx b/docs/unraid-os/using-unraid-to/run-docker-containers/overview.mdx index 3221f67838d..d7190d89ace 100644 --- a/docs/unraid-os/using-unraid-to/run-docker-containers/overview.mdx +++ b/docs/unraid-os/using-unraid-to/run-docker-containers/overview.mdx @@ -25,7 +25,7 @@ Unraid’s Docker integration is designed to be user-friendly for everyone. Each - **Storage:** All the data and programs for each container are stored in a single %%virtual disk image|virtual-disk-images%% file called `docker.img`. By default, this file is found in the `system` %%user share|user-share%%, which usually utilizes the %%cache pool|cache-pool%% for better speed. - **File system:** The `docker.img` file uses the %%BTRFS|btrfs%% file system and is mounted internally by Unraid. For more information on file systems, see [File systems](../manage-storage/file-systems.mdx). - - **Configuration:** When you set up a container, Unraid saves your configuration as a %%VM XML template|vm-xml-templates%% on the flash drive. This makes it easy to reinstall or restore containers with your preferred settings. + - **Configuration:** When you set up a container, Unraid saves your configuration as a %%VM XML template|vm-xml-templates%% on the boot device. This makes it easy to reinstall or restore containers with your preferred settings. - **Templates:** Many popular containers come with ready-made templates, making the initial setup less complicated. - **Performance:** It’s a good idea to store `docker.img` on the %%cache pool|cache-pool%% (if you have one) for the best performance. - **Limitations:** Unraid does not natively support Docker Compose. For more complex setups, check out the [official Docker Compose documentation](https://docs.docker.com/compose/). diff --git a/docusaurus.config.ts b/docusaurus.config.ts index 1bbd6aeed24..97a80f0d4e2 100644 --- a/docusaurus.config.ts +++ b/docusaurus.config.ts @@ -506,7 +506,11 @@ const config: Config = { }, { from: "/unraid-os/manual/security/flash-drive/", - to: "/unraid-os/system-administration/secure-your-server/secure-your-flash-drive/", + to: "/unraid-os/system-administration/secure-your-server/secure-your-boot-drive/", + }, + { + from: "/unraid-os/system-administration/secure-your-server/secure-your-flash-drive/", + to: "/unraid-os/system-administration/secure-your-server/secure-your-boot-drive/", }, { from: "/unraid-os/manual/security/good-practices/", diff --git a/glossary.yaml b/glossary.yaml index bff875c5070..084895df005 100644 --- a/glossary.yaml +++ b/glossary.yaml @@ -135,7 +135,7 @@ guest-agent: guid: term: GUID - def: “Globally Unique Identifier,” a unique reference number for identifying hardware devices or software components. Each Unraid USB flash drive has a unique GUID that is used for licensing. + def: “Globally Unique Identifier,” a unique reference number used to identify hardware devices or software components. In Unraid, licensing can be bound either to a USB flash device GUID or to TPM-based hardware identity. link: See GUID - Wikipedia hba-mode: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx b/i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx index 361d3490b8d..968439ff521 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx @@ -265,7 +265,7 @@ Dieser Prozess hält Ihre Daten sicher, während der Partitionierungsstil geänd - **2TB oder kleiner**: Verwendet immer MBR-Partitionierung - **Größer als 2TB**: Verwendet immer GPT-Partitionierung -- Ab Unraid OS 6.9 beginnt Partition 1 bei 32 KiB für rotierende Geräte und 1 MiB für nicht rotierende Geräte, unabhängig vom Partitionsstil.\n -- Sichern Sie immer [Ihr Flash-Laufwerk](../system-administration/secure-your-server/secure-your-flash-drive.mdx#backups), bevor Sie diesen Konvertierungsprozess starten. +- Ab Unraid OS 6.9 beginnt Partition 1 bei 32 KiB für rotierende Geräte und 1 MiB für nicht rotierende Geräte, unabhängig vom Partitionsstil.\n -- Sichern Sie immer [Ihr Flash-Laufwerk](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups), bevor Sie diesen Konvertierungsprozess starten. ::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx b/i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx index 7649197c846..decbd68586d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx +++ b/i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx @@ -60,7 +60,7 @@ Um das Community-Anwendungs-Plugin zu installieren: :::tip -Bevor Sie installieren, sollten Sie in Erwägung ziehen, Ihr Flash-Laufwerk zu sichern, um Ihre Konfiguration zu schützen. Siehe [Sichern Sie Ihr Flash-Laufwerk](../../system-administration/secure-your-server/secure-your-flash-drive.mdx) für Sicherungsanweisungen. +Bevor Sie installieren, sollten Sie in Erwägung ziehen, Ihr Flash-Laufwerk zu sichern, um Ihre Konfiguration zu schützen. Siehe [Sichern Sie Ihr Flash-Laufwerk](../../system-administration/secure-your-server/secure-your-boot-drive.mdx) für Sicherungsanweisungen. ::: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx b/i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx index 217dd3e9772..14880e5ab8d 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx @@ -269,7 +269,7 @@ Este proceso mantiene su información segura mientras cambia el estilo de partic - **Mayor a 2TB**: Siempre usa particionamiento GPT - A partir de Unraid OS 6.9, la partición 1 comienza a las 32KiB para dispositivos rotacionales y a las 1MiB para dispositivos no rotacionales, independientemente del estilo de partición. - \-- Siempre [respalda tu unidad flash](../system-administration/secure-your-server/secure-your-flash-drive.mdx#backups) antes de comenzar este proceso de conversión. + \-- Siempre [respalda tu unidad flash](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) antes de comenzar este proceso de conversión. ::: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx b/i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx index f0312645088..d147fec0a2d 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx @@ -52,7 +52,7 @@ Para instalar el complemento Aplicaciones de la Comunidad: :::tip -Antes de instalar, considera realizar una copia de seguridad de tu flash para proteger tu configuración. Consulta [Asegura tu unidad flash](../../system-administration/secure-your-server/secure-your-flash-drive.mdx) para obtener orientación sobre copias de seguridad. +Antes de instalar, considera realizar una copia de seguridad de tu flash para proteger tu configuración. Consulta [Asegura tu unidad flash](../../system-administration/secure-your-server/secure-your-boot-drive.mdx) para obtener orientación sobre copias de seguridad. ::: diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx b/i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx index 3f740fabfbf..cec6e9aedb9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx @@ -269,7 +269,7 @@ Ce processus garde vos données en sécurité tout en changeant le style de part - **2 To ou moins** : Utilise toujours un partitionnement MBR - **Plus grand que 2 To** : Utilise toujours un partitionnement GPT -- À partir d'Unraid OS 6.9, la partition 1 commence à 32KiB pour les dispositifs rotatifs et à 1MiB pour les dispositifs non rotatifs, quel que soit le style de partition.\n -- Toujours [sauvegarder votre clé USB](../system-administration/secure-your-server/secure-your-flash-drive.mdx#backups) avant de commencer ce processus de conversion. +- À partir d'Unraid OS 6.9, la partition 1 commence à 32KiB pour les dispositifs rotatifs et à 1MiB pour les dispositifs non rotatifs, quel que soit le style de partition.\n -- Toujours [sauvegarder votre clé USB](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) avant de commencer ce processus de conversion. ::: diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx b/i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx index 0807676069f..aee54660030 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx @@ -52,7 +52,7 @@ Pour installer le plugin Community Applications : :::tip -Avant d'installer, envisagez de sauvegarder votre clé USB pour protéger votre configuration. Consultez [Sécurisez votre clé USB](../../system-administration/secure-your-server/secure-your-flash-drive.mdx) pour obtenir des conseils de sauvegarde. +Avant d'installer, envisagez de sauvegarder votre clé USB pour protéger votre configuration. Consultez [Sécurisez votre clé USB](../../system-administration/secure-your-server/secure-your-boot-drive.mdx) pour obtenir des conseils de sauvegarde. ::: diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx b/i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx index 6acf02c9340..5a3fb64c2bd 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx +++ b/i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx @@ -269,7 +269,7 @@ MBR (主引导记录) 分区支持的磁盘最大为 2TB，并且仅允许最多 - **大于2TB**：始终使用GPT分区 - 从 Unraid OS 6.9 开始，分区 1 无论分区样式如何，旋转设备的起始位置为 32KiB，非旋转设备的起始位置为 1MiB。 - \-- 在开始此转换过程之前，请始终[备份您的闪存驱动器](../system-administration/secure-your-server/secure-your-flash-drive.mdx#backups)。 + \-- 在开始此转换过程之前，请始终[备份您的闪存驱动器](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups)。 ::: diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx b/i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx index a1efaa5758d..868fb846a31 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx +++ b/i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx @@ -52,7 +52,7 @@ Lime Technology 并不提供或者直接支持社区应用程序（Community App :::tip -在安装前，建议备份您的闪存盘以保护配置。查看 [保护您的闪存盘](../../system-administration/secure-your-server/secure-your-flash-drive.mdx) 以获取备份指南。 +在安装前，建议备份您的闪存盘以保护配置。查看 [保护您的闪存盘](../../system-administration/secure-your-server/secure-your-boot-drive.mdx) 以获取备份指南。 ::: diff --git a/static/img/onboarding_step1.png b/static/img/onboarding_step1.png new file mode 100644 index 00000000000..b9f34b76a65 Binary files /dev/null and b/static/img/onboarding_step1.png differ diff --git a/static/img/onboarding_step2.png b/static/img/onboarding_step2.png new file mode 100644 index 00000000000..b52442181e1 Binary files /dev/null and b/static/img/onboarding_step2.png differ diff --git a/static/img/onboarding_step3a.png b/static/img/onboarding_step3a.png new file mode 100644 index 00000000000..65f7e3d85b2 Binary files /dev/null and b/static/img/onboarding_step3a.png differ diff --git a/static/img/onboarding_step3b.png b/static/img/onboarding_step3b.png new file mode 100644 index 00000000000..bc29299112d Binary files /dev/null and b/static/img/onboarding_step3b.png differ diff --git a/static/img/onboarding_step4.png b/static/img/onboarding_step4.png new file mode 100644 index 00000000000..637e10fbeed Binary files /dev/null and b/static/img/onboarding_step4.png differ diff --git a/static/img/onboarding_step5.png b/static/img/onboarding_step5.png new file mode 100644 index 00000000000..e805c0c43eb Binary files /dev/null and b/static/img/onboarding_step5.png differ diff --git a/static/img/onboarding_step6.png b/static/img/onboarding_step6.png new file mode 100644 index 00000000000..00e60be6418 Binary files /dev/null and b/static/img/onboarding_step6.png differ