Possible issue with forced filesystem check on 167 upgrade

Getting Started with IPFire Updates Trouble
1

This morning I upgraded from 166 to 167. Once the install completed with no apparent errors, I used the GUI option to reboot with a forced filesystem check. The unit rebooted, but failed during the reboot due to an apparent syntax error in the e2fsck command. The error was reported as an unknown option ’ ', and there did appear to be an extra space immediately after the “-f” and before the filesystem was specified. I executed the command manually and was able to continue the boot successfully.

I’m in the middle of my workday, so I can’t re-test this scenario at the moment, but if someone else on 167 could execute a reboot with forced filesystem check, I’d appreciate it if this issue can be confirmed before I report it.

2

Screenshots of the test VM after clicking “Reboot&check filesystem”
(when the IPFire starts up)

obraz

obraz

edit:

After typing shutdown -rF now in the console after logging in
(when the IPFire starts up)

obraz

obraz

obraz

1 Like
3

Thank you very much; I guess that it is confirmed. I’ll take care of the bug report and reference this thread with your screenshots.

UPDATE: Bug #12842 submitted.

1 Like
4

@tphz: Did you try to manually perform e2fsck -a -f /dev/disk/<…> ? That’s what I did immediately after the initial crash.

5

No, I just checked to see if the error persists.

1 Like
6

Yes, I had the same issue

7

Hi,

since this just came up elsewhere: This bug has been fixed in the stable release of Core Update 167.

Thanks, and best regards,
Peter Müller

2 Likes