Add documentation page for duplicate_os_installation unhealthy state #40022
Conversation
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
Add documentation for unhealthy state implemented in home-assistant/supervisor#6024 Refs home-assistant/supervisor#6021
|
It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the |
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Pull Request Overview
This PR adds a new documentation page explaining the “duplicate_os_installation” unhealthy state and how to resolve it in Home Assistant OS. Key changes include:
- Introduction of a dedicated markdown file outlining the detected issue and its causes
- Step-by-step resolution instructions with backup and reinstall guidance
- A special section for devices with non-removable storage, such as Home Assistant Yellow
Comments suppressed due to low confidence (3)
source/more-info/unhealthy/duplicate_os_installation.md:12
- [nitpick] Either remove the trailing period since these are fragments or convert each bullet into a full sentence (e.g., "Your system boots into an old version of Home Assistant OS even after updating.") to comply with list punctuation rules.
- Your system booting into an old version of Home Assistant OS even after updating.
source/more-info/unhealthy/duplicate_os_installation.md:23
- [nitpick] Rephrase step 4 for clarity. For example: "Install Home Assistant OS on the storage device you want to use, wiping the other devices." — this removes the duplicate "using" and reads more smoothly.
4. [Install Home Assistant OS][installation] on the storage device you want to use using, wiping the other devices.
source/more-info/unhealthy/duplicate_os_installation.md:26
- For consistency with the rest of the document, use "Home Assistant OS" instead of spelling out "Operating System."
By following these steps, the Home Assistant Operating System should be installed on a single device only. In case you are using the [external data disk][data-disk] feature, wipe this disk as well prior to starting the device for the first time with this storage device connected.
Merged
14 tasks
agners
previously requested changes
Jul 15, 2025
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Co-authored-by: Stefan Agner <stefan@agner.ch>
Co-authored-by: Stefan Agner <stefan@agner.ch>
c0ffeeca7
approved these changes
Jul 16, 2025
Requested changes have been implemented
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Proposed change
Add documentation for unhealthy state implemented in home-assistant/supervisor#6024
Refs home-assistant/supervisor#6021
This change is intentionally targeted at the
currentbranch, as it's implemented in Supervisor and as such will be rolled out independently on the next Core release. Also, the page is reachable only from the unhealthy issue description, so it does no harm if it's deployed before the change is actually merged.Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.