[SOLVED] Should I worry about this error messages?

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
MrT
Level 3
Level 3
Posts: 143
Joined: Tue Jun 20, 2017 3:21 pm

[SOLVED] Should I worry about this error messages?

Post by MrT »

I made the upgrade from 19.3 to 20 and it seems to work. However, when I start it, I get a lot of messages that I'd rather not seeing.
Is it something I should worry about.

Code: Select all

- Logs begin at Thu 2020-07-09 17:54:21 PDT, end at Thu 2020-07-09 17:57:35 PDT. --
Jul 09 17:54:21 mrt-WT73VR-7RM kernel: Initramfs unpacking failed: Decoding failed
Jul 09 17:54:22 mrt-WT73VR-7RM kernel: cgroup1: Unknown subsys name '__DEVEL__sane_behavior'
Jul 09 17:54:22 mrt-WT73VR-7RM kernel: cgroup1: Unknown subsys name '__DEVEL__sane_behavior'
Jul 09 17:54:22 mrt-WT73VR-7RM kernel: cgroup1: Unknown subsys name '__DEVEL__sane_behavior'
Jul 09 17:54:22 mrt-WT73VR-7RM kernel: cgroup1: Unknown subsys name '__DEVEL__sane_behavior'
Jul 09 17:54:22 mrt-WT73VR-7RM kernel: cgroup1: Unknown subsys name '__DEVEL__sane_behavior'
Jul 09 17:54:22 mrt-WT73VR-7RM systemd[1]: Failed to start Cgroup management daemon.
Jul 09 17:54:26 mrt-WT73VR-7RM systemd[1]: Failed to start LSB: This service starts and stops VMware services.
Jul 09 17:54:27 mrt-WT73VR-7RM lightdm[1563]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jul 09 17:54:27 mrt-WT73VR-7RM lightdm[1563]: PAM adding faulty module: pam_kwallet.so
Jul 09 17:54:27 mrt-WT73VR-7RM lightdm[1563]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jul 09 17:54:27 mrt-WT73VR-7RM lightdm[1563]: PAM adding faulty module: pam_kwallet5.so
Jul 09 17:54:28 mrt-WT73VR-7RM lightdm[1664]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jul 09 17:54:28 mrt-WT73VR-7RM lightdm[1664]: PAM adding faulty module: pam_kwallet.so
Jul 09 17:54:28 mrt-WT73VR-7RM lightdm[1664]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jul 09 17:54:28 mrt-WT73VR-7RM lightdm[1664]: PAM adding faulty module: pam_kwallet5.so
Jul 09 17:54:37 mrt-WT73VR-7RM lightdm[1664]: gkr-pam: unable to locate daemon control file
Jul 09 17:54:37 mrt-WT73VR-7RM pulseaudio[1586]: Error opening PCM device front:0: No such file or directory
Jul 09 17:54:37 mrt-WT73VR-7RM pulseaudio[1586]: Error opening PCM device hw:1: No such file or directory
Jul 09 17:54:37 mrt-WT73VR-7RM pulseaudio[1586]: Error opening PCM device front:0: No such file or directory
Jul 09 17:54:40 mrt-WT73VR-7RM ntpd[1452]: bind(29) AF_INET6 fe80::c20f:adf4:c658:ddbd%3#123 flags 0x11 failed: Cannot assign requested address
Jul 09 17:54:40 mrt-WT73VR-7RM ntpd[1452]: unable to create socket on wlp2s0 (10) for fe80::c20f:adf4:c658:ddbd%3#123
Jul 09 17:56:46 mrt-WT73VR-7RM sudo[3583]:      mrt : a password is required ; TTY=pts/0 ; PWD=/home/mrt ; USER=root ; COMMAND=/usr/sbin/hddtemp -nq -u C /d
Last edited by MrT on Fri Jul 10, 2020 6:56 pm, edited 1 time in total.

