ajayjohn

Thank you, @JorgeB! It's been a week now and I have not had any issues with the hard disk so far.

No problem! Just started the rebuild process. Will report back if the issue gets solved. Thanks!

@JorgeB Can you please check my latest diagnostics when you get a chance, and suggest how I can get my HDD enabled again?

Got it. I made the updates, rebooted and the earlier error no longer appears! Here are my latest diagnostics, if you can guide me further on getting my HDD enabled again. tower-diagnostics-20250301-0328.zip

Sure, here are the updated diagnostics. tower-diagnostics-20250301-0244.zip

Thanks for clarifying that! I made the changes and rebooted the machine. I can confirm that the USB storage driver is now in use. Oh, there's it? I still have the same error as before and the disk is still disabled. Is there anything else that I can try to fix this? # lsusb -vt: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/3p, 20000M/x2 ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=uas, 10000M ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter |__ Port 003: Dev 003, If 0, Class=Hub, Driver=hub/4p, 10000M ID 2109:8822 VIA Labs, Inc. |__ Port 001: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor |__ Port 002: Dev 005, If 0, Class=Mass Storage, Driver=usb-storage, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor |__ Port 003: Dev 006, If 0, Class=Mass Storage, Driver=usb-storage, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor |__ Port 004: Dev 007, If 0, Class=Mass Storage, Driver=usb-storage, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 003: Dev 002, If 0, Class=Hub, Driver=hub/2p, 480M ID 2109:2822 VIA Labs, Inc. |__ Port 001: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 480M ID 058f:6387 Alcor Micro Corp. Flash Drive |__ Port 006: Dev 003, If 0, Class=Hub, Driver=hub/5p, 480M ID 2109:2822 VIA Labs, Inc. |__ Port 005: Dev 005, If 0, Class=[unknown], Driver=[none], 480M ID 2109:8818 VIA Labs, Inc. /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 003: Dev 002, If 0, Class=Hub, Driver=hub/2p, 10000M ID 2109:0822 VIA Labs, Inc. Error: Feb 28 15:08:07 Tower kernel: critical target error, dev sdf, sector 1031549968 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2

Thanks for the deduction. I added the quirk and rebooted, but unfortunately, I still continue to get the error below: Feb 28 12:40:44 Tower kernel: I/O error, dev sda, sector 208013128 op 0x0:(READ) flags 0x80700 phys_seg 60 prio class 2 For reference: Do you need a fresh dump of diagnostics since I did a reboot?

Understood and you're right, I am using a 4-bay HDD enclosure (https://www.amazon.com/Mediasonic-SATA-Hard-Drive-Enclosure/dp/B078YQHWYW) connected via a USB-C cable since Unraid is running on a mini PC, which cannot support a 3.5 inch HDD. Here is the output from lsusb -vt. Is there a way to revert the USB driver from within Unraid or is this something I will handle via the command line? /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/3p, 20000M/x2 ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=uas, 10000M ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter |__ Port 003: Dev 003, If 0, Class=Hub, Driver=hub/4p, 10000M ID 2109:8822 VIA Labs, Inc. |__ Port 001: Dev 004, If 0, Class=Mass Storage, Driver=uas, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor |__ Port 002: Dev 005, If 0, Class=Mass Storage, Driver=uas, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor |__ Port 003: Dev 006, If 0, Class=Mass Storage, Driver=usb-storage, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor |__ Port 004: Dev 007, If 0, Class=Mass Storage, Driver=uas, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 003: Dev 002, If 0, Class=Hub, Driver=hub/2p, 480M ID 2109:2822 VIA Labs, Inc. |__ Port 001: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 480M ID 058f:6387 Alcor Micro Corp. Flash Drive |__ Port 006: Dev 003, If 0, Class=Hub, Driver=hub/5p, 480M ID 2109:2822 VIA Labs, Inc. |__ Port 005: Dev 005, If 0, Class=[unknown], Driver=[none], 480M ID 2109:8818 VIA Labs, Inc. /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 003: Dev 002, If 0, Class=Hub, Driver=hub/2p, 10000M ID 2109:0822 VIA Labs, Inc.

@JorgeB My bad. I updated the opening post with the diagnostic instead.

One of my disks keeps going offline with the following error Feb 27 20:25:59 Tower kernel: critical target error, dev sdc, sector 2049660712 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Feb 27 20:25:59 Tower kernel: md: disk1 write error, sector=2049660648 I already did a full rewrite of the disk and also checked the cabling but the error comes back in a few days. This disk is in an external HDD enclosure with other disks, that are not affected in any way. Is this the end of the line for this specific HDD? Any guidance would be appreciated. (Logs attached) tower-diagnostics-20250228-0821.zip