System crash/hang - NVME ext4 error- troubleshooting tips?

kdwoellert · 11-18-2018, 12:33 PM

My Dell 9560 crashes/hangs on average once/day. Either a system message like the quoted happens (excerpt - not the full message), or sometimes Gnome just becomes unresponsive. I've tried various things like ensuring OS is updated, Dell boot diagnostics, memory checks, temperature monitoring, etc. I'm convinced the problem is with the Samsung SSD drive. Looking for any advice and in particular any tips on how I can setup logging to run this problem down. The Samsung PM961 is not compatible with the standard disk diagnostics so looking for advice on this point also.

Edit: a little more background. This is a 2year old Dell 9560. When purchased it came with Win10. First thing I did was blow away Windows, and install Ubuntu.

Output of fdisk -l:
/dev/nvme0n1: 953.9 GiB, 1024209543168 bytes, 2000409264 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x86e05aaf

Device Boot Start End Sectors Size Id Type
/dev/nvme0n1p1 2048 1934479359 1934477312 922.4G 83 Linux
/dev/nvme0n1p2 1934481406 2000408575 65927170 31.4G 5 Extended
/dev/nvme0n1p5 1934481408 2000408575 65927168 31.4G 82 Linux swap / Solaris

OS Ubuntu 16.04 64bit
Dell XPS-15 9560
Intel® Core™ i7-7700HQ CPU @ 2.80GHz × 8

Graphics GeForce GTX 1050/PCIe/SSE2
Mem 32Gb
Drive Dell 400-APWJ, SSDR, 1TB, P34, 80S3, SAMSUNG, PM961

Quote:

