mnt/NAS/movies if using the above example mount. Next, use a client app (I enjoy the Serviidroid app for Android devices) to locate and configure the instance, remembering that paths to media directories are always from the Pi's point of view, e.g. mynas/video /mnt/NAS cifs username=naspi,password=naspi,auto This is also a good time to set up the filesystem mount of the video media directory from my NAS, which the NAS user naspi has been given read-only access to: $ tail -f /opt/serviio-2.0/logs/serviio.log It's also very handy to watch the logs while using Serviio: Loaded: loaded (/etc/systemd/system/rvice enabled )Īctive: active (running) since Sat 16:54:48 AEST 7min ago # chown -R serviio:serviio /opt/serviio-2.0Ĭreate the a file rvice with the following contents:ĮxecStart=/opt/serviio-2.0/bin/serviio.shĮxecStop=/opt/serviio-2.0/bin/serviio.sh -stopĬopy it into position, enable the service, and reboot: # tar -xvzf -C /optĬreate a serviio user, and give them ownership of the install directory:

This will result in serviio being located in /opt/serviio-2.0: # apt-get install -no-install-recommends openjdk-11-jdk Here's what I did to get the Serviio Media Streamer, version 2.0, to work on Raspbian Buster (*):Ĭoming from the 'lite' install, we'll need a JDK, plus the various encode/decode tools Serviio uses to do the heavy lifting:

It's been a good opportunity to get the latest-and-greatest, even if it means sometimes the various instructional guides are slightly out-of-date.

After a recent SD card corruption (a whole-house power outage while the Raspberry Pi Model 3B must have been writing to the SD card), I have been forced to rebuild the little guy.

Serviio 1.9