Arch Linux

penguin

Member

From: Gotham City

Registered: 2010-12-31

Posts: 163

No partitions fsck'ed at bootup anymore (/home partition encrypted)

Problem: fsck used to check my partitions every 20-something mounts at boot up. Now it seems to be deactivated. (No check for hundreds of boots)
Background: +1 year ago I encrypted my /home partition. I'm not sure if that has anything to do with it, or I might not have kept up with the systemd changes? (I follow all instructions posted on arch mainpage when upgrading)
Goal: I'd like fsck to run on boot up on both my unencrypted "/" partition, and on my encrypted "/home" partition every N-mounts, like it used to (i.e. the default behaviour after installation).

Here's my fstab:

# NOTE: I now use /etc/crypttab to remap /dev/sda8->/dev/mapper/home
#       and /dev/sda6->/dev/mapper/swap
#
#<file sys>         <dir>           <type>      <options>       <dump>   <pass>
tmpfs              /tmp            tmpfs       nodev,nosuid     0         0
/dev/sda7          /               ext4        rw,relatime,data=ordered 0 1

#/dev/sda8         /home           ext3        defaults,noatime 0         2
/dev/mapper/home   /home           ext4        defaults,noatime 0         2
#/dev/sda6         none            swap        sw               0         0
/dev/mapper/swap   none            swap        sw               0         0

/dev/sr0           /media/cdrom0   udf,iso9660 user,noauto,nofail,ro    0 0

#user=any user can [u]mount, umask111=remove executable rights., dmask000=add executable for folders.
/dev/sdb1          /media/disk  auto    user,noauto,rw,umask=111,dmask=000 0 0

Here's my /etc/crypttab

# crypttab: mappings for encrypted partitions
#
# Each mapped device will be created in /dev/mapper, so your /etc/fstab
# should use the /dev/mapper/<name> paths for encrypted devices.
#
# The Arch specific syntax has been deprecated, see crypttab(5) for the
# new supported syntax.
#
# NOTE: Do not list your root (/) partition here, it must be set up
#       beforehand by the initramfs (/etc/mkinitcpio.conf).

# <name>     <device>                                        <password>          <options>
home          /dev/sda8                                       none                luks
swap          /dev/disk/by-id/ata-ST9500420AS_5VJE3KFA-part6  /dev/urandom        swap,cipher=aes-cbc-essiv:sha256,size=256
# data1       /dev/hda3                                       /etc/mypassword2
# data2       /dev/hda5                                       /etc/cryptfs.key
# vol         /dev/hdb7                                       none

# useful to check swap: "cat /proc/swaps",  "free -m"
#
# BIG FUCKING WARNING: use /dev/disk/by-id/ for swap or else risk swap getting
#                      placed on the wrong device, thus wiping the wrong partition!
# https://wiki.archlinux.org/index.php/Dm-crypt_with_LUKS/Swap_Encryption

I have fsck in my /etc/mkinitcpio.conf

MODULES="i915 ahci ac"

BINARIES=""

FILES=""

HOOKS="base udev autodetect modconf block filesystems keyboard fsck"

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,804

Re: No partitions fsck'ed at bootup anymore (/home partition encrypted)

Have you tried this?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

penguin

Member

From: Gotham City

Registered: 2010-12-31

Posts: 163

Re: No partitions fsck'ed at bootup anymore (/home partition encrypted)

Have you tried this?

I'll give that a try, thanks!

In your link it says "mkinitcpio offers you the option to fsck your root filesystem before mounting it via the fsck hook. If you do this, you should mount root read-write via the appropriate rw kernel parameter".

When I check what the actual boot paramter was, I see:

[~/]% cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=b1245bf1-ef01-43b1-a752-0dc607aba0b7 rw ro

It says both "rw" and "ro"?

In my /etc/default/grub it looks like it's setting it to be read only. What is the recommended default? I realize I haven't done any "arch" in a long time, I feel like I'm more than a little rusty on my arch-fu. I'm not aware of changing the GRUB_CMDLINE_LINUX_DEFAULT.

Either way, this is what I've got in /etc/default/grub, does it look "sane"? Or can my fsck not running be traced to something wrong in it?

GRUB_DEFAULT=0
GRUB_TIMEOUT=2
GRUB_DISTRIBUTOR="Arch"

# ro = root is read only
GRUB_CMDLINE_LINUX_DEFAULT="ro"
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=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=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep