July 14, 20241 yr I have two usb ports on my mini pc, one of which has a usb flash drive inserted for running the system. When I insert a portable usb drive into the other port, there is a banner that says: "Your flash drive is corrupted or offline. Post your diagnostics in the forum for help." At the same time the top right corner reminds me "There is a physical problem accessing your USB Flash boot device". At the same time, my interface goes back to English from Chinese, and neither the app nor the docker can be opened anymore. Does anyone know what's going on here? Thank you in advance. nas-ssd-diagnostics-20240714-1230.zip
July 14, 20241 yr Community Expert See if the other flash drive is also labeled UNRAID, if yes change it.
July 14, 20241 yr Author Just now, JorgeB said: See if the other flash drive is also labeled UNRAID, if yes change it. 查看另一个闪存驱动器是否也标记为 UNRAID，如果是，请更改它。 Thank you for your reply! I just checked and it is a 2TB WD portable drive named "Elements".
July 14, 20241 yr Community Expert Your diagnostics show that as soon as the USB drive was plugged in you started getting errors of the form: Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30720) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30721) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30722) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30723) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30724) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30725) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30726) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30727) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30728) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30729) failed which is the flash drive. Why is not clear.
July 14, 20241 yr Author Solution 7 minutes ago, itimpi said: Your diagnostics show that as soon as the USB drive was plugged in you started getting errors of the form: 您的诊断显示，一旦插入 USB 驱动器，您就开始收到以下形式的错误： Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30720) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30721) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30722) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30723) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30724) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30725) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30726) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30727) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30728) failed Jul 14 12:30:42 NAS-SSD kernel: FAT-fs (sda1): Directory bread(block 30729) failed which is the flash drive. Why is not clear. 这是闪存驱动器。 为什么还不清楚。 Thank you for your reply! I just tried booting the system using another flash drive. Then plugged in my Western Digital portable usb drive, but the results were still the same. I think it might be a motherboard or driver issue? When this problem occurs, the only way I can get back to normal is to unplug the portable drive and reboot. By the way, the WebUI interface seemed to be running when the system flash crashed. ------ I plugged in both the system flash and the WD portable drive before booting up, then booted up and the system booted normally and recognised the external drive! But I'm still confused as to why plugging in an external storage device after booting causes the system flash to crash. Thank you
July 14, 20241 yr Community Expert 18 minutes ago, Yuwen said: But I'm still confused as to why plugging in an external storage device after booting causes the system flash to crash. Unraid expects the flash drive to be permanently connected, so if plugging in the external drive causes it to disconnect (and then possibly reconnect) it will cause a problem. That could be why having them both plugged in at the start works OK.
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.