[clug] Debian Jessie file system checking on boot up

[George at Clug]

    Scott,

Does your second email suggest removing the "quiet" parameter?

This is what I currently have;
GRUB_CMDLINE_LINUX_DEFAULT="quiet fsck.mode=force"


# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        95G   46G   44G  52% /
udev             10M     0   10M   0% /dev
tmpfs           3.2G  8.5M  3.2G   1% /run
tmpfs           7.9G     0  7.9G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           7.9G     0  7.9G   0% /sys/fs/cgroup

# cat /etc/default/rcS | grep FSCK
FSCKFIX=yes

# cat /etc/default/grub 
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet fsck.mode=force"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that
obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD
...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports
via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter
to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"


At Wednesday, 06-04-2016 on 16:48 Scott Ferguson wrote:


Not sure whether you fixed the problem or not. It's an intriguing
question so I thought I'd spent a little time trying to create a
non-default GRUB entry that would allow me to reboot a remote headless
server into a forced full fsck of the root (ext4) file system (I don't
have any production servers with single slice file systems (as it'd
take
forever to fsck), but I'm not going to fiddle with production servers
anyway so I'll test with a single slice VM headless server spun up
just
for this purpose).

Just quickly, check that you haven't inherited from Squeeze fsck on
boot
disabled with:-
grep FSCK /etc/default/rcS

(If you installed Jessie from scratch you should not have that
handicap,
unless you followed random intertubes suggestions).

On 05/04/16 21:36, George at Clug wrote:
>     Scott,
> 
> I get the following results from the below commands, any idea why
fsck
> is not running?, or how to fix it?
> 


Kind regards

-- 
    A: Because we read from top to bottom, left to right.
    Q: Why should I start my reply below the quoted text?

    A: Because it messes up the order in which people normally
read text.
    Q: Why is top-posting such a bad thing?

    A: The lost context.
    Q: What makes top-posted replies harder to read than
bottom-posted?

    A: Yes.
    Q: Should I trim down the quoted part of an email to which I'm
reply

http://www.idallen.com/topposting.html

-- 
linux mailing list
linux at lists.samba.org
https://lists.samba.org/mailman/listinfo/linux