I’m still struggling with my computer freezing. I want to run a diagnostic test on my SSD. When I go to Gnome Disk Manager. The SMART Data and Self Tests option is grayed out. Any thoughts on what I need to do to check my drive?
You can try running sudo smartctl -a /dev/nvme0n1 to check the status.
This might be interesting read, Disk "SMART Data" no more accessible since installation of kernel 6.10.3 - #25 by catanzaro - Fedora Discussion
As a side note, have you recently changed GNOME Icons theme?
if that is a yes, please try the following gtk-update-icon-cache -q ~/.local/share/icons/[ADD_THEME_NAME] for all theme folders
e.g.,
gtk-update-icon-cache -q ~/.local/share/icons/Papirus
gtk-update-icon-cache -q ~/.local/share/icons/Papirus-Dark
gtk-update-icon-cache -q ~/.local/share/icons/Papirus-Light
...After reading the original thread, you can try also enabling magic SysRq. Please keep in mind that Fedora disables the magic SysRq key by default for security reasons.
sudo sysctl kernel.sysrq=500
Once enabled, you can use the “Reboot Even If System Utterly Broken” (REISUB) sequence by pressing Alt + SysRq + r , Alt + SysRq + e , Alt + SysRq + i , Alt + SysRq + s , Alt + SysRq + u , and finally Alt + SysRq + b to perform the actions in sequence.
to make it permanent:
echo kernel.sysrq=500 | sudo tee --append /etc/sysctl.d/99-sysctl.conf
SysRq 500 = no logs and keyboard input, for security reasons
SysRq codes
2 = 0x2 - enable control of console logging level
4 = 0x4 - enable control of keyboard (SAK, unraw)
8 = 0x8 - enable debugging dumps of processes etc.
16 = 0x10 - enable sync command
32 = 0x20 - enable remount read-only
64 = 0x40 - enable signalling of processes (term, kill, oom-kill)
128 = 0x80 - allow reboot/poweroff
256 = 0x100 - allow nicing of all RT tasks
4+16+32+64+128+256 = 500
RESISUB
- R: Switch the keyboard from raw mode to XLATE mode
- E: Send the SIGTERM signal to all processes except init, allowing them to terminate gracefully
- I: Send the SIGKILL signal to all processes except init, forcing them to terminate immediately
- S: Sync all mounted filesystems and flush data to disk
- U: Unmount and Remount all mounted filesystems in read-only mode
- B: Immediately reboot the system
For more information - Linux Magic System Request Key Hacks — The Linux Kernel documentation
Note: the SysRq key may be disabled if the system is in a state where it cannot process keyboard input, e.g., kernel panic
Thanks, that did the trick. I don’t see that the SSD is the issue:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.11.8-300.fc41.x86_64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF INFORMATION SECTION ===
Model Number: SAMSUNG MZVLB256HAHQ-000L7
Serial Number: S41GNX2M328756
Firmware Version: 1L2QEXD7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 256,060,514,304 [256 GB]
Unallocated NVM Capacity: 0
Controller ID: 4
NVMe Version: 1.2
Number of Namespaces: 1
Namespace 1 Size/Capacity: 256,060,514,304 [256 GB]
Namespace 1 Utilization: 23,968,468,992 [23.9 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 8391bd3c65
Local Time is: Fri Jan 17 11:03:11 2025 EST
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Log Page Attributes (0x03): S/H_per_NS Cmd_Eff_Lg
Maximum Data Transfer Size: 512 Pages
Warning Comp. Temp. Threshold: 81 Celsius
Critical Comp. Temp. Threshold: 82 CelsiusSupported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 7.02W - - 0 0 0 0 0 0
1 + 6.30W - - 1 1 1 1 0 0
2 + 3.50W - - 2 2 2 2 0 0
3 - 0.0760W - - 3 3 3 3 210 1200
4 - 0.0050W - - 4 4 4 4 2000 8000Supported 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: PASSEDSMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 37 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 6%
Data Units Read: 50,612,115 [25.9 TB]
Data Units Written: 53,570,396 [27.4 TB]
Host Read Commands: 730,874,471
Host Write Commands: 1,631,661,180
Controller Busy Time: 3,894
Power Cycles: 146
Power On Hours: 11,139
Unsafe Shutdowns: 65
Media and Data Integrity Errors: 0
Error Information Log Entries: 579
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 37 Celsius
Temperature Sensor 2: 40 CelsiusError Information (NVMe Log 0x01, 16 of 64 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message
0 579 0 0x100e 0x4004 - 0 0 - Invalid Field in CommandSelf-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged
Why would I want to use REISUB, when I can shut down by pushing the power button and then reboot? I was hoping to be able to kill each program to see if it unfreezes the computer.
If the system is somewhat responsive, single press of the power button should initiate standard shutdown process, if configured to do so (default is to suspend the computer).
Holding down the power button will force the system to shut down immediately, without allowing processes to terminate cleanly or syncing file systems. This can lead to data corruption or loss, especially if the system was in the middle of writing data to disk.
Here are few things to consider about Data Integrity and System Stability:
-
REISUB attempts to ensure that data is handled cleanly before rebooting, reducing the risk of corruption
-
REISUB allows the system to shut down and restart more gracefully, which can help prevent issues that might arise from a forced shutdown
In the end it’s up to you what you are going to use. Now you have the option to take informed decision.
1 Like