SMART status for /dev/nvme0 is failing

Issues & Assistance
1

Hey all,

Since garuda-update this morning i have this error

-– System Health Check Report —21/21 checks run in 0.49 seconds ⌛Powered by garuda-health 🦅

— CRITICAL —

  • SMART status for /dev/nvme0 is failing

Here’s my inxi

System:
Kernel: 6.16.0-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=757bd212-d869-4ca0-9f38-27a158278ff7 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.4.4 tk: Qt v: N/A info: frameworks v: 6.17.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Convertible System: LENOVO product: 83DL v: Yoga 7 2-in-1 16IML9
serial: <filter> Chassis: type: 31 v: Yoga 7 2-in-1 16IML9 serial: <filter>
Mobo: LENOVO model: LNVNB161216 v: SDK0T76463 WIN serial: <filter>
part-nu: LENOVO_MT_83DL_BU_idea_FM_Yoga 7 2-in-1 16IML9
uuid: 20240207-6045-2e70-d078-60452e70d07c UEFI: LENOVO v: NWCN19WW
date: 12/30/2024
Battery:
ID-1: BAT0 charge: 72.9 Wh (100.0%) condition: 72.9/71.0 Wh (102.7%)
volts: 16.6 min: 15.4 model: SMP L22M4PA1 type: Li-poly serial: <filter>
status: full cycles: 8
CPU:
Info: model: Intel Core Ultra 7 155U socket: U3E1 bits: 64 type: MCP
arch: Meteor Lake level: v3 note: check built: 2023+ process: Intel 4 (7nm)
family: 6 model-id: 0xAA (170) stepping: 4 microcode: 0x25
Topology: cpus: 1x dies: 1 clusters: 5 cores: 12 smt: <unsupported> cache:
L1: 1.2 MiB desc: d-10x32 KiB, 2x48 KiB; i-12x64 KiB L2: 10 MiB
desc: 5x2 MiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 400 min/max: 400/4800:3800:2100 base/boost: 4059/4800
scaling: driver: intel_pstate governor: powersave volts: 0.9 V
ext-clock: 100 MHz cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400
8: 400 9: 400 10: 400 11: 400 12: 400 bogomips: 64512
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Meteor Lake-P [Intel Graphics] vendor: Lenovo driver: i915
v: kernel alternate: xe arch: Xe-LPG process: Intel 4 (7nm+) built: 2023+
ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:7d45 class-ID: 0300
Device-2: Luxvisions Innotech Integrated RGB Camera driver: uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-9:4
chip-ID: 30c9:00c2 class-ID: fe01 serial: <filter>
Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: BOE Display 0x0a31 built: 2021 res:
mode: 1920x1200 hz: 60 scale: 100% (1) dpi: 141 gamma: 1.2
size: 345x215mm (13.58x8.46") diag: 407mm (16") ratio: 16:10
modes: 1920x1200
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
drv: iris x11: drv: iris
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.1.7-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (MTL)
device-ID: 8086:7d45 memory: 14.7 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.4.321 layers: 5 device: 0 type: integrated-gpu
name: Intel Graphics (MTL) driver: mesa intel v: 25.1.7-arch1.1
device-ID: 8086:7d45 surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 20.1.8 256 bits) driver: mesa llvmpipe v: 25.1.7-arch1.1 (LLVM
20.1.8) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Meteor Lake-P HD Audio vendor: Lenovo
driver: sof-audio-pci-intel-mtl
alternate: snd_hda_intel,snd_sof_pci_intel_mtl bus-ID: 00:1f.3
chip-ID: 8086:7e28 class-ID: 0401
API: ALSA v: k6.16.0-zen2-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.4.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Meteor Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:7e40 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:5 chip-ID: 8087:0033
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: N/A
Drives:
Local Storage: total: 953.87 GiB used: 206.58 GiB (21.7%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix model: HFS001TEJ4X112N
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 51040C31 temp: 36.9 C
scheme: GPT
SMART: yes health: PASSED on: 152d 13h cycles: 674
read-units: 16,024,436 [8.20 TB] written-units: 28,413,225 [14.5 TB]
Partition:
ID-1: / raw-size: 195.31 GiB size: 195.31 GiB (100.00%)
used: 153.15 GiB (78.4%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6
maj-min: 259:6
ID-2: /boot/efi raw-size: 1000 MiB size: 998 MiB (99.80%)
used: 332 KiB (0.0%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p5
maj-min: 259:5
ID-3: /home raw-size: 195.31 GiB size: 195.31 GiB (100.00%)
used: 153.15 GiB (78.4%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6
maj-min: 259:6
ID-4: /var/log raw-size: 195.31 GiB size: 195.31 GiB (100.00%)
used: 153.15 GiB (78.4%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6
maj-min: 259:6
ID-5: /var/tmp raw-size: 195.31 GiB size: 195.31 GiB (100.00%)
used: 153.15 GiB (78.4%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6
maj-min: 259:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.05 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
Src: /sys System Temperatures: cpu: 42.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB note: est. available: 15.05 GiB used: 3.19 GiB (21.2%)
Processes: 343 Power: uptime: 15m states: freeze,mem,disk suspend: s2idle
wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
image: 5.99 GiB services: org_kde_powerdevil, power-profiles-daemon,
upowerd Init: systemd v: 257 default: graphical tool: systemctl
Packages: pm: pacman pkgs: 1419 libs: 371 tools: octopi,paru Compilers:
gcc: 15.2.1 Shell: Bash v: 5.3.3 running-in: konsole inxi: 3.3.38
Garuda (2.7.5-1):
System install date:     2024-06-24
Last full system update: 2025-08-16
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Yes
Failed units:

That’s what i did

[root@jacques-83dl jacques]# smartctl -a /dev/nvme0
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.16.0-zen2-1-zen] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       SKHynix_HFS001TEJ4X112N
Serial Number:                      4YCCN03181430CR5O
Firmware Version:                   51040C31
PCI Vendor/Subsystem ID:            0x1c5c
IEEE OUI Identifier:                0xace42e
Controller ID:                      1
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1’024’209’543’168 [1.02 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            ace42e 003b248a8c
Local Time is:                      Sat Aug 16 07:38:28 2025 CEST
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x1e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size:         64 Pages
Warning  Comp. Temp. Threshold:     86 Celsius
Critical Comp. Temp. Threshold:     87 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
0 +   4.5000W       -        -    0  0  0  0      100     100
1 +   3.0000W       -        -    1  1  1  1      200     200
2 +   0.6000W       -        -    2  2  2  2      400     400
3 -   0.0150W       -        -    3  3  3  3     2000    2000
4 -   0.0030W       -        -    4  4  4  4     5000   10000

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, NSID 0xffffffff)
Critical Warning:                   0x00
Temperature:                        35 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    16’024’321 [8.20 TB]
Data Units Written:                 28’412’493 [14.5 TB]
Host Read Commands:                 162’347’286
Host Write Commands:                585’848’549
Controller Busy Time:               11’736
Power Cycles:                       674
Power On Hours:                     3’661
Unsafe Shutdowns:                   34
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               37 Celsius
Temperature Sensor 2:               35 Celsius

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

Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
No Self-tests Logged

But i dont know what to do…

Any idea ?

2

I think tne is working on a solution.

4 Likes
3

It’s possible that borderline stats might be interpreted by smartmon as pre-failure indications. I wouldn’t get overly concerned until someone familiar with all the smartmon readouts tells you that you truly have something to be concerned about.

1 Like
4

Here it is

[root@jacques-83dl jacques]#  smartctl -H /dev/sdb
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.16.0-zen2-1-zen] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

Smartctl open device: /dev/sdb failed: No such device
[root@jacques-83dl jacques]#

[root@jacques-83dl jacques]# fdisk -l
Disque /dev/nvme0n1 : 953.87 GiB, 1024209543168 octets, 2000409264 secteurs
Modèle de disque : SKHynix_HFS001TEJ4X112N
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Type d'étiquette de disque : gpt
Identifiant de disque : 2B0373AE-D366-4622-B291-E8F1693DAF95

Périphérique        Début        Fin  Secteurs Taille Type
/dev/nvme0n1p1       2048     534527    532480   260M Système EFI
/dev/nvme0n1p2     534528     567295     32768    16M Réservé Microsoft
/dev/nvme0n1p3     567296  587317247 586749952 279.8G Données de base Microsoft
/dev/nvme0n1p4 1996312576 2000408575   4096000     2G Environnement de récupération Windows
/dev/nvme0n1p5  587317248  589365247   2048000  1000M Données de base Microsoft
/dev/nvme0n1p6  589365248  998965247 409600000 195.3G Système de fichiers Linux
/dev/nvme0n1p7  998965248 1996312575 997347328 475.6G Système de fichiers Linux

Les entrées de la table de partitions ne sont pas dans l'ordre du disque.


Disque /dev/zram0 : 15.05 GiB, 16157507584 octets, 3944704 secteurs
Unités : secteur de 1 × 4096 = 4096 octets
Taille de secteur (logique / physique) : 4096 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
[root@jacques-83dl jacques]#
5

Same mistake here this morning too…

smartctl -H :
SMART overall-health self-assessment test result: PASSED :man_shrugging:

6

Sorry, wrong command :innocent:

if sudo smartctl -H /dev/nvme0

Checking Basic SMART Attributes

sudo smartctl -a /dev/nvme0 # Replace “nvme0” with your NVMe device

OR (if smartctl fails):

nvme smart-log /dev/nvme0 (nvme-cli must be installed to use this command)

Performing Tests on NVMe

Long Test:

sudo smartctl -t long /dev/nvme0

Short Test:

sudo smartctl -t short /dev/nvme0

Viewing NVMe Test Results

sudo smartctl -l selftest /dev/nvme0

nvme self-test-log /dev/nvme0 # Alternative (if nvme-cli is installed)

7

Mistake ?
Passed = ?
passed mean = :+1: or :clap: or ?

8

I just got a CRITICAL smart failure message also this morning after updating.

However, when I loaded up KDE Partition Manager to look at the disk and opened the smart status page its all good’s theres no critical messages. Is this a spurious error message?

Its a HDD not a SSD.

╰─λ sudo smartctl -H /dev/sdb
[sudo] password for pauls:
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.15.9-zen1-1.1-zen] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

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

wizzard8,
Pls open a topic for this, post current garuda-inxi + smart error.log

10

sure, where do I find/generate the smart error log?

11

That tells you..all is fine
my result

🕙 12:21:52
╰─λ sudo smartctl -H /dev/sda
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.16.0-zen2-1-zen] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

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

Where you read this…and post this in your topic

13

Hey, you all asking about the smart message from garuda-health should read every post in this thread…

I got a CRITICAL smart error message after updating
14

Thanks for the report. This is a different issue (caused by the fix to the first) that has now been fixed.

4 Likes
15

No, I wanted to join the FenDanT thread, it was just a report. Anyway, yes, it’s not really an error, but a report.
I assume Passed means it didn’t return errors after smartctl.
I’m closing the intrusion and apologize :sweat_smile:

16

Sorry, that was on my laptop at work…

I have to wait until monday morning to answer to your questions :grinning_face:

17

Hey again,

Back to work…

After garuda-update, no more message in Konsole…

Do you need some commands ?

18

No, the issue has been fixed.

2 Likes
19

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.