f2fs root
by andygoth from LinuxQuestions.org on (#5J692)
I'm trying to boot an f2fs root filesystem, but ELILO hangs with the following on the screen:
Code:ELILO v3.16 for EFI/x86_64
.
Loading kernel vmlinuz... done
Loading file initrd.gz...doneAt the moment, /boot is ext4, but I doubt that's necessary because ELILO gets all of the files it needs from EFI, but I went ahead and did that anyway out of desperation.
I ensured the f2fs partition is aligned on a 2-megabyte boundary, though once again I don't think that's necessary. I saw reference to it here and guessed 2-megabyte because this says 2MB. But it also says (reading between the lines) that it puts padding between the superblock and the first checkpoint in order to align the checkpoint.
I made the initrd.gz like so:
Code:mkinitrd -c -k 5.12.6 -m vmd:f2fsI also tried adding ext4 to that list, but since the kernel doesn't need to read /boot at boot time (kernel and initrd are already loaded before the kernel starts), that shouldn't matter.
Really, I'm just trying things and guessing since I don't have any diagnostics to go on.
One very important data point: everything works fine when I use an ext4 root. This suggests I have ELILO configured properly.
This is with kernel version 5.12.6. I had the same problem with 5.11.something and put this project aside for a while as a result, but this evening I had some time to try again.
Code:ELILO v3.16 for EFI/x86_64
.
Loading kernel vmlinuz... done
Loading file initrd.gz...doneAt the moment, /boot is ext4, but I doubt that's necessary because ELILO gets all of the files it needs from EFI, but I went ahead and did that anyway out of desperation.
I ensured the f2fs partition is aligned on a 2-megabyte boundary, though once again I don't think that's necessary. I saw reference to it here and guessed 2-megabyte because this says 2MB. But it also says (reading between the lines) that it puts padding between the superblock and the first checkpoint in order to align the checkpoint.
I made the initrd.gz like so:
Code:mkinitrd -c -k 5.12.6 -m vmd:f2fsI also tried adding ext4 to that list, but since the kernel doesn't need to read /boot at boot time (kernel and initrd are already loaded before the kernel starts), that shouldn't matter.
Really, I'm just trying things and guessing since I don't have any diagnostics to go on.
One very important data point: everything works fine when I use an ext4 root. This suggests I have ELILO configured properly.
This is with kernel version 5.12.6. I had the same problem with 5.11.something and put this project aside for a while as a result, but this evening I had some time to try again.