Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 09-26-2014, 04:08 AM   #1
Registered: Nov 2007
Location: India
Distribution: Debian Stable, Debian Testing
Posts: 218

Rep: Reputation: 27
Debian fsck failed with error code 8


I am getting the following error message at boot:
fsck exited with status code 8
failed(code 8)
[FAIL] File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... failed!
[warn] A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... (warning)
Give root password for maintenance
(or type Control-D to continue):


I am running Debian GNU/Linux Jessie/Sid

I have tried running fsck from the maintenance shell on all partitions, for each of them fsck returns saying they are clean. I have uploaded a "Screenshot" here.

I have also tried to boot from a LiveCD and running fsck manually, errors are not detected there either. I have also tried running fsck through GParted on the LiveCD, it didn't report any errors either.

The partition table is:
# parted -l
Model: ATA ST500DM002-1BD14 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system     Name  Flags
 1      1049kB  512MB   511MB   fat32                 boot
 2      512MB   1012MB  500MB   ext4                  msftdata
 3      1012MB  8012MB  7000MB  ext4                  msftdata
 4      8012MB  11.0GB  3000MB  ext4                  msftdata
 5      11.0GB  15.0GB  4032MB  linux-swap(v1)
 6      15.0GB  15.4GB  400MB   ext4                  msftdata
 7      15.4GB  500GB   485GB   ext4                  msftdata
I am able to boot into the machine and use it fine.

Hope to hear on ways to fix this.

Old 09-26-2014, 11:44 AM   #2
LQ Addict
Registered: Jul 2002
Location: East Centra Illinois, USA
Distribution: Debian stable
Posts: 5,894

Rep: Reputation: 351Reputation: 351Reputation: 351Reputation: 351
Here is a thread at crunchbang that details how one individual solved that problem:

I hope it works for you.

PS: have you looked at the log file /var/log/fsck/checkfs to see what it has to say?

Last edited by bigrigdriver; 09-26-2014 at 11:54 AM.
1 members found this post helpful.
Old 09-29-2014, 01:02 AM   #3
Registered: Nov 2007
Location: India
Distribution: Debian Stable, Debian Testing
Posts: 218

Original Poster
Rep: Reputation: 27

thanks for replying

the contents of /var/log/fsck/checkfs are:
# cat /var/log/fsck/checkfs 
Log of fsck -C -R -A -a 
Mon Sep 29 10:13:49 2014

fsck from util-linux 2.20.1
fsck.fat 3.0.26 (2014-03-07)
/dev/sda1: 3 files, 33/124424 clusters
/dev/sda7: clean, 14070/29589504 files, 35292691/118326016 blocks
/dev/sda6: clean, 16/97536 files, 22572/390144 blocks
/dev/sda3 is mounted.
e2fsck: Cannot continue, aborting.

/dev/sda4: clean, 11320/183264 files, 260334/732416 blocks
fsck exited with status code 8

Mon Sep 29 10:13:50 2014
The Crunchbang user had an issue with the UUID of one of his partitions changing. My UUIDs seem unchanged, either that or I have been spending too much time on the computer
# blkid
/dev/sda5: UUID="8cba2281-c6c4-4de7-8ecc-68cf95044da1" TYPE="swap" 
/dev/sda1: UUID="0502-D895" TYPE="vfat" 
/dev/sda2: UUID="90686687-d42c-46dc-82f6-b483229c8ea7" TYPE="ext4" 
/dev/sda3: UUID="e648b45d-6300-4447-90d8-4bb69536a360" TYPE="ext4" 
/dev/sda4: UUID="985e0647-bfbf-4043-bade-1f2c16f75970" TYPE="ext4" 
/dev/sda6: UUID="07e69fdc-c9ee-49a2-8a8d-9cb463040db7" TYPE="ext4" 
/dev/sda7: UUID="6d68a663-fd68-438b-9847-6181f16c0578" TYPE="ext4"
# cat /etc/fstab
# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=90686687-d42c-46dc-82f6-b483229c8ea7 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=0502-D895  /boot/efi       vfat    defaults        0       1
# /home was on /dev/sda7 during installation
UUID=6d68a663-fd68-438b-9847-6181f16c0578 /home           ext4    defaults        0       2
# /tmp was on /dev/sda6 during installation
UUID=07e69fdc-c9ee-49a2-8a8d-9cb463040db7 /tmp            ext4    defaults        0       2
# /usr was on /dev/sda3 during installation
UUID=e648b45d-6300-4447-90d8-4bb69536a360 /usr            ext4    defaults        0       2
# /var was on /dev/sda4 during installation
UUID=985e0647-bfbf-4043-bade-1f2c16f75970 /var            ext4    defaults        0       2
# swap was on /dev/sda5 during installation
UUID=8cba2281-c6c4-4de7-8ecc-68cf95044da1 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
I am unable to install smartmontools:
# apt-get install smartmontools
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Suggested packages:
  gsmartcontrol smart-notifier
The following NEW packages will be installed:
0 upgraded, 1 newly installed, 0 to remove and 443 not upgraded.
Need to get 0 B/460 kB of archives.
After this operation, 1,650 kB of additional disk space will be used.
(Reading database ... 152903 files and directories currently installed.)
Preparing to unpack .../smartmontools_6.2+svn3841-1.2_amd64.deb ...
Unpacking smartmontools (6.2+svn3841-1.2) ...
dpkg: error processing archive /var/cache/apt/archives/smartmontools_6.2+svn3841-1.2_amd64.deb (--unpack):
 unable to clean up mess surrounding `./usr/sbin/smartd' before installing another version: Read-only file system
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
I think this means that /dev/sda3 i.e., the /usr partition is the one having problems, but running fsck on it from a LiveCD or in maintenance mode shows it as being "clean".

what can i do next?
Old 10-02-2014, 11:33 AM   #4
Registered: Nov 2007
Location: India
Distribution: Debian Stable, Debian Testing
Posts: 218

Original Poster
Rep: Reputation: 27
i am closing the thread as i ended up reinstalling.
Old 10-05-2014, 02:49 PM   #5
Registered: Feb 2006
Distribution: Debian Sid
Posts: 675

Rep: Reputation: 255Reputation: 255Reputation: 255
Had the same problem. Courtesy of the Debian transition to systemd.

For the record it is fixed in initramfs-tools_0.118. Discussion here


debian, fsck

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Debian says "fsck failed" after i installed Pardus2009 ciden Linux - Newbie 2 02-02-2010 09:14 AM
Boot error fsck.reiserfs failed Run Manually anerusmc Linux - Newbie 5 11-03-2009 07:34 PM
FSCK failed error after resetting root password - help please, major problem ! mjwraw SUSE / openSUSE 6 06-19-2009 01:19 AM
fsck dies with error code 1 shirishag75 Linux - Software 3 05-02-2007 08:54 AM
Boot error fsck.reiserfs failed Run Manually anerusmc Linux - Software 0 02-21-2004 09:49 PM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 09:39 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration