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

Thread: /dev/sdc1 will be checked for errors at next reboot

  1. #1
    Join Date
    Jan 2009
    Beans
    4

    /dev/sdc1 will be checked for errors at next reboot

    Hi

    Everytime i log into my server, I get the message Displayed "/dev/sdc1 will be checked for errors at next reboot"

    However, despite many reboots this message does not clear.

    I cannot run FSCK on this partition as it is the boot partition.

    I would like the device to get checked at reboot, any ideas how I can trigger this check , and that might clear the message

    Thanks

    Si

  2. #2
    Join Date
    Apr 2007
    Beans
    2,578
    Distro
    Ubuntu

    Re: /dev/sdc1 will be checked for errors at next reboot

    If it is mounted to root (/) then
    Code:
    sudo touch /forcefsck
    will trigger the check on next reboot. In general, you put this file (forcefsck) in the root of the partition you want to be checked.

  3. #3
    Join Date
    Jan 2009
    Beans
    4

    Smile Re: /dev/sdc1 will be checked for errors at next reboot

    Many thanks,

    I tried that on both / and /boot, but still see the report.

    I only see sdc1 mentioned on /boot.

    Any ideas please

    thanks



    ~$ df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/mapper/emeaserver-root
    53G 5.8G 45G 12% /
    none 1.9G 700K 1.9G 1% /dev
    none 1.9G 0 1.9G 0% /dev/shm
    none 1.9G 628K 1.9G 1% /var/run
    none 1.9G 4.0K 1.9G 1% /var/lock
    /dev/ida/c0d0p1 338G 143G 178G 45% /raid/1
    /dev/sdc1 228M 180M 36M 84% /boot
    /dev/mapper/raid0
    214G 85G 119G 42% /raid/0
    /dev/mapper/lvm_md1-raid2
    135G 100G 29G 78% /raid/2

  4. #4
    Join Date
    Apr 2007
    Beans
    2,578
    Distro
    Ubuntu

    Re: /dev/sdc1 will be checked for errors at next reboot

    Such configuration is not familiar to me. You may try to check whether the partition is effectively checked or not, and whether the check proceeded normally. There are logs under /var/log/fsck. If that is the case, then there is only the problem with this message appearing, but it could not do harm.

  5. #5
    Join Date
    Aug 2006
    Beans
    13

    Re: /dev/sdc1 will be checked for errors at next reboot

    No news about this behaviour? i'm havin the same issue, i tried to force the check but it is impossible..

  6. #6
    Join Date
    Jun 2006
    Location
    Melbourne, Australia
    Beans
    265
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: /dev/sdc1 will be checked for errors at next reboot

    This could be the motd bug where the system has already done the fsck check but the message is still stuck in you motd.tail file.

    Try deleting /etc/motd.tail and then restart

  7. #7
    Join Date
    Mar 2006
    Location
    Houston, TX
    Beans
    95
    Distro
    Dapper Drake Testing/

    Re: /dev/sdc1 will be checked for errors at next reboot

    this apparently still goes on

    i checked my fstab, it has non-zero values for the check field

    but it wont check them, it tells me ALL of my volumes will be checked but has never checked a single one ever. the fsck logs say none have ever occured

    also im using a raided boot and raided volumes
    Left here since creation...
    Forgotten in the river of time...

  8. #8
    Join Date
    May 2008
    Beans
    61

    Re: /dev/sdc1 will be checked for errors at next reboot

    I also met the same problem but the reported partition is not the partition mounted to /

    After rebooting serveral times, the problem is still there. And then I remove the the failure info in /etc/mtd file, and then I reboot. The problem sound have gone!
    Bill Z
    stat -c %a filename

  9. #9
    Join Date
    Apr 2008
    Location
    NC
    Beans
    142
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: /dev/sdc1 will be checked for errors at next reboot

    I'm having this same issue on my raid5 /dev/md127..

    It keeps saying on next boot it will be check...

  10. #10
    Join Date
    May 2005
    Beans
    40
    Distro
    Ubuntu Development Release

    root volume will be checked for errors at next reboot

    I had this too:

    I booted with 0 and 1 as sixth field for the / partition in /etc/fstab, that made no difference.
    There was no /etc/motd.tail, removing /etc/motd gave back the same message (fsck at next reboot) after reboot.

    It took an "apt-get update && apt-get upgrade" + "apt-get install libgnome2-0 linux-headers-server linux-image-server linux-server linux-tools" + a touch /forcefsck and a reboot to resolve it, it is now on
    Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-33-generic x86_64)

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
  •