Grobalt

A bit strange, i did not change anything on my system since many weeks and suddenly TMM is not working any more. Logfile: Fontconfig error: No writable cache directories 2024-01-29 22:02:52,046 INFO success: x11 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-01-29 22:02:52,046 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-01-29 22:02:52,046 INFO success: websockify entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-01-29 22:02:52,046 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Fontconfig error: No writable cache directories Fontconfig error: No writable cache directories Fontconfig error: No writable cache directories Fontconfig error: No writable cache directories

thanks, enabled and waiting for reproduction

Is there a new way, easier, in the meantime? I have like 2000 movies l, managing with TMM and all small files are in the movies folder. Would be nice to have a fast Kodi etc that can access the small files on SSD instead spinning the harddrives

is this still the correct one ? cannot see it in the community apps and the link to My Repository: https://github.com/SmartPhoneLover/unraid-docker-templates is dead as well

no they dont draw more power and most of the time they are spin down. Spin up and spin down causing issues on drives is a myth I have customers with more then 30k disks with a "zero watt storage" design where disks are used like a tape without any problem.

Yes, parity will be done after all files are written, I upgraded all disks and have another copy of the files. But an additional nic will be more power draw, not the best option. And no write cache is default at enterprise data disks, therefore I enable that in the go.cfg

as shown in post 1 - both are unraid, both are running same version and i copy via MC in a putty instance

adding NFS share on main page and click on mount :)

/etc/nfsmount.conf # Protocol Version [3,4] # This defines the default protocol version which will # be used to start the negotiation with the server. Defaultvers=4 then restartet nfs service unraid-diagnostics-20230802-1455.zip

I have 2 unraid systems which i currently "clone". Copying 40TB of large files from one to the other. Default is v3, but i changed to NFS v4 and restartet the nfs server as well -> behaves same. When i start the nfs service it starts copying with around 180-200 MB/s over 2.5gbit ethernet. After like 12 hours it is around 80-100 MB/s left. Stopping and Starting nfs service again revices original speed. Any idea ? I can find some google results with same problem but no solution. - NFS simply gradually slows down over time - NFSv4.1 mount is extremly slow until remount - NFS low performance after some activity - Severe NFS performance degradation after LP #2003053 - https://access.redhat.com/solutions/6271621 ( i cannot read the solution) Both running 6.12.3

DVB-S2 Card for TVheadend, location Germany, sending to EU. 90 euro + shipping

After a week with array on compressed ZFS ... i copy everything back to XFS. Huge cpu workload, nearly all time a core is 100% load, the copy speed is below 50 MB/s with 18TB enterprise SATA spindles (both write methods).

Ich habe nur einen Unraid Server und (Dateigröße bezogen) von der Struktur meiner Daten und Wichtigkeit reicht mir eigentlich eine Parity Disk (da es mich nicht stört wenn Medien verloren gehen). Dennoch gibt es natürlich auch papierkram, eMail Archiv etc, was aber nur paar Gigabyte sind -> da hätte ich gerne aber double parity oder .. zumindest eine Kopie auf einer zweiten Disk. Dachte an einen Share der nur auf einer Platte läuft und auf den täglich ein Backup gemacht wird vom eigentlich großen Array. Mit welchem Container wäre das am einfachsten umzusetzen ? Ich möchte einfach nicht wegen 5 Gigabyte eine zweite 18TB Parity Disk vergeuden oder deswegen Controller nachrüsten für weitere SATA ports etc.

Hi, so ein B660M Mortar DDR4 (ohne wifi) habe ich zum Verkauf, liegt hier schon eine Weile und wurde nie verbaut.