rene
Level 16
Level 16
Posts: 6540
Joined: Sun Mar 27, 2016 6:58 pm

Re: Should I worry about this error messages?

Post by rene »

Did you upgrade using https://community.linuxmint.com/tutorial/view/2485? The short of it is that I get the definite impression from this that your system is a bleedin' mess and needs to be reinstalled from scratch rather than supposedly be upgraded for years and years now. I.e.,
MrT wrote:
Thu Jul 09, 2020 9:09 pm

Code: Select all

Jul 09 17:54:21 mrt-WT73VR-7RM kernel: Initramfs unpacking failed: Decoding failed
Do you have compress=gzip in /etc/initramfs-tools/initramfs.conf? If not, you'd make it so, and in any case run sudo update-initramfs -u -k all and try and see if it's fixed on reboot.
MrT wrote:
Thu Jul 09, 2020 9:09 pm

Code: Select all

Jul 09 17:54:22 mrt-WT73VR-7RM kernel: cgroup1: Unknown subsys name '__DEVEL__sane_behavior'
Jul 09 17:54:22 mrt-WT73VR-7RM kernel: cgroup1: Unknown subsys name '__DEVEL__sane_behavior'
Jul 09 17:54:22 mrt-WT73VR-7RM kernel: cgroup1: Unknown subsys name '__DEVEL__sane_behavior'
Jul 09 17:54:22 mrt-WT73VR-7RM kernel: cgroup1: Unknown subsys name '__DEVEL__sane_behavior'
Jul 09 17:54:22 mrt-WT73VR-7RM systemd[1]: Failed to start Cgroup management daemon.
This seems to say that you are still trying to start cgmanager.service and that has not been a thing since 18 so I'd assume you've had this issue during all of 19 as well. sudo apt-get purge cgmanager?
MrT wrote:
Thu Jul 09, 2020 9:09 pm

Code: Select all

Jul 09 17:54:26 mrt-WT73VR-7RM systemd[1]: Failed to start LSB: This service starts and stops VMware services.
You probably need to recompile/reinstall the VMware kernel module against your kernel. VMware has for years and years violated the kernel copyright so they can do their own support though.
MrT wrote:
Thu Jul 09, 2020 9:09 pm

Code: Select all

Jul 09 17:54:27 mrt-WT73VR-7RM lightdm[1563]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jul 09 17:54:27 mrt-WT73VR-7RM lightdm[1563]: PAM adding faulty module: pam_kwallet.so
Jul 09 17:54:27 mrt-WT73VR-7RM lightdm[1563]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jul 09 17:54:27 mrt-WT73VR-7RM lightdm[1563]: PAM adding faulty module: pam_kwallet5.so
Jul 09 17:54:28 mrt-WT73VR-7RM lightdm[1664]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jul 09 17:54:28 mrt-WT73VR-7RM lightdm[1664]: PAM adding faulty module: pam_kwallet.so
Jul 09 17:54:28 mrt-WT73VR-7RM lightdm[1664]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jul 09 17:54:28 mrt-WT73VR-7RM lightdm[1664]: PAM adding faulty module: pam_kwallet5.so
This, then, seems to suggest you even have KDE remnants on your system, specifically libpam-kwallet-common, libpam-kwallet4 and/or libpam-kwallet5.
MrT wrote:
Thu Jul 09, 2020 9:09 pm

Code: Select all

Jul 09 17:54:37 mrt-WT73VR-7RM lightdm[1664]: gkr-pam: unable to locate daemon control file
This one seems to indicate a corrupt/obsolete setting in your user's dconf database.
MrT wrote:
Thu Jul 09, 2020 9:09 pm

Code: Select all

