System boots only in recovery mode - Error message: Failed to start Load Kernel Module

English Install/Boot/Login
1

Hello,

I can currently get to the GUI login only through the recovery-mode. The battery ran out and the laptop shutdown (or perhaps hibernated?). After rebooting, I got the following error:

sparse file not allowed

followed by
**
[FAILED] Failed to start Load Kernel Module
See ‘systemctl status systemd-modules-load.service’ for details.**

Here’s is the output for ‘systemctl status systemd-modules-load.service’:

● systemd-modules-load.service - Load Kernel Modules


   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: active (exited) since Thu 2017-06-15 19:38:55 EDT; 11min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 886 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS)
 Main PID: 886 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/systemd-modules-load.service

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
~

Before this incident, the laptop was rebooting fine after the most recent upgrades. So, I am not sure if this post about grubenv applies in this case. (Link: https://forums.opensuse.org/showthread.php/506811-Grub-message-quot-sparse-file-not-allowed-quot-and-continuing-in-recovery-mode) I have not tried to do anything to grubenv or grub.cfg.

Here are the contents of grubenv:

# GRUB Environment Block


# WARNING: Do not edit this file other than by grub2-editenv
saved_entry=openSUSE Tumbleweed
##########################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################

Here are the contents of grub.cfg:

   save_env -f "${env_block}" next_entry


   fi
   set boot_once=true
else
   set default="${saved_entry}"
fi

if  x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if  "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if  -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    if  "${env_block}" ] ; then
      save_env -f "${env_block}" saved_entry
    fi

  fi
}

function load_video {
  if  x$feature_all_video_module = xy ]; then
    insmod all_video

System information:
Tumbleweed (XFCE) kernel version: 4.11.4-1-default, filesystem: btrfs (/home partition encrypted LVM)
Repositories enabled: Only official repositories + Google chrome (no Packman)
BIOS info: no UEFI

(My linux experience level: determined novice)

Questions:

  1. What additional information can I provide to get to the bottom of this?

  2. Is there anything I can do through YaST’s bootloader options to solve this?

Thank you.

(PS: This is my first post on the forum. If I am making any mistakes please let me know, and I’ll readily correct them.)

2

I wonder what sparse file is being referenced.
Is virtualization involved either as a HostOS or GuestOS?
If not, then I’d suspect that a sparse file related to your initrd has either been damaged or a setting misconfigured.

In any case, have you tried upgrading again?
(Of course with a reliable power connection).

TSU

3

Thank you for your reply, TSU.

Is virtualization involved either as a HostOS or GuestOS?

No, Tumbleweed is the only OS on this system.

have you tried upgrading again?

I upgraded using the most recent ISO. Towards the end of the upgrade, I got
the following error message:

**
Error**
Execution of the command ""/usr/sbin/grub2-install","-target=i386-pc","force","-skip-fs-probe","/dev//sda"]]" failed. 

Exit code: 1

Error output: installing for i386-pc-platform.
/usr/sbin//grub2-install: error: the drive hd0 is defined multiple times in the device map /boot/grub2/device.map

After I clicked OK on that error message dialog box, the rest of the installation went fine.

I can still login through recovery-mode.

How should I proceed?

Thanks.