Will smartctl work with an Intel nvme (with Optane)? I get the following error when executing what I believe is the code for a long test:
Read Error Information Log failed: NVMe Status 0x02
The complete response is here:https://susepaste.org/42841735
Current smartctl version on TW is 7.1. You could try booting a live TW. Also look for firmware updates. I noticed a high number of unsafe shutdowns btw.
Hi
Does the drive support a log file…?
I see here (On Tumbleweed) WD NVMe WDS250G1B0C-00S6U0;
smartctl -l error /dev/nvme0
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.5.7-1-default] (SUSE RPM)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF SMART DATA SECTION ===
Error Information (NVMe Log 0x01, max 256 entries)
No Errors Logged
Malcolm -
I don’t believe the drive supports a log per se. I posted a query about the overall issue two days ago, and have since run a memory test that didn’t turn up any errors. See https://forums.opensuse.org/showthread.php/539402-Internet-browsers-on-laptop-crashing?p=2929221.
A badblocks test also passed without errors.
The unit is a Dell Inspiron 15 5000 laptop purchased new about six months ago, running Leap 15.1 with the default btrfs file system (perhaps btrfs is the problem?). This morning, I booted into a seldomly-used Windows 10 Home partition and Firefox similarly crashed. But the browser appeared to be stable with a live 15.1 OS on a USB drive.
Hi
If you haven’t booted into WinX then likely updates required… and probably a move to Build 1909… Aside from the Unsafe shutdowns (In WinX I use shutdown /s /t 3) to ensure it’s all closed down. I have had a few with my NVMe device but that was caused at first install as had to add a boot option to my NVMe device…
I did previously boot into Windows, and this morning did the update and restart. As best as I can tell, Windows is functioning.
It’s the Internet browsers that crash on either platform. And as mentioned in the other post, I’ve been using the Leap 15.1 setup for months without incident.
Another way to retrieve the error log: install nvme-cli and run
sudo nvme error-log /dev/nvme0n1p4
From the paste it seems no errors are logged but it should at least retrieve them zeroed out.
Could you try without specifying the partition, to see if there’s any change?
awerlang -
I ran it both ways - no errors. Same for badblocks with non-destructive read-write testing (partition and entire drive) - no errors.