Custom Query (1560 matches)
Results (448 - 450 of 1560)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1858 | fixed | INTENSO SSD 128g not in the smartctl database | ||
| Description |
Hi Guys, my SSD is not in the smartctl database 7.3/5610, could you add it? Thanks and best, Patrick smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.8.4-2-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: INTENSO SSD
Serial Number: 1642312006001303
Firmware Version: W0714A0
User Capacity: 128,035,676,160 bytes [128 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
TRIM Command: Available
Device is: Not in smartctl database 7.3/5610
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 Aug 1 11:00:00 2024 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM level is: 254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
Wt Cache Reorder: Unavailable
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x02) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0002) Does not save SMART data before
entering power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 10) minutes.
SCT capabilities: (0x0001) SCT Status supported.
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate -O--CK 100 100 050 - 0
5 Reallocated_Sector_Ct -O--CK 100 100 050 - 1
9 Power_On_Hours -O--CK 100 100 050 - 1547
12 Power_Cycle_Count -O--CK 100 100 050 - 23
160 Unknown_Attribute -O--CK 100 100 050 - 0
161 Unknown_Attribute PO--CK 100 100 050 - 94
163 Unknown_Attribute -O--CK 100 100 050 - 6
164 Unknown_Attribute -O--CK 100 100 050 - 5053
165 Unknown_Attribute -O--CK 100 100 050 - 82
166 Unknown_Attribute -O--CK 100 100 050 - 2
167 Unknown_Attribute -O--CK 100 100 050 - 20
168 Unknown_Attribute -O--CK 100 100 050 - 5050
169 Unknown_Attribute -O--CK 100 100 050 - 100
175 Program_Fail_Count_Chip -O--CK 100 100 050 - 0
176 Erase_Fail_Count_Chip -O--CK 100 100 050 - 0
177 Wear_Leveling_Count -O--CK 100 100 050 - 0
178 Used_Rsvd_Blk_Cnt_Chip -O--CK 100 100 050 - 1
181 Program_Fail_Cnt_Total -O--CK 100 100 050 - 0
182 Erase_Fail_Count_Total -O--CK 100 100 050 - 0
192 Power-Off_Retract_Count -O--CK 100 100 050 - 14
194 Temperature_Celsius -O---K 100 100 050 - 40
195 Hardware_ECC_Recovered -O--CK 100 100 050 - 0
196 Reallocated_Event_Count -O--CK 100 100 050 - 0
197 Current_Pending_Sector -O--CK 100 100 050 - 1
198 Offline_Uncorrectable -O--CK 100 100 050 - 0
199 UDMA_CRC_Error_Count -O--CK 100 100 050 - 0
232 Available_Reservd_Space -O--CK 100 100 050 - 94
241 Total_LBAs_Written ----CK 100 100 050 - 13616
242 Total_LBAs_Read ----CK 100 100 050 - 22095
245 Unknown_Attribute -O--CK 100 100 050 - 29419
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 1 Comprehensive SMART error log
0x03 GPL R/O 1 Ext. Comprehensive SMART error log
0x04 GPL,SL R/O 8 Device Statistics log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x24 GPL R/O 88 Current Device Internal Status Data log
0x25 GPL R/O 32 Saved Device Internal Status Data log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged
SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 1547 -
# 2 Extended offline Completed without error 00% 1547 -
# 3 Extended offline Completed without error 00% 1405 -
Selective Self-tests/Logging not supported
SCT Status Version: 3
SCT Version (vendor specific): 0 (0x0000)
Device State: Active (0)
Current Temperature: 40 Celsius
Power Cycle Min/Max Temperature: 40/40 Celsius
Lifetime Min/Max Temperature: 22/40 Celsius
Specified Max Operating Temperature: 100 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Data Table command not supported
SCT Error Recovery Control command not supported
Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 1) ==
0x01 0x008 4 23 --- Lifetime Power-On Resets
0x01 0x010 4 1547 --- Power-on Hours
0x01 0x018 6 892360040 --- Logical Sectors Written
0x01 0x020 6 20563297 --- Number of Write Commands
0x01 0x028 6 1448028657 --- Logical Sectors Read
0x01 0x030 6 14096700 --- Number of Read Commands
0x07 ===== = = === == Solid State Device Statistics (rev 1) ==
0x07 0x008 1 0 --- Percentage Used Endurance Indicator
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized value
Pending Defects log (GP Log 0x0c) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 4 0 Command failed due to ICRC error
0x0002 4 0 R_ERR response for data FIS
0x0005 4 0 R_ERR response for non-data FIS
0x000a 4 3 Device-to-host register FISes sent due to a COMRESET
|
|||
| #1850 | fixed | Ignore individual NVME temperature sensors | ||
| Description |
I have a Kingston Fury Renegade NVMe SSD, SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 62 Celsius ... Temperature Sensor 2: 67 Celsius
and as nvme-pci-0100
Adapter: PCI adapter
Composite: +61.9°C (low = -20.1°C, high = +83.8°C)
(crit = +88.8°C)
Sensor 2: +66.8°C
The problem is, only
I track this drive with
This, however, now causes me to get the notification on every boot, because Jun 30 15:38:29 hostname smartd[18016]: Device: /dev/disk/by-id/nvme-KINGSTON_SFYRDK4000G_..., Temperature 67 Celsius reached critical limit of 65 Celsius (Min/Max 67/67)
Effectively making the whole So it seems like this behaviour, described in the man page, is messing with me:
Is there a way to instruct
If there isn't, could you consider this enhancement? It seems like a valid use case with no other solution. For now I'll have to pass |
|||
| #204 | wontfix | Illegal request CDBs submit to some models of Fujitsu SCSI disks | ||
| Description |
Since smartmontools 5.41, on our Solaris 9/10 systems when using "smartctl -a" against a Fujitsu SCSI disk, it appears smartctl is submitting invalid CDBs to the underlying drive (which rejects the command, citing ILLEGAL REQUEST). "smartctl -x" induces two rejections. smartmontools 5.40 does not cause this behaviour. The problem with the rejection is that the Solaris kernel logs this in such a way that it appears as a disk failure to our NOC, which results tickets opened to have disks replaced when in fact there's nothing wrong with the disk at all. Relevant details: # iostat -E -n
c0t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAW3147NC Revision: 0104 Serial No:
Size: 147.09GB <147086327296 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
# smartctl -x /dev/rdsk/c0t0d0s0
smartctl 5.42 2011-10-20 r3458 [i386-pc-solaris2.10] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
Vendor: FUJITSU
Product: MAW3147NC
Revision: 0104
User Capacity: 147,086,327,808 bytes [147 GB]
Logical block size: 512 bytes
Serial number: DAA0P7B05H9C
Device type: disk
Transport protocol: Parallel SCSI (SPI-4)
Local Time is: Wed Nov 9 01:49:21 2011 PST
Device supports SMART and is Enabled
Temperature Warning Enabled
SMART Health Status: OK
Current Drive Temperature: 26 C
Drive Trip Temperature: 65 C
Manufactured in week 46 of year 2007
Specified cycle count over device lifetime: 10000
Accumulated start-stop cycles: 19
Elements in grown defect list: 0
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: 0 0 0 0 0 6208.306 0
write: 0 9 0 0 0 24562.295 0
Non-medium error count: 53
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Self test in progress ... - NOW - [- - -]
# 2 Background long Self test in progress ... - NOW - [- - -]
Long (extended) Self Test duration: 3432 seconds [57.2 minutes]
Device does not support Background scan results logging
scsiPrintSasPhy Log Sense Failed [unsupported field in scsi command]
# iostat -E -n
c0t0d0 Soft Errors: 2 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAW3147NC Revision: 0104 Serial No:
Size: 147.09GB <147086327296 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 2 Predictive Failure Analysis: 0
Errors on console, which I imagine will greatly help since they include the request CDB: Nov 9 09:49:21 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci1022,7450@a/pci9005,ffff@a/sd@0,0 (sd0): Error for Command: inquiry Error Level: Informational Nov 9 09:49:21 scsi: [ID 107833 kern.notice] Requested Block: 0 Error Block: 0 Nov 9 09:49:21 scsi: [ID 107833 kern.notice] Vendor: FUJITSU Serial Number: DAA0P7B05H9C Nov 9 09:49:21 scsi: [ID 107833 kern.notice] Sense Key: Illegal Request Nov 9 09:49:21 scsi: [ID 107833 kern.notice] ASC: 0x24 (invalid field in cdb), ASCQ: 0x0, FRU: 0x0 Nov 9 09:49:22 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci1022,7450@a/pci9005,ffff@a/sd@0,0 (sd0): Error for Command: log sense(10) Error Level: Informational Nov 9 09:49:22 scsi: [ID 107833 kern.notice] Requested Block: 0 Error Block: 0 Nov 9 09:49:22 scsi: [ID 107833 kern.notice] Vendor: FUJITSU Serial Number: DAA0P7B05H9C Nov 9 09:49:22 scsi: [ID 107833 kern.notice] Sense Key: Illegal Request Nov 9 09:49:22 scsi: [ID 107833 kern.notice] ASC: 0x24 (invalid field in cdb), ASCQ: 0x0, FRU: 0x0 I believe the "scsiPrintSasPhy Log Sense Failed" error can explain one of the illegal requests, but I'm not sure where the other is. Pretty much all our Fujitsu disks behave like this -- more than just the model shown above (smaller models, etc.). If you need me to make a list of them all (for drivedb exclusions/quirks) I can do so. Let me know how to proceed, I have lots of systems to test with. :-) |
|||
Note:
See TracQuery
for help on using queries.
