"WD Red SA500 2.5 4TB" not in drivedb

[david]

This SSD doesn't appear to be in the database yet.

From my quick testing it appears to be like the other "WD Blue / Red / Green SSDs".

I will attach smartctl -x -a output.

[david]

smartctl -x -a

[david]

To expand, the minimal testing I mentioned was running smartctl with the lines from the "WD Blue / Red / Green SSDs" section in drivedb.h:

smartctl -a /dev/sdo                                            \
  "-v 165,raw48,Block_Erase_Count "                             \
  "-v 166,raw48,Minimum_PE_Cycles_TLC "                         \
  "-v 167,raw48,Max_Bad_Blocks_per_Die "                        \
  "-v 168,raw48,Maximum_PE_Cycles_TLC "                         \
  "-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_TLC "                         \
  "-v 174,raw48,Unexpected_Power_Loss "                         \
  "-v 230,hex48,Media_Wearout_Indicator "                       \
  "-v 233,raw48,NAND_GB_Written_TLC "                           \
  "-v 234,raw48,NAND_GB_Written_SLC "                           \
  "-v 241,raw48,Host_Writes_GiB "                               \
  "-v 242,raw48,Host_Reads_GiB "                                \
  "-v 244,raw48,Temp_Throttle_Status "

This changed the SMART Attribute section to this:

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0032   100   100   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       82
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2
165 Block_Erase_Count       0x0032   100   100   000    Old_age   Always       -       80
166 Minimum_PE_Cycles_TLC   0x0032   100   100   000    Old_age   Always       -       1
167 Max_Bad_Blocks_per_Die  0x0032   100   100   000    Old_age   Always       -       55
168 Maximum_PE_Cycles_TLC   0x0032   100   100   000    Old_age   Always       -       3
170 Grown_Bad_Blocks        0x0032   100   100   000    Old_age   Always       -       0
171 Program_Fail_Count      0x0032   100   100   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0032   100   100   000    Old_age   Always       -       0
173 Average_PE_Cycles_TLC   0x0032   100   100   000    Old_age   Always       -       1
174 Unexpected_Power_Loss   0x0032   100   100   000    Old_age   Always       -       1
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0032   100   100   000    Old_age   Always       -       37 (Min/Max 23/51)
199 UDMA_CRC_Error_Count    0x0032   100   100   000    Old_age   Always       -       0
230 Media_Wearout_Indicator 0x0032   100   100   000    Old_age   Always       -       0x000000000000
232 Available_Reservd_Space 0x0033   100   100   001    Pre-fail  Always       -       100
233 NAND_GB_Written_TLC     0x0032   100   100   000    Old_age   Always       -       7544
234 NAND_GB_Written_SLC     0x0032   100   100   000    Old_age   Always       -       1363
241 Host_Writes_GiB         0x0032   100   100   000    Old_age   Always       -       2157
242 Host_Reads_GiB          0x0032   100   100   000    Old_age   Always       -       53
244 Temp_Throttle_Status    0x0032   100   100   000    Old_age   Always       -       0

…which looked reasonable to me.

[Christian Franke]

BTW:

Serial Number:    ...
LU WWN Device Id: ...

You could use -q noserial option to suppress these lines.

[miaLDN]

Any idea why the device model isn't reported?

The model number (as printed on the label):

WDS400T2R0A-68CKB0

instead it shows as:

WD Red SA500 2.5 4TB

Can the model number be interrogated another way?

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-4.4.302+] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     WD Red SA500 2.5 4TB
Firmware Version: 540500WD
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        Not in smartctl database 7.3/5852
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Sep 21 00:36:06 2025 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Disabled
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Unknown

[miaLDN]

WD Red SA500 2.5 4TB [smartctl 7.4 2023-08-01 r5530][smartctl database 7.3/5852]

[Christian Franke]

Replying to miaLDN:

Any idea why the device model isn't reported?

The model number (as printed on the label):

WDS400T2R0A-68CKB0

instead it shows as:

WD Red SA500 2.5 4TB

Such differences happen occasionally. You need to ask WDC why the label shows the more technical model name but the ATA IDENTIFY data structure reports a name possibly invented by marketing department.

The existing drive database entry shows that both kind of model names may appear in the ATA IDENTIFY data:

  { "WD Blue / Red / Green SSDs", // tested with WDC WDS250G1B0A-00H9H0/X41000WD,
      // WDC WDS250G1B0A-00H9H0/X41100WD, WDC WDS100T1B0A-00H9H0,
      // ...
      // WD Blue SA510 2.5 1000GB/52008100, WD Blue SA510 2.5 4TB/530309WD
      // ...
  }

Can the model number be interrogated another way?

This is not possible with any ATA command covered by the standard. There may be an undocumented vendor specific command.

[Christian Franke]

[68b11e1683c9].