From c6827451bce4cd3774a9e066a4a1bf51bb83592e Mon Sep 17 00:00:00 2001 From: salmonik Date: Sun, 2 Aug 2026 15:34:45 +0200 Subject: v0.5.5: on-screen boot markers for disk/fs stage MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Real hardware has no serial console, and the ahci/fat/fs boot diagnostics were serial-only — a silent fs failure left the user with no way to see where boot stopped. Add boot_marker lines for the AHCI disk count, FAT volume count, and the VFS tree + fs self-test result. --- scripts/test-fault.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'scripts') diff --git a/scripts/test-fault.sh b/scripts/test-fault.sh index 59f741f..74d83eb 100755 --- a/scripts/test-fault.sh +++ b/scripts/test-fault.sh @@ -93,8 +93,8 @@ grep -aq "!!! halting" "$LOG" || fail "no halt message" echo "==> 6/6 crash.log persisted on the CRASHLOG stick" grep -aq "crashlog: vol .* (CRASHLOG)" "$LOG" || fail "crashlog did not target the CRASHLOG stick" grep -aq "crashlog: wrote" "$LOG" || fail "crashlog write did not complete" -mdir -i "$CRASH_IMG" "::" 2>/dev/null | grep -aqi "crash" \ - || fail "crash.log missing on the CRASHLOG stick" +mdir -i "$CRASH_IMG" "::" 2>/dev/null | grep -aqi "crash" || + fail "crash.log missing on the CRASHLOG stick" # The boot ESP must NOT receive the crash log. if [ -f "$ESP_DIR/crash.log" ]; then fail "crash.log landed on the boot ESP instead of the CRASHLOG stick" -- cgit v1.2.3