Custom Query (1376 matches)
Results (229 - 231 of 1376)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #549 | fixed | drivedb: Samsung D3 Station 4TB | ||
| Description |
Please add the Samsung D3 Stations 4TB external drive to drivedb.h. The entry for the 3TB version can be extended: https://www.smartmontools.org/browser/trunk/smartmontools/drivedb.h#L3228 /dev/sdb: Unknown USB bridge [0x04e8:0x6125 (0x202)] # smartctl -d sat -i /dev/sdb smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build) Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1F2168 Serial Number: XXXXXXX LU WWN Device Id: 5 000c50 07fbd5490 Firmware Version: CC54 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5900 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Sun May 10 22:31:41 2015 MDT SMART support is: Available - device has SMART capability. SMART support is: Enabled |
|||
| #550 | fixed | USB bridge 0x152d:0x2590 (0x8105) | ||
| Description |
Hi! I would like to let you know about unsupported USB bridge 0x152d:0x2590 (0x8105)
I bought it at https://www.amazon.de/gp/product/B00PTM661Q, ends up at Adding support would be cool if possible. If not, an entry to the table of unsupported bridges would be cool, too. I'll try to return the device so if you have questions about it, please be quick. Thanks! Best, Sebastian |
|||
| #551 | fixed | Seagate Vendor Specific Smart Attribute 188 | ||
| Description |
The raw data for attribute 188 is divided into three words from the seven raw bytes available. Each word defines a timeout and timing associated with the command timeout. [0:1] Command Timeout Occurred [2:3] Command Timeout Occurred, command was in queue >5 seconds [4:5] Command Timeout Occurred, command was in queue >7.5 seconds so the output 03 00 03 00 03 suggests that there are three timeouts, three 5 second timeouts, and three 7 second timeouts. Note that a 7 second timeout also counts as a five second. But a 5 second timeout doesn't count as a 7 second timeout. So this number really means that there were 3 7 second timeouts. So the issue is that smartctl is reading that entire block as a single very large number. So I'm going to see if their is a more up to date version of smartctl, to see if this fixes the issue -- if not I'll open a bug report to smartctl so they know to fix it. |
|||
