SCIENTIFIC-LINUX-USERS Archives

January 2016

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Brandon Vincent <[log in to unmask]>
Reply To:
Brandon Vincent <[log in to unmask]>
Date:
Sat, 16 Jan 2016 19:11:40 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
On Sat, Jan 16, 2016 at 3:38 PM, ToddAndMargo <[log in to unmask]> wrote:
> How do I force an fsck on next reboot on all
> three of the following partitions:
>
>      /
>      /boot
>      /home

First check if all of the systemd-fsck services are enabled. Running
blkid(8) should provide you with the UUID for all of your partitions.

systemctl is-enabled systemd-fsck-root.service and systemctl
is-enabled systemd-fsck@ (use tab competition to check all the
partitions) should output "static". If they don't, enable the
service(s) using systemctl enable.

At this point, all you have to do is append the kernel parameters with
fsck.mode=force and fsck.repair=preen or fsck.repair=yes. preen is the
default and will only fix safe issues that don't require user
interaction, while yes will repair more serious problems and may not
be a great idea unattended.

Brandon Vincent

ATOM RSS1 RSS2