gilladur

Just an addition - Spotify changed their API and the Spotty Plugin needed an update (thanks to mherger the fix came quite fast): https://forums.lyrion.org/forum/user-forums/3rd-party-software/1802770-announce-spotty-v4-60-0-the-christmas-crash-release-%F0%9F%8E%84%F0%9F%8E%81 I could not get the needed Token, if using the client ID, but without the client ID I'm able to connect to Spotify again. I still have some issues losing the token / get the token refreshed and therefore need to reauthenticate quite often. But this could be an issue on my site.

I'm confused - on Docker Hub it says: https://hub.docker.com/r/lmscommunity/lyrionmusicserver Tags latest: the latest release version, currently v9.0.3 stable: the bug fix branch based on the latest release, currently v9.0.4 dev: the development version with new features, and potentially less stability, currently v9.1.0 I've tried: ghcr.io/lms-community/lyrionmusicserver:dev and the Server is now on: Lyrion Music Server Version: 9.1.0 - 1766418462 But according to this: - RC should be a valid Tag - but maybe :stable would be the best option?

I have the issue too, and it seems all the affecting Docker which are hosted on Github ghcr.io or LinuxServer.io lscr.io (which as far as I know often which often points to ghcr.io too). Could this be the issue - Github?

I don't know if this was already answered or asked before but what is about the for me new AppApi settings which shows up as an Error: AppAPI Deployment Daemon AppAPI's default deployment daemon is not set up. Please register a default deploy daemon in the settings to install external apps (ex-apps).https://docs.nextcloud.com/server/latest/admin_manual/exapps_management/AppAPIAndExternalApps.html#setup-deploy-daemon What would be the right way to get the AppApi correctly implemented. I could not find more answers which fit to our Unraid scenario on Discord. Is there a tutorial?

Just a short update on my X14SAE-F board - it finally arrived. Migration was straight forward. The only issues I have, is with the Fan control and to get the IPMI support tool to control the Fans. The build in fan profiles from supermicro struggle all (except full speed) to keep the fans running, or at least from time to time the IPMI report 0 rpm. I've played around with ipmitool to change the thresholds but that did not help so far. Besides that, I'm quite happy with the performance... I'll write an update after some more testing. Just one remark, even that it took ages to get the board - the communication and support via Serverparts.pl where I got the board from was perfect, and they did everything possible to get the board from supermicro.

I've ordered the board via: They are one of the official distributors for Supermicro for Poland. Most of the distributors in the EU and especially in DE only sell to business partners. But I didn't order it via their shop on the webpage, instead I've just asked for an offer and the overall price to ship it to DE including tax was better than what I've found on other stores. Nevertheless, they've sent me the expected ETA given by Supermicro two days ago and currently Supermicro is having an estimated lead time about 12-16 weeks for the board So, basically it is also currently not available for me, at least not within a decent delivery time. Due to the fact, that I'm not in a rush to replace my current setup, it's fine for me. However, I can say that the communication with this seller is very good so far, and they usually respond within a day.

Thanks for your reply - I've actually changed plans, I could not resist going a bit more modern and ordered an X14SAE-F and an Intel Ultra 7 265K + 94 GB ECC DDR5. It was certainly not the most economical decision, but I was in the mood for such an over-the-top project for my needs.

Lowering the PL1 and PL2 state should be possible (the Bios of the X14SAE-F does have this option according to the manual). I could not find the manual of the ASUS Pro WS W880-ACE SE - but I assume it will allow this too. For me, having full ECC is more important than having the option to undervolt or lower the multiplier. Unfortunately, ECC UDIMMS are really expensive currently. The idle power consumption when the server is just doing nothing should be fine even with the K version. Nevertheless, it would be nice to see a review of the T and if the lower base clocks improve idle power usage. In Germany there are today 4 sellers offering the T but nearly 50€ more expensive than the K. And to be honest, one reason to upgrade the server is to have more cores but also more CPU power and the T will be slower.

Just one remark - the Cure Ultra CPUs don't have any Hyper-Threating anymore

