RAX30 1.0.9.92: verify guest boot after native extraction #110

I'm tracking the kernel/init failure reported later in #88 here so it stays visible when the original extraction report closes.

The exact RAX30-V1.0.9.92_1.img image is available in the Netgear vendor archive. Its MD5 matches the original report: 49241d7f2502d60e14e8f6005116fe3d. Its SHA-256 is 26cbc9cd66252c8270fffc487905bfa4b45437e7dec09741c6afe83c8e392424.

PR #108 fixes extraction for this image. All 2,134 regular files and symlink targets matched independent reference extraction. I also retested it with the published FAT 2.0.1 Apple Silicon binary: it recovered the rootfs and the same 2,134 files and symlinks on case-sensitive APFS. Guest boot has not been verified.

This image contains kernel-module filenames that differ only by case. Use case-sensitive storage for the project, such as Linux ext4 or case-sensitive APFS on macOS. On the default Mac filesystem, FAT reports partial recovery at the filename collision.

The older thread includes FATAL: kernel too old and an init undefined-instruction panic with a 4.1.17 kernel. Those are historical observations to compare with a fresh run, not confirmed behavior on FAT 2.0.1.

The next check is a fresh project using FAT 2.0.1 and matching runtime data. Record the backend, kernel version/hash, QEMU version, launch output, and full serial log. Then check whether init completes and the intended service starts and stays reachable. Keep this open until that result is known.