Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Not checking for errors at boot.

  1. #1
    Join Date
    Feb 2009
    Beans
    86

    Not checking for errors at boot.

    Hi all,

    After I upgraded my desktop to 11.04, I started receiving this message everytime I ssh'd in:

    Code:
    *** /dev/sdb1 will be checked for errors at next reboot ***
    *** /dev/sdc1 will be checked for errors at next reboot ***
    *** /dev/sdd1 will be checked for errors at next reboot ***
    *
    Unfortunately, it doesn't seem to check for errors at the boot. I have rebooted it many times since it first started (a couple of weeks back), with the hope that over time the problem would somehow rectify itself. It hasn't (and I guess usually doesn't!).

    Thanks in advance.

  2. #2
    Join Date
    Feb 2008
    Location
    Texas
    Beans
    29,809
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Not checking for errors at boot.

    Quote Originally Posted by djmac View Post
    Hi all,

    After I upgraded my desktop to 11.04, I started receiving this message everytime I ssh'd in:

    Code:
    *** /dev/sdb1 will be checked for errors at next reboot ***
    *** /dev/sdc1 will be checked for errors at next reboot ***
    *** /dev/sdd1 will be checked for errors at next reboot ***
    *
    Unfortunately, it doesn't seem to check for errors at the boot. I have rebooted it many times since it first started (a couple of weeks back), with the hope that over time the problem would somehow rectify itself. It hasn't (and I guess usually doesn't!).

    Thanks in advance.
    Hi, I do not know why you are getting that message but ubuntu checks for errors every 30 boot ups.

  3. #3
    Join Date
    Feb 2009
    Beans
    86

    Re: Not checking for errors at boot.

    Right, can you manually force it to? I guess that it is not that big an issue. Just wait until the 30th boot up?

  4. #4
    Join Date
    Feb 2008
    Location
    Texas
    Beans
    29,809
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Not checking for errors at boot.

    Quote Originally Posted by djmac View Post
    Right, can you manually force it to? I guess that it is not that big an issue. Just wait until the 30th boot up?
    Hi, you can run this command from the terminal to check your desk. I do not know how to make it check at start up.
    Code:
    sudo badblocks /dev/sda1
    That is if your ubuntu is on /sda1 other wise you would make it /sda plus the number that your ubunt partiton is on.

  5. #5
    Join Date
    Feb 2010
    Location
    Washington, DC Area
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Not checking for errors at boot.

    Try this command
    Code:
    sudo touch /forcefsck
    to check the filesystem for errors on your next boot up.
    Last edited by dcsoldschool53; May 28th, 2011 at 11:52 PM. Reason: adding more info

  6. #6
    Join Date
    Feb 2009
    Beans
    86

    Re: Not checking for errors at boot.

    Thanks,

    I tried:

    Code:
    sudo touch /forcefsck
    And rebooted, but it didn't do any checks at boot (also get the same message when ssh'ing in).

    Also tried:

    Code:
    sudo badblocks -v /dev/sda1
    (Would perhaps recommend adding verbosity just so you know what is happening - it took a long time)

    But I also still got the same message - is the problem actually an issue?

  7. #7
    Join Date
    May 2011
    Beans
    1

    Re: Not checking for errors at boot.

    ive came across the same behvior,on 11.04 while opening bybou
    i tried out sudo badblocks /-v dev/sda1 and fsck -y /dev/sda1 which didn't work
    did you succeed in fixing it,

  8. #8
    Join Date
    Apr 2008
    Beans
    10

    Re: Not checking for errors at boot.

    I have the same problem. Anyone ever find a fix for this?

    This is just one of the many problems I had updating to Natty but this seems to be the only one I have yet to get around or fix.

  9. #9
    Join Date
    Apr 2008
    Beans
    10

    Re: Not checking for errors at boot.

    Fixed my own problem. Posting in case others come across this thread they can try for themselves. Hope it helps someone.

    I was getting:
    *** /dev/sdb will be checked for errors at next reboot ***
    All I had to do to fix this was edit my fstab file.
    sudo vi /etc/fastab
    Then for me I changed the last "0" (zero) to a 2 at the end of the line mounting my HDD.

    Before:
    /dev/sdb /mnt/hdd1 ext3 defaults 0 0
    After:
    /dev/sdb /mnt/hdd1 ext3 defaults 0 2
    Then when you reboot your PC it will check that harddrive for errors. After it completes this check you can just go back and edit your fstab file and put the 2 back to a 0.

    Now from then on you shouldn't get that error.

  10. #10
    Join Date
    Nov 2007
    Beans
    3

    Re: Not checking for errors at boot.

    I checked the 6th field of my fstab file for the /dev/sda1 and /dev/sda2 (the ones the message referenced) and found it was already set to "2". I changed them to zero, rebooted, and no change. I changed them back to "2", entered "sudo touch /forcefsck" and did a hard shutdown. When I turned the machine back on the messages were gone.

    I'd done most of this before, but hadn't edited my fstab file or done a hard reboot. I don't KNOW what made the difference this time so I'm posting every step and hoping something in there helps.

    John

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •