升级 Unraid

升级 Unraid OS 可确保您获得最新功能、安全更新和硬件支持。本页概述了标准升级过程，提供了疑难解答技巧和手动升级选项。

:::note[Prerequisites]

在开始升级之前，请确保完整备份您的USB闪存设备。有关更多详细信息，请参阅备份闪存设备。

:::

Best 升级前的实践

1. 备份您的闪存驱动器和任何重要数据。
2. 阅读您计划安装版本的发布说明。
3. 将所有插件更新至最新版本。
4. 可选步骤，停止阵列后再进行。
5. Update Unraid OS using the Tools → Update OS page.
6. 重启服务器以完成升级。

标准升级流程

Unraid 7.x及更高版本

使用新的 更新操作系统工具 升级 Unraid，界面友好：

1. 在 WebGUI 中，点击右上角的下拉菜单并选择检查更新或者进入工具 → 更新OS。
2. 选择 稳定 通道以获取稳定版本，或选择 下一个 通道以获取测试版和 RC。
3. 点击 查看更改日志开始更新。更改日志将显示，供您在点击 继续 之前查看。
4. 单击 确认并开始更新 以应用最新的稳定版本。
5. 当提示时，重启服务器以完成升级。

备注

您可能需要登录到 Unraid 帐户以访问更新，尤其是对于“下一个”分支版本。

Unraid 6.11到6.12

对于 Unraid 版本 6.11 和 6.12，请遵循传统更新方法：

1. 在 WebGUI 中，转到 工具 → 更新OS。
2. 点击 检查更新。
3. 如果有新版本可用，点击 更新。
4. 当提示时，重启服务器。

ZFS 存储池升级警告

When upgrading to Unraid 7.x, you may see warnings about ZFS pool feature upgrades during boot or in the WebGUI. These warnings are not a sign of a problem; they simply indicate that your ZFS pool is using features from an older version of ZFS.

升级您的池并不紧急，但如果您决定升级，请注意它可能无法与以前的 Unraid 版本一起使用。这意味着进行升级后，您可能无法返回到以前的 Unraid 版本。

如以往一样，升级您的ZFS池之前，请记得备份数据。

---

排查升级问题

如果升级后遇到问题，请查看下面相关部分获取帮助。

升级后 Docker 容器无法正常工作 - 点击以展开/收起

如果您遇到类似 "layers from manifest don't match image configuration" 的错误，您可能需要重新构建您的 Docker 镜像文件。以下是方法：

VMs 显示“无法获取接口 MTU”或网络错误 - 点击以展开/收起

If you encounter errors like "layers from manifest don't match image configuration," you may need to rebuild your Docker image file. Here’s how:

1. Go to Settings → Docker and stop the Docker service.
2. 然后键入 cd efi/boot。
3. 最后，键入 bootx64.efi。
4. 导航到 应用 标签页，选择 先前的应用，勾选要重新安装的应用并点击 安装 xx 应用。

VNC 无法访问或速度慢 - 点击以展开/收起

为了解决此问题，在 WebGUI 中编辑 VM，然后在不进行任何修改的情况下点击 Apply。此操作将更新机器类型为最新支持版本。

1. 前往 VMs 标签页并编辑每个 %%VM%%（确保启用 高级视图）。
2. 将网络桥接设置为 br0 并点击 应用。
3. Navigate to Settings → VM Manager (in Advanced View) and set the default bridge to br0.

VM 无法启动（出现 EFI shell） - 点击以展开/收起

If you have OVMF-based VMs created in older Unraid versions, you might encounter an EFI shell. You can boot the VM by entering the following commands:

1. 在 VMs 标签页编辑 %%VM%%（选择 高级视图）。
2. 将 VNC 视频驱动程序 设置为 QXL（推荐）。如果 QXL 不成功，可以尝试 Cirrus 或 vmvga。
3. 点击 应用 以保存更改。

VMs 显示“无法获取接口 MTU”或网络错误 - 点击以展开/收起

If you have OVMF-based VMs created in older Unraid versions, you might encounter an EFI shell. You can boot the VM by entering the following commands:

1. 键入 fs0:。
2. 然后键入 cd efi/boot。
3. 最后，键入 bootx64.efi。

如果 fs0: 不起作用，您可以尝试 fs1:。如果问题仍然存在，请访问 Unraid 论坛 寻求帮助。

VNC 无法访问或速度慢 - 点击以展开/收起

为了解决此问题，在 WebGUI 中编辑 VM，然后在不进行任何修改的情况下点击 Apply。此操作将更新机器类型为最新支持版本。

VM 无法启动（出现 EFI shell） - 点击以展开/收起

If you have OVMF-based VMs created in older Unraid versions, you might encounter an EFI shell. You can boot the VM by entering the following commands:

---

Manual downgrade

