Opened 2 years ago
Closed 2 years ago
#1581 closed defect (invalid)
smartctl never completes when all information is requested from a 4K Native WD drive over USB
| Reported by: | Eaton Zveare | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | smartctl | Version: | 7.3 |
| Keywords: | ata usb | Cc: |
Description
When the drive is configured 512e, there is no problem.
When the drive is configured 4K Native, running "smartctl --xall pd1" results in an infinite loading condition and the only way to stop it is to unplug the drive. This only happens over USB and works fine over a direct SATA connection. It's worth noting I have tested a lot of drives over USB and this is the only time I have seen this issue.
The drive was originally 512e, but was changed to 4K Native using this tool: https://github.com/pig1800/WD4kConverter
Disk model: WDC WD4005FZBX-00K5WB0 (WD Black 4 TB 3.5")
USB docking station: Sabrent DS-UTC1
I believe the chipset on the docking station is the ASMedia ASM235CM.
When the drive is unplugged, smartctl immediately returns the attached information (there are many errors).
The LED activity light on the docking station blinks the whole time and never stops until it's powered off.
My theory is that the the USB chip can't handle one of the commands you are sending. It's a bit odd it took a sector size change to expose the issue, though.
Attachments (4)
Change History (14)
by , 2 years ago
| Attachment: | smartctl Output.txt added |
|---|
comment:1 by , 2 years ago
comment:3 by , 2 years ago
And to answer your question, I do not know if they advertise support for 4K Native. Everything works fine though (reads, writes, etc) - everything except for obtaining all information using smartctl.
comment:4 by , 2 years ago
Log of second command
PD1: Unable to detect device type
Please retry with pd1 as device name.
comment:6 by , 2 years ago
The results suggest that the SMART WRITE LOG command does not work with this USB-bridge, at least with 4Kn drives.
The command:
smartctl -x ...
is the same as:
smartctl -i -g all -g wcreorder -H -c -A -f brief -l xerror,error -l xselftest,selftest -l selective -l directory -l scttemp -l scterc -l devstat -l defects -l sataphy ...
If this reduced option set works, the guess might be correct:
smartctl -i -g all -H -c -A -f brief -l xerror,error -l xselftest,selftest -l selective -l directory -l devstat -l defects -l sataphy ...
comment:7 by , 2 years ago
Both of those commands hang, unfortunately. Let me know if you want the output, or have another reduced option to try.
comment:8 by , 2 years ago
Further diagnostics would require trial and error with commands subsets. Possibly not worth the effort because this is likely a bug in the firmware of the USB-bridge which cannot be fixed by smartctl.
Does smartctl -x work if a 512n/512e drive is connected to this docking station?
comment:10 by , 2 years ago
| Keywords: | ata usb added |
|---|---|
| Milestone: | undecided |
| Resolution: | → invalid |
| Status: | new → closed |
This is a likely a bug in the firmware of the USB bridge in conjunction with 4Kn drives. This cannot be fixed by smartctl.
Is there any evidence that Sabrent or ASMedia advertise full 4Kn support for this USB->SATA bridge?
The modes 512n, 512e (LPS) or 4Kn (LLS) make no difference for smartctl operation. The ATA commands IDENTIFY, SMART READ DATA, SMART READ LOG and READ LOG EXT always use the traditional 512 byte sector size. The LLS (Long Logical Sector) feature set only affects regular R/W commands. See for example Table 5 of T13/2015-D Revision 7 (ATA ACS-2).
Please provide the output of the following commands as attachments and indicate which of the commands hangs until the device is disconnected:
PS: Please do not set the Milestone in future submissions.