As far as I know, you would reduce the maximum allowed power limit to the PL1 and PL2 values of the non-K or T - or something in-between: PL1 = Processor Base Power and PL2 = Maximum Turbo Power K = 125W (Processor Base Power), 250W (Maximum Turbo Power) non-K = 65W (Processor Base Power), 182W (Maximum Turbo Power) T = 35W (Processor Base Power), 112W (Maximum Turbo Power) And please correct me if I'm wrong, but this should bring down the clock speeds to the value that your CPU could achieve with the given power according to the intel standard curve for power/frequency. This should not impact stability but will reduce maximum performance but on the other hand also the used power and generated heat - but only for the higher CPU workloads. It is like putting a brick under your gas paddle in your car so that you can't push it as far down as without the brick Another approach would be to undervolt the CPU (which is not available on most boards without overclocking settings - and afaik not on workstation or server boards like the X14SAE-F). This would give the CPU less voltage per MHZ. You would herewith shift or alter the curve for power/frequency down for the voltage per frequency. So the overall power consumption drops, but depending on the given undervolt it will affect stability. You would need to find the sweet spot - which is dependent on your silicone quality - where your CPU could keep the frequencies stable with less juice. I would say as we need max stability for servers, this is more an approach for a normal Desktop PC, where you could run benchmarks of different types and see at which reduced voltage the system is not crashing anymore - but still then it could happen at special workloads, also like lighter once.

Thanks for your answer. I'm currently waiting for the board to be shipped from supermicro to my supplier. CPU (265k) and the DDR5 ECC UDIMMS are already here. But I think it will take a while till I hold the board in my hands. I'll give an update as soon as I receive it.

I could get my hands on a X14SAE-F for a decent price, and I'm wondering now, which Core Ultra to buy? The first decision to be made would be if Core Ultra 5 or 7, and I'm currently uncertain how much Unraid profits from more cores. The second question would be if it would make sense to go for a non-K or even a T version if available or just the more available K version. Is there some kind of sweet spot with the best balance of performance and low power consumption? I've seen some test results, where the Core Ultra 5 245 vs. 7 265K had a quite similar idle consumption: https://www.computerbase.de/artikel/prozessoren/intel-core-ultra-200s-285k-265k-245k-test.90019/seite-4 https://www.hardwareluxx.de/index.php/artikel/hardware/prozessoren/65794-intel-core-ultra-5-235-225f-im-test.html?start=9 But I can't find a test with a non-K and T version.

The Core Ultra 2 series is the one based on Arrow Lake-S or? Like the Intel Core Ultra 7 265K? As this one runs under the same chipsets B860, H810, W880, Z890 and the same LGA 1851 why should they not work on an X14SAE which does have the same W880 as the 14SAZ-F? I think the only difference between these two main boards is the size of the motherboard (which comes for the X14SAZ with the negative effect that they only have 2 ram slots and less SATA ports - the X14SAZ-F in fact have none and the X14SAV-TLN4F only 4). https://www.supermicro.com/en/products/compare?sku=X14SAV-TLN4F,X14SAE-F,X14SAV-F

I'm still confused - as far as I understand is the X14SBI using the LGA 4710 for Xeon CPUS - how should a Core Ultra which uses LGA 1851 would fit?

I'm confused, isn't the X14SBI (Socket LGA-4710 -> Intel® Xeon® 6700/6500) for a different platform than the Core Ultra 7 which needs LGA-1851 like on the X14SAE?

Hi community, I'm currently thinking about using the CPU a Motherboard which will maybe replaced from a desktop setup and use it in my Unraid server. Currently, I'm using this setup: Intel Xeon E-2246G on Supermicro X11SCH-LN4F with 96 GiB DDR4 ECC 4 HDD for the array and 2 SSDs for cache + 2 NVMEs for Docker and VMs I could then exchange the Motherboard and CPU to this combination: Intel i7-12700k on PRO Z790-A WIFI DDR4 with 32 GiB non ECC @4000mhz (nice Samsung B-Die) the board would have the 6 Sata ports I'm using currently but would not support IPMI and ECC Would this switch make sense with regard to performance, and how do you think would the power consumption change? I would have this spare hardware, if my son would upgrade his setup to an AMD AM5 9800x3D system, the i7 is currently in his rig. Maybe some additional information why I already have the AMD AM5 9800X3D - I could not resist getting the 9950X3D for my desktop system and currently the 9800X3D is selling so bad at Ebay and co that I would lose +100€. Then I thought to keep it and put it with a cheap mobo in my sons PC and use the Intel for Unraid. Is this idea total nonsense, or would this improve and future-proof my Unraid server enough? It's not that my server feels underpowered currently - with running Homeassistant VM, pi-Hole LXC, + ~20 running Dockers including Nextcloud, Vaultwarden, Jellyfin, LyrionMusicServer and from time to time some game servers I could then sell the old Xeon + Ram + Supermicro or build a second Server for family members What do you think?

