[Bug 219382] Re: fsck not run on boot if on battery power

Phillip Susi psusi at ubuntu.com
Mon Jun 3 19:00:01 UTC 2013


The automatic periodic checks were intentionally suppressed when on
battery and were generally an unneeded waste of time, which is why they
have now been removed completely.  The skip when on battery power also
seems to have been removed.  If something is actually wrong with your
fs, then you should boot into rescue mode and choose the friendly fsck
option from the menu, rather than rely on rebooting until the automatic
periodic check happens.


** Changed in: sysvinit (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/219382

Title:
  fsck not run on boot if on battery power

Status in “sysvinit” package in Ubuntu:
  Invalid

Bug description:
  I can see that this is deliberate - a 'feature' - in that
  /etc/init.d/checkroot.sh (and checkfs.sh) has an explicit check for
  being on batteries and then skips fsck if it is.

  The problem is that if you are on batteries, it becomes difficult to
  run fsck on the root partition.

  So, you're on battery power, something goes wrong, the file system is
  corrupted / the journal is not consistent, and... you're stuffed. When
  you next reboot, the file system won't be mended, it'll be left in a
  mess.

  Why yes, this did affect me (thanks to a problem with Hardy alpha and
  beta causing kernel panics and lock ups). What I ended up having to do
  was editing the relevant bit out of the script.

  I can't imagine skipping fsck saves any power - if the file system is
  ok, running it is extremely short. But ultimately, if the file system
  is in a mess, it needs to be sorted, on boot, whether you're on
  battery power or not.

  The alternative of booting into maintenance mode, manually umounting
  the partition, then mounting read-only, then fsck-ing is beyond most
  users.

  So please either lose this 'feature' or provide a way around it (check
  if a key is held down?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/219382/+subscriptions




More information about the foundations-bugs mailing list