Jul 09 17:54:37 mrt-WT73VR-7RM pulseaudio[1586]: Error opening PCM device front:0: No such file or directory
Jul 09 17:54:37 mrt-WT73VR-7RM pulseaudio[1586]: Error opening PCM device hw:1: No such file or directory
Jul 09 17:54:37 mrt-WT73VR-7RM pulseaudio[1586]: Error opening PCM device front:0: No such file or directory
Seems little point chasing this one given all of the above, but would not seem harmless.
MrT wrote:
Thu Jul 09, 2020 9:09 pm

Code: Select all

Jul 09 17:54:40 mrt-WT73VR-7RM ntpd[1452]: bind(29) AF_INET6 fe80::c20f:adf4:c658:ddbd%3#123 flags 0x11 failed: Cannot assign requested address
Jul 09 17:54:40 mrt-WT73VR-7RM ntpd[1452]: unable to create socket on wlp2s0 (10) for fe80::c20f:adf4:c658:ddbd%3#123
It appears you have IPv6 disabled through kernel command line or sysctl? In any case, in essence harmless.
MrT wrote:
Thu Jul 09, 2020 9:09 pm

Code: Select all

Jul 09 17:56:46 mrt-WT73VR-7RM sudo[3583]:      mrt : a password is required ; TTY=pts/0 ; PWD=/home/mrt ; USER=root ; COMMAND=/usr/sbin/hddtemp -nq -u C /d
Was this inxi? See man inxi, /hddtemp.

Or better, don't, and if I'm not just misinterpreting this barrage of "interesting" errors, backup your private files and start again with a clean install of Mint 20.

MrT
Level 3
Level 3
Posts: 143
Joined: Tue Jun 20, 2017 3:21 pm

Re: Should I worry about this error messages?

Post by MrT »

Thank you Rene. I installed Linux Mint 18 from scratch and then I upgraded to 19 and, today, to 20.
Following your advice I was able to eliminate some of the error messages.

However, the Initramfs error is still there. It does not prevent me from using the PC or anything (so far). For the file you mentioned... I did run the command you suggested, just in case and this is what i see: compress = lz4. Should I change that to gzip?

Code: Select all

# initramfs.conf
# Configuration file for mkinitramfs(8). See initramfs.conf(5).
#
# Note that configuration options from this file can be overridden
# by config files in the /etc/initramfs-tools/conf.d directory.

#
# MODULES: [ most | netboot | dep | list ]
#
# most - Add most filesystem and all harddrive drivers.
#
# dep - Try and guess which modules to load.
#
# netboot - Add the base modules, network modules, but skip block devices.
#
# list - Only include modules from the 'additional modules' list
#

MODULES=most

#
# BUSYBOX: [ y | n | auto ]
#
# Use busybox shell and utilities.  If set to n, klibc utilities will be used.
# If set to auto (or unset), busybox will be used if installed and klibc will
# be used otherwise.
#

BUSYBOX=auto

#
# COMPCACHE_SIZE: [ "x K" | "x M" | "x G" | "x %" ]
#
# Amount of RAM to use for RAM-based compressed swap space.
#
# An empty value - compcache isn't used, or added to the initramfs at all.
# An integer and K (e.g. 65536 K) - use a number of kilobytes.
# An integer and M (e.g. 256 M) - use a number of megabytes.
# An integer and G (e.g. 1 G) - use a number of gigabytes.
# An integer and % (e.g. 50 %) - use a percentage of the amount of RAM.
#
# You can optionally install the compcache package to configure this setting
# via debconf and have userspace scripts to load and unload compcache.
#

COMPCACHE_SIZE=""

#
# COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz ]
#

COMPRESS=lz4

#
# NFS Section of the config.
#

#
# DEVICE: ...
#
# Specify a specific network interface, like eth0
# Overridden by optional ip= or BOOTIF= bootarg
#

DEVICE=

#
# NFSROOT: [ auto | HOST:MOUNT ]
#

NFSROOT=auto

#
# RUNSIZE: ...
#
# The size of the /run tmpfs mount point, like 256M or 10%
# Overridden by optional initramfs.runsize= bootarg
#

