Re: Arch installation image::when will support for F2FS be added

Re: Arch installation image::when will support for F2FS be added

I just did a f2fs installation with April.1 official live media + f2fs tools from AUR built on my previous installation. I guess a customized archboot may do it too?

What I did was to 1) install the precompiled AUR pkg during installation, 2) mkfs.f2fs for rootfs + mkfs.ext2 for boot, 3) modprobed "f2fs" before mounting rootfs, 4) put "f2fs" in mkinitcpio.conf's module list before mkinitcpio---actually I failed to do the last step and was dropped to the emergency shell several times, but it can be overcome by manually mounting rootfs to new_root.

Currently it runs well. But I do get some errors displayed about fsck during bootup: not sure if it's the f2fs or ext2 partition, because it is too quick. Anyone know how to check/fix that? Thanks.

mount, install and chroot as per official installation guideadd f2fs to modules section (should be empty) in /etc/mkinitcpio.confremove fsck from hooks section (since f2fs doesn't have fsck yet)re-generate the initramfs image

mkinitcpio -p linux

after you're done with everything, reboot and voila, there you have it.

Re: Arch installation image::when will support for F2FS be added

Currently it runs well. But I do get some errors displayed about fsck during bootup: not sure if it's the f2fs or ext2 partition, because it is too quick. Anyone know how to check/fix that? Thanks.

Think of it this way. The fsck hook exists because it is checking the rootfs before having it mounted. The other partitions are checked by systemd during the boot process. This is because although the rootfs can be checked after the initramfs if mounted ro, if errors are found a reboot is required. So it makes sense to check the other filesystems/mount points, but the rootfs should be done from the initramfs.

Therefore, the error is because there is no f2fs fsck binary. As the initramfs should not be trying to check your ext2 /boot anyway, asn this will be done by systemd. You can probably safely take the fsck hook out of mkinitcpio.conf, as it will not do anything until/unless a fsck is released for f2fs.

This is the same for btrfs, as the btrfsck is not meant to be run regularly like other filesystems, and would produce a nearly identical error if the fsck hook is present with a btrfs root.

Edit:

jasonwryan wrote:

pkoretic wrote:

Add repo which contains yaourt to /etc/pacman.conf

Other than that, this should be a wiki page...

I did enjoy you blog post about this. I never used yaourt when I started with Arch, picking packer instead (at random). But this required me to actually learn how to use makepkg to get it installed, and it didn't take vary long for me to discover cower (and meat for when I am lazy).

Re: Arch installation image::when will support for F2FS be added

This was just (supposed to be) an easy example, of course those who know and want, will do It manually, the same as I did it my first, second, third and fourth time.I've put some simple steps to the wiki - https://wiki.archlinux.org/index.php/F2fsHopefully somebody will improve it, I always find it unnatural when writing something on wiki.