Desktop files are missing

PopeRigby · 2023-01-09 18:04:52

I was getting a bunch of SSL errors (Steam couldn't connect), and couldn't update (Every category reported 'failed' when running 'pacman -Syyu'), and I saw that it was looking for '/etc/ssl/certs/ca-certificates.crt'. I checked that file, and it was a broken symlink to '/etc/ca-certificates/extracted/ca-bundle.trust.crt'. I deleted the broken symlink, and reinstalled 'ca-certificates-utils'. The symlink seemed to have been fixed, and I was able to update. But, when I rebooted, all of my applications were missing from KDE Plasma's application launcher, and the icons for my open applications aren't in the task bar.

This is the output of 'sudo journalctl -p 3 -xb':

Jan 08 19:27:37 snowy systemd-udevd[496]: event17: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
Jan 08 19:27:38 snowy bluetoothd[690]: src/plugin.c:plugin_init() Failed to init vcp plugin
Jan 08 19:27:38 snowy bluetoothd[690]: src/plugin.c:plugin_init() Failed to init mcp plugin
Jan 08 19:27:38 snowy bluetoothd[690]: src/plugin.c:plugin_init() Failed to init bap plugin
Jan 08 19:27:39 snowy systemd[798]: Failed to start Update XDG user dir configuration.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 28 and the job result is failed.
Jan 08 19:27:45 snowy systemd[877]: Failed to start Update XDG user dir configuration.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 30 and the job result is failed.
Jan 08 19:27:48 snowy bluetoothd[690]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
Jan 08 19:27:59 snowy bluetoothd[690]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Jan 08 19:30:32 snowy login[2698]: PAM unable to dlopen(/usr/lib/security/pam_gnome_keyring.so): /usr/lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory
Jan 08 19:30:32 snowy login[2698]: PAM adding faulty module: /usr/lib/security/pam_gnome_keyring.so
Jan 08 19:30:41 snowy bluetoothd[690]: sdp_extract_attr: Unknown data descriptor : 0x1 terminating
Jan 08 19:30:43 snowy bluetoothd[690]: sdp_extract_attr: Unknown data descriptor : 0x1 terminating
Jan 08 19:30:46 snowy bluetoothd[690]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Jan 08 19:32:43 snowy systemd-networkd-wait-online[2888]: Timeout occurred while waiting for network connectivity.
Jan 08 19:32:43 snowy systemd[1]: Failed to start Wait for Network to be Configured.
░░ Subject: A start job for unit systemd-networkd-wait-online.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-networkd-wait-online.service has finished with a failure.
░░ 
░░ The job identifier is 2751 and the job result is failed.
Jan 08 19:33:41 snowy systemsettings[3509]: Failed to find desktop file for "systemsettings"
Jan 08 19:33:41 snowy systemsettings[3509]: Failed to find desktop file for "systemsettings"
Jan 08 19:34:47 snowy systemsettings[3640]: Failed to find desktop file for "systemsettings"

My applications are all still there, because they can be opened indirectly (Firefox autostarted, I could open my text editor by trying to open a text file from Firefox's downloads menu, etc.), and their binaries and desktop files are still in the correct spot on the filesystem, but they don't show up in the launcher.

V1del · 2023-01-09 19:58:19

Post your pacman log covering a successful transaction and the full output of

pacman -Qkk > /dev/null

If this happened randomly out of the blue you might be looking at disk failures, any error in dmesg? Check/post

smartctl -a /dev/sdX #replace with your actual device

from the smartmontools package?

Last edited by V1del (2023-01-09 20:00:09)

PopeRigby · 2023-01-10 22:30:40

Thank you, and sorry for the delayed response.

Pacman log from successful transaction: https://gist.github.com/poperigby/49568 … 2b1405635c
Output of 'pacman -Qkk': https://gist.github.com/poperigby/60ed2 … 9f3f8fbe6c

I don't think it's a disk failure. I ran both a long and short test with 'smartctl' and it reported no issues. I also ran a BTRFS check on the device, and it's a brand new NVME drive.

V1del · 2023-01-11 00:36:07

Any funky snapshot setup that might interfere here? How do your mounts look? There's a bunch of files missing, reinstall all the packages from that output that mentioned they miss certain files.

When things mounted like you think they should what do you get from

findmnt
smartctl -a /dev/nvme0n1 #You can lose at the silicon lottery, if smartctl ran the test you only know the test succeeded, actually look at/post the values

On the off chance this is actually an issue outside of the system, which mirrors are you using? Make sure you use known good and actively syncing mirrors, check for low score and high completion values in: https://archlinux.org/mirrors/status/#successful

Last edited by V1del (2023-01-11 00:38:07)

PopeRigby · 2023-01-11 02:02:17

V1del wrote:

Any funky snapshot setup that might interfere here?

I don't think so. I don't even have snapper running currently.

How do your mounts look?

Like this:

/                                      /dev/nvme0n1p3[/@]
                                                      btrfs       rw,noatime,compress-force=zstd:3,ssd,space_cache,subvolid=1492,subvol=/@
├─/proc                                proc           proc        rw,nosuid,nodev,noexec,relatime
│ └─/proc/sys/fs/binfmt_misc           systemd-1      autofs      rw,relatime,fd=33,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=17069
│   └─/proc/sys/fs/binfmt_misc         binfmt_misc    binfmt_misc rw,nosuid,nodev,noexec,relatime
├─/sys                                 sysfs          sysfs       rw,nosuid,nodev,noexec,relatime
│ ├─/sys/kernel/security               securityfs     securityfs  rw,nosuid,nodev,noexec,relatime
│ ├─/sys/fs/cgroup                     cgroup2        cgroup2     rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot
│ │ └─/sys/fs/cgroup/net_cls           net_cls        cgroup      rw,relatime,net_cls
│ ├─/sys/fs/pstore                     pstore         pstore      rw,nosuid,nodev,noexec,relatime
│ ├─/sys/firmware/efi/efivars          efivarfs       efivarfs    rw,nosuid,nodev,noexec,relatime
│ ├─/sys/fs/bpf                        bpf            bpf         rw,nosuid,nodev,noexec,relatime,mode=700
│ ├─/sys/kernel/debug                  debugfs        debugfs     rw,nosuid,nodev,noexec,relatime
│ ├─/sys/kernel/tracing                tracefs        tracefs     rw,nosuid,nodev,noexec,relatime
│ ├─/sys/fs/fuse/connections           fusectl        fusectl     rw,nosuid,nodev,noexec,relatime
│ └─/sys/kernel/config                 configfs       configfs    rw,nosuid,nodev,noexec,relatime
├─/dev                                 devtmpfs       devtmpfs    rw,nosuid,size=4096k,nr_inodes=2033559,mode=755,inode64
│ ├─/dev/shm                           tmpfs          tmpfs       rw,nosuid,nodev,inode64
│ ├─/dev/pts                           devpts         devpts      rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
│ ├─/dev/hugepages                     hugetlbfs      hugetlbfs   rw,relatime,pagesize=2M
│ └─/dev/mqueue                        mqueue         mqueue      rw,nosuid,nodev,noexec,relatime
├─/run                                 tmpfs          tmpfs       rw,nosuid,nodev,size=3257260k,nr_inodes=819200,mode=755,inode64
│ ├─/run/credentials/systemd-sysctl.service
│ │                                    ramfs          ramfs       ro,nosuid,nodev,noexec,relatime,mode=700
│ ├─/run/credentials/systemd-sysusers.service
│ │                                    ramfs          ramfs       ro,nosuid,nodev,noexec,relatime,mode=700
│ ├─/run/credentials/systemd-tmpfiles-setup-dev.service
│ │                                    ramfs          ramfs       ro,nosuid,nodev,noexec,relatime,mode=700
│ ├─/run/credentials/systemd-tmpfiles-setup.service
│ │                                    ramfs          ramfs       ro,nosuid,nodev,noexec,relatime,mode=700
│ └─/run/user/1000                     tmpfs          tmpfs       rw,nosuid,nodev,relatime,size=1628628k,nr_inodes=407157,mode=700,uid=1000,gid=1000,inode64
│   └─/run/user/1000/doc               portal         fuse.portal rw,nosuid,nodev,relatime,user_id=1000,group_id=1000
├─/tmp                                 tmpfs          tmpfs       rw,nosuid,nodev,size=8143148k,nr_inodes=1048576,inode64
├─/.snapshots                          /dev/nvme0n1p3[/@snapshots]
│                                                     btrfs       rw,noatime,compress-force=zstd:3,ssd,space_cache,subvolid=1525,subvol=/@snapshots
├─/home                                /dev/nvme0n1p3[/@home]
│                                                     btrfs       rw,noatime,compress-force=zstd:3,ssd,space_cache,subvolid=1523,subvol=/@home
├─/var/log                             /dev/nvme0n1p3[/@var_log]
│                                                     btrfs       rw,noatime,compress-force=zstd:3,ssd,space_cache,subvolid=1527,subvol=/@var_log
├─/boot                                /dev/nvme0n1p1 vfat        rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
└─/media/hdd

There's a bunch of files missing, reinstall all the packages from that output that mentioned they miss certain files.

Okay, I'll give that a shot.

smartctl -a /dev/nvme0n1 #You can lose at the silicon lottery, if smartctl ran the test you only know the test succeeded, actually look at/post the values

Here's the output of 'sudo smartctl -t long /dev/nvme0n1 && sudo smartctl -a /dev/nvme0n1'.:

smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.4-arch1-1] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 980 PRO 2TB
Serial Number:                      S6B0NL0TB03653M
Firmware Version:                   5B2QGXA7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 2,000,398,934,016 [2.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      6
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          2,000,398,934,016 [2.00 TB]
Namespace 1 Utilization:            1,125,152,804,864 [1.12 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 bb21a05728
Local Time is:                      Tue Jan 10 17:55:35 2023 PST
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         128 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 +     8.49W       -        -    0  0  0  0        0       0
 1 +     4.48W       -        -    1  1  1  1        0     200
 2 +     3.18W       -        -    2  2  2  2        0    1000
 3 -   0.0400W       -        -    3  3  3  3     2000    1200
 4 -   0.0050W       -        -    4  4  4  4      500    9500

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:                        40 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    5,582,980 [2.85 TB]
Data Units Written:                 3,977,436 [2.03 TB]
Host Read Commands:                 23,684,163
Host Write Commands:                27,244,126
Controller Busy Time:               128
Power Cycles:                       15
Power On Hours:                     18
Unsafe Shutdowns:                   4
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               40 Celsius
Temperature Sensor 2:               47 Celsius

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

Surprisingly, the test finishes instantly. I'm not sure if that's good or bad.

On the off chance this is actually an issue outside of the system, which mirrors are you using? Make sure you use known good and actively syncing mirrors, check for low score and high completion values in: https://archlinux.org/mirrors/status/#successful

Here's my `/etc/pacman.d/mirrorlist`:

################################################################################
################# Arch Linux mirrorlist generated by Reflector #################
################################################################################

# With:       reflector --country US --age 12 --protocol https --sort rate --save /etc/pacman.d/mirrorlist
# When:       2023-01-09 03:46:54 UTC
# From:       https://archlinux.org/mirrors/status/json/
# Retrieved:  2023-01-09 03:46:14 UTC
# Last Check: 2023-01-09 03:41:31 UTC

Server = https://ziply.mm.fcix.net/archlinux/$repo/os/$arch
Server = https://codingflyboy.mm.fcix.net/archlinux/$repo/os/$arch
Server = https://archmirror1.octyl.net/$repo/os/$arch
Server = https://mirrors.xtom.com/archlinux/$repo/os/$arch
Server = https://irltoolkit.mm.fcix.net/archlinux/$repo/os/$arch
Server = https://ord.mirror.rackspace.com/archlinux/$repo/os/$arch
Server = https://arch.mirror.ivo.st/$repo/os/$arch
Server = https://plug-mirror.rcac.purdue.edu/archlinux/$repo/os/$arch
Server = https://mirror.ette.biz/archlinux/$repo/os/$arch
Server = https://coresite.mm.fcix.net/archlinux/$repo/os/$arch
Server = https://mirrors.mit.edu/archlinux/$repo/os/$arch
Server = https://forksystems.mm.fcix.net/archlinux/$repo/os/$arch
Server = https://mirror.arizona.edu/archlinux/$repo/os/$arch
Server = https://arch.mirror.constant.com/$repo/os/$arch
Server = https://mirror.clarkson.edu/archlinux/$repo/os/$arch
Server = https://mirror.pit.teraswitch.com/archlinux/$repo/os/$arch
Server = https://iad.mirrors.misaka.one/archlinux/$repo/os/$arch
Server = https://mirrors.vectair.net/archlinux/$repo/os/$arch
Server = https://dfw.mirror.rackspace.com/archlinux/$repo/os/$arch
Server = https://iad.mirror.rackspace.com/archlinux/$repo/os/$arch
Server = https://repo.ialab.dsu.edu/archlinux/$repo/os/$arch
Server = https://mirror.tmmworkshop.com/archlinux/$repo/os/$arch
Server = https://mirrors.bloomu.edu/archlinux/$repo/os/$arch

Faulty mirrors was the first thing I thought of, so I ran `reflector --country US --age 12 --protocol https --sort rate --save /etc/pacman.d/mirrorlist` soon after it happened, as you can see.

I also see that my top mirror is on the successfully syncing mirrors list, so I don't think that's the issue.

V1del · 2023-01-11 08:53:03

SMART tests on nvme devices will generally be quick yes (... afaik most will basically keep a record of everything that's relevant SMART wise pretty much immediately) and this does look good. One general suggestion Samsung SSDs are somewhat notorious for power-saving issues, do you see anything/do you have a journal entry from the time where the issue appeared that points to SSD issues and/or filesystem problems? https://wiki.archlinux.org/title/System … ing_output

If the remaining issue is really just about the plasma launcher running

kbuildsycoca5 --noincremental

should rebuild the cache for that.

If that doesn't help post a journal of the current boot

sudo journalctl -b

PopeRigby · 2023-01-11 18:20:53

I reinstalled those packages like you said, and it's fixed now. So, thank you! Now to get to the root of the problem.

V1del wrote:

do you see anything/do you have a journal entry from the time where the issue appeared that points to SSD issues and/or filesystem problems?

I don't think so. I ran `sudo journalctl --since "2023-01-08" -p3`(the 8th is when it originally happened) and I don't see anything about SSD's or power-saving.

seth · 2023-01-11 18:35:35

-p3

Don't.
You're also lookig for messages from the filesystem.

I rebooted, all of my applications were missing from KDE Plasma's application launcher

Are you also using SDDM and do you occasionally have slow/stalled reboots/shutdowns and then push the power button?

PopeRigby · 2023-01-11 18:55:09

seth wrote:

-p3
Don't.
You're also lookig for messages from the filesystem.

Ah, what priority should I use then? It's hard to find anything with all the info messages.

Are you also using SDDM and do you occasionally have slow/stalled reboots/shutdowns and then push the power button?

Yes! Oh no, has that been causing issues? I installed sddm-git and that seems to have fixed the delayed shutdowns, but I was doing that fairly often before.

Last edited by PopeRigby (2023-01-11 18:56:59)

seth · 2023-01-11 19:01:49

Yes! Oh no, has that been causing issues?

Yes, the filesystem doesn't necessarily get synced.
I bet your right arm that this is the cause for your previous symptoms - your left arm on top if they now ceased.

Ah, what priority should I use then?

No priority filter.

It's hard to find anything with all the info messages.

Not if you're using an excellent, if not the best, text editor in the world (tribute) that allows to quickly filter large bodies of text for random strings, searching (the filtered part) and also provides syntax highlighting for the systemd journal.

PopeRigby · 2023-01-11 19:21:51

seth wrote:

Yes, the filesystem doesn't necessarily get synced.
I bet your right arm that this is the cause for your previous symptoms - your left arm on top if they now ceased.

Why would this just now come to a head though? It seems weird. I haven't hard rebooted for a bit.

I've searched through the systemd journal for "power", "ssd", and "samsung." I can't find anything particularly interesting.

seth · 2023-01-11 19:26:56

Because the messages would be more from like "btrfs" or include IO or I/O … post the journal for the relevant timeframe (unfiltered - and no "-x"!!)
If you had files on your hard disk and did a clean shutdown/reboot and they were gone afterwards, that's not because of some forced reboots you did a year ago.
What happens is you "write" the files, but they're not actually written to the disk and then you reboot w/ a hammer and that prevents the files from ever getting actually written and then they're lost.

PopeRigby · 2023-01-11 20:12:49

I believe this is the correct time frame: https://gist.github.com/poperigby/883a7 … 93a54af549

So you think it's not because of the hard shutdown?

Last edited by PopeRigby (2023-01-11 20:13:29)

seth · 2023-01-11 21:57:22

The journal covers only one hour and this

Jan 08 19:11:17 snowy systemd[1]: btrfs-scrub@-.timer: Deactivated successfully.
Jan 08 19:11:17 snowy systemd[1]: Stopped Monthly Btrfs scrub on /.
Jan 08 19:11:17 snowy systemd[1]: btrfs-scrub@home.timer: Deactivated successfully.
Jan 08 19:11:17 snowy systemd[1]: Stopped Monthly Btrfs scrub on /home.
Jan 08 19:11:52 snowy systemd[1]: Started Monthly Btrfs scrub on /.
Jan 08 19:11:52 snowy systemd[1]: Started Monthly Btrfs scrub on /home.
Jan 08 19:20:12 snowy systemd[1]: btrfs-scrub@-.timer: Deactivated successfully.
Jan 08 19:20:12 snowy systemd[1]: Stopped Monthly Btrfs scrub on /.
Jan 08 19:20:12 snowy systemd[1]: btrfs-scrub@home.timer: Deactivated successfully.
Jan 08 19:20:12 snowy systemd[1]: Stopped Monthly Btrfs scrub on /home.
Jan 08 19:20:48 snowy systemd[1]: Started Monthly Btrfs scrub on /.
Jan 08 19:20:48 snowy systemd[1]: Started Monthly Btrfs scrub on /home.
Jan 08 19:24:03 snowy systemd[1]: btrfs-scrub@-.timer: Deactivated successfully.
Jan 08 19:24:03 snowy systemd[1]: Stopped Monthly Btrfs scrub on /.
Jan 08 19:24:03 snowy systemd[1]: btrfs-scrub@home.timer: Deactivated successfully.
Jan 08 19:24:03 snowy systemd[1]: Stopped Monthly Btrfs scrub on /home.
Jan 08 19:27:38 snowy systemd[1]: Started Monthly Btrfs scrub on /.
Jan 08 19:27:38 snowy systemd[1]: Started Monthly Btrfs scrub on /home.

is in it…
So there's a monthly incident related to FS maintainance and it by happen chance coincides w/ your data loss.

There's also a bunch of I/O errors, but they're on an optical drive.

PopeRigby · 2023-01-11 23:39:02

It certainly is interesting that they keep starting and stopping, but I don't think that's the problem.

BTRFS scrub should just being validating metadata, and it doesn't touch the actual data: https://btrfs.readthedocs.io/en/latest/btrfs-scrub.html

Maybe I should widen the search window? I kind of forget when exactly it happened, but it was definitely on that day. What should I be searching for exactly?

Yes, I've been trying to get those I/O errors to stop. They're probably harmless, but quite annoying.

seth · 2023-01-12 08:22:49

BTRFS scrub should just being validating metadata

https://btrfs.readthedocs.io/en/latest/Scrub.html
https://www.youtube.com/watch?v=5RyYrs5tu60

What should I be searching for exactly?

Problems.
Since we don't know what specifically caused the data loss, we've no specific idea what to look for.

I'll re-iterate though that the universe isn't lazy enough for such coincidences.
It might be that the data had been corrupted before (when you were hard-rebooting) and got removed by the scrub.

PopeRigby · 2023-01-12 21:07:21

You know, that's probably it. I wonder why it didn't get cleared out earlier though.

seth · 2023-01-12 21:22:36

On an unrelated note, you seem to have systemd-networkd and networkmanager enabled.
Pick one, disable the other.

cfr · 2023-01-15 06:43:04

PopeRigby wrote:

Here's the output of 'sudo smartctl -t long /dev/nvme0n1 && sudo smartctl -a /dev/nvme0n1'.:

smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.4-arch1-1] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 980 PRO 2TB
Serial Number:                      S6B0NL0TB03653M
Firmware Version:                   5B2QGXA7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 2,000,398,934,016 [2.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      6
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          2,000,398,934,016 [2.00 TB]
Namespace 1 Utilization:            1,125,152,804,864 [1.12 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 bb21a05728
Local Time is:                      Tue Jan 10 17:55:35 2023 PST
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         128 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 +     8.49W       -        -    0  0  0  0        0       0
 1 +     4.48W       -        -    1  1  1  1        0     200
 2 +     3.18W       -        -    2  2  2  2        0    1000
 3 -   0.0400W       -        -    3  3  3  3     2000    1200
 4 -   0.0050W       -        -    4  4  4  4      500    9500

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:                        40 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    5,582,980 [2.85 TB]
Data Units Written:                 3,977,436 [2.03 TB]
Host Read Commands:                 23,684,163
Host Write Commands:                27,244,126
Controller Busy Time:               128
Power Cycles:                       15
Power On Hours:                     18
Unsafe Shutdowns:                   4
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               40 Celsius
Temperature Sensor 2:               47 Celsius

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

Surprisingly, the test finishes instantly. I'm not sure if that's good or bad.

It finishes instantly because it isn't applicable/supported. There's no indication your drive supports SMART tests (short/long/whatever). My nvme also has smart 1.3. I consider it bad I can't run tests, because I feel I have less information about the state of my storage. But the speed isn't good or bad as far as the actual health of the drive is concerned.

Arch Linux

#1 2023-01-09 18:04:52

Desktop files are missing

#2 2023-01-09 19:58:19

Re: Desktop files are missing

#3 2023-01-10 22:30:40

Re: Desktop files are missing

#4 2023-01-11 00:36:07

Re: Desktop files are missing

#5 2023-01-11 02:02:17

Re: Desktop files are missing

#6 2023-01-11 08:53:03

Re: Desktop files are missing

#7 2023-01-11 18:20:53

Re: Desktop files are missing

#8 2023-01-11 18:35:35

Re: Desktop files are missing

#9 2023-01-11 18:55:09

Re: Desktop files are missing

#10 2023-01-11 19:01:49

Re: Desktop files are missing

#11 2023-01-11 19:21:51

Re: Desktop files are missing

#12 2023-01-11 19:26:56

Re: Desktop files are missing

#13 2023-01-11 20:12:49

Re: Desktop files are missing

#14 2023-01-11 21:57:22

Re: Desktop files are missing

#15 2023-01-11 23:39:02

Re: Desktop files are missing

#16 2023-01-12 08:22:49

Re: Desktop files are missing

#17 2023-01-12 21:07:21

Re: Desktop files are missing

#18 2023-01-12 21:22:36

Re: Desktop files are missing

#19 2023-01-15 06:43:04

Re: Desktop files are missing

Board footer