Custom Query (1438 matches)
Results (337 - 339 of 1438)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #766 | fixed | JSON output mode for smartctl reports | ||
| Description |
More and more command line programs now have an option to output information as a single big JSON string. It makes it super easy for anybody to integrate another program or even simple scripts. Pretty much any programming/scripting language can read JSON very easily with only a few lines of code. A good example of one program that does this (of many now) is "exiftool". Adding "-json" to the command arguments will have it output all information in a big JSON string (with pretty print so its not just one long line). For example, the command... exiftool -json /usr/sbin/smartctl Will output: [{
"SourceFile": "/usr/sbin/smartctl",
"ExifToolVersion": 9.74,
"FileName": "smartctl",
"Directory": "/usr/sbin",
"FileSize": "620 kB",
"FileModifyDate": "2014:12:21 05:29:41+10:00",
"FileAccessDate": "2016:11:11 08:02:52+10:00",
"FileInodeChangeDate": "2015:04:15 00:36:10+10:00",
"FilePermissions": "rwxr-xr-x",
"FileType": "ELF executable",
"MIMEType": "application/octet-stream",
"CPUArchitecture": "64 bit",
"CPUByteOrder": "Little endian",
"ObjectFileType": "Shared object file",
"CPUType": "AMD x86-64"
}]
This is a much simpler method of effectively giving the same functionality requested in ticket "#501 make smartctl into a library". And would be usable to a much wider audience, much more easily. I recommend this for any command line program that outputs any kind of information these days. In fact, considering that JSON is quite human readable anyway, I'd even suggest making it the first output format for any new program before bothering to create your own custom ASCII layout. In a lot of cases, the JSON would be all you really need. And anyone else can easily make their own scripts to generate a nicer looking ASCII output if they like. Much easier than doing it in reverse, i.e. writing custom code to parsing an ASCII table. |
|||
| #767 | fixed | Please add WD Blue PC SSD to the DB | ||
| Description |
The related smart data was .rsrc/BIN/41 .rsrc/BIN/42 xml files contains the SSD related attribute names and IDs. I added the following entry to my drivedb.h . { "WD Blue PC SSD",
"WDC WDS...[TG]1B0[AB].*",
"", "", // all extra attribute is raw48 until otherwise proven
"-v 165,raw48,Block_Erase_Count "
"-v 166,raw48,Minimum_PE_Cycles "
"-v 167,raw48,Max_Bad_Blocks_per_Die "
"-v 168,raw48,Maximum_PE_Cycles "
"-v 169,raw48,Total_Bad_Blocks "
"-v 170,raw48,Grown_Bad_Blocks "
"-v 171,raw48,Program_Fail_Count "
"-v 172,raw48,Erase_Fail_Count "
"-v 173,raw48,Average_PE_Cycles "
"-v 174,raw48,Unexpected_Power_Loss "
"-v 230,raw48,Media_Wearout_Indicator "
"-v 234,raw48,NAND_GB_Written_SLC " //233 NAND GB Written TLC
"-v 241,raw48,Total_GB_Written "
"-v 242,raw48,Total_GB_Read "
"-v 244,raw48,Temp_Throttle_Status "
},
It seams to be working on my: === START OF INFORMATION SECTION === Model Family: WD Blue PC SSD Device Model: WDC WDS100T1B0A-00H9H0 Serial Number: 163966421753 LU WWN Device Id: 5 001b44 4a64c7f6f Firmware Version: X41000WD User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 T13/2015-D revision 3 SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Thu Nov 17 07:26:20 2016 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled I narrowed the regexp to the https://www.wdc.com/products/solid-state-drives/wd-blue-ssd.html , but IMHO it could be added to all "WDC WDS.*" at the moment. |
|||
| #772 | fixed | WD My Passport X not in drivedb | ||
| Description |
As the title says, the WD My Passport X is not in the drive database. To make it work it needs only '-d sat'. Attached you can find the output of 'smartctl -x', the relevant dmesg output and lsusb output in case it is needed. There are already two regular expressions in the database that could be extended to include this disk, but I don't know if you'd prefer to create a new entry for this model so I have not attached any patches. |
|||
