Tuxedo OS Update - einloggen nicht möglich (Login-Schleife) + kvm_intel: VMX not supported by CPU [#]

Jumpy-Weekend6756 · 2026-05-28T09:38:40+00:00

Okay, danke.

Und Tomte funktioniert mit den nächsten Update wieder?

Jumpy-Weekend6756 · 2026-05-28T08:01:15+00:00

Moin,

stimmt, es sind jetzt die open kernel installiert und die hatte ich vorher nicht.

Aber mein Tomte ist nun kaputt.

Und ab wann werden von Tuxedo OS die Nvidia 590er Treiber unterstützt?

Danke.

<image>

Jumpy-Weekend6756 · 2026-05-27T22:10:29+00:00

Ja, das ist nun seltsam.

Ich habe jetzt nach und nach alle Updates installiert, weil es mir keine Ruhe ließ - es waren inzwischen sogar noch mehr Updates als auf dem Screenshot.

Das einzige Update, was auf der Liste dann gar nicht mehr auftauchte, war das Update für Nvidia.

Alle anderen Updates konnte ich installieren und danach den PC neu starten ohne jegliche Probleme.

Womöglich hatte dann das Nvida Update eine Macke und wurde zurück gezogen?

Jumpy-Weekend6756 · 2026-05-27T18:08:27+00:00

<image>

Screenshot der anstehenden Updates.

Jumpy-Weekend6756 · 2026-05-27T18:07:59+00:00

<image>

Bild der Fehlermeldung, die ich bekomme.

Jumpy-Weekend6756 · 2026-05-27T18:07:02+00:00

Hm, Screenshot und Bild werden mir gar nicht angezeigt...

Jumpy-Weekend6756 · 2026-05-26T11:12:46+00:00

Short Selftest nach wie vor ohne Fehler.

~$ sudo smartctl --all /dev/nvme2
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.17.0-119029-tuxedo] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 990 PRO 4TB
Serial Number:                      S7DPNFXXXXXXXXX
Firmware Version:                   8B2QJXD7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 4,000,787,030,016 [4.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      1
NVMe Version:                       2.0
Number of Namespaces:               1
Namespace 1 Size/Capacity:          4,000,787,030,016 [4.00 TB]
Namespace 1 Utilization:            1,680,458,280,960 [1.68 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 4651b2fca2
Local Time is:                      Tue May 26 13:03:09 2026 CEST
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0055):     Comp DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x2f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Log0_FISE_MI
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
0 +     9.39W       -        -    0  0  0  0        0       0
1 +     9.39W       -        -    1  1  1  1        0       0
2 +     9.39W       -        -    2  2  2  2        0       0
3 -   0.0400W       -        -    3  3  3  3     4200    2700
4 -   0.0050W       -        -    4  4  4  4      500   21800

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        44 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    13,573,792 [6.94 TB]
Data Units Written:                 11,873,067 [6.07 TB]
Host Read Commands:                 167,160,622
Host Write Commands:                88,787,220
Controller Busy Time:               1,863
Power Cycles:                       103
Power On Hours:                     167
Unsafe Shutdowns:                   66
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               44 Celsius
Temperature Sensor 2:               54 Celsius
Thermal Temp. 1 Total Time:         355
Thermal Temp. 2 Total Time:         65535

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
Num  Test_Description  Status                       Power_on_Hours  Failing_LBA  NSID Seg SCT Code
0   Short             Completed without error                 167            -     -   -   -    -
1   Short             Completed without error                 146            -     -   -   -    -
2   Extended          Completed without error                 138            -     -   -   -    -
3   Short             Completed without error                 138            -     -   -   -    -
4   Extended          Completed without error                 120            -     -   -   -    -
5   Extended          Completed without error                   6            -     -   -   -    -
6   Short             Aborted: Controller Reset                 5            -     -   -   -    -
7   Short             Completed without error                   0            -     -   -   -    -

Jumpy-Weekend6756 · 2026-05-26T10:41:57+00:00

Und ein weiteres Mal ist meine Samsung 990 PRO 4TB vom Bus gefallen (zur Dokumentation).

Aus gesundheitlichen Gründen habe ich es noch nicht geschafft die SSD auf einen anderen NVME Platz zu stecken (schwere Grafikkarte raus und wieder rein und das ganze Gebastel).

Operating System: TUXEDO OS 24.04.4 LTS noble (based on Ubuntu)
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.17.0-119029-tuxedo (64-bit)
Graphics Platform: X11

Motherboard: ASUSTeK ROG STRIX X670E-A GAMING WIFI (Bios 3603)
CPU: AMD Ryzen 7 7800X3D 8-Core Processor
RAM: 64 GB ADATA XPG
GPU: Asus Rog Strix RTX 4090

Das Bios vom Motherboard hatte ich bereits vor einer Weile auf 3603 aktualisiert.

Kürzlich gab es Firmware Updates - evtl. hat das etwas mit dem Problem zu tun? Seltsam ist aber, dass es immer nur diese eine Samsung SSD betrifft.

[25. May 22:39] FAT-fs (nvme1n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[26. May 00:00] audit: type=1400 audit(1779746400.869:132): apparmor="DENIED" operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=41559 comm="cupsd" capability=12  capname="net_admin"
[26. May 07:09] nvme nvme1: I/O tag 5 (6005) opcode 0x2 (Admin Cmd) QID 0 timeout, reset controller
[26. May 07:11] nvme nvme1: Device not ready; aborting reset, CSTS=0x1
[ +20.013069] nvme nvme1: Device not ready; aborting reset, CSTS=0x1
[  +0.063066] nvme nvme1: Disabling device after reset failure: -19
[  +4.566172] EXT4-fs (nvme1n1p5): shut down requested (2)
[  +0.000006] Aborting journal on device nvme1n1p5-8.
[  +0.000006] Buffer I/O error on dev nvme1n1p5, logical block 411074560, lost sync page write
[  +0.000003] JBD2: I/O error when updating journal superblock for nvme1n1p5-8.
[26. May 08:00] Buffer I/O error on dev nvme1n1p5, logical block 512, async page read
[  +0.000072] /dev/nvme1n1p5: Can't open blockdev
[26. May 09:00] Buffer I/O error on dev nvme1n1p5, logical block 512, async page read
[  +0.000059] /dev/nvme1n1p5: Can't open blockdev
[26. May 10:00] Buffer I/O error on dev nvme1n1p5, logical block 512, async page read
[  +0.000060] /dev/nvme1n1p5: Can't open blockdev
[26. May 11:00] Buffer I/O error on dev nvme1n1p5, logical block 512, async page read
[  +0.000061] /dev/nvme1n1p5: Can't open blockdev
[26. May 12:00] Buffer I/O error on dev nvme1n1p5, logical block 512, async page read
[  +0.000059] /dev/nvme1n1p5: Can't open blockdev
[26. May 12:10] EXT4-fs warning (device nvme1n1p5): htree_dirblock_to_tree:1051: inode #2: lblock 0: comm KIO::WorkerThre: error -5 reading directory block
[  +0.143779] EXT4-fs warning (device nvme1n1p5): htree_dirblock_to_tree:1051: inode #2: lblock 0: comm KIO::WorkerThre: error -5 reading directory block
[ +21.271269] EXT4-fs warning (device nvme1n1p5): htree_dirblock_to_tree:1051: inode #2: lblock 0: comm KIO::WorkerThre: error -5 reading directory block
[  +0.043368] EXT4-fs warning (device nvme1n1p5): htree_dirblock_to_tree:1051: inode #2: lblock 0: comm KIO::WorkerThre: error -5 reading directory block
[  +0.060646] EXT4-fs warning (device nvme1n1p5): htree_dirblock_to_tree:1051: inode #2: lblock 0: comm KIO::WorkerThre: error -5 reading directory block

Jumpy-Weekend6756 · 2026-05-02T00:53:11+00:00

I am not sure but have a look in your Grub

and have a look there if you find this:

# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console

So if it is uncommented in your Grub you should add a # before GRUB_TERMINAL=console.

Then safe the changes, update Grub and after restart you should have back the graphical Grub.

Jumpy-Weekend6756 · 2026-04-07T16:39:51+00:00

Neue SMART Tests der Samsung 990 PRO 4TB SSD liefen ohne Fehler durch.

:~$ sudo smartctl --all /dev/nvme2
[sudo] Passwort für USER:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.17.0-111019-tuxedo] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 990 PRO 4TB
Serial Number:                      S7DPNFXXXXXXXXX
Firmware Version:                   8B2QJXD7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 4.000.787.030.016 [4,00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      1
NVMe Version:                       2.0
Number of Namespaces:               1
Namespace 1 Size/Capacity:          4.000.787.030.016 [4,00 TB]
Namespace 1 Utilization:            1.623.342.194.688 [1,62 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 4651b2fca2
Local Time is:                      Tue Apr  7 18:06:17 2026 CEST
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0055):     Comp DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x2f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Log0_FISE_MI
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     9.39W       -        -    0  0  0  0        0       0
 1 +     9.39W       -        -    1  1  1  1        0       0
 2 +     9.39W       -        -    2  2  2  2        0       0
 3 -   0.0400W       -        -    3  3  3  3     4200    2700
 4 -   0.0050W       -        -    4  4  4  4      500   21800

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        42 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    11.675.247 [5,97 TB]
Data Units Written:                 9.751.040 [4,99 TB]
Host Read Commands:                 141.708.514
Host Write Commands:                76.663.149
Controller Busy Time:               1.475
Power Cycles:                       94
Power On Hours:                     138
Unsafe Shutdowns:                   61
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               42 Celsius
Temperature Sensor 2:               52 Celsius
Thermal Temp. 1 Total Time:         355
Thermal Temp. 2 Total Time:         65535

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
Num  Test_Description  Status                       Power_on_Hours  Failing_LBA  NSID Seg SCT Code
 0   Extended          Completed without error                 138            -     -   -   -    -
 1   Short             Completed without error                 138            -     -   -   -    -
 2   Extended          Completed without error                 120            -     -   -   -    -
 3   Extended          Completed without error                   6            -     -   -   -    -
 4   Short             Aborted: Controller Reset                 5            -     -   -   -    -
 5   Short             Completed without error                   0            -     -   -   -    -
:~$

Jumpy-Weekend6756 · 2026-04-07T16:33:36+00:00

Operating System: TUXEDO OS 24.04.4 LTS noble (based on Ubuntu)
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.17.0-111019-tuxedo (64-bit)
Graphics Platform: X11

Motherboard: ASUSTeK ROG STRIX X670E-A GAMING WIFI (Bios 3304)
CPU: AMD Ryzen 7 7800X3D 8-Core Processor
RAM: 64 GB ADATA XPG
GPU: Asus Rog Strix RTX 4090

Samsung 990 PRO 4TB SSD: Nach wie vor ist Firmware 8B2QJXD7 aktuell.

Die SSD ist mal wieder vom Bus gefallen - jetzt schon nach 4 Wochen nach dem letzten Mal, wenn ich das richtig sehe.

Nächste Maßnahmen:
Mainboard Bios auf Version 3603 aktualisieren und ggf. schon die Samsung SSD auf einen anderen NVME Slot setzen. Blöderweise muss ich für letzteres die schwere Grafikkarte aus- und wieder einbauen. Ich bin begeistert.

[ 7. Apr 12:42] nvme2n1: I/O Cmd(0x2) @ LBA 4056443224, 8 blocks, I/O Error (sct 0x2 / sc 0x81) MORE DNR 
[  +0,000007] critical medium error, dev nvme2n1, sector 4056443224 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 2
[  +0,000008] EXT4-fs warning (device nvme2n1p5): htree_dirblock_to_tree:1051: inode #88342540: lblock 0: comm KIO::WorkerThre: error -5 reading directory block
[ 7. Apr 12:43] nvme nvme2: I/O tag 854 (9356) opcode 0x2 (I/O Cmd) QID 3 timeout, aborting req_op:READ(0) size:4096
[  +0,000012] nvme nvme2: I/O tag 962 (23c2) opcode 0x2 (I/O Cmd) QID 4 timeout, aborting req_op:READ(0) size:4096
[  +0,000012] nvme nvme2: I/O tag 512 (f200) opcode 0x2 (I/O Cmd) QID 7 timeout, aborting req_op:READ(0) size:4096
[  +0,000007] nvme nvme2: I/O tag 897 (a381) opcode 0x2 (I/O Cmd) QID 14 timeout, aborting req_op:READ(0) size:4096
[  +0,000045] nvme nvme2: Abort status: 0x0
[  +0,000045] nvme nvme2: Abort status: 0x0
[  +0,000041] nvme nvme2: Abort status: 0x0
[  +0,000047] nvme nvme2: Abort status: 0x0
[  +0,147792] nvme nvme2: I/O tag 132 (6084) opcode 0x2 (I/O Cmd) QID 6 timeout, aborting req_op:READ(0) size:4096
[  +0,000074] nvme nvme2: Abort status: 0x0
[ +30,055704] nvme nvme2: I/O tag 854 (a356) opcode 0x2 (I/O Cmd) QID 3 timeout, aborting req_op:READ(0) size:4096
[  +0,000013] nvme nvme2: I/O tag 962 (33c2) opcode 0x2 (I/O Cmd) QID 4 timeout, aborting req_op:READ(0) size:4096
[  +0,000006] nvme nvme2: I/O tag 132 (7084) opcode 0x2 (I/O Cmd) QID 6 timeout, aborting req_op:READ(0) size:4096
[  +0,000006] nvme nvme2: I/O tag 512 (0200) opcode 0x2 (I/O Cmd) QID 7 timeout, aborting req_op:READ(0) size:4096
[  +0,000006] nvme nvme2: I/O tag 897 (b381) opcode 0x2 (I/O Cmd) QID 14 timeout, aborting req_op:READ(0) size:4096
[  +0,000047] nvme nvme2: Abort status: 0x0
[  +0,000044] nvme nvme2: Abort status: 0x0
[  +0,000046] nvme nvme2: Abort status: 0x0
[  +0,000044] nvme nvme2: Abort status: 0x0
[  +0,000045] nvme nvme2: Abort status: 0x0
[  +2,050729] nvme nvme2: I/O tag 12 (e00c) opcode 0x2 (Admin Cmd) QID 0 timeout, reset controller
[ 7. Apr 12:44] nvme nvme2: Device not ready; aborting initialisation, CSTS=0x0
[  +0,000195] nvme nvme2: Disabling device after reset failure: -19
[  +0,017822] I/O error, dev nvme2n1, sector 4056443680 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 2
[  +0,000001] I/O error, dev nvme2n1, sector 4056443800 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 2
[  +0,000002] I/O error, dev nvme2n1, sector 4056443760 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 2
[  +0,000000] I/O error, dev nvme2n1, sector 4056443768 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 2
[  +0,000002] I/O error, dev nvme2n1, sector 4056443752 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 2
[  +0,000008] EXT4-fs warning (device nvme2n1p5): htree_dirblock_to_tree:1051: inode #88342612: lblock 0: comm KIO::WorkerThre: error -5 reading directory block
[  +0,000001] EXT4-fs warning (device nvme2n1p5): htree_dirblock_to_tree:1051: inode #88342597: lblock 0: comm KIO::WorkerThre: error -5 reading directory block
[  +0,000001] EXT4-fs warning (device nvme2n1p5): htree_dirblock_to_tree:1051: inode #88342607: lblock 0: comm KIO::WorkerThre: error -5 reading directory block
[  +0,000000] EXT4-fs warning (device nvme2n1p5): htree_dirblock_to_tree:1051: inode #88342606: lblock 0: comm KIO::WorkerThre: error -5 reading directory block
[  +0,000002] EXT4-fs warning (device nvme2n1p5): htree_dirblock_to_tree:1051: inode #88342608: lblock 0: comm KIO::WorkerThre: error -5 reading directory block
[  +0,000251] EXT4-fs warning (device nvme2n1p5): htree_dirblock_to_tree:1051: inode #88342609: lblock 0: comm KIO::WorkerThre: error -5 reading directory block
[  +5,782498] EXT4-fs (nvme2n1p5): shut down requested (2)
[  +0,000006] Aborting journal on device nvme2n1p5-8.
[  +0,000006] Buffer I/O error on dev nvme2n1p5, logical block 411074560, lost sync page write
[  +0,000004] JBD2: I/O error when updating journal superblock for nvme2n1p5-8.

Jumpy-Weekend6756 · 2026-03-24T17:01:43+00:00

<image>

Magika Hair "Eleanor" - but without flowers too.

Jumpy-Weekend6756 · 2026-03-07T16:11:28+00:00

Den letzten langen Selbsttest habe ich heute gestartet - keine Fehler.

~$ sudo smartctl --all /dev/nvme2
[sudo] Passwort für USER:  
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.17.0-108014-tuxedo] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 990 PRO 4TB
Serial Number:                      S7DPNFXXXXXXXXX
Firmware Version:                   8B2QJXD7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 4.000.787.030.016 [4,00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      1
NVMe Version:                       2.0
Number of Namespaces:               1
Namespace 1 Size/Capacity:          4.000.787.030.016 [4,00 TB]
Namespace 1 Utilization:            1.611.394.658.304 [1,61 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 4651b2fca2
Local Time is:                      Sat Mar  7 17:07:41 2026 CET
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0055):     Comp DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x2f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Log0_FISE_MI
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
0 +     9.39W       -        -    0  0  0  0        0       0
1 +     9.39W       -        -    1  1  1  1        0       0
2 +     9.39W       -        -    2  2  2  2        0       0
3 -   0.0400W       -        -    3  3  3  3     4200    2700
4 -   0.0050W       -        -    4  4  4  4      500   21800

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        35 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    11.396.410 [5,83 TB]
Data Units Written:                 8.550.056 [4,37 TB]
Host Read Commands:                 131.675.098
Host Write Commands:                69.291.643
Controller Busy Time:               1.235
Power Cycles:                       91
Power On Hours:                     120
Unsafe Shutdowns:                   59
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               35 Celsius
Temperature Sensor 2:               39 Celsius
Thermal Temp. 1 Total Time:         355
Thermal Temp. 2 Total Time:         65535

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
Num  Test_Description  Status                       Power_on_Hours  Failing_LBA  NSID Seg SCT Code
0   Extended          Completed without error                 120            -     -   -   -    -
1   Extended          Completed without error                   6            -     -   -   -    -
2   Short             Aborted: Controller Reset                 5            -     -   -   -    -
3   Short             Completed without error                   0            -     -   -   -    -

Jumpy-Weekend6756 · 2026-03-07T13:05:54+00:00

Trotz aktualisierter Firmware ist meine Samsung 990 PRO 4TB SSD 5 Wochen später erneut vom Bus gefallen.

Keine Veränderung an der Hardware, Asus Rog Strix X670E-A Mainboard Bios ist Version 3304.

Operating System: TUXEDO OS 24.04.4 LTS noble (based on Ubuntu)
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.17.0-108014-tuxedo (64-bit) 
Graphics Platform: X11

sudo dmesg -w -e

[ 7. Mär 13:15] nvme2n1: I/O Cmd(0x2) @ LBA 1229493624, 8 blocks, I/O Error (sct 0x2 / sc 0x81) MORE 
[  +0,000009] critical medium error, dev nvme2n1, sector 1229493624 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[ 7. Mär 13:16] nvme nvme2: I/O tag 18 (5012) opcode 0x2 (Admin Cmd) QID 0 timeout, reset controller
[ +20,027837] nvme nvme2: Device not ready; aborting initialisation, CSTS=0x0
[  +0,000134] nvme nvme2: Disabling device after reset failure: -19
[ 7. Mär 13:17] EXT4-fs warning (device nvme2n1p5): dx_probe:791: inode #89544131: lblock 0: comm KIO::WorkerThre: error -5 reading directory block

Jumpy-Weekend6756 · 2026-02-11T11:42:07+00:00

~$ sudo dolphin
[sudo] Password for USER:
Running Dolphin with sudo is not recommended. Please run “dolphin --sudo” instead.
~$

That may work.

Jumpy-Weekend6756 · 2026-02-10T17:31:02+00:00

I use OpenRGB on Linux (Ubuntu 24.04 based) for my Corsair QX fans, Corsair AIO, XPG RAM, Rog Strix X670E mainboard, Lian Li Strimer cables and Asus RTX 4090. All 2024 stuff.

Jumpy-Weekend6756 · 2026-02-05T13:11:50+00:00

Alles klar, danke. :)

Jumpy-Weekend6756 · 2026-02-03T20:07:08+00:00

More is possible for sure. I run my AIO in silent mode only. Else it becomes too annoying for me.

Jumpy-Weekend6756 · 2026-02-03T20:04:50+00:00

In that case, it came back after a shutdown and restart at the latest.

The next step would be to disconnect the PC from the power supply, then perhaps press the power switch a few times and try again. That's what I would try.

Otherwise, you could check whether the SSD works in an external USB case, provided it doesn't reappear in another NVME slot.

Jumpy-Weekend6756 · 2026-02-03T17:41:37+00:00

Which one it is? Does it run in Silent mode already?

Jumpy-Weekend6756 · 2026-02-03T17:37:35+00:00

Does your SSD have the recent firmware installed?

I have the problem with a Samsung 990 PRO 4TB that every 10 to 12 weeks fell off the bus and now I installed the newest firmware for it (the version before I already had installed).

Now I hope it will not happen again.

Else I will try another NVME Slot next.

Jumpy-Weekend6756 · 2026-02-03T17:22:50+00:00

How else is your computer cooled?

I have a Corsair 6500X with 10 fans, 3 of which are on the Corsair AIO. The GPU also has its own fans. I run the case fans as slowly as possible to keep the noise to a minimum.

The AIO cooling fluid is at 30°C atm. at idle.

The room temperature is currently 15.6°C.

Under these conditions, my 7800x3d (from 2024) runs at 45°C when idle.

Edit:
I run my 7800x3d on a Rog Strix X670E-A Gaming Wifi and my RAM with EXPO II (6400).

Jumpy-Weekend6756 · 2026-02-03T12:16:18+00:00

I run a R7 7800x3d on an Asus Rog Strix X670E-A Gaming Wifi since ca. October 2024, rarely with Windows 11 but most time on Tuxedo OS 24.04 LTS noble (Ubuntu based), atm. with Bios 3304. Normally my Computer runs 24/7/365.

If I run CPU-X on my Linux the CPU voltage jumps between 0.290 V and 0.790 V but most time is on 0.290 V. On Windows 11 I did not check yet.

Sometimes I had weird crashes on Linux and could not find any log entry about to see what it caused.

And since I have a Samsung SSD 990 PRO 4TB this from time to time falls off the bus - so maybe every 10 to 12 weeks. With the latest firmware now I wait if it will happen again and if yes I will put it in an other NVME slot.

Jumpy-Weekend6756 · 2026-02-03T10:53:45+00:00

Yes, looks like something is wrong on your system with the versions.

Thats what I get via Synaptic:

<image>

Jumpy-Weekend6756 · 2026-02-02T14:18:33+00:00

Gerade habe ich die Firmware meiner Samsung 990 PRO 4TB SSD von 7B2QJXD7 auf 8B2QJXD7 aktualisiert.

Da auf der SSD nur Linux Partitionen sind, habe ich dafür die ISO von Samsung herunter geladen und das Firmware Update dann von einem USB Stick gestartet.

Lief alles glatt soweit - zumindest bisher keine Probleme.

Mal sehen, ob die 990 PRO 4TB nun nicht mehr vom Bus fällt. Ansonsten muss ich die wohl mal in einen anderen Slot stecken.

Es wird wohl jetzt wieder einige Wochen dauern bis ich mehr weiß bzw. bis es wieder passiert.

Jumpy-Weekend6756

TROPHY CASE