raeserfisk

I love this community! Thank you kindly :) Now fingers crossed: here we go!

Thank you for your quick reply! I've moved all data from the 10TB (to be replaced) and the 20TB (to become parity). What would be my best way forward?

Hi! I am about to enter uncharted (for me) territories and would love some expertise from experienced users :) Some context: I currently have an array with 1x20TB parity and a set of data drives 1x20TB, 4x18TB, 5x12TB and 1x10TB. What I would like to do, preferably in one go, is replacing the 10TB with a spare 12TB I have available (for a totalt of 6x12TB) and also move the 20TB data drive to second parity. The end goal would then be 2x20TB parity and a set of data drives 4x18TB and 6x12TB. Could I do this in one go and what would be best practise? Cheers! Kalle

Could someone help me with my new chassis? I can strongly recommend it! Excellent case for 12 drives available at https://www.aliexpress.com/item/1005007758856989.html Big thanks in advance!

This isnt related to the laptop resolution. I have the same issue on my 4k monitor and my 1440p laptop. Is there a solution in sight? As of now the JetKVM is not usable together with Unraid to work directly in the Unraid Shell :/

@JorgeB, @Kilrah & @itimpi: Thank you so much for all your efforts. I'll keep an eye out if the actual usage starts increasing and I'll relax on the warning from Netdata.

Done! Here's the updated version Overall: Device size: 100.00GiB Device allocated: 54.06GiB Device unallocated: 45.94GiB Device missing: 0.00B Device slack: 0.00B Used: 51.92GiB Free (estimated): 47.19GiB (min: 24.22GiB) Free (statfs, df): 47.19GiB Data ratio: 1.00 Metadata ratio: 2.00 Global reserve: 136.19MiB (used: 0.00B) Multiple profiles: no Data Metadata System Id Path single DUP DUP Unallocated Total Slack -- ---------- -------- -------- -------- ----------- --------- ----- 1 /dev/loop2 50.00GiB 4.00GiB 64.00MiB 45.94GiB 100.00GiB - -- ---------- -------- -------- -------- ----------- --------- ----- Total 50.00GiB 2.00GiB 32.00MiB 45.94GiB 100.00GiB 0.00B Used 48.75GiB 1.59GiB 16.00KiB --- It seems there's now a big difference in allocated space. Should I keep an eye out here for increasing allocation? And what could be the reason if it starts increasing?

Absolutley! Overall: Device size: 100.00GiB Device allocated: 99.91GiB Device unallocated: 93.00MiB Device missing: 0.00B Device slack: 0.00B Used: 51.93GiB Free (estimated): 46.19GiB (min: 46.14GiB) Free (statfs, df): 46.19GiB Data ratio: 1.00 Metadata ratio: 2.00 Global reserve: 139.89MiB (used: 0.00B) Multiple profiles: no Data Metadata System Id Path single DUP DUP Unallocated Total Slack -- ---------- -------- -------- -------- ----------- --------- ----- 1 /dev/loop2 94.85GiB 5.00GiB 64.00MiB 93.00MiB 100.00GiB - -- ---------- -------- -------- -------- ----------- --------- ----- Total 94.85GiB 2.50GiB 32.00MiB 93.00MiB 100.00GiB 0.00B Used 48.75GiB 1.59GiB 16.00KiB

Yes I was currently running a balance on all cache pools but this was initiated after the warning occured - to possibly amend the problem Thank you for the info regarding docker.img - this seems to be the culprint. Is there anyway I can investigate further what caused the issue? Regarding other issues: - The Docker.img is quite big I agree. It doesnt seem to grow anymore but I've tried reviewing all Dockers (50ish or so) to see if anyone is writing internally instead of to a set path outside the Docker. Could this be found in some automatic manner? I've failed to find anything myself. - The appdata to array is a great find! I'll review and see if I can make some changes. Cheers! Kalle

Thank you kindly for the advise. Please find my diagnostics attached ash-diagnostics-20250216-0958.zip

Hi! Since a week or so back I've had this error reported in Netdata: BTRFS allocated space utilization. Since the only drives I have that uses BTRFS is the cache-drives (my main storage NVME, my media cache disk and my NVR cache disk) I've isolated these three. I don't, however, know how to decipher which of these three that it concerns. I also dont know what the problem is and how to ammend it? I am sorry if this question is asked in the wrong part of this forum - fairly new here but eager to learn. Cheers! Kalle

Hi! Since this morning I've had a critical error: Out of Memory - reported. I've looked through the logs and isolated this: Feb 9 07:25:59 Ash kernel: out_of_memory+0x399/0x3cb Feb 9 07:25:59 Ash kernel: Out of memory: Killed process 19699 (ffmpeg) total-vm:51582180kB, anon-rss:51146476kB, file-rss:384kB, shmem-rss:0kB, UID:0 pgtables:100400kB oom_score_adj:0 To my knowledge the only two applications that use FFMPEG is Plex and Frigate (but I might be wrong). I am unsure if this only concerns RAM usage so I made sure that the transcode directory in Plex is using /dev/shm and it is. I am unsure if there are any way to dictate the same in Frigate. /dev/shm should only use up to 50% of RAM right so this should not be able to break..? I would love to get to the bottom of this before rebooting. To my knowledge this is the first time I've encountered this problem during my many years of Unraid usage. Cheers! Kalle ash-diagnostics-20250216-0958.zip

Hi! I am trying out the Tailscale-route to see if it would fit my needs but I cant have it work the way I want it to: - Single Unraid-host with Tailscale-plugin. - Tailscale-account with Mullvad-plugin activated. I would like to have Mullvad as exit node for the entire Unraid-platform. My intention is this helping my services on the Unraid server communicating with eachother while all outbound traffic is routed through Mullvad for privacy. Am I thinking about this the right way? Because what I fail to do is activating Mullvad as exit node in the Tailscale plugin? The "Exit Node" part is not clickable so None is the only choice?

I'll add to the discussion as well - just built a 116TB (available with 2 parity drives on top) system in this little bad boy Managed this by going 4x12 + 4x10 + 1x12 (on the floor) in the drive chamber. Another 2x12 and 2x8 in the floor in the main chamber for a total of 13 3,5 drives. On top of this 2TB nvme and 4TB SSD for system/cache. I'll try to add 2 additional SSDs for additional cache at a later stage.