/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. Enter the boot menu and choose Advanced Options. Select the Recovery mode and then "fsck". …. To run fsck from a live distribution: Boot the live distribution. Use fdisk or parted to find the root partition name. Open the terminal and run: sudo fsck -p /dev/sda1. Once done, reboot the live distribution and boot your system. fsck is a command-line tool for checking and optionally repairing Linux file systems. To learn more about the fsck command, visit the fsck man page or type man fsck in your terminal. If you have any questions or feedback, feel free to leave a comment. fsck terminal fsck -fy /dev/sda1 if sda1 is the right partition - the prompt will tell you exactly which one requires fsck. After that if the systems boots up you may have another problem with the package management system, so if you open a terminal and type sudo apt-get update you may get an error. Do not worry. Run these commands: system:UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) fsck died with exit status 4. failed (code 4) [] An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. the fsck should be performed in maintenance mode with the root filesystem mount Force fsck on boot using /forcefsck. By creating /forcefsck file you will force the Linux system (or rc scripts) to perform a full file system check. First, login as the root user: $ su -. OR. $ sudo -s. Change directory to root (/) directory [optional]: # cd /. Create a file called forcefsck: On my systems, I would run a script containing grub-reboot 'fsck>fsck' followed by either reboot or /sbin/shutdown -P now (to leave checking until the next day). Yes, it involves either editing the Grub menu, or learning how to change it the official way through the scripts in /etc/grub.d/. For 17.10 or older…. boot to the GRUB menu. choose Advanced Options. choose Recovery mode. choose Root access. at the # prompt, type sudo fsck -f /. repeat the fsck command if there were errors. type reboot. Take a normal micro-USB to USB-A cable (the most common type) & connect it to your PC, plugging the micro-USB into the Pi's USB, (not the PWR_IN). If the Zero is alive, your Windows PC will make a "ding" sound for the presence of new hardware & you should see "BCM2708 Boot" in Device Manager. So log in as root and run fsck manually, without -a or -p options If sda2 is your root partition, you will want to do this from a 'recovery shell' (init 1, or 'recovery mode' grub entry) with the partition mounted ro, or from a livecd, as you shouldn't fsck a mounted filesystem. Linux fsck utility is used to check and repair Linux filesystems (ext2, ext3, ext4, etc.). Depending on when was the last time a file system was checked, the system runs the fsck during boot time to check whether the filesystem is in consistent state. System administrator could also run it manually when there is a In actuality, fsck is simply a front-end for the various file system checkers ( fsck. fstype) available under Linux. The file system-specific checker is searched for in /sbin first, then in /etc/fs and /etc, and finally in the directories listed in the PATH environmen