|FROM ||From: "Tameek"
|SUBJECT ||R: Re: [NYLXS - HANGOUT] FSCK died with exit status 4
This has been solved. I ended up running fsck with auto-fixing and in verbose mode. Took a nap and when I woke up my lovely Gnome desktop was waiting for me.
Sent via BlackBerry Mobile
From: Ruben Safir
Date: Mon, 12 Oct 2009 22:58:24
Subject: Re: [NYLXS - HANGOUT] FSCK died with exit status 4
On Mon, Oct 05, 2009 at 01:05:35AM -0400, Kevin Mark wrote:
> On Sun, Oct 04, 2009 at 02:23:50AM +0000, tameek-at-gmail.com wrote:
> > Hey,
> > May I please have some assistance? I rebooted my Buntu system and shortly after a file system check I was greeted with a lovely black screen and the aforementioned error.
> > Thanks in advance.
> have you done a manual 'fsck -y'? hopefully you have your data/home backed-up.
> | .''`. == Debian GNU/Linux == | http://kevix.myopenid.com |
> | : :' : The Universal OS | mysite.verizon.net/kevin.mark/ |
> | `. `' http://www.debian.org/ | http://counter.li.org [#238656]|
> |___`-____Unless I ask to be CCd, assume I am subscribed _________|
I don't know how you did it but you killed your file system on the boot
device and you need to do a low level check on the system and just tell
fsck to ignor errors is can't fix and hope that works.
fsck - check and repair a Linux file system
fsck [ -sACVRTNP ] [ -t fstype ] [filesys ... ] [--] [
fsck is used to check and optionally repair one or more Linux
tems. filesys can be a device name (e.g. /dev/hdc1,
mount point (e.g. /, /usr, /home), or an ext2 label or UUID
(e.g. UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root).
mally, the fsck program will try to run filesystems on different
cal disk drives in parallel to reduce total amount time to check
If no filesystems are specified on the command line, and the -A
is not specified, fsck will default to checking
/etc/fstab serial. This is equivalent to the -As options.
The exit code returned by fsck is the sum of the following
0 - No errors
1 - File system errors corrected
2 - System should be rebooted
4 - File system errors left uncorrected
8 - Operational error
16 - Usage or syntax error
32 - Fsck canceled by user request
128 - Shared library error
The exit code returned when multiple file systems are checked
bit-wise OR of the exit codes for each file system that is
In actuality, fsck is simply a front-end for the various file
checkers (fsck.fstype) available under Linux. The file
checker is searched for in /sbin first, then in /etc/fs and
finally in the directories listed in the PATH environment
Please see the file system-specific checker manual pages for
-s Serialize fsck operations. This is a good idea if
checking multiple filesystems and the checkers are in an
active mode. (Note: e2fsck(8) runs in an interactive
default. To make e2fsck(8) run in a non-interactive
must either specify the -p or -a option, if you wish for
to be corrected automatically, or the -n option if you do
Specifies the type(s) of file system to be checked. When
flag is specified, only filesystems that match
checked. The fslist parameter is a comma-separated
filesystems and options specifiers. All of the
this comma-separated list may be prefixed by a negation
'no' or '!', which requests that only those
listed in fslist will be checked. If all of the
fslist are not prefixed by a negation operator, then only
filesystems listed in fslist will be checked.
Options specifiers may be included in the comma
fslist. They must have the format opts=fs-option.
options specifier is present, then only filesystems which
tain fs-option in their mount options field of
be checked. If the options specifier is prefixed by a
operator, then only those filesystems that do not have
in their mount options field of /etc/fstab will be
For example, if opts=ro appears in fslist, then only
listed in /etc/fstab with the ro option will be checked.
For compatibility with Mandrake distributions whose boot
depend upon an unauthorized UI change to the fsck program,
filesystem type of loop is found in fslist, it is treated
opts=loop were specified as an argument to the -t option.
Normally, the filesystem type is deduced by
filesys in the /etc/fstab file and using the
entry. If the type can not be deduced, and there is only
gle filesystem given as an argument to the -t option,
use the specified filesystem type. If this type is not
able, then the default file system type (currently
-A Walk through the /etc/fstab file and try to check all file
tems in one run. This option is typically used from the
system initalization file, instead of multiple
checking a single file system.
The root filesystem will be checked first unless the -P
is specified (see below). After that, filesystems
checked in the order specified by the fs_passno (the
field in the /etc/fstab file. Filesystems with a
value of 0 are skipped and are not checked at all.
with a fs_passno value of greater than zero will be
order, with filesystems with the lowest fs_passno number
checked first. If there are multiple filesystems with the
pass number, fsck will attempt to check them in
although it will avoid running multiple filesystem checks
same physical disk.
Hence, a very common configuration in /etc/fstab files is
the root filesystem to have a fs_passno value of 1 and
all filesystems to have a fs_passno value of 2. This will
fsck to automatically run filesystem checkers in parallel
is advantageous to do so. System administrators might
not to use this configuration if they need to avoid
filesystem checks running in parallel for some reason
example, if the machine in question is short on memory so
excessive paging is a concern.
-C Display completion/progress bars for those filesystems
(currently only for ext2) which support them. Fsck will
the filesystem checkers so that only one of them will
progress bar at a time.
-N Don't execute, just show what would be done.
-P When the -A flag is set, check the root filesystem in
with the other filesystems. This is not the safest thing
world to do, since if the root filesystem is in doubt
like the e2fsck(8) executable might be corrupted! This
is mainly provided for those sysadmins who don't want to
tition the root filesystem to be small and compact
really the right solution).
-R When checking all file systems with the -A flag, skip the
file system (in case it's already mounted read-write).
-T Don't show the title on startup.
-V Produce verbose output, including all file
mands that are executed.
Options which are not understood by fsck are passed
filesystem-specific checker. These arguments must
arguments, as there is no way for fsck to be able to
guess which arguments take options and which don't.
Options and arguments which follow the -- are treated
system-specific options to be passed to the file
Please note that fsck is not designed to pass
plicated options to filesystem-specific checkers. If
doing something complicated, please just execute the
specific checker directly. If you pass fsck some horribly
plicated option and arguments, and it doesn't do
expect, don't bother reporting it as a bug. You're almost
tainly doing something that you shouldn't be doing with
Options to different filesystem-specific fsck's are not
If in doubt, please consult the man pages of the
checker. Although not guaranteed, the following options are
by most file system checkers:
-a Automatically repair the file system without any questions
this option with caution). Note that e2fsck(8) supports
backwards compatibility only. This option is mapped to
-p option which is safe to use, unlike the -a option
file system checkers support.
-n For some filesystem-specific checkers, the -n option will
the fs-specific fsck to avoid attempting to repair any
but simply report such problems to stdout. This is
true for all filesystem-specific checkers. In
fsck.reiserfs(8) will not report any corruption if given
option. fsck.minix(8) does not support the -n option at
-r Interactively repair the filesystem (ask for
Note: It is generally a bad idea to use this option if
fsck's are being run in parallel. Also note that
e2fsck's default behavior; it supports this option for
compatibility reasons only.
-y For some filesystem-specific checkers, the -y option will
the fs-specific fsck to always attempt to fix any
filesystem corruption automatically. Sometimes an expert
able to do better driving the fsck manually. Note that
filesystem-specific checkers implement this option. In
lar fsck.minix(8) and fsck.cramfs(8) does not support
option as of this writing.
Theodore Ts'o (tytso-at-mit.edu)
The fsck program's behavior is affected by the following
If this environment variable is set, fsck will attempt
all of the specified filesystems in parallel,
whether the filesystems appear to be on the same device.
is useful for RAID systems or high-end storage systems
those sold by companies such as IBM or EMC.)
This environment variable will limit the maximum number of
system checkers that can be running at one time. This
configurations which have a large number of disks to avoid
starting too many file system checkers at once, which
overload CPU and memory resources available on the
this value is zero, then an unlimited number of processes
spawned. This is currently the default, but future
fsck may attempt to automatically determine how many file
checks can be run based on gathering accounting data
PATH The PATH environment variable is used to find file system
ers. A set of system directories are searched first:
/sbin/fs.d, /sbin/fs, /etc/fs, and /etc. Then the set of
tories found in the PATH environment are searched.
This environment variable allows the system
override the standard location of the /etc/fstab file.
also use for developers who are testing fsck.
This environment variable allows the early boot scripts to
ride the standard location of the /etc/blkid.tab file.
file contains a mapping between UUID, LABEL and TYPE
device nodes. The information in the blkid.tab might be
after a reboot if hardware was changed or disks were
fstab(5), mkfs(8), fsck.ext2(8) or e2fsck(8),
fsck.minix(8), fsck.jfs(8) fsck.xfs(8), fsck.xiafs(8)