Hi, Stev, Your fork of Arch-Config zfs script is excellent. Particularly the improvements you made. Please consider adding a feature to create encrypted swap partition. Your thoughts about this? Much appreciated. Thanks

See this link for information and syntax about swap. Perhaps can copy and paste this into your scripts...
https://wiki.archlinux.org/title/User:Kayvlim/Install_UEFI_and_BIOS_compatible_Arch_Linux_with_Encrypted_ZFS_and_ZFSBootMenu#Swap...
Please note sections 2.1.4, 2.2, 2.3.2, 2.3.3, and 4.2 regarding swap.

[The issues tab did not appear in your Arch-Config repo so posted here.]

Hi Stev, I'm looking for a live distribution that comes with both, BTRFS and ZFS. Since the official arch iso comes with BTRFS your iso seemed to be perfect, but unfortunately in the current release BTRFS is not working, /proc/filesystems does not contain it. So I tried to load the module:

modprobe: ERROR: could not insert 'btrfs': Key was rejected by service

I looked for "signature" in the modinfo output of some modules to find details about the key that has been used for signing the modules. But I couldn't find what's causing the problem, because the btrfs module is signed with the same key as all the other (loaded) modules - except for zfs, which is signed with a different key. But the zfs module also works fine. So I have no clue what's wrong with the btrfs module.

Current Behavior

If you start to build a iso file, your dynamic_data/out path will contain files like archlinux-archzfs-linux-git-2023.05.26-x86_64.iso.

Furthermore, there is no *.sha512sum file created

Expected Behavior

After a build, the path dynamic_data/out should contain the following files, fitting to the currently used build options (kernel, package, git):

• archlinux-archzfs-linux-lts-dkms-git.iso
• archlinux-archzfs-linux-lts-dkms-git.iso.sha512sum

The naming is highly dynamic and the notation could be expressed as followed.

