mirror of
https://github.com/archr-linux/Arch-R.git
synced 2026-07-12 18:19:42 -07:00
Douglas Teles
235f113c25
Analysis of a first-boot resize log (docs/resize.log):
- The two FAT warnings it records are expected and harmless. The 256MB
boot partition ships the same out-of-spec FAT32 (16375 clusters, below
the 65525 minimum) as ROCKNIX and the rest of the RK3326 ecosystem;
vendor U-Boots are only tested against that layout, so reformatting it
is exactly the change that has caused boot loops before. The
boot-sector/backup difference is the kernel vfat dirty flag, written
to the primary sector only while /flash is mounted read-write; the
shipped image was verified to carry identical primary and backup
sectors. The script now appends a NOTE to the log so the warnings stop
being reported as failures.
Real defects fixed:
- resize2fs ran regardless of the e2fsck result; on unfixed corruption
(exit above 2) growing the filesystem would compound the damage. The
resize is now skipped in that case, leaving the grown partition for a
later retry after a manual fsck.
- The boot-partition path was hardcoded as ${DISK}p1, which is wrong for
/dev/sdX disks (sdXp1 does not exist), so the FAT serial
randomization silently never ran there. Derive the partition name per
device type alongside DISK.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>