Samba share

[voterpublic]

I have mostly used Rune, Volumio, RAudio & MoodeAudio over the last 10+ years.
They all have pros & cons however, for me, the biggest con they all share is terrible 'random playback' from your own library. Just does not work in my experience.

I discovered Odio & wanted to give it a try. Full disclosure, I am novice level at command line changes to Linux distributions so I want to keep it a simple as possible.
I have now been using this setup for the last 1.5 months & am very happy with Odio's responsiveness, myMPD interface options.
I have had Odio system crash (probably 3 times) but each time power off power on & Odio just picks up where it left off! Mid song, I mean wow!
I tried other Odio setup suggestions but they did not work for me for a variety of reasons (mostly my very limited Linux knowledge & unwillingness to 'hack my NAS').

My equipment:
Raspberry Pi 3B+
HiFiBerry DAC Pro+
Yamaha Stereo Receiver AV RX-396
Synology NAS 213J (my music's home - old & very under powered)
Equipment is LAN cabled, no use of WIFI (except mobile phone controls to Odio) or bluetooth.

This is how I did it.
Probably not the best nor most efficient, however I could not get any of the other methods to work with my Synology NAS without doing changes to my NAS operating system, which I have neither the skill nor adequate knowledge to do.
This guide (https://docs.odio.love/guides/mpd/ section 'Mount the share over NFS') did work, but was allot more involved with permissions on my NAS to get it right.

Setting up Synology NAS as a media source for Odio involved configuring network shares on the NAS & mounting them on the Raspberry Pi running Odio.

Synology side.

1. Create a user with read only access to your music folder.
2. Ensure smb is enabled in file service settings.

Odio side.

You do not need the /etc/samba directory to mount a Synology share; you only need the cifs-utils package.

1. Install Required Package

First, ensure the SMB client utilities are installed:

sudo apt update
sudo apt install cifs-utils

2. Create Credentials File (Alternative to /etc/samba)

Since /etc/samba doesn't exist, store your credentials in a custom location like /etc/odio-smb.credentials:

sudo nano /etc/odio-smb.credentials

Add your Synology details:

username=your_syno_user
password=your_syno_user_password

Secure the file:

sudo chmod 600 /etc/odio-smb.credentials

Now you can mount your Synology NAS directly to Odio's library path (/media/USB/):

sudo mkdir -p /media/USB/<Music>
sudo mount -t cifs //<SYNOLOGY_IP>/<Music> /media/USB/<Music> -o credentials=/etc/odio-smb.credentials,vers=3.0,uid=1000,gid=1000

(Replace <SYNOLOGY_IP> and with your actual NAS IP and shared folder name).

4. Make It Permanent

Edit /etc/fstab to mount automatically on boot:

sudo nano /etc/fstab

Add this line at the end:

//<SYNOLOGY_IP>/<Music>  /media/USB/<Music>  cifs  credentials=/etc/odio-smb.credentials,vers=3.0,uid=1000,gid=1000,x-systemd.automount,nofail  0  0

(Replace <SYNOLOGY_IP> and with your actual NAS IP and shared folder name).

Finally trigger MPD update

mpc update

And that is it. You are done.
Any information on errors I have made is more than welcome.
Hope this helps.

Thank you to @b0bbywan + contributors for a truly beautiful & well conceived/documented project (I now wish my NAS to give up so I could explore Odios properly :) )

[b0bbywan]

Thanks a lot for your kind comments, sharing your setup and this neat tutorial, looks really clean. I'll add that to the docs soon ! I've also started to work on the admin panel, it will probably end up there too in the future. But I'm glad If odio helps getting along with the CLI 😁

A bit worried about those crash, it's really not supposed to happen 😅 can you recall if you were you doing something in peculiar at the moment ?

[voterpublic]

The times it has crashed it was just playing media via my samba share. I noticed because it just stops playing. Try myMPD ui get error message about Odio being unreachable. Try Odio ui, unreachable. Try shell command, unreachable. On the Rapi itself LAN leds off & power led orange (flickering i think). Unplug power, wait a bit. Plug in, after boot all good and it starts playing exactly where i heard it stop playing. If it happens again, I could try and get log files at that point. Just tell me where to get them from and will share. Cheers and thanks.

…

On Fri, 4 Sept 2026, 07:46 b0bbywan, ***@***.***> wrote: Thanks a lot for your kind comments, sharing your setup and this neat tutorial, looks really clean. I'll add that to the docs soon ! I've also started to work on the admin panel, it will probably end up there too in the future. But I'm glad If odio helps getting along with the CLI 😁 A bit worried about those crash, it's really not supposed to happen 😅 can you recall if you were you doing something in peculiar at the moment ? — Reply to this email directly, view it on GitHub <#85?email_source=notifications&email_token=A23UG23DOQU4FXISXQTAD2L5NHRDRA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSG43DQMZRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18276831>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A23UG2425R3QWCHG5GJHWD35NHRDRAVCNFSNUABJKJSXA33TNF2G64TZHMYTCNJUHE2TMMBUGE5UI2LTMN2XG43JN5XDWMJQG4YTGMBUGKQXMAQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[b0bbywan]

Logs are not persisted between boots to save the SD, but I think that could look like a power supply issue.
You can check that with:

 sudo dmesg | grep -i voltage
#[   48.167416] hwmon hwmon1: Undervoltage detected!
#[   50.243559] hwmon hwmon1: Voltage normalised

[voterpublic]

Thanks but no luck. Command returns nothing, just jumps to new line. I am using the correct wattage power supply for the 3B+. Maybe I could remote write log to NAS (or monitor the Pi to NAS log). But I would need a spirit guide ;) Cheers

