Skip to content

Re-vendor qnxprobe 1.10: qnx6 boot block is not a partition table - #180

Merged
abrignoni merged 1 commit into
mainfrom
chore/revendor-qnxprobe-mbr-fix
Sep 2, 2026
Merged

abrignoni merged 1 commit into
mainfrom
chore/revendor-qnxprobe-mbr-fix

Conversation

@abrignoni

Copy link
Copy Markdown
Owner

Re-vendors qnxprobe at 1.10 (abrignoni/qnxprobe#9 and #10). The MBR parser no longer reads a qnx6 boot block ending in 0x55AA as a partition table, and the second superblock is probed where the Linux driver computes it. A whole-image qnx6 volume with x86 boot code is now listed and extracted instead of being reported as two nonsense partitions with an empty extraction. No VLEAPP code changes; the seekers hand raw images to the vendored reader.

Verified: the hash guard matches upstream 121c579 and the vendored self-test passes. -t raw over qnxmount's qnx6 reference image stages its volume with 23 files, where 1.9 staged nothing. Ford Sync Gen3 -t iva reproduces its 6115/6115/11/1629 volume baseline to a clean report with no database errors.

🤖 Generated with Claude Code

Vendors qnxprobe at 1.10 (121c579). The MBR parser no longer reads a qnx6
boot block ending in 0x55AA as a partition table, and the second superblock
is probed where the kernel computes it, so a whole-image qnx6 volume with
x86 boot code is listed and extracted instead of reported as two nonsense
partitions and an empty extraction.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@abrignoni
abrignoni merged commit 0d42dac into main Sep 2, 2026
8 checks passed
@abrignoni
abrignoni deleted the chore/revendor-qnxprobe-mbr-fix branch September 10, 2026 03:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant