Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Considerations for reinstalling SteamOS on a dual boot Steam Deck #49

Closed
jlobue10 opened this issue Mar 22, 2023 · 0 comments
Closed

Considerations for reinstalling SteamOS on a dual boot Steam Deck #49

jlobue10 opened this issue Mar 22, 2023 · 0 comments

Comments

@jlobue10
Copy link
Owner

jlobue10 commented Mar 22, 2023

This issue is being created for documentation and reference purposes (placed here in order to not clobber the main README).

If, for whatever reason, you feel the need to reinstall SteamOS on a functioning dual boot Steam Deck, there are some extra considerations and issues that you may encounter. Some common reasons for needing to reinstall SteamOS are software package or pacman configuration corruption (that can't be easily remedied), or some other system or partition error. If you feel this is happening on your Steam Deck and programs are either acting weird or not working at all, then the reinstall SteamOS from the SteamOS recovery USB may be the option that you're looking for. Reimage should be the last resort, and will delete the full drive before reimaging.

The reinstall option will redo the first 7 partitions, but the /home (8th partition) and subsequent partitions like your Windows installation (for instance) will not be touched. The problem is though, that the EFI boot loader files for Windows and any other Linux or other operating system will be wiped when the /esp partition is recreated. After a successful reinstallation of SteamOS, make sure to update immediately to the latest SteamOS upon first boot. This is to prevent software issues that may happen from running an older version of SteamOS. Programs like Decky Loader, CryoUtilities, and this rEFInd GUI will need to be reinstalled as well.

To restore the Windows EFI files and EFI entry properly, you will need the Windows installation USB to get to a command prompt. Boot off of the Windows installation USB and choose 'Repair your computer' when that option shows up. Use the buttons to get to a troubleshooting command prompt. From there, you will need to use a series of diskpart commands to prepare the proper volumes for the bcdboot command. It will look something like this.

diskpart_example

In this example screenshot, I would have to run these commands to get the /esp partition mounted in preparation for the bcdboot command.

diskpart
list vol
sel vol 4
assign letter=H
exit
cd C:\Windows\System32
bcdboot C:\Windows /s H:

The important things to note here is that my Windows partition is mounted as the C drive and the /esp partition is mounted as the H drive (in my example). If all went properly, the EFI files should be restored on the /esp partition and the Windows EFI entry would have been recreated (remember to disable again!!).

For Linux or other OS EFI files, I'd probably just recommend reinstalling, and I won't go into much detail about that since it's a much rarer use case that I can support as necessary (if people open issues, or respond here).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant