NAS Model: TerraMaster U4-500
TOS Version: 7.0.1298 (x86)
Linux Kernel: 6.12.63+
Report Date: October 15, 2026
Regression in TOS 7.0.1298: Storage Manager Becomes Unresponsive When a USB Drive Is Connected
After updating to TOS 7.0.1298, a previously resolved problem with an external Toshiba 1 TB USB drive and Storage Manager has returned.
Important: The USB drive and Storage Manager worked normally with the previously installed TOS version. The issue reappeared specifically after updating to TOS 7.0.1298.
1. Problem Description
The following issues occur after the update:
- When the external USB drive is connected, Storage Manager becomes unresponsive, freezes, and stops displaying up-to-date storage information.
- The problem occurs both when connecting the USB drive to an already running NAS and when booting TOS with the drive connected.
- The issue is not limited to the USB drive section. Other Storage Manager sections, including IronWolf Health Management, also become unresponsive.
- The encrypted USB drive is detected as crypto_LUKS, but unlocking it through the TOS GUI fails with both the password and the encryption key file.
- Restarting StorageManager.service temporarily restores GUI functionality, but the problem returns when the drive is accessed again.
- During these failures, StorageManager.service remains in the active (running) state.
2. Affected USB Device
Code: Select all
Manufacturer: Toshiba
Product: External USB 3.0
Capacity: 1 TB
USB Vendor ID: 0080
USB Product ID: a001
USB Device Path: 3-5.2
Linux Device: /dev/sdi
Partition: /dev/sdi1
Original Filesystem: crypto_LUKS
Original Driver: uas
USB Link Speed: 480 Mbps
The NAS also has two other USB drives connected through controllers with VID:PID
0bda:9201. These drives are members of an active RAID array, use the UAS driver, and continue operating normally.
3. Storage Manager Diagnostics
When Storage Manager accesses the affected USB drive, it launches a large number of concurrent
smartctl processes against the same device, /dev/sdi.
Dozens of processes were observed simultaneously:
Code: Select all
/usr/sbin/smartctl -d sat -a /dev/sdi
/usr/sbin/smartctl -d sat -j -a /dev/sdi
/usr/sbin/smartctl -a /dev/sdi
/usr/sbin/smartctl -j -a /dev/sdi
smartctl -i -j /dev/sdi
Most of these processes were in the
D state (uninterruptible sleep, waiting for kernel-level I/O operations).
Storage Manager repeatedly logged the following error:
Code: Select all
[ReportWithContext]::Failed to retrieve disk smart info Device:=/dev/sdi err=Timeout while retrieving disk(/dev/sdi) smart info
Another recurring message:
Code: Select all
Failed to retrieve disk smart info
Device:=/dev/sdi
err=Disk /dev/sdi slow response, skip the retrieval
The number of blocked smartctl processes continued to increase, while the Storage Manager GUI stopped responding normally.
4. Linux Kernel Errors
At the same time, the kernel log reported repeated USB protocol and UAS errors:
Repeated command aborts:
Code: Select all
sd 69:0:0:0: [sdi] uas_eh_abort_handler
CDB: ATA command pass through(16)
The UAS driver subsequently attempted device resets:
Code: Select all
scsi host69: uas_eh_device_reset_handler start
usb 3-5.2: reset high-speed USB device using xhci_hcd
scsi host69: uas_eh_device_reset_handler success
These resets did not resolve the problem. USB errors continued, smartctl processes remained blocked, and Storage Manager remained unreliable.
5. Diagnostic Test: Disabling UAS for the Affected Device
To isolate the problem, UAS was temporarily disabled only for the affected Toshiba USB device with VID:PID
0080:a001.
The following command was executed on the running system:
Code: Select all
printf '0080:a001:u\n' > /sys/module/usb_storage/parameters/quirks
After physically disconnecting and reconnecting the Toshiba drive, the Linux kernel confirmed that the device was switched from UAS to the standard usb-storage driver:
Code: Select all
usb 3-5.2: UAS is ignored for this device, using usb-storage instead
usb-storage 3-5.2:1.0: USB Mass Storage device detected
usb-storage 3-5.2:1.0: Quirks match for vid 0080 pid a001: 800000
scsi host69: usb-storage 3-5.2:1.0
The lsusb -t output confirmed the driver change.
Before:
Code: Select all
Class=Mass Storage, Driver=uas, 480M
Code: Select all
Class=Mass Storage, Driver=usb-storage, 480M
All other USB storage devices continued operating with their original UAS drivers. No changes were made to the RAID configuration.
6. Results After Disabling UAS
Switching the affected Toshiba device from uas to usb-storage eliminated the observed Storage Manager freezes.
Results:
- Storage Manager no longer freezes.
- The USB storage section opens and operates normally.
- IronWolf Health Management also works without freezing.
- The mass creation of blocked smartctl processes has stopped.
- No new USB protocol errors (-71) or UAS resets were observed in the checked kernel logs after reconnecting the device.
- StorageManager.service remained operational without additional restarts.
- The other USB drives continued operating normally with UAS enabled.
Storage Manager status after testing:
Code: Select all
Active: active (running)
Main PID: 80534 (storagemanager)
Tasks: 28
Memory: 41.9M
No blocked smartctl processes were present in the service process tree.
After restoring GUI functionality, I removed encryption from the Toshiba USB drive using the standard TOS GUI. The drive now operates normally.
LUKS unlocking was not retested after switching the USB driver, so the original encryption-unlocking failure has not been independently confirmed as resolved.
7. Additional Storage Manager Warnings
After switching the driver, the Storage Manager log contained several non-fatal warnings:
Code: Select all
WARNING: Device /dev/sdi1 not initialized in udev database even after waiting 10000000 microseconds.
Code: Select all
GetOverview1GetDiskData failed: not support device: not support current device
These warnings did not cause the GUI to freeze or prevent the drive from operating normally.
8. Summary
TOS 7.0.1298 exhibits a regression affecting Storage Manager when a Toshiba USB device with VID:PID 0080:a001 is connected using the UAS driver.
The observed failure sequence is:
- Storage Manager attempts to retrieve SMART information from the USB drive.
- ATA command timeouts and USB/UAS errors occur.
- Storage Manager launches numerous concurrent smartctl processes that become blocked in the D state.
- The Storage Manager GUI becomes unresponsive, including sections unrelated to the affected USB drive.
- Restarting StorageManager.service provides only temporary recovery.
- Switching the affected USB device from uas to usb-storage eliminates the observed freezes and USB/UAS errors.
Confirmed temporary workaround:
The workaround was successfully tested on the running system without affecting other USB drives or RAID arrays.
The runtime change is temporary and is not automatically preserved across system reboots.
The problem appeared after updating to TOS 7.0.1298 and was not present in the previously installed TOS version.
Status: The Storage Manager freezes have been eliminated using a temporary driver workaround. The regression in TOS 7.0.1298 remains unresolved.