Bug #16149
USB image is not bootable anymore
100%
Description
I’ve tried to boot a USB image built from feature/15292-usb-image
, both on bare metal and in a VM, and I see “This is not a bootable disk. Please insert a bootable floppy and press any key to try again …”. I guess one of the recent commits aimed at fixing reproducibility or GUIDs broke it.
Subtasks
History
#1 Updated by intrigeri 2018-11-23 15:52:19
Reverting commit:3adb896dd75e3b9a50875dc3e8ee33552cd52f5f does not fix this.
#2 Updated by segfault 2018-11-25 22:29:28
- Status changed from Confirmed to In Progress
Applied in changeset commit:tails|95a33f55dec4e4e66760a1df9c88deb2a2a4a62f.
#3 Updated by segfault 2018-11-25 22:31:16
- Assignee changed from segfault to intrigeri
- QA Check set to Ready for QA
Fixed by 95a33f55dec4e4e66760a1df9c88deb2a2a4a62f. It was broken because syslinux was installed while the system partition was mounted. I don’t know why this breaks things and didn’t investigate.
#4 Updated by intrigeri 2018-11-26 08:52:37
> Fixed by 95a33f55dec4e4e66760a1df9c88deb2a2a4a62f.
Thanks a lot for the quick fix! :) I’ll take a look today or first thing tomorrow.
> It was broken because syslinux was installed while the system partition was mounted. I don’t know why this breaks things and didn’t investigate.
Yeah, I’m not surprised that having two parties (syslinux and the vfat kernel driver) competing for concurrent write access to the same block device leads to “interesting” outcomes. Not worth investigating IMO.
#5 Updated by intrigeri 2018-11-26 10:28:30
- Status changed from In Progress to Resolved
- Assignee deleted (
intrigeri) - % Done changed from 0 to 100
- QA Check changed from Ready for QA to Pass
Code review passes and I confirm that the resulting image is bootable again :)