Check if Lidarr adds an artist* image in artist folder or add an integration for fetching images.
Make sure the SQL server is not writing/blocking any files: docker-compose stop vaultwarden
Backup that specific folder to another destination and restart docker-compose up -d
I think you can’t track data corruption either because you will find out only when it occurred. Same is valid for SMART values as you correctly state.
I believe it is a mix of using zfs, ECC and SMART monitoring.
https://phoenixnap.com/blog/data-corruption
Thanks for clarifying the intricacies connected to SMART monitoring.
SMART value monitoring helped me finding faulty drives, not only once. And drives are tested before adding to a production system.
Certainly system drives are separate from data drives. The latter can be perfectly monitored by SMART values.
If you want regular automatic hdd checks and don’t need a WebUI I recommend https://github.com/smartmontools
At last we keep it simple ;)
I set up custom bash scripts collecting information (df, docker json, smartCTL etc)
Either parse existing json info or assemble json strings and push it to Homeassistant REST api (cron)
In Homeassistant data is turned into sensors and displayed. HA sends messages of sensors fail.
Info served in HA:
Trying to keep my servers as barebones as possible. Additional services/apps put strain on CPU/RAM etc. Found out most of data necessary for monitoring is either available (docker json, smartCTL json) or can be easily caught, e.g.
df -Pht ext4 | tail -n +2 | awk '{ print $1}
It was fun learning and defining what must be monitored or not, and building a custom interface in HA.
Your friends will comment on interface when you share music to them :)
Hardly using the UI myself ;)
Had for years airsonic, later airsonic advanced. The overhead is huge compared to Navidrome.
Had never an issue with Navidrome and it is much snappier. No even starting to talk about the modern interface compared to Airsonic.
You are right Beets doesn’t allow for custom id3v2 fields.
However it has quite a lot of fields ‘’’beet fields’’’
You can write them specifically using ‘’’-F’’’
(Beets doc)[https://beets.readthedocs.io/en/stable/reference/cli.html#fields]
I’m not aware of a publisher nor producer field though.
Lidarr can be used for tagging too and it does have a web interface.
Cleaning a messed up library with Beets is tough and depends on how the individual files are sorted.
Start importing/organizing a small part or some albums to find out how it works. And a backup of data is always recommend!
I can recommend Navidrome. Organizing of library with Lidarr and (Beets)[https://beets.io]
I’m using Beets for tagging because of the Discogs plugin.
Lidarr for visual overview of the library.
Just put all commands into a bash file. Starting with ‘’docker tag’’ changing tag to something else in case I need to revert and than pull, compose up. All run by crontab weekly. In case something breaks the latest working container is still there.
beets music library management and tagging for geeks
Utmost appreciated! Thanks
Thanks. Now I have to buy a new device!
I’m using network overlays for individual containers and separation.
Secondly fail2ban installed on host to secure docker services. Ban FORWARDING chains specific to docker instead of INPUT chains. [fail2ban docker](Configure Fail2Ban for a Docker Container – seifer.guru)
Use 2FA for services if available.
Rootless docker has limitations when it comes to port exposing, storage drivers, network overlays etc.
The host is auto-updating security batches but rebooted manually only.
Docker containers are updated manually too. I built all containers from file and don’t pull them because most are modified (plugins, minimizing sizes, dedicated user rights etc.)
Active, links are valid for a long time and they post good quality imho
Pydf displaying df -h differently