Failed to load rescue target after fsck

Things happened:

  1. Get stuck on the black screen, press the power button to shutdown and reboot.

  2. Get the message “filesystem on /dev/sda3 requires a manual fsck”.

  3. Run command fsck -yf /dev/sda3 and exit.

  4. Get the message “Failed to load rescue target, freezing”.

Things I have tried for solving this problem:

  1. Add in the kernel line and boot. Still got the “Failed to load rescue target, freezing” message.

  2. Add in the kernel line and boot. Still got the “Failed to load rescue target, freezing” message.

  3. In GRUB, run commands set boot=(hd0,gpt3), set prefix=(hd0,gpt3)/boot/grub, insmod normal and normal, back to the menu, get additional “Ubuntu” and “Ubuntu Advanced Options”, choose either of the four options (two “Ubuntu” and two “Ubuntu Advanced Options”) will get the “Failed to load rescue target, freezing” message.

  4. Add init=/bin/bash in the kernel line, boot, and run the command mount -n -o remount,rw /. Not able to run fsck: “cannot execute binary file: Exec format error”. Not able to run passwd: “Permission denied password unchanged”.

The full error message when trying to boot normally: (typed manually)

[0.048909] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/evrgnini-245) [1.226507] Couldn't get size: 0x800000000000000e /dev/sda3: recovering journal /dev/sda3: clean, 139776/6545408 files, 1649034/26163200 blocks [4.271298] systemd[260]: /lib/systemd/system-generators/netplan failed with exit status 127. [4.420902] systemd[1]: Failed to load default target: No such file or directory [4.420938] systemd[1]: Failed to load rescue target: No such file or directory [!!!!!!] Failed to load rescue target, freezing. [4.429053] systemd[1]: Freezing execution. 


Windows 10 / Ubuntu 18.04 dual systems

If more information is needed, please tell me.

Unity settings and programs got messed up after fsck disk check

While doing my normal activity on my Ubuntu 16.04 (Unity) machine I noticed that Firefox stopped playing sounds from any tab (Applications tab in Sound Settings had something unknown to me listed several times and nothing else). Also the keyboard layout switching stopped working, while the indicator in the panel worked fine. I decided to reboot and after that saw the BusyBox prompt telling me that I had errors in my file system and needed to run fsck.
A similar thing happened to me about a year ago, but this time after running it on the specified drive and pressing y to every found error I typed reboot, logged back into my system and saw that the fonts are different from default and the theme switched back to Ambiance (from Radiance).
Nautilus changed it’s layout to (probably) non-patched gnome version, with nothing in the global menu. The ‘Recent’ folder returned despite still being turned off in the settings.
Image Viewer now has both global menu and local, under the title bar menu. Firefox got it’s icon changed to a folder.
Some programs wouldn’t start at all, including gedit and gnome-terminal. Running them in xterm outputs:

Failed to import the site module Traceback (most recent call last):   File "/usr/lib/python3.5/", line 78, in <module>     import os   File "/usr/lib/python3.5/", line 27, in <module>     import stat as st ImportError: No module named 'stat' 

Between some more reboots the fonts and the theme had partially changed to the selected, and then back again.
Each time after logging in the mouse buttons wouldn’t respect the settings (mine are set to RMB as primary), the settings page is correct, but after a while the screen goes black for a second and it is back to normal.

What may have caused this and how can I fix it? Thank you.

Sorry if something isn’t clear, I’m writing this late.

Additional, but possibly unrelated information:
Some strange bug causes my computer to turn on right after the shut-down. I dual-boot with Win7 and this only happens with Ubuntu, and only for the past 2 or so years. After a cursory search I was not able to find a solution to this and got used to turning it off from the back of the case right after it starts again.
During the last several months I had 3 times when my computer suddenly rebooted while I was doing something. I hadn’t yet investigated that.
The disk with Ubuntu is just ~45 gb and currently I work with mostly less than 400 mb on the ‘/home’ partition and 1.2 gb at ‘/’.
The hardware is also mostly more than 10 years old.

How to run a thorough check on a computer drive with `fsck`?

I have booted a computer from a Ubuntu USB stick and I want to use fsck to make a thorough check of the entire /dev/sdb2 disk. Just running

sudo fsck /dev/sdb2 

returns almost immedeately. But I want to check the entire disk. What options to use to do so (and to have verbose information to see the check is still going on)?


  • Thorough check of the harddrive /dev/sdb2
  • Verbose information
  • Using fsck (or some similar command which is included in a Ubuntu 18.04 live iso)

fsck on non-existent UUID on every boot

I’ve got a problem with XUbuntu 19.04. On every boot, it runs a file system check that times out after 1:30 (killed by systemd) before the boot process continues.

It all started after I installed Debian 10.0 alongside (removed after only one attempt to boot, as it didn’t recognize my video).

The tricky part:

The UUID that it’s trying to check does not exist.

So I can’t simply do a fsck on that drive once it’s finished booting. There is no “trigger file” for “all” file system checks at the root.

I cannot do “tune2fs -l <…>” or “tune2fs -c” on the drive because the drive (the UUID) does not exist.

I already restored the partition to an image from before the issues began – and the file system checks continued. So it seems to be the partitions (why and how and what’s changed?) and not Ubuntu, but… I also have Fedora installed on this computer and it boots without any strange file system checks just fine.

I also tried rebooting into single user mode – the drive’s UUID does not exist there either.

A photo of the file system check:

How can I troubleshoot this? Obviously, I’d like the system to stop trying to fsck a non-existent drive.

The root filesystem on /dev/sda3 requires a manual fsck

When I turn on my computer, it sends me directly to the GRUB menu. When I select Ubuntu, it sends me to a black screen. When I select Advanced Options, it sends me to a series of commands where I get an error: enter image description here / dev / sda3: Unexpected Inconsistency; RUN fsck MANUALLY (i.e., without -a or -p options) fsck exited status code 4 The root filesystem on / dev / sda3 requires a manual fsck BusyBox v1.27.2 (Ubuntu 1: 1.27.2-2ubntu3) built-in shell (ash) Enter ‘help’ for a list of built-in commands.

my system ka s asking me for user name when booting. fsck is done. the problem arisen when shutdown was not proper. how do i log in into my computer

I can’t access the terminal or the other resources in system.

Only thing is to press the power button and reach the login window again

Usernames such as HP, root and my name was given in upper and lower case letters

How to force Google Compute Engine ubuntu instance to do fsck?

I have an instance in Google Compute Engine (cloud server) running ubuntu 16.04.

I noticed filesystem corruption on the root filesystem as follows:

==>ls -l data/vocabulary/ ls: cannot access 'data/vocabulary/Makefile': Permission denied ls: cannot access 'data/vocabulary/vocab-count.txt': Permission denied ls: cannot access 'data/vocabulary/vocab-random-access.db': Permission denied ls: cannot access 'data/vocabulary/vocab-list.txt': Permission denied ls: cannot access 'data/vocabulary/vocab.db': Permission denied ls: cannot access 'data/vocabulary/CVS': Permission denied total 0 d????????? ? ? ? ?            ? CVS -????????? ? ? ? ?            ? Makefile -????????? ? ? ? ?            ? vocab-count.txt -????????? ? ? ? ?            ? vocab-list.txt -????????? ? ? ? ?            ? vocab-random-access.db -????????? ? ? ? ?            ? vocab.db 

However, my attempts to “force fsck” and reboot were unsuccessful. I would touch file “/forcefsck” and reboot but fsck just simply would not occur.

I also tried to set the fsck remaining count and that also does not seem to be effective.

What should I do to proceed with fsck?