Custom Query (1434 matches)
Results (94 - 96 of 1434)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1331 | duplicate | smartctl 7.1 doesn't show attributes on Seagate SAS drives but 6.6 does | ||
Description |
For this I'm using a Dell R720xd with an LSI 9211-8i HBA in IT Mode and a Seagate ST3300657SS. I'm testing 7.1 using Debian Buster and 6.6 using Ubuntu Bionic because that is the default version they come with. If there are downstream code changes by the distribution responsible for this difference I apologize and will redirect my issue there. Here is the result from Debian Buster root@cloud1:~# smartctl -a /dev/sda smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.3.18-2-pve] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: SEAGATE Product: ST3300657SS Revision: 000B Compliance: SPC-3 User Capacity: 300,000,000,000 bytes [300 GB] Logical block size: 512 bytes Rotation Rate: 15000 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000c5008db145bb Serial number: 6SJ840DR0000N4381HL2 Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Mon May 11 09:32:19 2020 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Enabled === START OF READ SMART DATA SECTION === SMART Health Status: OK Current Drive Temperature: 0 C Drive Trip Temperature: 0 C Elements in grown defect list: 0 Error Counter logging not supported Device does not support Self Test logging And here is the result for the same drive from Ubuntu Bionic root@ubuntu:~# smartctl -a /dev/sda smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.0.0-23-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: SEAGATE Product: ST3300657SS Revision: 000B User Capacity: 300,000,000,000 bytes [300 GB] Logical block size: 512 bytes Rotation Rate: 15000 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000c5008db145bb Serial number: 6SJ840DR0000N4381HL2 Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Mon May 11 14:48:23 2020 UTC SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Enabled === START OF READ SMART DATA SECTION === SMART Health Status: OK Current Drive Temperature: 33 C Drive Trip Temperature: 68 C Elements in grown defect list: 0 Vendor (Seagate) cache information Blocks sent to initiator = 1460697 Blocks received from initiator = 8989202 Blocks read from cache and sent to initiator = 170255 Number of read and write commands whose size <= segment size = 79689 Number of read and write commands whose size > segment size = 1 Vendor (Seagate/Hitachi) factory information number of hours powered up = 13257.17 number of minutes until next internal SMART test = 34 Error counter log: Errors Corrected by Total Correction Gigabytes Total ECC rereads/ errors algorithm processed uncorrected fast | delayed rewrites corrected invocations [10^9 bytes] errors read: 21440 0 0 21440 21440 0.748 0 write: 0 0 0 0 0 4.628 0 verify: 1976 0 0 1976 1976 0.000 0 Non-medium error count: 0 SMART Self-test log Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background short Completed - 366 - [- - -] # 2 Background short Completed - 1 - [- - -] # 3 Background short Completed - 0 - [- - -] Long (extended) Self Test duration: 3200 seconds [53.3 minutes] |
|||
#1892 | fixed | smartctl -x return value 4 if SCT ERC is not supported | ||
Description |
I have noticed a possible bug that causes the smartctl -x return value to be 4 instead of 0. It seems to be related to SCT support. On SATA drives that support SCT the return value is 4 while with no SCT support the return value is 0. My smartctl version is pre-7.5 r5618. The attached logs show smartctl -x output with the return value at the bottom.
|
|||
#1828 | duplicate | smartctl -x creates new NVMe errors | ||
Description |
I was given a drive to check the condition, but errors kept increasing. After a while I actually noticed that the errors increased by 1 by each smartctl -x call (I was repeatedly checking the state of the ssd while ext4 lazy inode init was doing its job after formatting the partition). Since the errors are not about failure, but rather a malformed command, could be done something in smartctl in order to prevent such things happening? My expectation: an error checking tool shall not generate errors while doing so. I see multiple reasons why to fix this - if somebody calls smartctl repetitively, the errors increase but its not actually representing any error condition of the drive. If somebody would call smartctl too aggressively, then actual errors might get lost. (if the nvme error log is a circular buffer which afaik is, 64 entries on mine). There was a #1222 ticket about something similar? Smartd should ignore non-error entries from NVMe Error Information log But hiding is one thing.. while making actual errors is something NOT desireable. So the drive in question is a WD SN640 nvme: === START OF INFORMATION SECTION === Model Number: WUS4BB076D7P3E3 Serial Number: ******** Firmware Version: R111000L PCI Vendor/Subsystem ID: 0x1b96 IEEE OUI Identifier: 0x0014ee Total NVM Capacity: 7,681,501,126,656 [7.68 TB] Unallocated NVM Capacity: 0 Controller ID: 0 NVMe Version: 1.3 Number of Namespaces: 1 Namespace 1 Size/Capacity: 7,681,501,126,656 [7.68 TB] Namespace 1 Formatted LBA Size: 4096 Namespace 1 IEEE EUI-64: 0014ee 83066cbb80 Local Time is: Tue Apr 30 20:30:15 2024 CEST Firmware Updates (0x19): 4 Slots, Slot 1 R/O, no Reset required Optional Admin Commands (0x001f): Security Format Frmw_DL NS_Mngmt Self_Test Optional NVM Commands (0x005e): Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Log Page Attributes (0x03): S/H_per_NS Cmd_Eff_Lg Warning Comp. Temp. Threshold: 70 Celsius Critical Comp. Temp. Threshold: 80 Celsius Namespace 1 Features (0x02): NA_Fields Current state at end of smartctl -x call: Error Information (NVMe Log 0x01, 16 of 256 entries) Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message 0 12 0 0xd009 0xc004 - 0 1 - Invalid Field in Command 1 11 0 0xc008 0xc004 - 0 1 - Invalid Field in Command 2 10 0 0xa00b 0xc004 - 0 1 - Invalid Field in Command 3 9 0 0x900a 0xc004 - 0 1 - Invalid Field in Command 4 8 0 0x8009 0xc004 - 0 1 - Invalid Field in Command 5 7 0 0xa00e 0xc004 - 0 1 - Invalid Field in Command 6 6 0 0x900d 0xc004 - 0 1 - Invalid Field in Command 7 5 0 0x7008 0xc004 - 0 1 - Invalid Field in Command 8 4 0 0x800c 0xc004 - 0 1 - Invalid Field in Command 9 3 0 0x600c 0xc004 - 0 1 - Invalid Field in Command 10 2 0 0x100a 0xc004 - 0 1 - Invalid Field in Command 11 1 0 0x300e 0xc004 0x028 0 0 - Invalid Field in Command And using nvme-cli error-log, i see that all these errors (except the oldest) are of this kind: ................. Entry[ 0] ................. error_count : 12 sqid : 0 cmdid : 0xd009 status_field : 0x6002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field) phase_tag : 0 parm_err_loc : 0xffff lba : 0 nsid : 0x1 vs : 0 trtype : The transport type is not indicated or the error is not transport related. csi : 0 opcode : 0 cs : 0 trtype_spec_info: 0 log_page_version: 0 How can we trace this to an exact query which smartctl does? |