AWS FreeBSD instance won’t come up. Screams for manual fsck.

This is a short write up if after a reset or a reboot your FreeBSD (or Linux) instance doesn’t come online, stalls and
“aws ec2 get-console-output” returns something like that among its lines:

UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

Hope everything is golden at this point.

Posted on June 27, 2015 at 4:07 pm by sergeyt · Permalink
In: FreeBSD

7 Responses

Subscribe to comments via RSS

  1. Written by Philip
    on May 30, 2016 at 11:19 pm
    Reply · Permalink

    Thanks, you saved me a panic attack

    • Written by sergeyt
      on May 30, 2016 at 11:27 pm
      Reply · Permalink

      Hi Philip,
      No worries.
      Thanks, for letting me know it worked for you.

      Cheers.
      BR,
      Sergey

  2. Written by Justin
    on June 15, 2016 at 6:30 am
    Reply · Permalink

    Awesome tip, thanks for the help on this and saving me from lots of panic or rebuilding from backups!!

    • Written by sergeyt
      on June 15, 2016 at 7:56 am
      Reply · Permalink

      Heya, Justin.
      Thanks for stopping by and leaving a comment.
      I’m excited to hear this smallish tip worked for you and saved you from restoring.

      Cheers.
      Sergey

  3. Written by Flagword.net » Another FreeBSD drop into the Digital Ocean
    on November 9, 2016 at 7:30 pm
    Reply · Permalink

    […] was totally useless with its succinct single-worded output – “Output”. Last time when I had a similar issue after another upgrade I at least was able to glean some helpful […]

  4. Written by ChadF
    on April 18, 2018 at 12:14 am
    Reply · Permalink

    I find it odd/annoying that after all these years, AWS still doesn’t provide a simple interactive “serial” console (even if limited to TERM=dumb). Not that a basic in webpage vt100 emulator is beyond Amazon’s abilities.

    • Written by sergeyt
      on April 18, 2018 at 6:56 pm
      Reply · Permalink

      Can’t agree more. The lack of any console support and a blank response from “aws ec2 get-console-output” another day after OS upgrade triggered that “enough is enough” moment and I eventually kissed AWS goodbye.

Subscribe to comments via RSS

Leave a Reply