Hi everyone,

I have Unraid set up on a Lenovo m920q tiny PC and use one SSD as disk and one as parity due to the space constraints that come with that. Unfortunately, every two to three months, the parity disk drops out and is disabled.

I am not good at understanding the reports but googled and ChatGPTed my way through them and believed the disk diagnostics to be okay. From that and similar forum posts, I gathered that it might be an issue with the SATA cable or controller. I therefore ran the disk in an USB enclosure to at least rule out an issue with the flimsy ribbon cable. Unfortunately, the error occurred once more today. I have built up a very similar system using the same tiny PC and the same drives (with lower capacity though) for an acquaintance and recently found out that the parity disk in that system ran into the same error. Although I haven't been to their place yet to take a look. Since the two systems are so similar, this could mean that either the PC or the disks are not really up to the job.

Now I am unsure if I should replace that (admittedly not very high end) parity SSD, the whole PC or if I could do anything else.

If someone could offer a second opinion on the attached logs, I would greatly appreciate it! Thank you!

unraid-diagnostics-20250807-0844.zip

Edited August 7, 2025Aug 7 by Luckytaube

USB is not recommended for array or pol devices, but I guess you don't have many other options. You can try disabling UASP to see if it helps; post the output from lsusb -vt

I only ran the drive in the USB enclosure since the last time this happened. Before that, I used the internal SATA-port. I switched to USB to check if the SATA-cable or port might be faulty. The second system that encountered the issue also uses the internal SATA-port. I should have stated this more clearly.

Regardless, this is the output of lsusb -vt:

/: Bus 001.Port 001: Dev 001, Class root_hub, Driver=xhci_hcd/16p, 480M

ID 1d6b:0002 Linux Foundation 2.0 root hub

|__ Port 006: Dev 002, If 0, Class Mass Storage, Driver-usb-storage, 480M

ID 05dc:a81d Lexar Media, Inc. LJDTT16G [JumpDrive 16GB]

|__ Port 014: Dev 003, If 0, Class Wireless, Driver-btusb, 12M

ID 8087:0a2b Intel Corp. Bluetooth wireless interface

|__ Port 014: Dev 003, If 1, Class Wireless, Driver=btusb, 12M

ID 8087:0a2b Intel Corp. Bluetooth wireless interface

/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver xhci_hcd/10p, 10000M

ID 1d6b:0003 Linux Foundation 3.0 root hub

|__ Port 004: Dev 002, If 0, Class Mass Storage, Driver uas, 10000M

ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153

SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge

Edited August 7, 2025Aug 7 by Luckytaube

If it happens with SATA and USB it may be a different issue, but it may still be worth trying without UASP, since the log contains erros that are apparent related to that.

Click on the flash drive, scroll down to the Syslinux configuration section, make sure Menu View is enabled, top-right, and add after /bzroot to the default boot option, the one in green:

usb_storage.quirks=174c:55aa:u

Then reboot and retest, post new diags if it happens again.

Thank you for the suggestion! It's unfortunate I didn't keep the logs from the times it happened when connected via SATA. But instead of deactivating UASP, I could also give SATA another try and post the error log, when it happens again, right? I assume it will once again take a few months till I see the error again. That makes it a bit frustrating to test.

Can you comment on the likelihood that the SSD is just not up for the job? It's a Verbatim Vi550 S3. I know that it's not made for NAS-duty, but was willing to risk it dying at some point. These frequent disconnects however are much more annoying than what I was expecting. I am obviously not keen on buying another drive, but if it was the most likely culprit, I would replace it.

1 hour ago, Luckytaube said:

But instead of deactivating UASP, I could also give SATA another try and post the error log, when it happens again, right?

You can.

1 hour ago, Luckytaube said:

Can you comment on the likelihood that the SSD is just not up for the job? It's a Verbatim Vi550 S3.

Unless it's failing, it should be fine. SATA controllers are usually better than USB at showing if it's an actual device problem or a power/connection issue.

Hello everyone,

it just happened again: After the last time, I put the drive back in the SATA slot and rebuilt parity. Just this evening, the drive dropped out again. The short SMART self-test shows no error. The extended one is still running. The diagnostics are attached.

As I mentioned, I have a second system that used the same drive but with 1 TB and had a similar error. I recently got hold of that one again and the drive was completely dead.

So right now, I am just assuming that I shouldn't trust this type of drive with my data. Or am I missing something?

unraid-diagnostics-20251005-2136.zip

Still looks more like a power/connection issue.