Document that GhostBSD and FreeBSD must not share a disk - #98
Merged
Merged
Conversation
GhostBSD uses the FreeBSD UEFI loader. When both systems are installed on the same disk, that loader can boot the existing FreeBSD installation instead of GhostBSD, even when GhostBSD is selected in the firmware boot menu or in rEFInd. Add warnings to the installation guide and custom installation guide, a troubleshooting entry for the "selecting GhostBSD boots FreeBSD" symptom with recovery steps, and an FAQ entry pointing to both. The Polish translations receive the same additions.
Contributor
Reviewer's GuideThe documentation now warns that GhostBSD and FreeBSD must be installed on separate disks because their shared FreeBSD UEFI loader can select the wrong system, provides recovery guidance for the resulting boot symptom, and extends the guidance to Polish documentation and the FAQ. Flow diagram for shared-disk UEFI boot behaviorflowchart TD
A["Firmware menu or rEFInd selects GhostBSD"] --> B["Shared FreeBSD UEFI loader starts"]
B --> C["Loader searches the boot disk"]
C --> D["Existing FreeBSD may boot instead"]
D --> E["Install GhostBSD on a separate disk"]
E --> F["Dual-boot with Windows or Linux remains supported"]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Hey - I've found 1 issue
Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments
### Comment 1
<location path="user/installation-guide/troubleshooting.md" line_range="61" />
<code_context>
+
+Install GhostBSD on a separate disk. Dual-boot with Windows or Linux on the same disk is supported.
+
+If both are already on one disk, boot from the GhostBSD live USB and keep only one of the two systems on that disk, or move GhostBSD to its own disk.
</code_context>
<issue_to_address>
**issue:** The recovery guidance only tells users to “keep only one” system or move GhostBSD, without explaining how to identify and remove the conflicting installation, restore the GhostBSD loader, or preserve the desired system. A user who follows it still cannot recover an existing GhostBSD installation without guessing at destructive disk operations.
**Triggers:** When both systems are already installed on one disk and the user wants to retain GhostBSD or both installations.
**Suggested fix:** Provide concrete recovery steps, including backing up data, identifying the GhostBSD and FreeBSD partitions, removing or relocating one installation, and reinstalling or repairing the GhostBSD boot loader.
```suggestion
If both are already on one disk, boot from the GhostBSD live USB and back up all data from both installations to an external disk. Use `gpart show` and the partition labels and filesystems to identify the GhostBSD and FreeBSD partitions; mount candidate partitions read-only if necessary and verify their contents before making changes. Remove the FreeBSD installation by deleting only its partitions, or relocate one installation to another disk, while preserving the desired system and its data. Finally, use the GhostBSD installer to reinstall or repair the GhostBSD boot loader, then reboot and verify that GhostBSD starts.
```
</issue_to_address>Sourcery assessment
Approval pending. 1 finding to address first.
Blocking findings: user/installation-guide/troubleshooting.md:61
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
github-project-automation
Bot
moved this from In Review
to Done
in Documentation Management
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
GhostBSD uses the FreeBSD UEFI loader. When both systems are installed on the same disk, that loader can boot the existing FreeBSD installation instead of GhostBSD, even when GhostBSD is selected in the firmware boot menu or in rEFInd.
Add warnings to the installation guide and custom installation guide, a troubleshooting entry for the "selecting GhostBSD boots FreeBSD" symptom with recovery steps, and an FAQ entry pointing to both. The Polish translations receive the same additions.
Related to ghostbsd/issues#247
Summary by Sourcery
Warn users to install GhostBSD and FreeBSD on separate disks and provide guidance for preventing and recovering from incorrect UEFI boots.
Enhancements:
Documentation: