I am new to the forum and at best a novice user , at best I can install manjaro and do a few very basic commands .
What I am experiencing is every time I go to restart or power down I get a message for a brief second saying:
sd-umoun: Failed to unmount /oldroot: Device or resource busy
shutdown: Failed to finalize file systems, ignoring
I have been living with this for some time , tried different kernels , different NVIDIA drivers .
As of 1-19-2021 I just got a major upgrade and installed it new drivers and kernal 22.214.171.124
the problem does not seem to efect anything , just annoying . Tried googling the issue seems to be a common issue with no fix I understand
ok I opened a terminal and typed " sudo nano /etc/mkinitcpio.conf"
and at the bottom of the page added " HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)"
ran " sudo mkinitcpio -P"
Sorry I probably messed it up or misunderstand
I also added " #hooks=shutdown " to the file and tried that nothing
oh well probably beyond my abilities
sudo mkinitcpio -P
I get "Invalid config: No hooks found"
I have 2 etc/mkinitcpio.conf files in my machine
one is that has a output that reads like this
# vim:set ft=sh
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(piix ide_disk reiserfs)
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS=(base udev autodetect block filesystems)
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev block filesystems)
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS=(base udev block mdadm encrypt filesystems)
## This setup loads an lvm2 volume group on a usb device.
# HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)
# HOOKS=(base udev block lvm2 filesystems)
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
#HOOKS="base udev autodetect modconf block keyboard keymap resume filesystems shutdown "
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
# Additional options for the compressor
Then their is another that is called " OSTREE mkinitcpio.conf
ok I believe it is fixed , the messages are gone ! Yahhoo !! I am not getting on startup some message like " cleaned blocks 0000 on nvme"
but I had to add to the 1st line on the config file " HOOKS=(base)"
then add "
HOOKS="shutdown base systemd ostree autodetect modconf block filesystems keyboard fsck shutdown "
On the second line
When I tried just adding only the
"HOOKS="shutdown base systemd ostree autodetect modconf block filesystems keyboard fsck shutdown "
the cleaning blocks on boot up would disappear so I added it back in
Hi, I used the guide here to disable the watchdog on my system: Arch Watchdog:
To add kernel parameter: sudo nano etc/default/grub
on the line starting GRUB_CMDLINE_LINUX_DEFAULT=" I added nowatchdog, so my line read for example GRUB_CMDLINE_LINUX_DEFAULT="quiet nowatchdog udev.log_priority=3" and saved the file
ran sudo update-grub to update my grub
Just to make sure, I also blacklisted iTCO_wdt by creating the file /etc/modprobe.d/blacklist.conf and added blacklist iTCO_wdt in that file. You may already have a blacklist.conf here, or other other .conf files; I believe you can just add as many .conf files with modules to blacklist in as you wish (so you could add e.g. nowatchdog.conf if you don’t want to edit anything already present), but I prefer to keep everything in the same file
Watchdog should no longer be present after reboot!
that did it and all I had to do was make the blacklist.conf file . all messages are now gone . Did not have to do all You suggested just make the file
thanks to all who helped it has been a learning experience