-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
e2fsck has unsupported feature(s): FEATURE_C12 #79
Comments
@ikarus23 The version of e2fsck in our inits is a bit outdated. Can you try replacing your init with the one in this release and let me know if you still have the same issue. How to update your init.
|
Hi. Thanks for the detailed instructions. I will try that. Please be patient (It might take some time until I will have the opportunity to test it). |
I'm really glad y'all have both the detail reasoning and instructions, I have moved my home lab up to the above mentioned devel kernel, added both init's per the instructions, even rebuilt fog, and still I get this C12 for a Manjaro capture. I'm a total noob to making my own PXE boot happen, but shouldn't the error have changed? I'm missing something. I have been able to check the manifest for mantic minotaur: |
Thanks for testing. For me it will still be some more time before I can test. But your findings already seem to confirm: the version is still too old. |
@ikarus23 I just release the newest kernels/inits https://github.com/FOGProject/fos/releases/tag/EXP_20240430 Can you try it out and let us know of any issues? |
Hi! Sorry, I'm not sure if I'm at the right pace.
I set up an Archlinux image using ext4 which I wanted to manage with fog. However, the tool for "collecting" or rolling out the image (small Linux environment booed via PXE, fog-client?!) stops with an error:
It seams the ext4 used by Arch has a "modern" filesystem flag, which the version of e2fsck from the PXE image has no support yet.
Is there an easy way to fix this? Do I have to build a "modern" PXE image myself? Thanks for any hints.
The text was updated successfully, but these errors were encountered: