From 484f4b6becb97fda72df485053dcd4fe8572cdd0 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 25 Jan 2026 08:34:47 -0600 Subject: Phase 4.3 complete: btrfs validation testing - Non-LUKS tests all pass (single, mirror, stripe) - LUKS reboot automation attempted but blocked (encrypt hook limitation) - Added manual LUKS verification task to todo.org - Session notes updated --- todo.org | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'todo.org') diff --git a/todo.org b/todo.org index 7871590..e2fd34c 100644 --- a/todo.org +++ b/todo.org @@ -24,6 +24,22 @@ New format: archzfs-2026-01-24-vmlinuz-6.12.66-lts-x86_64.iso Date should come right after project name for easier sorting and identification. Update build.sh ISO_NAME variable. +** TODO [#A] Manually verify LUKS btrfs installations boot correctly +Automated reboot testing for LUKS configs is blocked - can't send passphrase to +initramfs encrypt hook via QEMU. Installation tests pass, but need manual verification +that systems actually boot and decrypt correctly. + +Test on physical hardware or VM with manual interaction: +1. Boot from archzfs ISO +2. Run: archangel --config-file with LUKS config +3. Reboot, enter passphrase at GRUB prompt +4. Enter passphrase at initramfs prompt +5. Verify system boots to login + +Configs to test: btrfs-luks (single disk), btrfs-mirror-luks (2-disk RAID1) + +See [[file:docs/TESTING-STRATEGY.org][TESTING-STRATEGY.org]] for background on automation limitations. + ** TODO [#A] Fix mkinitcpio configuration in install-archzfs (causes boot failure) After kernel updates or mkinitcpio regeneration, systems fail to boot because install-archzfs leaves incorrect mkinitcpio configuration from the live ISO environment. -- cgit v1.2.3