1

Everything worked fine last time I used Solus, and now I cannot boot because of the error below.

Let's try to solve it without using a live USB.

enter image description here

enter image description here

**Failed to start File System Check on /dev/disk/by-partuuid/5ff8cfe6-53e1-43b1-9275-dc6f24ad812a**
  • What is your assessment of what is wrong? Can you try to type/include the relevant lines from journalctl as text in your question in code formatting? (datetime and hostname prefixes can be removed for improved reading). – Pro Backup Dec 25 '17 at 13:02
  • @ProBackup the problem is that i cannot initialize the operative system, i dont know how to copy the information of the photo – Ginés Díaz Dec 25 '17 at 13:09
6

According to the man page, fsck's error code 4 means "Filesystem errors left uncorrected".

This is not good. It means that the file system is corrupted beyond what is safe to automatically repair on boot, so manual intervention is required.

As the error message on your screen says, you need to manually run fsck to attempt to fix the errors. You can probably do that from the initramfs root prompt (try fsck /dev/sda6). If not, you'll need a rescue disk like gparted. IMO, Clonezilla also serves as a good rescue disk - it's got just about every file-system related utility you could possibly need.

Alternatively, since your Linux box is running systemd, you could interrupt the GRUB boot process and edit the linux kernel's command line to make system perform a forced fsck:

  • before grub times out and boots a kernel, press a key to cancel the timeout countdown.
  • move the cursor as required to the entry you want to edit (probably the default menu entry).
  • press e to enter grub's editor.
  • scroll through the editor and look for the line that starts with linux followed by a whole bunch of kernel options.
  • add fsck.mode=force fsck.repair=preen to the end of that line.
  • press F10 or Ctrl-X to accept the changes and boot that menu entry.

Note: these grub edits are not persistent across reboots. They're temporary one-time changes for this boot session only.

Also note: it's possible that your filesystem is corrupted beyond repair. fsck will do its best to get the fs back to a consistent state, but it's not magic: it can't repair or restore corrupted data.

  • Looks like fsck could be run from the emergency mode prompt, so it is not necessary to mess with GRUB. – multithr3at3d Dec 25 '17 at 15:01
  • @multithr3at3d - yes, that's why i mentioned the initrams root prompt first. – cas Dec 25 '17 at 15:06
  • Isn't an initramfs shell different from the systemd rescue target terminology-wise? Just to clarify. – multithr3at3d Dec 25 '17 at 15:18
  • at the point that error will come up, it's still in an initramfs - the rootfs hasn't been mounted. systemd doesn't replace initramfs, it uses it. – cas Dec 25 '17 at 15:26
  • thank you guys very much! I will try and tell you as soon as I get home. – Ginés Díaz Dec 25 '17 at 17:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.