Custom Query (1358 matches)


Show under each result:

Results (91 - 93 of 1358)

Ticket Resolution Summary Owner Reporter
#1612 wontfix Change JMicron JM20337/8 device type to sat Eaton Zveare

I have 2 USB adapters, one with a JMicron JM20337/8 chip, and another with JMicron JM20339.

The JM20339 is set up to use "-d usbjmicron" in drivedb.

  • When I run "smartctl --xall pd1", it prints everything.
  • When I run "smartctl --xall -d sat pd1", it prints "Read Device Identity failed: scsi error unsupported scsi opcode".
  • Experience with IDE_COMMAND_SECURITY_UNLOCK is described in this ticket.
  • There is nothing wrong with the JM20339 drivedb entry.

On the other hand, the JM20337/8, appears to behave differently.

  • When I run "smartctl --xall pd1", it prints everything.
  • When I run "smartctl --xall -d sat pd1", it also prints everything.
  • When I run a custom command (IDE_COMMAND_SECURITY_UNLOCK), letting it use the JMicron pass-through, the command appears successful. Sense data empty, no check condition. But, the disk was not unlocked. Attempting this 5 times, even with the wrong password, does not result in exceeded attempts.
  • When I run a custom command (IDE_COMMAND_SECURITY_UNLOCK), this time specifying "-d sat", the command appears successful. Sense data empty, no check condition. 2 differences though:
    1. With the correct password, the disk is actually unlocked.
    2. With the wrong password, there is still no sense data or check condition, but after 5 attempts, security data indicates attempts exceeded.

The "custom command" code is described here.

Conclusion: It is slightly beneficial to change the JM20337/8 drivedb device type to sat in order to improve the chances of certain commands succeeding. Exact line to be changed The JM20337/8 appears very buggy. It's even worse than the JM20339 which at least returned a check condition for failed commands. Changing JM20337/8 to sat makes a bad situation slightly better.

#1613 fixed Add ADATA ED600 USB enclosure to drive database (0x125f:0xa76a) Christian Franke Eaton Zveare

This USB bridge is not recognized as of drive database version 7.3/5364 and smartctl says: Unknown USB bridge [0x125f:0xa76a]

Any HDD can go in it, so I've attached some USB-specific information.

Product page:

#1631 worksforme add to drivedb: WDC WD10PURZ-85U8XY0 Egal

Western Digital Purple SATA Drive is not in Drivedb. This is a 1TB surveillance drive as used in Ubiquiti Unifi products.

I will attach the output of smartctl -q noserial -x /dev/sda to this ticket.

Device Model:     WDC WD10PURZ-85U8XY0
Firmware Version: 01.01A01
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Jul 10 13:16:02 2022 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Enabled
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.