• Feature requests for installer re: ZFS


    OK, I hope this is the right forum topic to ask this question.

    I am the originator of this thread re: ZFS-on-root installation not booting. The topic is discussed at length there for more info:

    https://forum.antergos.com/topic/8539/zpool-wouldn-t-boot

    I think if the installer had a process at the end where the zpool is disassociated from the installer ISO, e.g. # zpool export <-f> poolname would help relieve this problem. The newly installed OS cannot boot from the zpool due to it ‘belonging’ to another system that created it, the installer ISO.

    I am happy to test any changes as I have a small home lab with resources for many VMs.

    Also, this is not as important obviously, but I’d like to recommend an installer options to automatically add to /etc/modprobe.d/zfs.conf items such as options zfs zfs_arc_max=--size-in-bytes to help rein in memory usage.

    Thank you so much for packaging ZFS with Antergos! It is the single best thing to happen to Linux in the last decade!

    Antergos x86_64 ZFS root w/Cinnamon est Nov 25, 2017 – because after a long week of struggling, I got tired of trying to put Arch on ZFS root…

    "Linux … is more a phenomenon than an OS" - Joekamprad

  • Thanks for the flowers:

    “Linux … is more a phenomenon than an OS” - Joekamprad

    To have some users working on enhance ZFS installation is needed hardly!

    So everybody using #ZFS join here !!!
    @AveryFreeman and to get developers informed use the @ sign: @developers you can also make users informed @joekamprad or @Community-Moderators

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

  • @AveryFreeman said in Feature requests for installer re: ZFS:

    zpool export <-f> poolname

    That’s odd. In my tests this wasn’t necessary, maybe something has changed.

    I’ll trust you and add this at the end of the installation process.

    Cheers!

  • @karasu Thanks so much! Yeah, if nothing else, it couldn’t hurt.

    I’m going to do some testing of the installer today in a VM.

    I also saw an interesting development in the AUR regarding systemd (vs grub) startup with the option to boot from snapshots:

    https://github.com/dasJ/sd-zfs

    Is there any plan to include systemd as a bootloader alternative to grub? I noticed there is a pulldown list in the installer for bootloader type… I will search about this and start another thread if necessary

    Thanks again!

    Edit: Interesting, I found an old thread regarding this - I did not notice a systemd option for booting my Thinkpad, which was set to UEFI-only in the BIOS when I installed Antergos.

    I wonder what happened…

    Antergos x86_64 ZFS root w/Cinnamon est Nov 25, 2017 – because after a long week of struggling, I got tired of trying to put Arch on ZFS root…

    "Linux … is more a phenomenon than an OS" - Joekamprad

  • Systemd-boot is aviable inside installer for EFI Systems, as you say as a option on drop down menu.

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

  • I’m exploring the Cnchi right now in a VM and it looks as if systemd-boot is available for other filesystems, but if the “Use ZFS with this installation” option is ticked, systemd-boot is not available in the bootloader drop-down menu on the following screen.

    Do you think I should start a new thread in @developers regarding this one topic, or would you rather it continue here?

    Thanks

    Antergos x86_64 ZFS root w/Cinnamon est Nov 25, 2017 – because after a long week of struggling, I got tired of trying to put Arch on ZFS root…

    "Linux … is more a phenomenon than an OS" - Joekamprad

  • you can add this on github as enhancement offer

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

  • @joekamprad I created an issue in GitHub:

    https://github.com/Antergos/Cnchi/issues/824

    I can’t get ZFS install to work at all in the current Cnchi 0.14.404 build (!) I’ve tried two different VM platforms (KVM and ESXi), UEFI, MBR, different option combinations, you name it … doesn’t work anymore (at least not for me)

    Glad I got it installed on my Thinkpad when I did, otherwise I might not be here!

    Antergos x86_64 ZFS root w/Cinnamon est Nov 25, 2017 – because after a long week of struggling, I got tired of trying to put Arch on ZFS root…

    "Linux … is more a phenomenon than an OS" - Joekamprad

  • @karasu “I’ll trust you and add this at the end of the installation process.”

    I noticed the ZFS option wasn’t working anymore when I tried 17.12 (Cnchi 0.14.404) - and I discovered that it was because the zpool was being exported before the OS was being installed on it:

    https://github.com/Antergos/Cnchi/issues/824

    If it’s an issue putting it in Cnchi, maybe put the zpool export in a shutdown script for the ISO?

    Antergos x86_64 ZFS root w/Cinnamon est Nov 25, 2017 – because after a long week of struggling, I got tired of trying to put Arch on ZFS root…

    "Linux … is more a phenomenon than an OS" - Joekamprad

  • @karasu ask for confirmation of the cnchi version… The change he take from you, is included in cnchi 0.14.410

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

  • @joekamprad Cool, I will try it out. Thanks!

    Antergos x86_64 ZFS root w/Cinnamon est Nov 25, 2017 – because after a long week of struggling, I got tired of trying to put Arch on ZFS root…

    "Linux … is more a phenomenon than an OS" - Joekamprad

  • I will do a install in a vm too, so i will be able to play around with it

    [updates once a week] = [90% less problems]
    http://gofccyourself.com
    my-blog#k
    how to add system logs
    i3 GNOME

  • Yeah, give it a shot

    If you’re using KVM, I couldn’t get it to install using a virtio drive (e.g. /dev/vda) – only QEMU emulated SATA or SCSI.

    It still has the # zpool export poolname issue that prevents the pool loading on the first boot. I am installing it again right now to see if manually exporting after the install works and prevents the # zpool import -f poolname requirement.

    I put these two issues on github/Antergos/Cnchi, they’re numbers 825 and 826.

    Antergos x86_64 ZFS root w/Cinnamon est Nov 25, 2017 – because after a long week of struggling, I got tired of trying to put Arch on ZFS root…

    "Linux … is more a phenomenon than an OS" - Joekamprad

  • So I tried manually exporting the pool before rebooting the installer ISO, and it booted on the first try without having to manually export

    but I had to navigate to /EFI/antergos_grub/grubx64.efi to get it to boot

    I tried naming the pool that time, so now I’m checking to see if it will boot properly if I don’t name the pool (let the installer name it for me).

    https://github.com/Antergos/Cnchi/issues/827 this time! ;)

    Antergos x86_64 ZFS root w/Cinnamon est Nov 25, 2017 – because after a long week of struggling, I got tired of trying to put Arch on ZFS root…

    "Linux … is more a phenomenon than an OS" - Joekamprad

  • Lots of good testing for the ZFS portion of the installer today:

    1. Naming the pool may prevent EFI from detecting GRUB – might want to disable the option to name the pool for now

    2. Exporting the pool manually before restarting the installer ISO allows the system to boot on the first try without having to type # zpool import -f poolname

    3. For some reason, can’t install using ZFS to a VirtIO drive in KVM - these use the dev name /dev/vda rather than /dev/sda like “normal” drives … something to look into for virtual machine compatibility in the future …

    Antergos x86_64 ZFS root w/Cinnamon est Nov 25, 2017 – because after a long week of struggling, I got tired of trying to put Arch on ZFS root…

    "Linux … is more a phenomenon than an OS" - Joekamprad

  • @AveryFreeman said in Feature requests for installer re: ZFS:

    Thanks!

    1. Naming the pool may prevent EFI from detecting GRUB – might want to disable the option to name the pool for now

    mmmm… that’s odd. I’ll check this one. If I must I’ll disable the option.

    1. Exporting the pool manually before restarting the installer ISO allows the system to boot on the first try without having to type # zpool import -f poolname

    That was included in the latest Cnchi 0.14.410 … it didn’t work?

    1. (…) these use the dev name /dev/vda rather than /dev/sda like “normal” drives

    Yep, that could be it. I’ll check the code asap. Thanks.

  • @karasu

    Naming the pool may prevent EFI from detecting GRUB – might want to disable the option to name the pool for now

    mmmm… that’s odd. I’ll check this one. If I must I’ll disable the option.

    Yes, I was pretty shocked. This was installing on a QEMU SATA emulated drive, so the device name was /dev/sda - so nothinig odd there.

    I don’t think it’s really that big of a deal to be able to name the pool as long as it works, so just disabling the option for now until you find out what’s wrong shouldn’t upset anybody.

    I did not try and update the bootloader on this installation, but I imagine the fix could be as easy as # update-grub, or at most another # mkinitcpio -p before # grub-install etc. However many users may not know about these, or even how to navigate to the EFI partition using the EFI shell.

    Exporting the pool manually before restarting the installer ISO allows the system to boot on the first try without having to type # zpool import -f poolname

    That was included in the latest Cnchi 0.14.410 … it didn’t work?

    Nope, the export worked when I did it manually, but it was not automated by Cnchi – when I rebooted after installation, if I didn’t manually export the pool, the volume would not boot I got the screen that recommended that I invoke # zpool import -f poolname – the same behavior as before.

    (…) these use the dev name /dev/vda rather than /dev/sda like “normal” drives

    Yep, that could be it. I’ll check the code asap. Thanks.

    Thank you! VirtIO drives are considerably faster than QEMU emulated drives - they’re nearly bare-metal speed.

    However for testing, the emulated drive works fine, so this might not be a big deal considering there is probably not a large user base of people trying to emulate Antergos w/ ZFS on KVM. ;) I wouldn’t spend too much time on it if it’s difficult for you.

    One last thing I’d like to mention is that GRUB2 is the only bootloader option at the moment. Do you know how hard it would be to implement systemd boot for ZFS? It would open up a whole new range of possibilities, but I think it might be a little complicated.

    There’s this project I’d like to call your attention to: https://github.com/dasJ/sd-zfs

    It allows choosing a ZFS dataset to boot from using systemd initrd. It also allows booting from snapshots. It could be really helpful for people who have configuration issues, which, let’s be honest, are not that uncommon with Arch repositories.

    That, in combination with properly configured znapzend could make a virtually unbreakable system:
    http://www.znapzend.org/
    https://github.com/oetiker/znapzend

    I’ll be working behind the scenes to try and get this implemented on my own, and then I’d love to share my work with you and see if we can make these part of the Antergos repo. I really think it could be a show-stopper.

    I’m starting by making a PKGBUILD for the AUR of znapzend.
    I’ve got a manual install working, but there are a few issues in Arch/Antergos with the service when trying to install directly from the git clone.

    Edit: nevermind, it’s already in the AUR. I thought I checked but I must’ve been wrong… https://aur.archlinux.org/packages/znapzend/

    What would it take for me to be a package maintainer if Antergos would consider putting znapzend in their repo?

    Thanks for all your wonderful work, I really appreciate it! Very excited…

    Antergos x86_64 ZFS root w/Cinnamon est Nov 25, 2017 – because after a long week of struggling, I got tired of trying to put Arch on ZFS root…

    "Linux … is more a phenomenon than an OS" - Joekamprad

  • @AveryFreeman said in Feature requests for installer re: ZFS:

    Thanks for all your suggestions ;)

    What would it take for me to be a package maintainer if Antergos would consider putting znapzend in their repo?

    I’ll add both packages to our repo. If you find any mistakes or want to do any changes, just create a Pull Request to https://github.com/antergos/antergos-packages with your changes, we’ll be more than glad to add them.

    I’m eager to improve our zfs support in the installer, so give us all suggestions you have, they are really helpful (just be patient with me as I’m really busy these days with exams).

    Cheers!

Posts 18Views 260
Log in to reply