Custom Query (1557 matches)
Results (13 - 15 of 1557)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1973 | fixed | Please add Transcend TS2GSSD25H-S to the database | ||
| Description |
Transcend TS2GSSD25H-S is a Half-Slim SATA SSD. The controller is a Silicon Motion SM2242 (SM2242G, as far as I can tell from the print on the chip). There are four variants of this drive with 1, 2, 4 and 8GB capacity per datasheet https://www.transcend-info.com/products/images/modelpic/513/Datasheet_Flash_SSD_Half-Slim_SSD25H_SLC_V2.2.pdf TS1GSSD25H-S TS2GSSD25H-S TS4GSSD25H-S TS8GSSD25H-S Please find attached the output of smartctl -a -x /dev/sdX |
|||
| #1972 | duplicate | SMART Alert Reports Wrong Drive Information (S/N and Model) | ||
| Description |
Hi, I'm reporting an issue where smartd uses cached device information when a device path gets reassigned to a different physical drive, leading to incorrect device identification in alert emails. I initially reported this to Proxmox VE (https://bugzilla.proxmox.com/show_bug.cgi?id=6875) but they confirmed it's a smartmontools behavior that should be addressed upstream. Here's what happened: My Proxmox host has a SATA controller with PCIe passthrough to a TrueNAS VM. During boot, smartd scans all devices including a 16TB Seagate ST16000NM000J on that controller. After boot, the controller is passed through to the VM. Later, I connected a 4.5TB USB drive with SMART errors that appeared as /dev/sda. When smartd detected 2435 pending sectors on /dev/sda, the email alert showed the serial number, model, and capacity of the Seagate drive instead of the actual USB drive. The Seagate was never /dev/sda on Proxmox - smartd just cached its information during the initial scan and reused it when a different drive appeared at that path. This is problematic because administrators might replace the wrong drive based on incorrect serial numbers, while the actually failing drive goes unnoticed. Device paths like /dev/sdX aren't stable identifiers, and smartd should either detect when a device has changed (via WWN/serial mismatch) or re-query the device before sending alerts. As a workaround, I can configure smartd to explicitly exclude or include specific devices, but the default behavior of trusting cached information for reassigned device paths seems fundamentally unsafe for modern dynamic storage environments with hot-swappable bays, USB drives, or passthrough configurations. Is this the intended behavior, or could smartd be made to verify device identity before using cached information? Thanks |
|||
| #1971 | wontfix | Please add support for Crucial X9 Pro CT2000X9PROSSD9 | ||
| Description |
Here is a regular -x output: root@RaspberryPi:~# smartctl -x /dev/sde2 smartctl 7.2 2020-12-30 r5155 [aarch64-linux-6.1.21-v8+] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: Micron Product: CT2000X9PROSSD9 Revision: 1000 Compliance: SPC-4 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Logical block size: 512 bytes LU is resource provisioned, LBPRZ=1 Rotation Rate: Solid State Device Logical Unit id: 0x5000000000000001 Serial number: 2508E8C5B78E Device type: disk Local Time is: Wed Oct 1 02:17:03 2025 CEST SMART support is: Available - device has SMART capability. SMART support is: Disabled Temperature Warning: Disabled or Not Supported Read Cache is: Enabled Writeback Cache is: Enabled === START OF READ SMART DATA SECTION === SMART Health Status: OK Current Drive Temperature: 0 C Drive Trip Temperature: 0 C Error Counter logging not supported Device does not support Self Test logging Device does not support Background scan results logging The output with -d sat is more informative but does not show vendor and model.
root@RaspberryPi:~# smartctl -x -d sat /dev/sde2
smartctl 7.2 2020-12-30 r5155 [aarch64-linux-6.1.21-v8+] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: [No Information Found]
Serial Number: [No Information Found]
LU WWN Device Id: 0 000000 000000000
Firmware Version: U1CR1A08
User Capacity: 2,000,398,933,504 bytes [2.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
TRIM Command: Available
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is: SATA 3.1, >6.0 Gb/s (4)
Local Time is: Wed Oct 1 02:19:25 2025 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Unavailable
=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error unsupported scsi opcode
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x00) Offline data collection not supported.
SMART capabilities: (0x0000) Automatic saving of SMART data is not implemented.
Error logging capability: (0x00) Error logging supported.
General Purpose Logging 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 POSR-K 100 100 000 - 0
5 Reallocated_Sector_Ct -O--CK 100 100 010 - 0
9 Power_On_Hours -O--CK 100 100 000 - 8
12 Power_Cycle_Count -O--CK 100 100 000 - 6
171 Unknown_Attribute -O--CK 100 100 000 - 0
172 Unknown_Attribute -O--CK 100 100 000 - 0
173 Unknown_Attribute -O--CK 100 100 000 - 0
174 Unknown_Attribute -O--CK 100 100 000 - 2
180 Unused_Rsvd_Blk_Cnt_Tot PO--CK 000 000 000 - 7552
183 Runtime_Bad_Block -O--CK 100 100 000 - 0
184 End-to-End_Error -O--CK 100 100 000 - 0
187 Reported_Uncorrect -O--CK 100 100 000 - 0
194 Temperature_Celsius -O---K 063 063 000 - 37 (Min/Max 24/37)
196 Reallocated_Event_Count -O--CK 100 100 000 - 0
197 Current_Pending_Sector -O--CK 100 100 000 - 0
198 Offline_Uncorrectable ----CK 100 100 000 - 0
199 UDMA_CRC_Error_Count -O--CK 100 100 000 - 0
202 Unknown_SSD_Attribute ----CK 100 100 001 - 0
206 Unknown_SSD_Attribute -OSR-- 100 100 000 - 0
210 Unknown_Attribute -O--CK 100 100 000 - 0
246 Unknown_Attribute -O--CK 100 100 000 - 61626256
247 Unknown_Attribute -O--CK 100 100 000 - 485476
248 Unknown_Attribute -O--CK 100 100 000 - 3178
250 Read_Error_Retry_Rate -O--CK 000 000 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
Read SMART Log Directory failed: scsi error unsupported scsi opcode
ATA_READ_LOG_EXT (addr=0x00:0x00, page=0, n=1) failed: scsi error unsupported scsi opcode
Read GP Log Directory failed
SMART Extended Comprehensive Error Log (GP Log 0x03) not supported
Read SMART Error Log failed: scsi error unsupported scsi opcode
SMART Extended Self-test Log (GP Log 0x07) not supported
Read SMART Self-test Log failed: scsi error unsupported scsi opcode
Selective Self-tests/Logging not supported
SCT Commands not supported
Device Statistics (GP/SMART Log 0x04) not supported
Pending Defects log (GP Log 0x0c) not supported
ATA_READ_LOG_EXT (addr=0x11:0x00, page=0, n=1) failed: scsi error unsupported scsi opcode
Read SATA Phy Event Counters failed
|
|||
