Custom Query (1560 matches)

Modify SSSTC/SATA ERX-GD/CD to database add CD480G,SGD1T92,CD960GA,SSSTC GD3T84 for ER5

Request to add Acer SA100 SSDs to drivedb.

The drives are manufactured by BIWIN Storage Technology.

​https://www.acerstorage.com/products/sata-25-ssd/acer-ssd-sa100/

I have several 480GB SSDs, and only one of these has the SN11873 firmware. This drive seems to be a Maxio based (variant 2) kind. The patch for this drive:

--- drivedb.h.20260416  2026-04-16 08:41:00.000000000 -0600
+++ drivedb.h   2026-04-22 16:54:53.879638186 -0600
@@ -645,6 +645,7 @@
     "-v 245,raw16(raw16),Bit_Error_Count"
   },
   { "Maxio based SSDs (variant 2)", // MAS0902, MAS1102
+    "Acer SSD SA100 (12|24|48|96)0GB|"               // tested with Acer SSD SA100 480GB/SN11873
     "Fanxiang S101 ((128|256|500|512)G|[124]T)B|"    // Fanxiang S101, tested with Fanxiang S101 2TB/SN14130
     "FORESEE ((128|256|512)G|[12]T)B SSD|"           // Foresee S58A, tested with FORESEE 512GB SSD/V1.2.7
     "HP SSD S600 (120|240)GB|"                       // tested with HP SSD S600 240GB/SN8108

All other SA100 drives have very different firmware versions, and they seem to be well suited for the following description:

  { "BIWIN Storage Technology SSDs",
    "Acer SSD SA100 (12|24|48|96)0GB", // tested with Acer SSD SA100 240GB/W0419B0,
      // Acer SSD SA100 480GB/U0302B0 and U0401A0
    "[UW]0[34]..[AB]0", "",
  //"-v 1,raw48,Raw_Read_Error_Rate "
  //"-v 5,raw16(raw16),Reallocated_Sector_Ct "
  //"-v 9,raw24(raw8),Power_On_Hours "
  //"-v 12,raw48,Power_Cycle_Count "
    "-v 160,raw48,Uncorrectable_Sectors "
    "-v 161,raw48,Valid_Spare_Block_Cnt "
    "-v 163,raw48,Initial_Bad_Block_Count "
    "-v 164,raw48,Total_Erase_Count "
    "-v 165,raw48,Max_Erase_Count "
    "-v 166,raw48,Min_Erase_Count "
    "-v 167,raw48,Average_Erase_Count "
    "-v 168,raw48,Max_Erase_Count_of_Spec "
    "-v 169,raw48,Remaining_Lifetime_Perc "
  //"-v 175,raw48,Program_Fail_Count_Chip "
  //"-v 176,raw48,Erase_Fail_Count_Chip "
  //"-v 177,raw48,Wear_Leveling_Count "
    "-v 178,raw48,Runtime_Invalid_Blk_Cnt "
  //"-v 181,raw48,Program_Fail_Cnt_Total "
  //"-v 182,raw48,Erase_Fail_Count_Total "
  //"-v 192,raw48,Power-Off_Retract_Count "
    "-v 194,raw48,Device_Temperature "
  //"-v 195,raw48,Hardware_ECC_Recovered "
  //"-v 196,raw16(raw16),Reallocated_Event_Count "
  //"-v 196,raw48,Reallocated_Event_Count "
  //"-v 197,raw48,Current_Pending_Sector "
  //"-v 198,raw48,Offline_Uncorrectable "
  //"-v 199,raw48,UDMA_CRC_Error_Count "
  //"-v 232,raw48,Available_Reservd_Space "
  //"-v 241,raw48,Total_LBAs_Written "
  //"-v 242,raw48,Total_LBAs_Read "
    "-v 245,raw48,Flash_Writes_Sectors "
  },

Both drives have exactly the same part numbers on their labels:

P/N: BL.9BWWA.103

Both kinds of drives are recognized by the BIWIN Intellifence application, and corresponding SMART reports can be seen in the attached PDFs.

​https://www.acerstorage.com/biwin-intelligence/

After automatic drivedb.h update on April 12 2026, smartd crashes immediately when monitoring a WD Red Plus (WD20EFRX-68EUZN0).

Error message: malloc(): unaligned tcache chunk detected

Drive details:

• Model: WDC WD20EFRX-68EUZN0
• Firmware: 82.00A82
• WWN: 5-0014ee-26338ef76

Environment:

• smartd version: 7.4 2023-08-01 r5530
• OS: TrueNAS 25.04.2.6 (Linux 6.12.15)

Steps to reproduce:

1. Install WD20EFRX-68EUZN0
2. Use drivedb.h dated April 12 2026
3. Start smartd with this drive configured
4. smartd crashes immediately after identifying the drive

Workarounds that fix the issue:

• Roll back to drivedb.h dated March 1 2026 -> works
• Use -P ignore directive in smartd.conf -> works

The March 1 drivedb.h works perfectly with the same drive and same smartd binary, confirming the bug is in the April 12 drivedb.h.