RUNSIZE=10%
I did use the official document released today (July 9). That was the reason I only did the upgrade today. I do not have an issue per se to do a new installation. However when I went from 17 to 18 it was not a good memory mostly because I am on a dual booting system and that action lost GRUB for me and I could not even enter Windows which I need for a few things. Had to fight with recovery in Windows and it was a big scare. That is the only reason I am going for upgrades like this. I reinstalled Virtual Box. I only need it to use SAS and nothing else these days.
Everything else I supposed I can live with. I do my best to keep the system as clean as possible, but I am not a Linux expert of any kind. Thank you for your assistance.

MrT
Level 3
Level 3
Posts: 143
Joined: Tue Jun 20, 2017 3:21 pm

Re: Should I worry about this error messages?

Post by MrT »

I ran dmesg | grep error and I received the following:

Code: Select all

    4.917349] EXT4-fs (nvme0n1p6): re-mounted. Opts: errors=remount-ro
inxi - Fxz .. I am not seeing anything suspicious at this point.

rene
Level 16
Level 16
Posts: 6540
Joined: Sun Mar 27, 2016 6:58 pm

Re: Should I worry about this error messages?

Post by rene »

MrT wrote:
Fri Jul 10, 2020 12:37 am
However, the Initramfs error is still there. It does not prevent me from using the PC or anything (so far). For the file you mentioned... I did run the command you suggested, just in case and this is what i see: compress = lz4. Should I change that to gzip?
Yes, try changing that to COMPRESS=gzip and rerunning sudo update-initramfs -u -k all and rebooting. Am not myself on Mint 20 and don't know what's standard and/or why it's bombing out fr you, but his should in any case supposedly fix it.
MrT wrote:
Fri Jul 10, 2020 12:56 am
I ran dmesg | grep error and I received the following:

Code: Select all

[    4.917349] EXT4-fs (nvme0n1p6): re-mounted. Opts: errors=remount-ro
That's not an error, so looking good there then.

The gkr-pam one I didn't really comment on due to the solution probably being rm ~/.config/dconf/user which would cost you many of your per-user settings, whereas the upgrade-path is/was considered to have been taken due to you wanting to preserve as much as possible in the first place. You can also just rename it

Code: Select all

mv ~/.config/dconf/user{,.orig}
and rename it back with

Code: Select all

mv ~/.config/dconf/user{.orig,}
if it didn't help. You'd preferably do so from a virtual-console before logging in, i.e., Ctrl-Alt-F1 from the GUI-login screen which you get either always or after explicitly logging out. If you do it from a terminal in X instead be at least sure to log out and back in.

MrT
Level 3
Level 3
Posts: 143
Joined: Tue Jun 20, 2017 3:21 pm

Re: Should I worry about this error messages?

Post by MrT »

@ rene

The initramfs "issue" is gone as you indicated. So thank you! for that.
Everything seems in order, all my programs work, audios and movies play.

I will try to clean the rest little by little.

If I may take advantage of your expertise, the only other issue I have (and that started really recently in 19.3 and is continuing in 20) is that when I log out, I get some message to the tune of "Failed to unmount old [root]...." it just stays there for 2-3 seconds, a couple of lines.. Not sure what to make of it as it is beyond my level of knowledge...

Thank you.

rene
Level 16
Level 16
Posts: 6540
Joined: Sun Mar 27, 2016 6:58 pm

Re: Should I worry about this error messages?

Post by rene »

I'm afraid I couldn't tell either from that description. What's happening is is that something is refusing to die and release its hold on open files on your drive, disallowing it from being cleanly unmounted. If it's for 3 seconds only it's apparently not something fundamental, but I'd still be able to say anything more at best upon seeing the complete message(s) and likely not then. I tend to suspect the binary Nvidia driver in situations like that but you may not even have Nvidia graphics and/or its binary driver installed. It's in any case without further information fairly impossible to comment on.

Post Reply

Return to “Installation & Boot”