Bug report IPFire 2.27 (x86_64) - Core Update 167 Development Build: master/24c8e6a6

Hello,
I just upgraded to the test release 167. And did - as usual - a “Reboot & check filesystem”. This time the system did not come back after the reboot…

Serial console showed the following:

[...]
EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
dracut: Checking ext4: /dev/disk/by-uuid/15592274-7e1a-44a4-a764-7accb30db27e
dracut: issuing e2fsck -a -f  /dev/disk/by-uuid/15592274-7e1a-44a4-a764-7accb30db27e
e2fsck: invalid dracut Warning: e2fsck returned with 16
option -- ' '
Udracut Warning: *** An error occurred during the file system check.
sage: e2fsck [-pdracut Warning: *** Dropping you to a shell; the system will try
anyrcdfktvDFV] [dracut Warning: *** to mount the filesystem(s), when you leave the shell.
-b superblock] [dracut Warning:
-B blocksize]
                [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
                [-E extended-options] [-z undo_file] device

Emergency help:
 -p                   Automatic repair (no questions)
 -n                   Make no changes to the filesystem
 -y                   Assume "yes" to all questions
 -c                   Check for bad blocks and add them to the badblock list
 -f                   Force checking even if filesystem is marked clean
 -v                   Be verbose
 -b superblock        Use alternative superblock
 -B blocksize         Force blocksize when looking for superblock
 -j external_journal  Set location of the external journal
 -l bad_blocks_file   Add to badblocks list
 -L bad_blocks_file   Set badblocks list
 -z undo_file         Create an undo file
dracut Warning: e2fsck returned with 16
dracut Warning: *** An error occurred during the file system check.
dracut Warning: *** Dropping you to a shell; the system will try
dracut Warning: *** to mount the filesystem(s), when you leave the shell.


dracut Warning:


Generating "/run/initramfs/rdsosreport.txt"
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.

To get more debug information in the report,
reboot with "rd.debug" added to the kernel command line.

Dropping to debug shell.

(Repair filesystem):/#

Doing a “e2fsck -a -f /dev/disk/by-uuid/15592274-7e1a-44a4-a764-7accb30db27e” did not show any error (as expected):

Dropping to debug shell.

accb30db27eesystem):/# e2fsck -a -f  /dev/disk/by-uuid/15592274-7e1a-44a4-a764-7
/dev/disk/by-uuid/15592274-7e1a-44a4-a764-7accb30db27e: 30998/3842048 files (0.2% non-contiguous), 889776/15341878 blocks
(Repair filesystem):/# echo $?
0
(Repair filesystem):/#

After ending the debug shell the system booted without any problems.

This happens on every “Reboot & check filesystem”.

Regards,
Uwe

Already been raised as a bug by another forum user #12842

See thread
https://community.ipfire.org/t/possible-issue-with-forced-filesystem-check-on-167-upgrade/7681

1 Like