Recent content by wefinet

Hallo Thomas, sorry, dass ich mich so spät hier erst melde. Die Ursache liegt hier darin, dass bislang bei Elkhart Lake Systemen das SATA Link Power Management nicht vom Linux Kernel aktiviert wird. Ich habe dazu soeben einen Patch an die linux-ide Mailing Liste geschrieben, der das ergänzt...

That's great news, Colin. You will not receive further emails from smartd when ID 197 flips from 0 -> 1 from time to time. Have a nice weekend and lot of fun with your Proxmox setup :)

Thank you Colin for your output. To get rid of the ID 197 emails, just create the file /etc/smart_drivedb.h with the following content: { "Netac SSD", "NS128GSSD340", "V0823A0", "", "-v 1,raw48,Raw_Read_Error_Count " "-v 5,raw16(raw16),Realloc_Flash_Blocks_Ct " //"-v...

No, there is no need at all to recompile smartmontools. You just need to add an entry for your drive, e.g. based on the Crucial drives with a similar entry for ID 197. You can use a local drivedb.h for this - see...

Hi Colin, it seems your SSD has a Silicon Motion SM2259 controller chip. The SMART attribute 197 has the following meaning for those controllers: This value represents the total number of ECC events found as a result of host commands (for example, READ commands) or during background operations...

@t.lamprecht I did not do tests with your 5.15 kernel by now, but it seems this fix of the mellanox mlx5 driver would be important to include (the fix is included with Vanilla Kernel 5.15.20)...

@spirit it seems you are right: Vanilla Kernel 5.13.0 (which is the first Kernel which has the issue) contains this commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e19b0a3474ab9ef90dd110af9f39fc87329755f1 (net/mlx5: Refactor module EEPROM query) Vanilla...

We did a lot of research on this and here is the current result: Linux (Vanilla) Kernels starting with Kernel 5.13.0 have this issue. Somewhere between Linux Kernel 5.15.12 and Linux Kernel 5.15.25 the issue has been fixed. We assume that one of these Kernel Updates fixed the issue (we will do...

Jonas and I have been able to fix this issue by applying X12SPL-F BIOS update 1.1c. Details can be found here (in German): https://www.thomas-krenn.com/de/wiki/Supermicro_X12SPL-F_mit_Proxmox_VE_7_ethX_statt_enoX_NICs_mit_BIOS_1.1

We have seen such an issue on a system with Debian 10 and KVM (not running Proxmox). The mainboard is a Supermicro H11DSi-NT (revision 1) with BIOS version 1.0c. We think that maybe the new BIOS version 1.3 could fix it, as there is an updated AGESA and in it. As the reboots happen randomly...

Hallo maxprox, erstmals gern geschehen für die Info und den Wiki Artikel :) > Als Folgefrage, wenn in das Linux System, ist das Microcode Update unabhängig von der Kernel Version oder kann man sich evtl. das Microcode Update ab einer gewissen Kernel Version sparen? [wefinet] Das Microcode...

(Vorab Disclaimer: ich bin Thomas-Krenn-Mitarbeiter). Grundsätzlich können wir zwar natürlich keinen Support von Systemen übernehmen, die nicht bei uns bezogen wurden. Gerade bei Systemabstürzen können viele unterschiedliche Komponenten die Ursache sein - bis hin zu Netzteilen, die nicht...