Skip to content

Instantly share code, notes, and snippets.

@chrisarusso

chrisarusso/gist:96d509665aeb5291617d

Created July 30, 2015 02:03
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save chrisarusso/96d509665aeb5291617d to your computer and use it in GitHub Desktop.
Save chrisarusso/96d509665aeb5291617d to your computer and use it in GitHub Desktop.
Download ZIP
Raw
gistfile1.txt
Freeing unused kernel memory: 1428K (ffffffff81f35000 - ffffffff8209a000)
Write protecting the kernel read-only data: 14336k
Freeing unused kernel memory: 600K (ffff88000196a000 - ffff880001a00000)
Freeing unused kernel memory: 32K (ffff880001df8000 - ffff880001e00000)
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevdudevd[1589]: starting version 175
. ok
[....] Synthesizing the initial hotplug events...random: nonblocking pool is initialized
done.
[ ok ] Waiting for /dev to be fully populated...done.
[ ok ] Setting preliminary keymap...done.
[....] Activating swap...Adding 262140k swap on /dev/xvdb. Priority:-1 extents:1 across:262140k SSFS
done.
EXT4-fs (xvda): re-mounted. Opts: (null)
[....] Checking root file system...fsck from util-linux 2.20.1
/dev/xvda contains a file system with errors, check forced.
/dev/xvda: Duplicate or bad block in use!
/dev/xvda: Multiply-claimed block(s) in inode 1556624: 6226837
/dev/xvda: Multiply-claimed block(s) in inode 1556732: 6226837
/dev/xvda: (There are 2 inodes containing multiply-claimed blocks.)
/dev/xvda: File /home/www/comowater.com/production/site/wordpressroot/wp-content/cache/db/000000/options (inode #1556624, mod time Wed Jul 29 20:19:47 2015)
has 1 multiply-claimed block(s), shared with 1 file(s):
/dev/xvda: /home/www/comowater.com/production/site/wordpressroot/wp-content/cache/db/000000/options/2db (inode #1556732, mod time Wed Jul 29 20:21:24 2015)
/dev/xvda:
/dev/xvda: 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
[FAIL with the root filesystem mounted in read-only mode. ... failed!
[....] The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D to terminate the m
[warnnance shell and restart the system. ... (warning).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment