I followed these installation steps exactly using Xubuntu 20.04: https://help.ubuntu.com/community/Fu...ion_Howto_2019 on a Dell Precision 5550 - for the record I installed a second 500G NVME drive (it supports 2), only "zapped" that one, and installed Xubuntu on that one. Now my problem is after my laptop is booted for a few days the root filesystem will all of a sudden go read-only, and doesn't seem to be related any power actions (suspend). When it goes read-only as you can imagine everything just crashes and nothing works, not even shutdown and I have to press and hold the power button to reboot it. Everything I have read so far says this happens when the filesystem is getting corrupted and to run fsck on it, but I have done that twice from a live usb immediately after the problem occurs and neither time did it report any issues, so I am more suspicious it's some kind of issue with the encryption/lvm. The NVME I installed it on was working perfectly fine prior to this install on it, so I don't think it's a hardware issue with that.
Here is last thing in the syslog before the problem happened around 08:00:00. dmesg logs don't show anything after the first ~19 secs of boot, and I didn't see any other relevant logs, please let me know where else I can look for clues.
Thanks for your timeCode:Feb 26 07:56:39 koln wpa_supplicant[1058]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=9999 txrate=360000 Feb 26 07:56:46 koln wpa_supplicant[1058]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-60 noise=9999 txrate=360000 Feb 26 07:56:47 koln wpa_supplicant[1058]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=360000 Feb 26 07:58:21 koln wpa_supplicant[1058]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-67 noise=9999 txrate=162000 Feb 26 07:58:24 koln wpa_supplicant[1058]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=9999 txrate=162000 Feb 26 07:58:31 koln obexd[1936]: disconnected: Transport got disconnected Feb 26 07:58:31 koln acpid: input device has been disconnected, fd 21 Feb 26 07:58:31 koln bluetoothd[1012]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107) Feb 26 07:58:31 koln bluetoothd[1012]: Unable to get io data for Phone Book Access: getpeername: Transport endpoint is not connected (107) Feb 26 07:58:33 koln wpa_supplicant[1058]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-80 noise=9999 txrate=81000 Feb 26 07:58:44 koln kernel: [385950.234020] input: Nick qc35 (AVRCP) as /devices/virtual/input/input47 Feb 26 07:58:44 koln obexd[1936]: CONNECT(0x0), <unknown>(0xff) Feb 26 07:58:44 koln obexd[1936]: CONNECT(0x0), <unknown>(0x0) Feb 26 07:58:44 koln obexd[1936]: SETPATH(0x5), <unknown>(0xff) Feb 26 07:58:44 koln obexd[1936]: stat(/home/nd18548/phonebook/): No such file or directory (2) Feb 26 07:58:44 koln obexd[1936]: SETPATH(0x5), Not Found(0x44) Feb 26 07:58:46 koln bluetoothd[1012]: /org/bluez/hci0/dev_04_52_C7_C2_FF_58/sep1/fd3: fd(53) ready Feb 26 07:58:46 koln rtkit-daemon[1340]: Supervising 3 threads of 1 processes of 1 users. Feb 26 07:58:46 koln rtkit-daemon[1340]: Successfully made thread 458926 of process 1630 owned by '18548' RT at priority 5. Feb 26 07:58:46 koln rtkit-daemon[1340]: Supervising 4 threads of 1 processes of 1 users. Feb 26 08:03:26 koln wpa_supplicant[1058]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-60 noise=9999 txrate=30000 Feb 26 08:03:27 koln wpa_supplicant[1058]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=30000 Feb 26 08:03:29 koln wpa_supplicant[1058]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-47 noise=9999 txrate=30000 Feb 26 08:03:36 koln xfce4-screensav[1748]: invalid uninstantiatable type '<unknown>' in cast to 'GSWindow' Feb 26 08:03:36 koln xfce4-screensav[1748]: gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed Feb 26 08:03:36 koln xfce4-screensav[1748]: message repeated 2 times: [ gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed] Feb 26 08:03:36 koln xfce4-screensav[1748]: gdk_event_set_source_device: assertion 'GDK_IS_DEVICE (device)' failed Feb 26 08:03:36 koln xfce4-screensav[1748]: gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed Feb 26 08:03:36 koln xfce4-screensav[1748]: gdk_event_set_source_device: assertion 'GDK_IS_DEVICE (device)' failed Feb 26 08:03:36 koln wpa_supplicant[1058]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-47 noise=9999 txrate=30000 Feb 26 08:03:39 koln wpa_supplicant[1058]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-45 noise=9999 txrate=30000 Feb 26 08:13:00 koln systemd-modules-load[661]: Inserted module 'lp' Feb 26 08:13:00 koln systemd-modules-load[661]: Inserted module 'ppdev' Feb 26 08:13:00 koln systemd-modules-load[661]: Inserted module 'parport_pc' Feb 26 08:13:00 koln systemd-sysctl[678]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Feb 26 08:13:00 koln systemd-sysctl[678]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Feb 26 08:13:00 koln lvm[659]: 2 logical volume(s) in volume group "ubuntu-vg" monitored Feb 26 08:13:00 koln systemd[1]: Starting Flush Journal to Persistent Storage... Feb 26 08:13:00 koln systemd[1]: Finished udev Coldplug all Devices. Feb 26 08:13:00 koln systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. Feb 26 08:13:00 koln systemd[1]: Reached target Local File Systems (Pre). Feb 26 08:13:00 koln systemd[1]: Starting Show Plymouth Boot Screen... Feb 26 08:13:00 koln systemd[1]: plymouth-start.service: Succeeded. Feb 26 08:13:00 koln systemd[1]: Started Show Plymouth Boot Screen. Feb 26 08:13:00 koln systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Feb 26 08:13:00 koln systemd[1]: Started Forward Password Requests to Plymouth Directory Watch. Feb 26 08:13:00 koln systemd[1]: Finished Flush Journal to Persistent Storage. Feb 26 08:13:00 koln systemd[1]: Starting Show Plymouth Boot Screen... Feb 26 08:13:00 koln systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Feb 26 08:13:00 koln systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Feb 26 08:13:00 koln systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Feb 26 08:13:00 koln systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Feb 26 08:13:00 koln systemd[1]: plymouth-start.service: Succeeded. Feb 26 08:13:00 koln systemd[1]: Started Show Plymouth Boot Screen. Feb 26 08:13:00 koln systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped.
Adv Reply
Bookmarks