forked-daapd fails to start on boot with software raid
Bug #1173548 reported by
Stewart Heitmann
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| forked-daapd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
forked-daapd fails to start on bootup when the music files are located on a software raid volume. This is because the system init scripts attempt to start forked-daapd before starting mdadm (the software raid daemon). The fix is simply to re-order the startup scripts so that mdadm starts first. On my system (Ubuntu Linux 12.04 LTS ) that amounts to renaming the startup script symlinks from:
/etc/
/etc/
to:
/etc/
/etc/
Hope this helps
-- stewart
Revision history for this message
| Balint Reczey (rbalint) wrote | #1 |
| Changed in forked-daapd (Ubuntu): | |
| status: | New → Incomplete |
| status: | Incomplete → Fix Released |
To post a comment you must log in.
Could you please try the latest version? Any version >= 22 should work nicely since I switched to a new active upstream in Debian.
Switching to a Ubuntu release with systemd as init also should resolve the issue.