/dev/nvme0n1p1: clean, 1346801/60456960 files, 201107763/241809664 blocks
[1368.906817] EXT4-fs error (device nvme0n1p1): ext4_find_entry: 1454: inode #34603013: comm gmain: reading directory lblock 0
[1368.906817] EXT4-fs error (device nvme0n1p1): _ext4_get_inode_loc:4117: inode #55312906: block 211249600: comm systemd-journal: unable to read itable block
.
.
(many more lines like the above...

dc.901 · 11-18-2018, 06:30 PM

Have you tried booting with OS DVD and running fsck?
Anything reported by SMART tools?
And, what make/model is this SSD?

Also, let's look at messages file:

Code:

grep nvme0n1 /var/log/messages*

kdwoellert · 11-19-2018, 06:05 PM

I have not tried booting with an Ubuntu startup USB stick and running fsck. I will do so tonight and report results an update to this post.

The drive is a Samsung PM961:

Quote:

kirk@Kirk-XPS-15-9560:~$ sudo nvme list
Node SN Model Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 S33XNX0HB02516 PM961 NVMe SAMSUNG 1024GB 1 883.17 GB / 1.02 TB 512 B + 0 B CXY74D1Q

This returns an error,

Quote:

kirk@kirk-XPS-15-9560:/var/log$ grep nvme0n1 /var/log/messages*
grep: /var/log/messages*: No such file or directory

Contents of /var/log/

Quote:

kirk@kirk-XPS-15-9560:/var/log$ ls -l
total 22384
-rw-r--r-- 1 root root 367 Nov 17 18:30 alternatives.log
-rw-r--r-- 1 root root 4325 Oct 31 06:18 alternatives.log.1
-rw-r--r-- 1 root root 649 Feb 1 2018 alternatives.log.10.gz
-rw-r--r-- 1 root root 281 Dec 31 2017 alternatives.log.11.gz
-rw-r--r-- 1 root root 1222 Nov 28 2017 alternatives.log.12.gz
-rw-r--r-- 1 root root 396 Sep 27 22:05 alternatives.log.2.gz
-rw-r--r-- 1 root root 340 Aug 29 19:08 alternatives.log.3.gz
-rw-r--r-- 1 root root 779 Jul 30 20:16 alternatives.log.4.gz
-rw-r--r-- 1 root root 656 Jun 23 12:59 alternatives.log.5.gz
-rw-r--r-- 1 root root 334 May 26 16:53 alternatives.log.6.gz
-rw-r--r-- 1 root root 394 May 1 2018 alternatives.log.7.gz
-rw-r--r-- 1 root root 278 Mar 29 2018 alternatives.log.8.gz
-rw-r--r-- 1 root root 539 Feb 25 2018 alternatives.log.9.gz
-rw-r----- 1 root adm 0 Nov 11 13:24 apport.log
-rw-r----- 1 root adm 524 Nov 11 01:22 apport.log.1
-rw-r----- 1 root adm 266 Nov 3 10:40 apport.log.2.gz
-rw-r----- 1 root adm 260 Oct 31 22:58 apport.log.3.gz
-rw-r----- 1 root adm 349 Oct 27 22:58 apport.log.4.gz
-rw-r----- 1 root adm 275 Sep 30 02:06 apport.log.5.gz
-rw-r----- 1 root adm 302 Sep 23 13:48 apport.log.6.gz
-rw-r----- 1 root adm 200 Sep 22 23:04 apport.log.7.gz
drwxr-xr-x 2 root root 4096 Nov 3 09:24 apt
-rw-r----- 1 syslog adm 0 Nov 19 18:47 auth.log
-rw-r----- 1 syslog adm 120291 Nov 19 18:45 auth.log.1
-rw-r----- 1 syslog adm 3953 Nov 11 13:22 auth.log.2.gz
-rw-r----- 1 syslog adm 5249 Nov 5 19:32 auth.log.3.gz
-rw-r----- 1 syslog adm 3345 Oct 28 11:36 auth.log.4.gz
-rw-r--r-- 1 root root 5323 Nov 19 18:42 boot.log
-rw-r--r-- 1 root root 57457 Jul 19 2016 bootstrap.log
-rw------- 1 root utmp 384 Nov 18 18:12 btmp
-rw------- 1 root utmp 384 Oct 4 18:42 btmp.1
drwxr-xr-x 2 root root 4096 May 29 17:58 cups
drwxr-xr-x 3 root root 4096 Jul 29 2017 dist-upgrade
-rw-r----- 1 root adm 31 Jul 19 2016 dmesg
-rw-r--r-- 1 root root 113397 Nov 19 18:43 dpkg.log
-rw-r--r-- 1 root root 181672 Oct 31 06:18 dpkg.log.1
-rw-r--r-- 1 root root 19325 Feb 1 2018 dpkg.log.10.gz
-rw-r--r-- 1 root root 9429 Dec 31 2017 dpkg.log.11.gz
-rw-r--r-- 1 root root 18713 Nov 30 2017 dpkg.log.12.gz
-rw-r--r-- 1 root root 9578 Sep 29 13:17 dpkg.log.2.gz
-rw-r--r-- 1 root root 11296 Aug 29 19:09 dpkg.log.3.gz
-rw-r--r-- 1 root root 13814 Jul 30 20:18 dpkg.log.4.gz
-rw-r--r-- 1 root root 8757 Jun 29 17:40 dpkg.log.5.gz
-rw-r--r-- 1 root root 12519 May 28 21:17 dpkg.log.6.gz
-rw-r--r-- 1 root root 11460 May 1 2018 dpkg.log.7.gz
-rw-r--r-- 1 root root 10653 Apr 1 2018 dpkg.log.8.gz
-rw-r--r-- 1 root root 27236 Feb 25 2018 dpkg.log.9.gz
-rw-r--r-- 1 root root 32032 Apr 23 2017 faillog
-rw-r--r-- 1 root root 3817 Oct 21 13:44 fontconfig.log
drwxr-xr-x 2 root root 4096 Jul 19 2016 fsck
-rw-r--r-- 1 root root 2727 Nov 19 18:42 gpu-manager.log
drwxrwxr-x 2 root root 4096 Feb 11 2017 installer
-rw-r----- 1 syslog adm 0 Nov 19 18:47 kern.log
-rw-r----- 1 syslog adm 3169230 Nov 19 18:47 kern.log.1
-rw-r----- 1 syslog adm 199267 Nov 11 13:24 kern.log.2.gz
-rw-r----- 1 syslog adm 240292 Nov 5 19:34 kern.log.3.gz
-rw-r----- 1 syslog adm 141218 Oct 28 11:37 kern.log.4.gz
-rw-rw-r-- 1 root utmp 292292 Apr 23 2017 lastlog
drwxr-xr-x 2 root root 4096 Nov 19 18:47 lightdm
-rw-r--r-- 1 root root 2416987 Nov 19 18:42 mcelog
-rw-r--r-- 1 root root 20 Nov 19 18:42 prime-supported.log
drwxr-x--- 3 root adm 4096 Nov 19 18:47 samba
drwx------ 2 speech-dispatcher root 4096 Feb 18 2016 speech-dispatcher
-rw-r----- 1 syslog adm 481 Nov 19 18:47 syslog
-rw-r----- 1 syslog adm 2296904 Nov 19 18:47 syslog.1
-rw-r----- 1 syslog adm 49186 Nov 18 10:05 syslog.2.gz
-rw-r----- 1 syslog adm 91491 Nov 17 18:35 syslog.3.gz
-rw-r----- 1 syslog adm 196623 Nov 15 07:05 syslog.4.gz
-rw-r----- 1 syslog adm 47835 Nov 14 08:00 syslog.5.gz
-rw-r----- 1 syslog adm 53067 Nov 13 19:59 syslog.6.gz
-rw-r----- 1 syslog adm 49625 Nov 12 08:24 syslog.7.gz
drwxr-xr-x 2 root root 4096 Aug 19 11:42 teamviewer13
drwxr-x--- 2 root adm 4096 Nov 3 09:24 unattended-upgrades
drwxr-xr-x 2 root root 4096 May 19 2016 upstart
-rw-r--r-- 1 root root 9207154 Jul 22 13:40 vbox-install.log
-rw-r--r-- 1 root root 140 Nov 14 19:19 vbox-setup.log
-rw-r--r-- 1 root root 140 Nov 3 09:19 vbox-setup.log.1
-rw-r--r-- 1 root root 140 Oct 4 18:42 vbox-setup.log.2
-rw-r--r-- 1 root root 140 Sep 22 12:15 vbox-setup.log.3
-rw-r--r-- 1 root root 140 Aug 28 18:10 vbox-setup.log.4
drwxr-xr-x 2 root root 4096 Nov 19 18:43 vmware
-rw-r--r-- 1 root root 382372 Nov 14 19:19 vmware-installer
-rw-r--r-- 1 root root 2935960 Nov 19 18:43 vnetlib
-rw-rw-r-- 1 root utmp 72576 Nov 19 18:43 wtmp
-rw-rw-r-- 1 root utmp 90240 Nov 3 09:19 wtmp.1
-rw-r--r-- 1 root root 53828 Nov 19 18:43 Xorg.0.log
-rw-r--r-- 1 root root 55260 Nov 18 21:18 Xorg.0.log.old
-rw-r--r-- 1 root root 37057 Nov 12 20:16 Xorg.1.log
-rw-r--r-- 1 root root 37057 Nov 12 17:32 Xorg.1.log.old
-rw-r--r-- 1 root root 39868 Oct 27 23:37 Xorg.failsafe.log
-rw-r--r-- 1 root root 42011 Oct 27 22:58 Xorg.failsafe.log.old
-rw------- 1 root root 0 Dec 21 2017 yum.log

Quote:

kirk@kirk-XPS-15-9560:~$ sudo nvme smart-log /dev/nvme0
Smart Log for NVME device:nvme0 namespace-id:ffffffff
critical_warning : 0
temperature : 29 C
available_spare : 100%
available_spare_threshold : 50%
percentage_used : 0%
data_units_read : 12,521,434
data_units_written : 11,520,127
host_read_commands : 198,152,301
host_write_commands : 273,175,048
controller_busy_time : 709
power_cycles : 1,020
power_on_hours : 3,700
unsafe_shutdowns : 178
media_errors : 0
num_err_log_entries : 1,966
Warning Temperature Time : 0
Critical Composite Temperature Time : 0
Temperature Sensor 1 : 29 C
Temperature Sensor 2 : 31 C
Temperature Sensor 3 : 0 C
Temperature Sensor 4 : 0 C
Temperature Sensor 5 : 0 C
Temperature Sensor 6 : 0 C
Temperature Sensor 7 : 0 C
Temperature Sensor 8 : 0 C

dc.901 · 11-19-2018, 07:52 PM

From output (sudo nvme smart-log /dev/nvme0), I see:

Quote:

num_err_log_entries : 1,966

Oh, let's review the error log:

Code:

nvme error-log /dev/nvme0n1

Instead of messages, I see syslog, so:

Code:

grep nvme0 /var/log/syslog*

There are some compressed syslog files, but let's look at the nvme errors first...

kdwoellert · 11-19-2018, 09:07 PM

Dug up my Ubuntu16.04 Live USB, Grub halted at the dots...then remembered a post a year ago for folks running Nvidia cards to use "nomodeset". Tried again holding the shift key down at boot, and was able select "try without installing". Unmounted the suspect SDD NVME drive as per below:

Quote:

ubuntu@ubuntu:~$ sudo fdisk -l
Disk /dev/loop0: 1.5 GiB, 1587904512 bytes, 3101376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/nvme0n1: 953.9 GiB, 1024209543168 bytes, 2000409264 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x86e05aaf

Device Boot Start End Sectors Size Id Type
/dev/nvme0n1p1 2048 1934479359 1934477312 922.4G 83 Linux
/dev/nvme0n1p2 1934481406 2000408575 65927170 31.4G 5 Extended
/dev/nvme0n1p5 1934481408 2000408575 65927168 31.4G 82 Linux swap / Solaris

Disk /dev/sda: 28.9 GiB, 31024349184 bytes, 60594432 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6be2cd0d

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 0 3221855 3221856 1.5G 0 Empty
/dev/sda2 9828 14563 4736 2.3M ef EFI (FAT-12/16/32)
ubuntu@ubuntu:~$ sudo umount /dev/nvme0n1p1
umount: /dev/nvme0n1p1: not mounted
ubuntu@ubuntu:~$ sudo fsck -CvMf /dev/nvme0n1p1
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

1460525 inodes used (2.42%, out of 60456960)
7833 non-contiguous files (0.5%)
1540 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 1385987/756/4
207703786 blocks used (85.90%, out of 241809664)
0 bad blocks
33 large files

1240914 regular files
128235 directories
55 character device files
25 block device files
1 fifo
313 links
90887 symbolic links (73290 fast symbolic links)
399 sockets
------------
1460829 files
ubuntu@ubuntu:~$

ubuntu@ubuntu:~$ sudo fsck -CvMf /dev/nvme0n1p2
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/nvme0n1p2
Could this be a zero-length partition?
ubuntu@ubuntu:~$ sudo fsck -CvMf /dev/nvme0n1p5
fsck from util-linux 2.27.1
ubuntu@ubuntu:~$

Then, grep nvme0 /var/log/syslog*

Quote:

kirk@kirk-XPS-15-9560:~$ sudo nvme error-log /dev/nvme0n1p1
[sudo] password for kirk:
Error Log Entries for device:nvme0n1p1 entries:64
.................
Entry[ 0]
.................
error_count : 1993
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[ 1]
.................
error_count : 1992
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[ 2]
.................
error_count : 1991
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[ 3]
.................
error_count : 1990
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[ 4]
.................
error_count : 1989
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[ 5]
.................
error_count : 1988
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[ 6]
.................
error_count : 1987
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[ 7]
.................
error_count : 1986
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[ 8]
.................
error_count : 1985
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[ 9]
.................
error_count : 1984
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[10]
.................
error_count : 1983
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[11]
.................
error_count : 1982
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[12]
.................
error_count : 1981
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[13]
.................
error_count : 1980
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[14]
.................
error_count : 1979
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[15]
.................
error_count : 1978
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[16]
.................
error_count : 1977
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[17]
.................
error_count : 1976
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[18]
.................
error_count : 1975
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[19]
.................
error_count : 1974
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[20]
.................
error_count : 1973
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[21]
.................
error_count : 1972
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[22]
.................
error_count : 1971
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[23]
.................
error_count : 1970
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[24]
.................
error_count : 1969
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[25]
.................
error_count : 1968
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[26]
.................
error_count : 1967
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[27]
.................
error_count : 1966
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[28]
.................
error_count : 1965
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[29]
.................
error_count : 1964
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[30]
.................
error_count : 1963
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[31]
.................
error_count : 1962
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[32]
.................
error_count : 1961
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[33]
.................
error_count : 1960
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[34]
.................
error_count : 1959
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[35]
.................
error_count : 1958
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[36]
.................
error_count : 1957
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[37]
.................
error_count : 1956
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[38]
.................
error_count : 1955
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[39]
.................
error_count : 1954
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[40]
.................
error_count : 1953
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[41]
.................
error_count : 1952
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[42]
.................
error_count : 1951
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[43]
.................
error_count : 1950
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[44]
.................
error_count : 1949
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[45]
.................
error_count : 1948
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[46]
.................
error_count : 1947
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[47]
.................
error_count : 1946
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[48]
.................
error_count : 1945
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[49]
.................
error_count : 1944
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[50]
.................
error_count : 1943
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[51]
.................
error_count : 1942
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[52]
.................
error_count : 1941
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[53]
.................
error_count : 1940
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[54]
.................
error_count : 1939
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[55]
.................
error_count : 1938
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[56]
.................
error_count : 1937
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[57]
.................
error_count : 1936
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[58]
.................
error_count : 1935
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[59]
.................
error_count : 1934
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[60]
.................
error_count : 1933
sqid : 0
cmdid : 0x4
status_field : 0x4202
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
.................
Entry[61]
.................
error_count : 1932
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[62]
.................
error_count : 1931
sqid : 0
cmdid : 0x7
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
Entry[63]
.................
error_count : 1930
sqid : 0
cmdid : 0x8
status_field : 0x4016
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
.................
kirk@kirk-XPS-15-9560:~$

Then, grep nvme0 /var/log/syslog*

Quote:

kirk@kirk-XPS-15-9560:~$ grep nvme0 /var/log/syslog*
/var/log/syslog:Nov 19 20:23:31 kirk-XPS-15-9560 kernel: [ 3.495632] nvme0n1: p1 p2 < p5 >
/var/log/syslog:Nov 19 20:23:31 kirk-XPS-15-9560 kernel: [ 3.978276] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
/var/log/syslog:Nov 19 20:23:31 kirk-XPS-15-9560 kernel: [ 4.166557] EXT4-fs (nvme0n1p1): re-mounted. Opts: errors=remount-ro
/var/log/syslog:Nov 19 20:23:31 kirk-XPS-15-9560 kernel: [ 4.870106] Adding 32963580k swap on /dev/nvme0n1p5. Priority:-1 extents:1 across:32963580k SSFS
/var/log/syslog:Nov 19 21:15:13 kirk-XPS-15-9560 kernel: [ 2.798786] nvme0n1: p1 p2 < p5 >
/var/log/syslog:Nov 19 21:15:13 kirk-XPS-15-9560 kernel: [ 3.742341] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
/var/log/syslog:Nov 19 21:15:13 kirk-XPS-15-9560 kernel: [ 3.910560] EXT4-fs (nvme0n1p1): re-mounted. Opts: errors=remount-ro
/var/log/syslog:Nov 19 21:15:13 kirk-XPS-15-9560 kernel: [ 4.353432] Adding 32963580k swap on /dev/nvme0n1p5. Priority:-1 extents:1 across:32963580k SSFS
/var/log/syslog:Nov 19 21:21:59 kirk-XPS-15-9560 kernel: [ 3.064561] nvme0n1: p1 p2 < p5 >
/var/log/syslog:Nov 19 21:21:59 kirk-XPS-15-9560 kernel: [ 3.653840] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
/var/log/syslog:Nov 19 21:21:59 kirk-XPS-15-9560 kernel: [ 3.830275] EXT4-fs (nvme0n1p1): re-mounted. Opts: errors=remount-ro
/var/log/syslog:Nov 19 21:21:59 kirk-XPS-15-9560 kernel: [ 4.522297] Adding 32963580k swap on /dev/nvme0n1p5. Priority:-1 extents:1 across:32963580k SSFS
/var/log/syslog:Nov 19 21:23:06 kirk-XPS-15-9560 kernel: [ 3.035969] nvme0n1: p1 p2 < p5 >
/var/log/syslog:Nov 19 21:23:06 kirk-XPS-15-9560 kernel: [ 3.655939] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
/var/log/syslog:Nov 19 21:23:06 kirk-XPS-15-9560 kernel: [ 3.826554] EXT4-fs (nvme0n1p1): re-mounted. Opts: errors=remount-ro
/var/log/syslog:Nov 19 21:23:06 kirk-XPS-15-9560 kernel: [ 4.575479] Adding 32963580k swap on /dev/nvme0n1p5. Priority:-1 extents:1 across:32963580k SSFS
/var/log/syslog:Nov 19 21:29:29 kirk-XPS-15-9560 kernel: [ 3.033305] nvme0n1: p1 p2 < p5 >
/var/log/syslog:Nov 19 21:29:29 kirk-XPS-15-9560 kernel: [ 3.482162] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
/var/log/syslog:Nov 19 21:29:29 kirk-XPS-15-9560 kernel: [ 3.650498] EXT4-fs (nvme0n1p1): re-mounted. Opts: errors=remount-ro
/var/log/syslog:Nov 19 21:29:29 kirk-XPS-15-9560 kernel: [ 4.668431] Adding 32963580k swap on /dev/nvme0n1p5. Priority:-1 extents:1 across:32963580k SSFS
/var/log/syslog:Nov 19 21:30:50 kirk-XPS-15-9560 kernel: [ 2.756811] nvme0n1: p1 p2 < p5 >
/var/log/syslog:Nov 19 21:30:50 kirk-XPS-15-9560 kernel: [ 3.638115] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
/var/log/syslog:Nov 19 21:30:50 kirk-XPS-15-9560 kernel: [ 3.804721] EXT4-fs (nvme0n1p1): re-mounted. Opts: errors=remount-ro
/var/log/syslog:Nov 19 21:30:50 kirk-XPS-15-9560 kernel: [ 4.576861] Adding 32963580k swap on /dev/nvme0n1p5. Priority:-1 extents:1 across:32963580k SSFS
/var/log/syslog:Nov 19 21:53:53 kirk-XPS-15-9560 kernel: [ 2.819073] nvme0n1: p1 p2 < p5 >
/var/log/syslog:Nov 19 21:53:53 kirk-XPS-15-9560 kernel: [ 3.577845] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
/var/log/syslog:Nov 19 21:53:53 kirk-XPS-15-9560 kernel: [ 3.757311] EXT4-fs (nvme0n1p1): re-mounted. Opts: errors=remount-ro
/var/log/syslog:Nov 19 21:53:53 kirk-XPS-15-9560 kernel: [ 4.516646] Adding 32963580k swap on /dev/nvme0n1p5. Priority:-1 extents:1 across:32963580k SSFS
/var/log/syslog.1:Nov 18 10:25:07 kirk-XPS-15-9560 kernel: [ 2.807784] nvme0n1: p1 p2 < p5 >
/var/log/syslog.1:Nov 18 10:25:07 kirk-XPS-15-9560 kernel: [ 3.466884] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
/var/log/syslog.1:Nov 18 10:25:07 kirk-XPS-15-9560 kernel: [ 3.631438] EXT4-fs (nvme0n1p1): re-mounted. Opts: errors=remount-ro
/var/log/syslog.1:Nov 18 10:25:07 kirk-XPS-15-9560 kernel: [ 4.417697] Adding 32963580k swap on /dev/nvme0n1p5. Priority:-1 extents:1 across:32963580k SSFS
Binary file /var/log/syslog.1 matches

kdwoellert · 11-19-2018, 09:25 PM

Been reading up on journalctl in an attempt to pin down exactly what happens when the OS crashes or Gnome freezes.

I tried this command and apparently persistent logging is not enabled. Perhaps I should do that?

Quote:

kirk@kirk-XPS-15-9560:~$ journalctl -b -1
Specifying boot ID has no effect, no persistent journal was found

kdwoellert · 11-19-2018, 09:37 PM

Aha! Someone else with a similar similar problem as me. Although for my Ubuntu system experience there is no correlation to use of a specific application. The behavior occurs randomly, whether under heavy CPU load or not, graphics intensive apps or not.

kdwoellert · 11-19-2018, 09:47 PM

This is a long thread but its seems to be very relevant. The issue involves a Samsung SSD and random OS crashes.