…

On Wed, 9 Sept 2026, 04:11 b0bbywan, ***@***.***> wrote: Logs are not persisted between boots to save the SD, but I think that could look like a power supply issue. You can check that with: sudo dmesg | grep -i voltage #[ 48.167416] hwmon hwmon1: Undervoltage detected! #[ 50.243559] hwmon hwmon1: Voltage normalised — Reply to this email directly, view it on GitHub <#85?email_source=notifications&email_token=A23UG26JVUB5W7JV6G6QYYD5OBDWLA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGU2DKMZZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18354539>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A23UG25NWPVWEN4FQGBOIDT5OBDWLAVCNFSNUABJKJSXA33TNF2G64TZHMYTCNJUHE2TMMBUGE5UI2LTMN2XG43JN5XDWMJQG4YTGMBUGKQXMAQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[b0bbywan]

Forwarding needs a bit too much configuration IMO, but we can persist recent logs to help the investigation next time :

sudo nano /etc/systemd/journald.conf

[Journal]
Storage=persistent
SystemMaxUse=100M
MaxRetentionSec=1day

sudo systemctl restart systemd-journald
# Check for configuration error
sudo journalctl -u systemd-journald --since "1 min ago"

Next time your system crash, after rebooting:

journalctl -p err -b1 should point the culprit.

[voterpublic]

Finally, another crash :). But no luck with those suggestions.

odio@odio:~ $ journalctl -p err -b1
Specifying boot ID or boot offset has no effect, no persistent journal was found.
Checked the setting above & they are correct as to your suggestion.

This returned,
odio@odio:~ $ sudo journalctl -u systemd-journald --since "1 min ago"
-- No entries --

So i expanded to 30min &,
odio@odio:~ $ sudo journalctl -u systemd-journald --since "30 min ago"
Oct 06 12:04:53 odio systemd-journald[230]: Collecting audit messages is disabled.
Oct 06 12:04:53 odio systemd-journald[230]: Journal started
Oct 06 12:04:53 odio systemd-journald[230]: Runtime Journal (/run/log/journal/ee10e11435384097b0aad5039e8d3991) is 2.2M>
Oct 06 12:04:53 odio systemd-journald[230]: Runtime Journal (/run/log/journal/ee10e11435384097b0aad5039e8d3991) is 2.2M>
Oct 06 12:04:53 odio systemd-journald[230]: Received client request to flush runtime journal.

I guess some process flush the journal at crash? Any ideas?
Thanks for your time. :)

[b0bbywan]

Hi, thanks for getting back! And sorry my instructions were wrong: Raspberry Pi OS ships /usr/lib/systemd/journald.conf.d/40-rpi-volatile-storage.conf, which overrides /etc/systemd/journald.conf, so the journal stayed in RAM...

You can revert your change in /etc/systemd/journald.conf, then:

sudo mkdir -p /etc/systemd/journald.conf.d
sudo tee /etc/systemd/journald.conf.d/99-persistent.conf >/dev/null <<'EOF'
[Journal]
Storage=persistent
SystemMaxUse=200M
SyncIntervalSec=10s
EOF
sudo systemctl restart systemd-journald
sudo journalctl --flush

SyncIntervalSec=10s makes the journal write to the SD card every 10 seconds instead of every 5 minutes, necessary if the Pi freezes completely, and I hope sufficient.

Next time it crashes, after rebooting:

journalctl -b -1 -p warning