Manual downgrades are infrequently necessary but may be needed if you can't access the WebGUI or need to revert to a prior version. Before proceeding, it's important to back up your USB flash device, details of which you can find in Backing up your flash device.

只有在无法访问 WebGUI 的情况下才使用这些方法：

最简单的方法

1. 从 版本历史 下载所需的 Unraid 版本 ZIP 文件。
2. 在电脑上解压文件。
3. 访问 flash 共享或者将 USB 闪存设备连接到电脑。
4. 如果不存在，请创建一个 previous 目录。
5. 将所有 bz* 和 changes.txt 文件移到 previous 目录中。
6. 将新 bz* 和 changes.txt 文件复制到闪存驱动器根目录。
7. 重新启动您的服务器。

命令行方法

注意

这种方法仅应在您熟悉 Linux 命令行时使用，因为操作错误可能会让系统无法启动。

1. 从 版本历史 复制所需 Unraid 版本 ZIP 文件的 URL。

2. 通过 SSH 或控制台登录。

3. 逐个执行以下命令（将 <URL> 替换为复制的链接）：

   cd /tmp
   rm -f unraid.zip
   rm -rf unraid_install
   wget -O unraid.zip <URL>
   [[ -s unraid.zip ]] && echo "OK to continue" || echo "STOP: the file was not downloaded"
   unzip -d unraid_install unraid.zip
   [[ -s unraid_install/bzroot ]] && echo "OK to continue" || echo "STOP: the file was not extracted properly"
   [[ ! -d /boot/previous ]] && mkdir /boot/previous
   mv /boot/bz* /boot/previous
   mv /boot/changes.txt /boot/previous
   cp unraid_install/bz* /boot
   cp unraid_install/changes.txt /boot
   sync -f /boot
   sleep 5
   reboot

What happens during the downgrade process

When using the Downgrade OS tool (WebGUI), the tool will automatically handle the following:

1. System validation: It checks that the downgrade is safe to perform.
2. File backup: A backup of your current system files will be created.
3. Version verification: The tool ensures that the files for the target version are valid and complete.
4. File replacement: It replaces the current OS files with the files from the previous version.
5. Configuration preservation: Your current settings will be maintained.
6. System preparation: The system will be prepared for the previous version.
7. Reboot scheduling: A reboot will be scheduled to finish the downgrade.

Post-downgrade verification

After the downgrade is complete and your server has rebooted:

1. Check the version: Verify that you're running the version of Unraid you expect.
2. Test core functionality: Ensure that the array, Docker, and VM services are working properly.
3. Verify plugins: Check that your installed plugins are compatible and functioning as expected.
4. Test Docker containers: Start your Docker containers and confirm they are working correctly.
5. Check VMs: If you have any virtual machines (VMs), make sure they start and operate properly. See VM setup for configuration guidance.
6. Monitor system logs: Keep an eye on the system logs for any error messages. Use diagnostics tools to capture detailed system information.

Troubleshooting downgrade issues

Downgrade option not available - Click to expand/collapse

If you don’t see an option to downgrade:

• Check system history: Make sure you've previously upgraded from a compatible version.
• Verify file integrity: Previous version files might be corrupted or missing.
• Check compatibility: The earlier version may not be compatible with your current hardware.
• Manual method: If needed, follow the manual downgrade methods outlined on this page.

Downgrade fails during process - Click to expand/collapse

If the downgrade process doesn't go as planned:

1. Don’t panic: Your system should still work with the current version.
2. Check logs: Take a look at the system logs to find specific error messages. Use diagnostics tools for comprehensive log analysis.
3. Verify files: Ensure that all required files for the target version are available.
4. Try the manual method: If the tool doesn't work, consider using the manual downgrade methods.
5. Contact support: If problems continue, reach out to Unraid support with your diagnostics.

System won't boot after downgrade - Click to expand/collapse

If your system doesn’t boot after downgrading:

1. Boot from USB: Use another computer to access your USB flash device. See boot troubleshooting for detailed recovery steps.
2. Restore from backup: Copy your backup files back to the USB device.
3. Check file integrity: Make sure all system files are present and not damaged.
4. Try Safe Mode: Boot into Safe Mode for further troubleshooting.
5. Manual recovery: If necessary, utilize the manual recovery methods.

Plugins or Docker containers not working - Click to expand/collapse

After downgrading, some plugins or containers may not function properly:

• Update plugins: Look for plugin updates that work with the downgraded version. Check Community Applications for compatible versions.
• Rebuild Docker: Delete and recreate your Docker image file. See Docker troubleshooting for detailed steps.
  • Check dependencies: Ensure that all necessary dependencies are available.
  • Plugin compatibility: Some plugins might not support earlier Unraid versions.
  • UI/WebGUI feature-dependent plugins: Plugins relying on newer WebGUI features may not operate correctly on older versions.
  • Theme plugins: Visual customization plugins may require updates or removal if they are incompatible.