Custom Query (1566 matches)
Results (367 - 369 of 1566)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1127 | wontfix | -l selftest should display current power on/lifetime hours | ||
| Description |
The LifeTime(hours) column in the smartctl -l selftest output would be much more useful if the output also displayed the current value for this, allowing the user to see how long ago the tests actually ran. Instead, currently one has to look at the output of e.g. smartctl -a to check the power on hours manually before that column is of any use other than as a relative time between different tests in the log. |
|||
| #1132 | wontfix | attrlog files contains attribute strings for SCSI disks, but attribute numbers for ATA disks | ||
| Description |
While trying to evaluate the numbers smartd write to attrlog files, I noticed that for SCSI disks the attributes have names like "temperature", while for ATA disks there are no attribute names, i.e. the attribute is specified by number (like 194). I'd prefer (ore or less) short and stable attribute names if known. For example a line in an ATA attrlog looks like: 2015-12-18 12:10:28; 1;63;38776360; 3;98;0; 4;99;1185; 5;100;0; 7;84;290151632; 9;68;28632; 10;100;0; 12;99;1191; 194;41;55834574889; 195;63;38776360; 197;100;0; 198;100;0; 199;200;0; 200;100;0; 202;100;0; A line from a SCSI attrlog looks like: 2016-03-08 15:05:07; read-corr-by-ecc-fast;0; read-corr-by-ecc-delayed;26075; read-corr-by-retry;0; read-total-err-corrected;26075; read-corr-algorithm-invocations;0; read-gb-processed;337052.962; read-total-unc-errors;0; write-corr-by-ecc-fast;0; write-corr-by-ecc-delayed;48719; write-corr-by-retry;0; write-total-err-corrected;48719; write-corr-algorithm-invocations;0; write-gb-processed;1481.749; write-total-unc-errors;0; verify-corr-by-ecc-fast;0; verify-corr-by-ecc-delayed;0; verify-corr-by-retry;0; verify-total-err-corrected;0; verify-corr-algorithm-invocations;0; verify-gb-processed;0.000; verify-total-unc-errors;0; non-medium-errors;366; temperature;28; |
|||
| #1153 | wontfix | Command timeout occurred when I used the command "smartctl -C -t short" on HDD test | ||
| Description |
Hi, When I used this command "smartctl -c -t short /dev/sdb" to verify SSD, smartctl (using smartctl -a)test result would show "Interrupt (host reset)" as following. # 6 Short captive Interrupted (host reset) 70% 2423 - # 7 Short captive Interrupted (host reset) 70% 2408 - And /dev/log/dmesg also occurred some error messages below. However, when I removed -C (captive mode), these issues would disappeared. I tried lots of SSDs (Intel, Samsung, HGST), I got the same symptom. Would you please advise if the parameter "-C" can't use with "-t" in the same test? Or is it a bug for smartctl tool? I will be grateful for any help you can provide. /var/log/dmesg ================================================================= [166867.098164] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [166867.098172] ata2.00: failed command: SMART [166867.098180] ata2.00: cmd b0/d4:00:81:4f:c2/00:00:00:00:00/00 tag 25
[166867.098184] ata2.00: status: { DRDY } [166867.098189] ata2: hard resetting link [166867.403151] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [166867.403678] ata2.00: supports DRM functions and may not be fully accessible [166867.404715] ata2.00: supports DRM functions and may not be fully accessible [166867.405200] ata2.00: configured for UDMA/133 [166867.405218] ata2: EH complete |
|||