I played around a bit with what ChatGPT gave me and tested it using the dry run function (to be honest, I'm a novice when it comes to these scripts). Added: Dry Run Mode Age-Based Pruning (optional) Error Handling #!/bin/bash # v0.10.4 ########################unraid-snapshot-zfs####################### ###################### User Defined Options ###################### # Enable or disable dry-run mode (set to true for testing without making changes) DRY_RUN=true # Set to false to perform actual operations # Enable or disable deletion of snapshots older than a specified number of months DELETE_OLD_SNAPSHOTS=false # Set to false to skip deleting old snapshots # Set the age threshold for old snapshot deletion (in months) DELETE_OLDER_THAN_MONTHS=12 # Change this to the desired number of months # List your ZFS datasets. You can add/remove sets DATASET=("/mnt/my_path_to_DATASET") mapfile -t DATASETS < <(zfs list -r -o name -H "${DATASET}") # Set Number of Snapshots to Keep SNAPSHOT_QTY=24 # Snapshot Name Format SNAPSHOTNAME=$(date "+simplesnap_%Y-%m-%d-%H:%M:%S") ###### Don't change below unless you know what you're doing ###### ################################################################## echo "Starting Snapshot ${SNAPSHOTNAME}" echo "Dry-run mode: ${DRY_RUN}" echo "Delete old snapshots: ${DELETE_OLD_SNAPSHOTS}" echo "Delete snapshots older than: ${DELETE_OLDER_THAN_MONTHS} months" echo "_____________________________________________________________" ## Validation Steps # Validate SNAPSHOT_QTY if ! [[ $SNAPSHOT_QTY =~ ^[0-9]+$ ]]; then echo "Error: SNAPSHOT_QTY must be a positive integer." exit 1 fi # Validate DATASETS for dataset in "${DATASETS[@]}"; do if ! zfs list "$dataset" &>/dev/null; then echo "Error: Dataset '$dataset' does not exist." exit 1 fi done # Function to handle errors handle_error() { local error_message="$1" echo "Error: $error_message" exit 1 } # Function to create snapshot if there is changed data create_snapshot_if_changed() { local DATASET="$1" local WRITTEN WRITTEN=$(zfs get -H -o value written "${DATASET}") if [[ "${WRITTEN}" != "0" ]]; then if [[ "$DRY_RUN" == "true" ]]; then echo "[DRY RUN] Would create snapshot: ${DATASET}@${SNAPSHOTNAME}" else if ! zfs snapshot "${DATASET}@${SNAPSHOTNAME}"; then handle_error "Failed to create snapshot for ${DATASET}" fi echo "Snapshot created: ${DATASET}@${SNAPSHOTNAME}" fi else echo "No changes detected in ${DATASET}. No snapshot created." fi } # Function to prune snapshots prune_snapshots() { local DATASET="$1" local KEEP="${SNAPSHOT_QTY}" # Declare the SNAPSHOTS array declare -a SNAPSHOTS # Use mapfile to split the output into the SNAPSHOTS array if ! mapfile -t SNAPSHOTS < <(zfs list -t snapshot -o name,creation -s creation -r "${DATASET}" | grep "^${DATASET}@"); then echo "Error: Failed to list snapshots for ${DATASET}" return 1 fi local SNAPSHOTS_COUNT=${#SNAPSHOTS[@]} echo "Total snapshots for ${DATASET}: ${SNAPSHOTS_COUNT}" local SNAPSHOTS_SPACE if ! SNAPSHOTS_SPACE=$(zfs get -H -o value usedbysnapshots "${DATASET}"); then echo "Error: Failed to get space used by snapshots for ${DATASET}" return 1 fi echo "Space used by snapshots for ${DATASET}: ${SNAPSHOTS_SPACE}" local NOW=$(date +%s) # Delete snapshots older than the specified number of months if [[ "$DELETE_OLD_SNAPSHOTS" == "true" ]]; then echo "Checking for snapshots older than ${DELETE_OLDER_THAN_MONTHS} months..." for snapshot_info in "${SNAPSHOTS[@]}"; do # Extract the snapshot name and creation date local snapshot_name=$(echo "$snapshot_info" | awk '{print $1}') local snapshot_creation_date=$(echo "$snapshot_info" | awk '{print $2}') local snapshot_timestamp=$(date -d "$snapshot_creation_date" +%s) # Calculate age in months local age_in_months=$(( (NOW - snapshot_timestamp) / (60 * 60 * 24 * 30) )) # Approximate 30 days per month if [[ $age_in_months -ge $DELETE_OLDER_THAN_MONTHS ]]; then if [[ "$DRY_RUN" == "true" ]]; then echo "[DRY RUN] Would delete old snapshot: ${snapshot_name} (Age: ${age_in_months} months)" else if ! zfs destroy "${snapshot_name}"; then echo "Error: Failed to delete snapshot: ${snapshot_name}" return 1 fi echo "Deleted old snapshot: ${snapshot_name} (Age: ${age_in_months} months)" fi fi done fi # Prune snapshots to retain only the desired quantity if [[ ${SNAPSHOTS_COUNT} -gt ${KEEP} ]]; then local TO_DELETE=$((SNAPSHOTS_COUNT - KEEP)) for i in "${SNAPSHOTS[@]:0:${TO_DELETE}}"; do local snapshot_name=$(echo "$i" | awk '{print $1}') if [[ "$DRY_RUN" == "true" ]]; then echo "[DRY RUN] Would delete snapshot: ${snapshot_name}" else if ! zfs destroy "${snapshot_name}"; then echo "Error: Failed to delete snapshot: ${snapshot_name}" return 1 fi echo "Deleted snapshot: ${snapshot_name}" echo "_____________________________________________________________" fi done else echo "_____________________________________________________________" fi } # Iterate over each dataset and call the functions for dataset in "${DATASETS[@]}"; do create_snapshot_if_changed "${dataset}" # Uncommented to enable snapshot creation prune_snapshots "${dataset}" done echo "----------------------------Done!----------------------------"

Thank you for the script - unfortunately, I can give you the answer you've asked for. Did you get any feedback on the script or do you experienced any issues while using it? Chat-GPT told me that there is maybe a typo: The variable SHANPSHOT_QTY contains a typo ("SHANPSHOT" instead of "SNAPSHOT"): ## Validation Steps # Validate SHANPSHOT_QTY if ! [[ $SHANPSHOT_QTY =~ ^[0-9]+$ ]]; then echo "Error: SHANPSHOT_QTY must be a positive integer." exit 1

Hallo zusammen, ich nutze ja schon länger den Container von ich777 und hätte noch eine Frage. Wenn es eine neue Version des Skripts auf Github gibt, werden die Anpassungen irgendwie eingespielt oder wie kann man die übernehmen, falls das nicht über die LXC Update Funktion im LXC Plugin eingespielt werden kann. Grüße

So wie ich das verstanden habe, ist das SVG Problem kein wirkliches Problem - nur wenn man SVG Dateien auf der Nextcloud verarbeiten möchte, dann hat man das passende Tool für imagick mit installiert. Das ist also höchstens eine Optimierung für SVG, aber sicher kein muss. Für die Verwendung eines eigenen Icons kann das Tool wohl eine Rolle spielen: Die Installation durchzuführen gibt einem also in den meisten Fällen nur das Gefühl, die Meldung nicht mehr angezeigt zu bekommen 😊

As far as I understood, the only thing needed is to turn off the "mysqueezebox.com-Service" plugin and that's it. I've also installed the replacement Tidal Plugin by "philippe_44, Michael Herger" and that's working perfect so far + I removed the old Logitech hosted plugins Tidal, Deezer etc.

I've actually done it already and the warning is gone 🙂 but I agree the documentation is quite hard to overlook. Basically, you just need to set up these two variables in the container in two steps... 1. add the universal-package-installl Mod by adding a new variable to the container (2. screenshot) linuxserver/mods:universal-package-install 2. save -> apply which restarts the Docker 3. Add a new variable "Install Packages" which lists the stuff for the mod to be installed on the next restart, in our case: imagemagick-svg After save and apply, the packet should be installed during restart of the container and the warning should be gone This should be also shown in the logs of container There is a good video on how use these Mods particular useful for the SWAG container - but the approach is the same: hope that helps 🙂

Das wird es wahrscheinlich sein, da ich die Version von linuxserver.io nutze. ---------------------------------------------------------------------------- Nur als Ergänzung, man kann auch mit der Linuxserver.io Version das SVG Problem lösen, und zwar über die Docker Mods, die mit dem io-container kommen - über diesen Weg kann man das Paket "imagemagick-svg" nachinstallieren: https://github.com/linuxserver/docker-mods/tree/universal-package-install Wie die Docker Mods funktionieren, kann man in diesem Video erfahren: die Mods die ich jetzt lade "linuxserver/mods:universal-docker|linuxserver/mods:universal-package-install" - wie es grundsätzlich funktioniert wird in dem Video gut erklärt

Hallo, vielleicht eine dumme Frage beim Hinzufügen dieses Postarguments bekomme ich folgende Fehlermeldung Den apt Befehl kennt mein Unraid wohl nicht und das einzige, was ich dazu gefunden habe, ist der Hinweis das gar nicht zu nutzen: Wo habe ich da meinen Denkfehler?

I have the same error with the missing SVG support. @blaine07 do I understand the github page correct, that it will be added later? I'm a bit confused how to fix or if I need to fix the issue? Edit: I've found the answer in the IO Discord by Driz- you could install the needed package via Docker Mods: