does the issue already exist here:…
- User
does the issue already exist here: https://gitlab.postmarketos.org/groups/postmarketOS/-/issues
Here’s a well-structured GitHub issue you can use to report your problem with postmarketOS installation on the Samsung Galaxy A3 2017 (a3y17lte):
Title:
Installation fails with "failed to mount /system (device or resource busy)" and boot stalls on "starting postmarketOS" (a3y17lte, TWRP recovery installer)
Description:
After successfully installing postmarketOS via the TWRP recovery installer on the Samsung Galaxy A3 2017 (a3y17lte), the installation completes but ends with the following errors:
-
Mount error:
failed to mount /system (device or resource busy) ... doneThis occurs regardless of whether I install to
/systemor/data. -
Fstab error:
error creating fstabThe files appear to be installed, but on boot, the device gets stuck at:
initializing and then starting postmarketOS(Channel:
edge) -
Kernel & ADB issues:
- The kernel seems to load successfully (visible in
dmesg). - ADB does not work in TWRP, making debugging difficult.
- When running:
It first errors with:pmbootstrap install --android-recovery-zip --recovery-install-partition=data
But then proceeds with:(buildroot_aarch64) chroot not initialized! This is a bug! Please report it.(buildroot_aarch64) initializing the chroot for you... (buildroot_aarch64) create recovery zip
- The kernel seems to load successfully (visible in
Steps to Reproduce:
- Flash TWRP recovery.
- Boot into TWRP and use the postmarketOS recovery installer.
- Attempt installation on either
/systemor/data. - Observe the mount error and fstab error at the end.
- Reboot and see the system stall at "starting postmarketOS".
Expected Behavior:
- Installation should complete without mount errors.
- Device should boot into postmarketOS successfully.
- ADB should be functional in TWRP for debugging.
Additional Information:
- Device: Samsung Galaxy A3 2017 (a3y17lte)
- Channel:
edge - Kernel: Unsure if the proposed kernel (linux-samsung-a3y17lte) is included.
- TWRP Version: (Specify if known)
- pmbootstrap Version: (Specify if known)
Possible Causes:
- Mount conflicts in TWRP preventing
/systemfrom being properly unmounted. - Fstab generation failure due to incorrect partitioning or missing kernel modules.
- ADB issues in TWRP preventing log collection.
Temporary Workarounds Attempted:
- Installing to both
/systemand/data→ same error. - Manually checking partitions → files seem present but system fails to boot.
Request for Help:
- Is the a3y17lte kernel properly included in the installer?
- Are there known issues with TWRP + postmarketOS on this device?
- How can we debug further if ADB is unavailable in TWRP?
This issue is clear, structured, and provides all necessary details for developers to investigate. You can post it in the postmarketOS GitLab issues (since they use GitLab, not GitHub).
Let me know if you'd like any modifications!
-
- Assistant
Based on the information available, it appears that the specific issue you're encountering with the Samsung Galaxy A3 2017 (a3y17lte) during postmarketOS installation has not been reported in the postmarketOS GitLab issues. While there are similar issues related to mounting errors during installation on other devices, such as the Samsung Galaxy Trend Lite[1] and the Samsung Galaxy S5 Mini[2], your particular problem with the a3y17lte does not seem to have been documented.
Given this, it would be beneficial to report your issue to the postmarketOS team. Providing detailed information, as you've outlined, will assist the developers in diagnosing and addressing the problem. You can submit your report through the postmarketOS GitLab issues page:
Additionally, you might find it helpful to consult the postmarketOS Wiki page for the Samsung Galaxy A3 2017[3], as it contains device-specific information that could aid in troubleshooting.
By reporting your issue, you'll contribute to the improvement of postmarketOS support for the a3y17lte and assist others who may encounter similar challenges.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.