Fix FAT32 partition issues on sd-image-based images #51158
Merged
+3
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
Fixes #51150.
The main issue:
Is already fixed using
mtools-4.0.21
. Forrelease-18.09
its update will need to be backported (#51159).This fixes the seemingly-always-existing issue where the FAT32 partition was subtly broken by
mtools
. It wouldn't pass anfsck
, even when freshly made. See #51150 for investigation details, and see commit messages for fixes details.To ensure no regression with regards to the integrity of the boot partition, an
fsck
pass is now made just after copying the files. This will add a negligible amount of time to the whole build process, but will ensure tools will be able to manipulate the boot partition with success.Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)cc @dezgeg @tilpner @bennofs