Custom Query (1563 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:

Results (439 - 441 of 1563)

← 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 →
Ticket Resolution Summary Owner Reporter
#1278 fixed update-smart-drivedb: Older releases return *** BAD signature *** Christian Franke Stanislav Brabec
Description

When calling update-smart-drivedb from smartmontools-6.6, it always fails: /usr/sbin/update-smart-drivedb: /usr/share/smartmontools/drivedb.h.error.raw: * BAD signature *

Digging deeper into this problem by sh -x, I see: ++ gpg --quiet --no-secmem-warnin --batch --no-tty --homedir=/usr/share/smartmontools/.gnupg.12981.tmp --verify /usr/share/smartmontools/drivedb.h.new.raw.asc /usr/share/smartmontools/drivedb.h.new.raw + out='gpg: Signature made Sat Dec 28 22:44:15 2019 CET gpg: using RSA key EA74AB25721042C5 gpg: Can'\t check signature: No public key' + rc=1

There is a problem:

smartmontools-6.6 hardcodes requirement of "Smartmontools Signing Key (through 2018)". But drivedb.h.raw.asc in the branch RELEASE_6_6_DRIVEDB is signed by "Smartmontools Signing Key (through 2020)". This cannot work.

drivedb.h.raw.asc in the branch RELEASE_6_6_DRIVEDB has to use "Smartmontools Signing Key (through 2018)" forever. You have to extend validity period of this signing key, and then use that key for signing of this branch.

Similarly, once RELEASE_7_0_DRIVEDB will be created, it has to be signed by "Smartmontools Signing Key (through 2020)" forever. And if it will not be created, you will go into unfixable problems in 2021 (version 7.0 will require a different signature than a future 7.3).

In general, replacement of signing key every two years is not smart. It does not increase security, but paradoxically it decreases the security. New signing key has no trusted developer signatures, no trusted ring, so there are no way to verify that the key was created by legitimate developers.

That is why I recommend to stop creating new keys every two years. Please create a well established trusted key, and when it will be required (e. g. signature considered as weak), add a signature to it. Developers should sign this key by their private keys, so people who have them in the trust ring could immediately trust this key.

To decrease problems with future compatibility (e. g. extended key validity period, added signature), the script should update the key from the GPG network: gpg --recv-keys {key_id}

This will also ensure security, as the possibly revoked key will be refused.

#1280 fixed Support TS120GMTS420S Christian Franke Thomas1024
Description

Add support for TS120GMTS420S. 

diff --git a/smartmontools/drivedb.h b/smartmontools/drivedb.h
index 804d8eca..e29172ab 100644
--- a/smartmontools/drivedb.h
+++ b/smartmontools/drivedb.h
@@ -2020,7 +2020,7 @@ const drive_settings builtin_knowndrives[] = {
       // TS256GSSD370/N0815B, TS256GSSD370S/N1114H, TS512GSSD370S/N1114H, TS32GSSD420I/N1114H,
       // TS32GSSD420K/P1225CE
     "TS(16|32|64|128|512|256)GMTS4[03]0S?|" // TS256GMTS400, TS256GMTS430S/S0423A
-    "TS(120|240)GMTS420|" // Transcend MTS420
+    "TS(120|240)GMTS420[S]|" // Transcend MTS420
     "TS(128G|256G|512G|1T)SSD230S|" // TS128GSSD230S/P1025F8
     "TS(120|240|480|960)GSSD220S|" // TS480GSSD220S/P0520AA
     "TS(16G|32G|64G|128G|256G|512G|1T)MTS800S?|" // MTS800, tested with TS1TMTS800/O1225H1

Before: 

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0032   100   100   050    Old_age   Always       -       0
  5 Reallocated_Sector_Ct   0x0032   100   100   050    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   050    Old_age   Always       -       7496
 12 Power_Cycle_Count       0x0032   100   100   050    Old_age   Always       -       713
160 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       0
161 Unknown_Attribute       0x0033   100   100   050    Pre-fail  Always       -       100
163 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       10
164 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       147280
165 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       472
166 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       225
167 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       299
168 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       1500
169 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       81
175 Program_Fail_Count_Chip 0x0032   100   100   050    Old_age   Always       -       0
176 Erase_Fail_Count_Chip   0x0032   100   100   050    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   100   100   050    Old_age   Always       -       0
178 Used_Rsvd_Blk_Cnt_Chip  0x0032   100   100   050    Old_age   Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   050    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   050    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       538
194 Temperature_Celsius     0x0022   100   100   050    Old_age   Always       -       54
195 Hardware_ECC_Recovered  0x0032   100   100   050    Old_age   Always       -       2991
196 Reallocated_Event_Count 0x0032   100   100   050    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0032   100   100   050    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   050    Old_age   Always       -       3
232 Available_Reservd_Space 0x0032   100   100   050    Old_age   Always       -       100
241 Total_LBAs_Written      0x0030   100   100   050    Old_age   Offline      -       210577
242 Total_LBAs_Read         0x0030   100   100   050    Old_age   Offline      -       4258163
245 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       373265

After: 

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0032   100   100   050    Old_age   Always       -       0
  5 Reallocated_Sector_Ct   0x0032   100   100   050    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   050    Old_age   Always       -       7496
 12 Power_Cycle_Count       0x0032   100   100   050    Old_age   Always       -       713
160 Uncorrectable_Error_Cnt 0x0032   100   100   050    Old_age   Always       -       0
161 Valid_Spare_Block_Cnt   0x0033   100   100   050    Pre-fail  Always       -       100
163 Initial_Bad_Block_Count 0x0032   100   100   050    Old_age   Always       -       10
164 Total_Erase_Count       0x0032   100   100   050    Old_age   Always       -       147279
165 Max_Erase_Count         0x0032   100   100   050    Old_age   Always       -       472
166 Min_Erase_Count         0x0032   100   100   050    Old_age   Always       -       225
167 Average_Erase_Count     0x0032   100   100   050    Old_age   Always       -       299
168 Max_Erase_Count_of_Spec 0x0032   100   100   050    Old_age   Always       -       1500
169 Remaining_Lifetime_Perc 0x0032   100   100   050    Old_age   Always       -       81
175 Program_Fail_Count_Chip 0x0032   100   100   050    Old_age   Always       -       0
176 Erase_Fail_Count_Chip   0x0032   100   100   050    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   100   100   050    Old_age   Always       -       0
178 Runtime_Invalid_Blk_Cnt 0x0032   100   100   050    Old_age   Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   050    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   050    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       538
194 Temperature_Celsius     0x0022   100   100   050    Old_age   Always       -       55
195 Hardware_ECC_Recovered  0x0032   100   100   050    Old_age   Always       -       2991
196 Reallocated_Event_Count 0x0032   100   100   050    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0032   100   100   050    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   050    Old_age   Always       -       3
232 Available_Reservd_Space 0x0032   100   100   050    Old_age   Always       -       100
241 Host_Writes_32MiB       0x0030   100   100   050    Old_age   Offline      -       210575
242 Host_Reads_32MiB        0x0030   100   100   050    Old_age   Offline      -       4258163
245 TLC_Writes_32MiB        0x0032   100   100   050    Old_age   Always       -       373265
#1281 fixed PNY CS900 (120 or 240GB) SSD not in database Christian Franke Pierre Jarillon
Description

From smartctl:

START OF INFORMATION SECTION

Device Model: PNY CS900 240GB SSD Device is: Not in smartctl database [for details use: -P showall]

Attributes: 194 Temperature_Celsius -> 33 (hddtemp : /dev/sdc: PNY CS900 240GB SSD: 33°C) 231 Temperature_Celsius -> 99 (shown as a failure)

The attribute 194 is correct but the attribute 231 is not relevant. It seems to have no signification.

I have used SSD 120GB with the same problem.

A screen copy is available at ​https://bugs.mageia.org/attachment.cgi?id=11399 for the bug report ​https://bugs.mageia.org/show_bug.cgi?id=25859

← 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 →
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.