Re: forced fsck
On Wed, Jan 20, 2016 at 5:36 PM, ToddAndMargo wrote: > Thank you! I have wondered about that for several years. > > Any idea if the touch thing applies to SL 7 as well? I'm pretty certain as I explained earlier that the forcefsck method is for non-systemd distributions (I could be wrong). Distributions that use forcefsck will usually check all filesystem listed in /etc/fstab except NFS filesystems with the mount option _netdev (which are mounted after the network is brought up). Brandon Vincent
Re: forced fsck
On 01/20/2016 05:18 AM, Michael Tiernan wrote: On 1/19/16 5:10 PM, ToddAndMargo wrote: This is what I used on SL6. I was never able to figure out whether is "all" the partitions or just "/" partition. It is all that are mounted by the /etc/fstab entries. Thank you! I have wondered about that for several years. Any idea if the touch thing applies to SL 7 as well?
Re: forced fsck
On 1/16/16 10:18 PM, ToddAndMargo wrote: Any way to do it once Don't know if it changed since SL6 but touch /forcefsck Then at boot time if there, the fsck will run on all file systems and the flag is deleted. -- << MCT >> Michael C Tiernan xmpp:mtier...@mit.edu +1 (617) 324-9173 MIT - Laboratory for Nuclear Science - http://www.lns.mit.edu High Perf Research Computing Facility at The Bates Linear Accelerator Please avoid sending me MS-Word or MS-PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
Re: forced fsck
On Sun, Jan 17, 2016 at 12:21 PM, Konstantin Olchanski wrote: > On Sat, Jan 16, 2016 at 02:38:23PM -0800, ToddAndMargo wrote: >> sl 7.2 (Yipee!) >> >> How do I force an fsck on next reboot on all >> three of the following partitions: >> >> / >> /boot >> /home >> > > Boot from installer image into rescue mode and run fsck. Or use "touch /forcefsck; reboot" ? It works pretty well with ext* based filesystems.
Re: forced fsck
On Sat, Jan 16, 2016 at 02:38:23PM -0800, ToddAndMargo wrote: > sl 7.2 (Yipee!) > > How do I force an fsck on next reboot on all > three of the following partitions: > > / > /boot > /home > Boot from installer image into rescue mode and run fsck. Presumably you are doing this because there is trouble, and in case of trouble, regular boot with "forced fsck requested" will just tell you "run fsck by hand" and dump you into single user mode, which is not as nice as the rescue mode in the installer (no VTs, no job control, no network, etc). -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: forced fsck
On 17 January 2016 04:18:22 CET, ToddAndMargo wrote: >On 01/16/2016 07:10 PM, Brandon Vincent wrote: >> On Sat, Jan 16, 2016 at 8:06 PM, ToddAndMargo >wrote: >>> Would this be a one time fsck or every boot? >> >> As long as the kernel parameter(s) is passed during boot (manually >> entered or set as the default in GRUB) a fsck should run every time. >> >> Brandon Vincent >> > >Any way to do it once? When you boot the box and see the grub menu, select the proper line with arrow keys and hit the E key on the keyboard; that enters the edit mode. Use arrow keys again to locate the kernel command line and append these options at the end of the line. IIRC correctly, it is ctrl-X to boot with these changes. But these changes are only temporary and only valid for the current boot. -- kind regards, David Sommerseth
Re: forced fsck
On 01/16/2016 07:10 PM, Brandon Vincent wrote: On Sat, Jan 16, 2016 at 8:06 PM, ToddAndMargo wrote: Would this be a one time fsck or every boot? As long as the kernel parameter(s) is passed during boot (manually entered or set as the default in GRUB) a fsck should run every time. Brandon Vincent Any way to do it once? -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~
Re: forced fsck
On Sat, Jan 16, 2016 at 8:06 PM, ToddAndMargo wrote: > Would this be a one time fsck or every boot? As long as the kernel parameter(s) is passed during boot (manually entered or set as the default in GRUB) a fsck should run every time. Brandon Vincent
Re: forced fsck
On 01/16/2016 06:11 PM, Brandon Vincent wrote: On Sat, Jan 16, 2016 at 3:38 PM, ToddAndMargo 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 Would this be a one time fsck or every boot?
Re: forced fsck
On Sat, Jan 16, 2016 at 3:38 PM, ToddAndMargo 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
