New-machine installs most often fail because mounts, UID/GID ownership, or root paths are wrong. Importarr should diagnose this like a service, not require log spelunking.
Proposed change
Add a diagnostics page/API for installation and runtime checks.
Scope
Read/download-root checks.
Write/create/delete .partial checks for media roots.
SAB storage path resolution under configured root.
Disk free space per configured root.
UID/GID and effective user display.
Suggested fix text for common permission failures.
UI exposes diagnostics clearly during setup and after setup.
Failed write checks do not leave test files behind.
Diagnostic output does not include secrets.
## Problem
New-machine installs most often fail because mounts, UID/GID ownership, or root paths are wrong. Importarr should diagnose this like a service, not require log spelunking.
## Proposed change
Add a diagnostics page/API for installation and runtime checks.
## Scope
- Read/download-root checks.
- Write/create/delete `.partial` checks for media roots.
- SAB storage path resolution under configured root.
- Disk free space per configured root.
- UID/GID and effective user display.
- Suggested fix text for common permission failures.
## Acceptance criteria
- `/api/diagnostics` returns structured pass/warn/fail checks.
- UI exposes diagnostics clearly during setup and after setup.
- Failed write checks do not leave test files behind.
- Diagnostic output does not include secrets.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
New-machine installs most often fail because mounts, UID/GID ownership, or root paths are wrong. Importarr should diagnose this like a service, not require log spelunking.
Proposed change
Add a diagnostics page/API for installation and runtime checks.
Scope
.partialchecks for media roots.Acceptance criteria
/api/diagnosticsreturns structured pass/warn/fail checks.