Re: Skipping fsck during boot with systemd?
On Wed 10 Dec 2014 at 08:53:08 +0300, firstname.lastname@example.org wrote:
> On 09/12/2014 22:11, Brian wrote:
> >GRUB can be told about an upcoming fsck and display a message inviting
> >you to choose to do it or not. So you get to know about it in advance;
> >which presumably you didn't know before.
> If grub could tell me if I am going to have electricity supply for
> the next coming hours, that could be a workaround. Otherwise it is
> not a substitute to being able to interrupt the fsck.
I'm glad you brought that up. Barring unannounced power cuts grub will
do it. Of course, it needs to know what you know. If you do not want to
tell it it is powerless to help you.
> >You, as the person best placed, can decide whether the fsck can be
> >afforded based on the status of the power supply. The ability to
> >interupt the fsck after a power cut is of dubious value but, assuming
> >you are aware of your present power reserves and what is drawn from them
> >by an fsck, you could maybe uncross your fingers.
> You must be living in rainbow pony and candy trees world. To
> calculate the remaining time you need to know how much power is
> drown by any specific drive in the raid array being checked, you
> need to know if your batteries have had time to fully recharge after
> the last cut, you need to know their self-discharge level and the
> maximum power they can hold given their age. You also need to know
> if more than one array is going to be checked during this specific
> boot, and the power drown by any other device sharing the same power
> source (systemd can send me donations if it wants me to have
This sounds like an excellent argument for never running fsck at boot.
Have you considered that? There is ample evidence it does you no harm.
Then your perceived problem disappears and you will be happier. Do an
fsck when it is convenient for you.
[Advocacy paragraph snipped].