Custom Query (1406 matches)
Results (52 - 54 of 1406)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#662 | fixed | A-DATA USB bridge 125f:a15a - A-DATA HD710 | ||
Description |
A-DATA HD710 (AHD710-1TU3) does not work without -d sat. Please recognize the USB bridge automatically. # lsusb -d 125f:a15a Bus 002 Device 004: ID 125f:a15a A-DATA Technology Co., Ltd. # ./smartctl -i /dev/sdb smartctl 6.5 2016-02-29 r4227 [x86_64-linux-3.16.0-4-amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org /dev/sdb: Unknown USB bridge [0x125f:0xa15a (0x100)] Please specify device type with the -d option. Use smartctl -h to get a usage summary # ./smartctl -d sat -i /dev/sdb smartctl 6.5 2016-02-29 r4227 [x86_64-linux-3.16.0-4-amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba 2.5" HDD MQ01ABD... Device Model: TOSHIBA MQ01ABD100 Serial Number: XXXXXXXXX LU WWN Device Id: XXXXXXXXXXXXXXXXX Firmware Version: AX1P1A User Capacity: 1 000 204 886 016 bytes [1,00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 2.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s) Local Time is: Tue Mar 1 20:10:25 2016 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled |
|||
#663 | fixed | Some of the Kingston SSD drives based on the phison chipset are wrongly added as Sandforce chipset | ||
Description |
It was found that at least some of the drives are built on the phison chipset, but using sandforce attributes. These are similar but not the same, see http://media.kingston.com/support/downloads/MKP_521_Phison_SMART_attribute.pdf (phison) and http://media.kingston.com/support/downloads/MKP_306_SMART_attribute.pdf (sandforce). We need to split them to the separate drivedb records instead. Need to check which controller belongs to each chipset. This is the list: bash-3.2$ grep \"KINGS drivedb.h [?] "KINGSTON SE50S3(100|240|480)G|" // tested with SE50S3100G/KE1ABBF0 [SF] "KINGSTON SH10[03]S3(90|120|240|480)G|" // HyperX (3K), SF-2281, tested with [SF] "KINGSTON SKC(300S37A|380S3)(60|120|180|240|480)G|" // KC300, SF-2281, tested with [SF] "KINGSTON SVP200S3(7A)?(60|90|120|240|480)G|" // V+ 200, SF-2281, tested with [SF] "KINGSTON SMS200S3(30|60|120)G|" // mSATA, SF-2241, tested with SMS200S3120G/KC3ABBF0 [SF] "KINGSTON SMS450S3(32|64|128)G|" // mSATA, SF-2281, tested with SMS450S3128G/503ABBF0 [SF] "KINGSTON (SV300|SKC100|SE100)S3.*G|" // other SF-2281 [PH] "KINGSTON SUV300S37A(120|240|480)G" // UV300 SSD, tested with KINGSTON SUV300S37A120G/SAFM11.K [?] "KINGSTON SSDNow 40GB", [??] "KINGSTON SSDNow 40GB", [?] "KINGSTON SNV425S2(64|128)GB|" // SSDNow V Series (2. Generation, JMF618), [?] "KINGSTON SSDNOW 30GB|" // tested with KINGSTON SSDNOW 30GB/AJXA0202 [?] "KINGSTON SS100S2(8|16)G|" // SSDNow S100 Series, tested with KINGSTON SS100S28G/D100309a [?] "KINGSTON SNVP325S2(64|128|256|512)GB|" // SSDNow V+ Series, tested with KINGSTON SNVP325S2128GB/AGYA0201 "KINGSTON SVP?100S2B?(64|96|128|256|512)G|" // SSDNow V100/V+100 Series, [?] "KINGSTON SV200S3(64|128|256)G|" // SSDNow V200 Series, tested with KINGSTON SV200S3128G/E120506a |
|||
#664 | fixed | Improved output on LB Provisioning |
Note:
See TracQuery
for help on using queries.