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.

Sign up for GitHub

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

boot rescue: Add step to regenerate EFI menu #510

Merged
merged 2 commits into from
Mar 19, 2024
Merged

boot rescue: Add step to regenerate EFI menu #510

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
71cd142
boot rescue: Add step to regenerate EFI menu
TraceyC77 Mar 12, 2024
096e866
Update clr-boot-manager command
TraceyC77 Mar 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion docs/user/troubleshooting/boot-rescue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,10 +179,18 @@ In the event that disk changes had caused the system to fail to boot, try the fo

In the chroot environment, run the following command which will perform various configuration triggers to update your icon cache, update GRUB and EFI configuration, re-compile settings, and more.

```
```bash
sudo usysconf run -f
```

### Regenerate UEFI Boot Entries

Run the following command, which will update the boot entries for your EFI menu:

```bash
clr-boot-manager update
TraceyC77 marked this conversation as resolved.
Show resolved Hide resolved
```

After this, you should exit your chroot with `exit` then reboot your system. In the event you are still unable to access Solus, please [contact us](/docs/user/contributing/getting-involved).

### Unmounting your system
Expand Down