Opened 3 years ago
Closed 3 years ago
#1543 closed enhancement (fixed)
Add to driveDB WDC WD102KFBX
Reported by: | Mitium | Owned by: | Christian Franke |
---|---|---|---|
Priority: | minor | Milestone: | Release 7.3 |
Component: | drivedb | Version: | 7.2 |
Keywords: | hdd | Cc: |
Description
10Tb Red Pro NAS drive
Attachments (2)
Change History (13)
by , 3 years ago
Attachment: | WDC-WD102KFBX.txt added |
---|
comment:1 by , 3 years ago
Component: | all → drivedb |
---|
comment:2 by , 3 years ago
Keywords: | hdd added; WD102KFBX add removed |
---|---|
Milestone: | → undecided |
comment:3 by , 3 years ago
Test was performed using a StarTech SATDOCK22RE which uses a JMicron JMB352U chipset.
The command used to perform the test is:
smartctl -q noserial -x -d sat /dev/sdb > WDC-WD102KFBX.txt
Is there some other flag that needs to added?
comment:4 by , 3 years ago
Some additional details from system logs:
[ 584.202040] usb 2-3: new SuperSpeed USB device number 4 using xhci_hcd [ 584.222777] usb 2-3: New USB device found, idVendor=152d, idProduct=9561, bcdDevice=62.07 [ 584.222788] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=XX [ 584.222793] usb 2-3: Product: JMS56x Series [ 584.222796] usb 2-3: Manufacturer: JMicron [ 584.222800] usb 2-3: SerialNumber: 00000000000000000000 [ 584.229796] scsi host5: uas [ 584.230618] scsi 5:0:0:0: Direct-Access WDC WD10 2KFBX-68M95N0 6207 PQ: 0 ANSI: 6 [ 584.231859] sd 5:0:0:0: Attached scsi generic sg1 type 0 [ 584.232771] sd 5:0:0:0: [sdb] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB) [ 584.232969] sd 5:0:0:0: [sdb] Write Protect is off [ 584.232974] sd 5:0:0:0: [sdb] Mode Sense: 67 00 10 08 [ 584.233342] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 584.233743] sd 5:0:0:0: [sdb] Optimal transfer size 33553920 bytes [ 584.349602] sd 5:0:0:0: [sdb] Attached SCSI disk [ 2397.999548] sdb: sdb1 [ 2399.024278] sdb: sdb1
comment:5 by , 3 years ago
-d sat
reportedly worked with this USB bridge. Older JMicron bridges require -d usbjmicron
. May also depend on firmware version.
comment:6 by , 3 years ago
I don't have any way to check the firmware version on the USB dock at this time. I will put together another computer to run Ubuntu 21.10 and install it internally to avoid the chipset issue. This will take about half a day.
comment:7 by , 3 years ago
Apologies for the delay, I had to wait for a replacement part to arrive. Directly connected to the motherboard yielded more results.
by , 3 years ago
Attachment: | WDC-WD102KFBX-2.txt added |
---|
comment:8 by , 3 years ago
Milestone: | undecided → Release 7.3 |
---|
Thanks, looks much better. Could be added to existing entry Western Digital Red Pro
.
Interestingly the WD102KFBX does not provide attribute 22 (Helium_Level
) but WD101KFBX (#1030) does. The firmware versions (83.00A83
vs. 83.H0A03
) may also suggest that only the WD101KFBX is a helium drive.
comment:9 by , 3 years ago
I doubt that it is a helium filled drive, since I see a vent hole in the upper cover.
I do recall reading elsewhere on the internet that it is one of the primary differences compared to the WD101KFBX.
comment:10 by , 3 years ago
Owner: | set to |
---|---|
Status: | new → accepted |
The output is not useful. The SMART data block is returned with all zeroes and the Log Directory could not be read:
This is a limitation (or bug) in the ATA/SCSI pass-through layer between smartctl and drive. Which controller, USB bridge, ... was used here?
Attribute set is likely similar to WD101KFBX (#1030), but this cannot be verified with the output attached above.