Custom Query (1222 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (13 - 15 of 1222)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#1612 wontfix Change JMicron JM20337/8 device type to sat Eaton Zveare
Description

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.

#1610 fixed Add database entry for Crucial MX500 (CT4000MX500SSD1, FW M3CR044) Gabriele Pohl Martin H.
Description

Despite the SSD comes with a newer firmware revision, it still seems to suffer from #1227 (fluctuating Current_Pending_Sector)

#1608 duplicate western_digital-WD161KRYZ-01AGBB0 drive to add to database Gabriele Pohl Cody Vaudrin
Description

Please add Western Digital WD161KRYZ-01AGBB0 HDD to the database.

Product description (PDF file): https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/public/western-digital/product/internal-drives/wd-gold/product-brief-wd-gold-hdd.pdf

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracQuery for help on using queries.