[SOLVED] How to Solve minissdpd Startup Failure on Excalibur

dummy@example.com (UnixRocks) — Wed, 19 Nov 2025 23:33:15 +0000

I just upgraded from Daedalus to Excalibur today. As a result I was paying attention to the startup messages when booting Excalibur after the upgrade. There were three failure messages:

Wed Nov 19 12:18:10 2025: Cannot persist initramfs fsck.log ... failed!
Wed Nov 19 12:18:10 2025: Checking file systems...Cannot persist the following output on disc ... failed!
Wed Nov 19 12:18:28 2025: MiniSSDPd: START_DAEMON is not set to 1; exiting: failed!

I haven't looked into the first two yet, so suggestions on fixing those are welcome.

The one I concentrated on was the minissdpd failure. After doing some digging and chatting with a friend online I found out the /etc/default/minissdpd file is apparently configured for use with systemd upstream, and so has the START_DAEMON line removed. I simply added that line and started it by hand successfully from the command line.

# MiniSSDPd default configuration
START_DAEMON=1

# Set this to the IPv4/interfaces you want the daemon to run on, separated by
# space.
# Notes:
#  1. Specifying IP when built with IPv6 support is disabled by original
#     author, so this option may not be available outside Debian.
#  2. No `-6' should be used when IPv4 specified. You will be flooded by
#     'peer [xxxx:xxxx]:1900 is not from a LAN' if you insist to do so.
MiniSSDPd_INTERFACE_ADDRESS="eth0"

# This defines other options which you might want to use when
# starting MiniSSDPd.
MiniSSDPd_OTHER_OPTIONS=""

### For IPv6 users:
# 1. Change MiniSSDPd_INTERFACE_ADDRESS to the correct interface name
# 2. Add `-6' to MiniSSDPd_OTHER_OPTIONS

# service minissdpd start
Starting UPnP devices daemon: MiniSSDPd.
# service minissdpd status
MiniSSDPd is running.

Dev1 Galaxy Forum / [SOLVED] How to Solve minissdpd Startup Failure on Excalibur

[SOLVED] How to Solve minissdpd Startup Failure on Excalibur