Skip to content

docs: troubleshoot Unraid 'Execution error / Bad parameter' #82

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

Merged
bakerboy448 merged 1 commit into from
Oct 30, 2026
Merged

docs: troubleshoot Unraid 'Execution error / Bad parameter' #82

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
25 changes: 25 additions & 0 deletions docs/pages/client/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,31 @@ Find tips for common problems on this page.
Corruption checks require a temp folder to write the db file. This may be a couple hundred megabytes or more.
Set the `TMPDIR` environment variable to a writable path, or mount `/tmp` to resolve the error.

## Unraid: Execution error / Bad parameter

Starting the container on Unraid shows an **Execution error** dialog that says **Bad parameter**.
That dialog is generic and does not name the cause. Get the real error first:

1. Open the *Docker* tab, click the container, and choose *Edit*. Click *Apply* and read the output.
Unraid prints the full `docker run` command and Docker's error text there.
1. Or run `docker start Notifiarr` in the Unraid terminal. Use your container's name.

Then match the error:

| Error text | Fix |
| --- | --- |
| `exec: "/init": permission denied` (or any `permission denied`) | Someone ran *New Permissions* on `appdata` instead of *Docker Safe New Perms*. Stop Docker, rebuild the Docker directory or restore `appdata` from backup, then reinstall from *Apps > Previous Apps*. |
| Same dialog, no `docker run` error, and other containers fail too | Docker's state or `docker.img` is damaged. Delete `/mnt/user/system/docker/installed/` or recreate `docker.img` (*Settings > Docker*), then reinstall from *Apps > Previous Apps*. |

Template items to check while you are in the editor:

- *Extra Parameters* should only hold `-h notifiarr`. Any other value is passed straight to `docker run`, and its error shows in the output above.
- Keep the `/config` path, `/etc/machine-id`, and `/var/run/utmp` mappings from the template. See [Install](install.md).

Sources: [Unraid Docker troubleshooting](https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/),
Unraid forum threads [177037](https://forums.unraid.net/topic/177037-completely-screwed-up-ran-new-permissions-on-every-share-including-appdata-now-no-containers-work-with-execution-error-bad-parameter-message/)
and [131566](https://forums.unraid.net/topic/131566-docker-container-starting-problem-error-execution-error-bad-parameter/).

## Duplicate Clients

If you have duplicate clients on the website:
Expand Down
Loading