`${BASE_NAME}-${KERNEL}-${?USE_DKMS}-{$?USE_GIT_PACKAGE}.iso

The build.sh script should ensure that only one iso file per naming should exist. If there is one, the script should abort and tell the user that he has to do something.
The check should be done before starting the time consuming build.

The current invalid could could be around line 334.

As we can see here we are able to update the profiledef.sh file.

• adapt iso_name
• adapt iso_label
• adapt iso_publisher
• add file_permissions and add arch-config files

Have a look to the official documentation. Another example file to get some ideas is here.

Hi, Also, note that Ubuntu has much more developed zfs on root install scripts (see the Sithuk link below). In the long term, would it save time and effort to fork and adapt the Ubuntu scripts to Arch Linux? Adapting the Sithuk scrips with help from the Kayvlim. Is there anyone in the Arch Linux community who knows how to do this? Would this benefit the community to keep up with Ubuntu? Replies are welcome. Thanks

https://github.com/Sithuk/ubuntu-server-zfsbootmenu

See this link for information and syntax about Arch Linux on ZFS...
https://wiki.archlinux.org/title/User:Kayvlim/Install_UEFI_and_BIOS_compatible_Arch_Linux_with_Encrypted_ZFS_and_ZFSBootMenu#Swap...

Also have a look on holoinstall

• See CPU_VENDOR
• See full_install
• Implement search for configuration.local.sh or use configuration.dist.sh

How about adding a github action for auto building the iso and pushing it to the package registry?

Read this article and check if it has benefits to switch to mkosi.

Given is

ls dynamic_data/out/
archlinux-archzfs-linux.iso  archlinux-archzfs-linux.iso.sha512sum

A build is started and this is the full log

:: Starting cleanup build path
:: Older build detected
:: Do you want to move the files somewhere? [y|N] (n means overwriting, n is default)

:: Finished cleanup build path
:: Starting setup environment
   Previous profile data detected.
   >>/home/.../arch-linux-live-cd-iso-with-zfs/dynamic_data/releng<< exists.
   Cleaning up now ...
   Creating >>/home/.../arch-linux-live-cd-iso-with-zfs/dynamic_data<<.
   Copying content off >>/usr/share/archiso/configs/releng<< to >>/home/.../arch-linux-live-cd-iso-with-zfs/dynamic_data<
:: Finished setup environment
:: Starting evaluating environment
   Updating pacman-init.service
:: Finished evaluating environment
:: Starting adding packages and repository
:: Adding repository and package >>archzfs-linux<<.
   Using following path to the archlive >>/home/.../arch-linux-live-cd-iso-with-zfs/dynamic_data/releng<<.
:: Finished adding packages and repository
:: Starting bulding archiso
[mkarchiso] INFO: Validating options...
[mkarchiso] INFO: Done!
mv: 'archlinux-archzfs-linux.iso' and '/home/.../arch-linux-live-cd-iso-with-zfs/dynamic_data/out/archlinux-archzfs-linux

   Iso created in path:
   >>/home/.../arch-linux-live-cd-iso-with-zfs/dynamic_data/out<<
   --------
   Listing directory content, filterd by >>archzfs<<...
-rw-r--r-- 1 root root  256 Mar 24 20:03 archlinux-archzfs-linux.iso.sha512sum
-rwxrw-r-x 1 root root 867M Mar 20 18:52 archlinux-archzfs-linux.iso
   --------
:: Finished bulding archiso
:: Do you want to run the iso for testing? [y|N

Current behavior

• old files are not removed
• no build was done (build was super fast)

Expected behavior

• old build files where removed
• regular build is done

With kernel 6.2.8 building of zfs-dkms is broken ->
openzfs/zfs#14555

e.g. discussion at
https://aur.archlinux.org/packages/zfs-dkms

openzfs/zfs#14658

Could you provide a last known working (iso) version?

Rather weird issue, maybe this log is helpful to you?

[spacekookie@rayya arch-linux-live-cd-iso-with-zfs]$ ./build.sh 
:: No archiso package installed.
:: We are going to install it now...
error: invalid option: '--search' and '--sysupgrade' may not be used together
:: Previous build data detected.
:: Cleaning up now...
cp: cannot stat '/usr/share/archiso/configs/releng/*': No such file or directory
:: There are 2 archzfs repositories available:
:: Repositories
   0) archzfs-linux   1) archzfs-linux-git

Enter a selection (default=0): 0
:: Building with archzfs repository archzfs-linux
sudo: ./build.sh: command not found

:: Build failed!
:: Cleaning up now...

With the release of 2.5.0, the newly created flag -r can result into an issue.

current behavior

• build.sh -r fails to build an image

error message

warning: cannot resolve "libicuuc.so=71-64", a dependency of "brltty"
:: The following package cannot be upgraded due to unresolvable dependencies:
      brltty

expected behavior

• build.sh -r results in a clean build

I see that the scheduled iso build has failed due to the fact that the zfs-linux package is a version behind the linux package.

warning: cannot resolve "linux=5.19.12.arch1-1", a dependency of "zfs-linux"
:: The following package cannot be upgraded due to unresolvable dependencies:
error: failed to prepare transaction (could not satisfy dependencies)
      zfs-linux

This is a problem that I suspect everyone that has used the archzfs packages is familiar with.

I wonder if we can somehow fix this issue in the script, I see a few possible options:

1. Run the schedule more often.
2. Run the schedule automatically again in one day or 12 hours or something if the scheduled run fails.
3. Take a look at what kernel version zfs-linux requires and if it's older than what's current then fetch it from https://archive.archlinux.org
4. Use the zfs dkms package.

Options 1 and 2 are probably the easiest ones to implement, but are also the least ideal imho since it doesn't really fix the issue and only applies to running the script here on github.
I'm not sure if the dkms package can be used for generating a iso but if it works then I think that might be the best option.
Option 3 feels a bit hackish and I think we should only consider it if dkms doesn't work.

What are your thoughts? Do you see any other possibilities?