Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

求助！！Unraid无法启动

austinshen
in Chinese / 简体中文

Featured Replies

我昨晚在docker里做check update时，出现问题，一直循环所有的docker，我就按了esc键退出了弹窗，然后在unraid的命令界面reboot下，然后就悲剧了，unraid无法启动了。有什么办法可以解决，docker里的一些内容是否可以保留，比如wordprss的内容。

  • Quote

    可以尝试重建 docker.img 文件，重建之后你的 docker 容器会消失，但是相对应的配置文件（appdata）并不会丢失，具体的解决办法和相关说明参考：

     

     

    Edited by JackieWu

  • Quote
    2024年2月11日上午12点10分，JackieWu说道：

    可以尝试重建docker。但是img文件，重建方法之后你的docker会消失，相对应的配置文件（appdata）也不会丢失，具体的解决方法及相关说明参考：

     

     

    你好，我又遇到了docker服务无法启动的问题，但是docker容器是正常运行的。当出现docker服务无法启动的问题时，我用docker npm反代的一些外链也无法访问（提示代码502） 。

    这是系统日志中的警告和报错的内容，请问您知道我应该怎么解决吗？

    这是系统日志中的报错和警告。

    Quote

    Feb 11 16:50:25 xzy-unraid kernel: critical medium error, dev sda, sector 588608 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2

    Feb 11 16:56:05 xzy-unraid kernel: critical medium error, dev sda, sector 588608 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2

    Feb 11 16:56:44 xzy-unraid kernel: critical medium error, dev sda, sector 585944 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 16:56:44 xzy-unraid kernel: critical medium error, dev sda, sector 586200 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 2

    Feb 11 17:22:02 xzy-unraid kernel: critical medium error, dev sda, sector 588216 op 0x0:(READ) flags 0x80700 phys_seg 9 prio class 2

    Feb 11 17:26:10 xzy-unraid kernel: critical medium error, dev sda, sector 588608 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 18:22:03 xzy-unraid kernel: critical medium error, dev sda, sector 587048 op 0x0:(READ) flags 0x80700 phys_seg 11 prio class 2

    Feb 11 19:22:02 xzy-unraid kernel: critical medium error, dev sda, sector 587040 op 0x0:(READ) flags 0x80700 phys_seg 8 prio class 2

    Feb 11 19:41:35 xzy-unraid kernel: critical medium error, dev sda, sector 588568 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2

    Feb 11 19:48:37 xzy-unraid kernel: critical medium error, dev sda, sector 588600 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2

    Feb 11 19:48:46 xzy-unraid kernel: critical medium error, dev sda, sector 588928 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2

    Feb 11 19:49:08 xzy-unraid kernel: critical medium error, dev sda, sector 589352 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2

    Feb 11 19:53:09 xzy-unraid kernel: critical medium error, dev sda, sector 589352 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2

    Feb 11 20:00:15 xzy-unraid kernel: critical medium error, dev sda, sector 588568 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2

    Feb 11 20:11:04 xzy-unraid kernel: critical medium error, dev sda, sector 588600 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2

    Feb 11 20:11:45 xzy-unraid kernel: critical medium error, dev sda, sector 588224 op 0x0:(READ) flags 0x84700 phys_seg 27 prio class 2

    Feb 11 20:17:18 xzy-unraid kernel: critical medium error, dev sda, sector 588608 op 0x0:(READ) flags 0x80700 phys_seg 15 prio class 2

    Feb 11 20:21:14 xzy-unraid kernel: critical medium error, dev sda, sector 587832 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2

    Feb 11 20:21:14 xzy-unraid kernel: critical medium error, dev sda, sector 587864 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 20:21:14 xzy-unraid kernel: critical medium error, dev sda, sector 587840 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2

    Feb 11 20:21:14 xzy-unraid kernel: I/O error, dev loop1, sector 87856 op 0x0:(READ) flags 0x800 phys_seg 8 prio class 2

    Feb 11 20:21:14 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 20:21:14 xzy-unraid kernel: critical medium error, dev sda, sector 587840 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2

    Feb 11 20:21:14 xzy-unraid kernel: I/O error, dev loop1, sector 87856 op 0x0:(READ) flags 0x800 phys_seg 8 prio class 2

    Feb 11 20:21:14 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 20:22:02 xzy-unraid kernel: critical medium error, dev sda, sector 588216 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 20:22:02 xzy-unraid kernel: critical medium error, dev sda, sector 588232 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 20:22:03 xzy-unraid kernel: critical medium error, dev sda, sector 588992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 20:22:03 xzy-unraid kernel: critical medium error, dev sda, sector 589008 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2

    Feb 11 20:22:03 xzy-unraid kernel: critical medium error, dev sda, sector 589000 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2

    Feb 11 20:22:03 xzy-unraid kernel: I/O error, dev loop1, sector 89016 op 0x0:(READ) flags 0x800 phys_seg 3 prio class 2

    Feb 11 20:22:03 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2b77930: -5

    Feb 11 20:22:03 xzy-unraid kernel: critical medium error, dev sda, sector 588608 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 20:22:03 xzy-unraid kernel: critical medium error, dev sda, sector 585560 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 20:22:04 xzy-unraid kernel: critical medium error, dev sda, sector 587088 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 20:29:17 xzy-unraid kernel: critical medium error, dev sda, sector 587840 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 20:29:17 xzy-unraid kernel: critical medium error, dev sda, sector 587856 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 20:29:17 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 20:29:17 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 20:29:17 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 20:29:17 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 20:55:23 xzy-unraid kernel: critical medium error, dev sda, sector 589376 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 20:57:23 xzy-unraid kernel: critical medium error, dev sda, sector 587864 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 20:57:23 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 20:57:23 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 20:57:23 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 20:57:23 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 20:59:24 xzy-unraid kernel: critical medium error, dev sda, sector 589376 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 20:59:24 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 20:59:24 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ba4784: -5

    Feb 11 21:01:07 xzy-unraid kernel: critical medium error, dev sda, sector 588608 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 21:01:07 xzy-unraid kernel: critical medium error, dev sda, sector 588616 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 21:01:07 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 21:01:07 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2b47930: -5

    Feb 11 21:02:18 xzy-unraid kernel: critical medium error, dev sda, sector 587856 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ae67ac: -5

    Feb 11 21:02:18 xzy-unraid kernel: critical medium error, dev sda, sector 589376 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ba4784: -5

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ba4784: -5

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: xz decompression failed, data probably corrupt

    Feb 11 21:02:18 xzy-unraid kernel: SQUASHFS error: Failed to read block 0x2ba4784: -5

    Feb 12 05:52:57 xzy-unraid kernel: WARNING: CPU: 5 PID: 0 at net/netfilter/nf_conntrack_core.c:1204 __nf_conntrack_confirm+0xb3/0x2c2 [nf_conntrack]

    Feb 12 05:52:57 xzy-unraid kernel: CPU: 5 PID: 0 Comm: swapper/5 Not tainted 6.4.4-Unraid #1 

     

    这是诊断信息

    请问您知道应该怎么解决吗？

    xzy-unraid-diagnostics-20240211-2320.zip

    Edited by a313403367

  • Quote
    1 minute ago, a313403367 said:

    你好，我又遇到了docker服务无法启动的问题，但是docker容器是正常运行的。当出现docker服务无法启动的问题时，我用docker反代的一些外链也无法访问(提示代码502)。

    这是系统日志中的警告和报错的内容，请问您知道我应该怎么解决吗？

    这是系统日志中的报错和警告。

    这是诊断信息

    请问您知道应该怎么解决吗？

    xzy-unraid-diagnostics-20240211-2320.zip 153.82 KB · 0 下载

    重建docker.img以及将docker存储改为文件模式都试过了，还是过几个小时就docker服务无法启动

  • Quote
    7 hours ago, a313403367 said:

    你好，我又遇到了docker服务无法启动的问题，但是docker容器是正常运行的。当出现docker服务无法启动的问题时，我用docker npm反代的一些外链也无法访问（提示代码502） 。

    这是系统日志中的警告和报错的内容，请问您知道我应该怎么解决吗？

    这是系统日志中的报错和警告。 

     

    这是诊断信息

    请问您知道应该怎么解决吗？

    xzy-unraid-diagnostics-20240211-2320.zip

     

    根据你提供的日志信息，显示 sda 这个设备，也就是 U 盘，出现了硬件上的问题导致无法正常读取，建议你检查一下。

    Edited by JackieWu

  • Quote
    1 hour ago, JackieWu said:

     

    根据你提供的日志信息，显示 sda 这个设备，也就是 U 盘，出现了硬件上的问题导致无法正常读取，建议你检查一下。

    好吧，谢谢，我换个u盘试试。

  • Quote

    • Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.