When I try to boot my laptop, I get this message: /dev/sda1 contains a file system with errors, check forced. Inodes that were part of a corrupted orphan linked list found.

/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) fsck exited with status code 4 The root filesystem on /dev/sda1 requires a manual fsck

Busybox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built in shell (ash) Enter 'help' for a list of built-in commands.

(initramfs) _

when I write: fsck/dev/sd1 I get the message: /bin/sh:fsck/dev/sd1

What shall I do???

  • 1
    you need a space and drive desegnation fsck /dev/sda1 – ravery Dec 8 '17 at 7:34
  • 1
    I suggest you run fsck from a live CD as well. In addition, as a caution, when you have to run fsck manually it is sometimes a sign your hard drive is failing. If you have not done so already, make a back up of any data you do not wish to loose ASAP, and run smartmontools - help.ubuntu.com/community/Smartmontools – Panther Dec 8 '17 at 16:16
  • @Panther That would be an good answer :) – vidarlo Dec 8 '17 at 17:57

You need space between command and argument. The command is fsck, and the argument is the device /dev/sda1. Try fsck /dev/sda1. Note that there is a space between fsck and /dev/sda1.

Additionally you may want to use fsck -y /dev/sda1 to answer yes automatically to any questions fsck asks.

  • thank you, I've done so. Now my desktop is black?? I wait – Silke Dec 9 '17 at 9:45
  • Nothing happens...what shall I do now? Help!! – Silke Dec 9 '17 at 10:03
  • Now I see: /dev/sda1:***** FILE SYSTEM WAS MODIFIED ***** – Silke Dec 9 '17 at 10:13
  • and /dev/sda1: 2353330/4825088 files (0.2% non-contiguous), 17131265/19277824 blocks – Silke Dec 9 '17 at 10:14
  • Then you have fixed your file system. Run fsck once more, and reboot. – vidarlo Dec 9 '17 at 10:35

Alternatively you use fsck /dev/sda2; then type y to any question fsck asks; there must be a space between fsck and /dev. look keenly at the GNU of your Ubuntu if its /sda1 or sda2 reported having the error. fsck the specific sda which is reported to be having the error it works!

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.