Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7758847
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 1, 20262026-06-01T13:28:21+00:00 2026-06-01T13:28:21+00:00

I have an ubuntu server (11.10) on a single-board computer that occasionally is subject

  • 0

I have an ubuntu server (11.10) on a single-board computer that occasionally is subject to being powered down unexpectedly. When it is booted afterward, fsck prompts the user to hit ‘f’ to check the drive. Because this server does not normally have a monitor and keyboard connected, and the only way to normally access it is through SSH, this is very inconvenient.

Is there a way of guaranteeing that on boot any required fsck check can be done without user input? Basically, I want it to always run ‘fsck -y’ on boot (when problems are detected), rather than prompting the user for input.

Thanks!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-01T13:28:23+00:00Added an answer on June 1, 2026 at 1:28 pm

    So I found two related solutions to my problem:

    I’m not sure these are valid everywhere, but they work on ubuntu server 11.10.

    /etc/default/rcS looks like this:

    #
    # /etc/default/rcS
    #
    # Default settings for the scripts in /etc/rcS.d/
    #
    # For information about these variables see the rcS(5) manual page.
    #
    # This file belongs to the "initscripts" package.
    
    # delete files in /tmp during boot older than x days.
    # '0' means always, -1 or 'infinite' disables the feature
    TMPTIME=0
    
    # spawn sulogin during boot, continue normal boot if not used in 30 seconds
    SULOGIN=no
    
    # do not allow users to log in until the boot has completed
    DELAYLOGIN=no
    
    # assume that the BIOS clock is set to UTC time (recommended)
    UTC=yes
    
    # be more verbose during the boot process
    VERBOSE=no
    
    # automatically repair filesystems with inconsistencies during boot
    FSCKFIX=no
    

    Make sure that that final line instead reads

    # automatically repair filesystems with inconsistencies during boot
    FSCKFIX=yes
    

    Another barrier I had to the system just booting always without requiring user intervention was the grub bootloader screen waiting for user input after a failed / interrupted boot.

    This requires editing the grub setup file in
    /etc/grub.d/00_header

    /etc/grub.d$ grep -r -n -C3 timeout ./
    ./00_header-229-    fi
    ./00_header-230-fi
    ./00_header-231-
    ./00_header:232:make_timeout ()
    ./00_header-233-{
    ./00_header-234-    cat << EOF
    ./00_header-235-if [ "\${recordfail}" = 1 ]; then
    ./00_header:236:  set timeout=-1
    ./00_header-237-else
    ./00_header:238:  set timeout=${2}
    ./00_header-239-fi
    ./00_header-240-EOF
    ./00_header-241-}
    

    simply change line 236 to

    set timeout = 0
    

    and line 238 to

    set timeout = 0
    

    This causes the system to never pause while booting. After editing the file, run
    sudo update-grub
    to get the changes implemented in the /boot/grub/grub.cfg file.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We have a web-app, that we're deploying to a remote Ubuntu server. The app
I have a server that is running Ubuntu Linux Server Edition. I once had
I have an Ubuntu natty server running on Amazon EC2. My problem is that
I have a ubuntu server which I've locked down to only HTTP, HTTPS and
I have an Ubuntu Oneiric server that runs several instances of ffmpeg (each one
I have an ubuntu server that i have some scripts that need to run
I have Maven on Ubuntu server. It seems to try lots and lots of
I have fresh installation of RabbitMQ on a linux/ubuntu server. Lets say the server
I have two websites running on my own root server (ubuntu/nginx/php-fpm). Now I want
I have setup the basic LAMP server on Ubuntu 11.10 and had a few

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.