{SOLVED} Unmount error messages on power down

[solarbear]

I have three spinners, two for OS and one for storage. I keep getting these unmount errors when i shut down. they appear in a flash before the machine powers off

here is my inxi

Code: Select all

  Kernel: 5.4.0-91-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: MATE 1.24.0 info: mate-panel wm: marco 1.24.0 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: Dell product: OptiPlex 990 v: 01 serial: <filter> 
  Chassis: type: 6 serial: <filter> 
  Mobo: Dell model: 06D7TR v: A00 serial: <filter> BIOS: Dell v: A20 
  date: 05/05/2017 
CPU:
  Topology: Quad Core model: Intel Core i7-2600 bits: 64 type: MT MCP 
  arch: Sandy Bridge rev: 7 L2 cache: 8192 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54278 
  Speed: 1596 MHz min/max: 1600/3800 MHz Core speeds (MHz): 1: 1596 2: 1596 
  3: 1596 4: 1596 5: 1596 6: 1593 7: 1596 8: 1596 
Graphics:
  Device-1: NVIDIA GF114 [GeForce GTX 560] vendor: ZOTAC driver: nvidia 
  v: 390.144 bus ID: 01:00.0 chip ID: 10de:1201 
  Display: x11 server: X.Org 1.20.11 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa compositor: marco v: 1.24.0 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: GeForce GTX 560/PCIe/SSE2 v: 4.6.0 NVIDIA 390.144 
  direct render: Yes 
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
  vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  chip ID: 8086:1c20 
  Device-2: NVIDIA GF114 HDMI Audio vendor: ZOTAC driver: snd_hda_intel 
  v: kernel bus ID: 01:00.1 chip ID: 10de:0e0c 
  Sound Server: ALSA v: k5.4.0-91-generic 
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Dell driver: e1000e 
  v: 3.2.6-k port: 4040 bus ID: 00:19.0 chip ID: 8086:1502 
  IF: eno1 state: down mac: <filter> 
  Device-2: Ralink RT5572 Wireless Adapter type: USB driver: rt2800usb 
  bus ID: 3-1:2 chip ID: 148f:5572 serial: <filter> 
  IF: wlx9cefd5faa6a1 state: up mac: <filter> 
Drives:
  Local Storage: total: 2.96 TiB used: 106.67 GiB (3.5%) 
  ID-1: /dev/sda vendor: Western Digital model: WD20EZRX-00D8PB0 
  size: 1.82 TiB speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> 
  rev: 0A80 scheme: MBR 
  ID-2: /dev/sdb vendor: Western Digital model: WD2500AAKX-753CA0 
  size: 232.89 GiB speed: 6.0 Gb/s serial: <filter> rev: 1H15 scheme: MBR 
  ID-3: /dev/sdc vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
  speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> rev: A750 scheme: MBR 
Partition:
  ID-1: / size: 915.40 GiB used: 106.67 GiB (11.7%) fs: ext4 dev: /dev/sdc5 
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A gpu: nvidia temp: 48 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 29% 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/atareao-atareao-focal.list 
  1: deb http://ppa.launchpad.net/atareao/atareao/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
  1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/home:stevenpusser.list 
  1: deb http://download.opensuse.org/repositories/home:/stevenpusser/xUbuntu_20.04/ /
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com uma main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/opera-stable.list 
  1: deb https://deb.opera.com/opera-stable/ stable non-free #Opera Browser (final releases)
Info:
  Processes: 243 Uptime: 7h 08m Memory: 15.59 GiB used: 2.01 GiB (12.9%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: mate-terminal inxi: 3.0.38

[SMG]

I keep getting these unmount errors when i shut down.

What unmount errors?
Are they showing in /var/log/syslog? If not, can you take a photo of them?

[solarbear]

the messages flash for a split second on power down. something like 3 lines of "failed to unmount" i am looking at the syslog now. I can't really discern unmount error messages from the piles of lines. i will keep looking..i have the search field, any key words to plug in for a search?

so far though, my OS is working good, but i thought this would be something common.

[AndyMH]

i have the search field, any key words to plug in for a search?

In a terminal:

Code: Select all

grep failed /var/log/syslog

[SMG]

the messages flash for a split second on power down. something like 3 lines of "failed to unmount"

If they flash by so fast you can not even get a photo of them, they are unlikely to be a problem.

It's possible they are the "failed to unmount old root" message which is a common one people see and relates to a bug in systemd version Mint uses.

[solarbear]

Thanks for the assurance that it is something that can be called a minor nuisance, i was afraid that it could lead to a hdd corruption or similar.

Code: Select all

$ grep failed /var/log/syslog
Dec  8 15:38:36 pOOter thermald[883]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
Dec  8 15:38:36 pOOter thermald[883]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
Dec  8 15:38:36 pOOter thermald[883]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml"
Dec  8 15:38:36 pOOter udisksd[886]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Dec  8 15:39:23 pOOter pulseaudio[1142]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Dec  8 15:39:31 pOOter NetworkManager[854]: <warn>  [1638995971.2266] sup-iface: failed to cancel p2p connect: P2P cancel failed

[SMG]

$ grep failed /var/log/syslog

My guess as to why the message did not show up is because that message did not happen until after the log stopped. Sometimes the signal to shut down the log completes before the computer is completely powered down. It can take time for the hardware to power down after the operating system sends the signal to shut down. That is why I mentioned taking a photo because sometimes that is the only way to see the message.