On Sat 03 Sep 2022 at 11:31:27 (-0400), Greg Wooledge wrote: > On Sat, Sep 03, 2022 at 10:06:56AM -0500, David Wright wrote: > > When I booted my system this morning, I naturally selected the FSCK > > option in Grub, and sure enough, I saw a progress bar as the root > > filesystem was checked. Nothing for the others, though. (I use > > systemd. I'm sure it's trivial to edit sysvinit scripts to add -C > > and make sequential if either is not the default.) > > That's great information. It sounds like the fsck of the root file system > is handled inside the initramfs, and that the scripts/whatever which do > it are already passing the -C option.
In view of Sven's post, I should point out my boot line was: linux /boot/vmlinuz-5.10.0-17-amd64 root=LABEL=toto05 ro systemd.show_status=true quiet forcefsck I also wrote: > > The root filesystem should never be checked at the same time as > > others. but I did notice that my /etc/fstab contains: LABEL=toto05 / ext4 errors=remount-ro 0 1 UUID=C027-B627 /boot/efi vfat umask=0077 0 1 /dev/mapper/swap none swap nofail LABEL=toto06 /home ext4 errors=remount-ro,nofail,noauto,user,exec,suid 0 2 LABEL=toto04 /axisbus ext4 errors=remount-ro,nofail 0 2 which has two filesystems marked 1 in field six. AFAIK that is the default. > So all that remains is to find a way to pass that option for the *other* > file systems, which are presumably done outside of the initramfs. > Unfortunately, that's where I hit a wall. It doesn't look like systemd > provides a friendly way to add that option. (I'll be happy to be proven > wrong.) So I changed the sixth fields above from 1 1 2 2 to 1 0 0 2, rebuilt the initfamfs just in case (though fstab is empty there), then rebooted with forcefsck again. I was worried about the fact that I get a 2–3 second blank during boot up, but no fear, when the login prompt appeared, toto04 was still being checked. The appearance is quite different: [ OK ] Started Disk Manager. (42.9% complete) Checking in progress on 1 disk (43.2% complete) Debian GNU/Linux 11 (bullseye) axis 192.168.1.14 … … Checking in progress on 0 disks (100.0% complete) _ Those are the final texts: the numbers were obviously increasing while being displayed, but no visual progress bar. I didn't see anything like that earlier today, nor after I had restored the fstab to normality (forcefsck each time). But I should point out that toto06 has a LUKS-encrypted filesystem on it, which can only be decrypted after I login as user unlock and type the passphrase. Cheers, David.
