The free version of Tailscale was crazy simple (unraid plugin vice docker container) with the only limitation being max 3 users. After that it's $5 / month for up to 6 users.
How big is your NAS?
- Thread starter sswilson
- Start date
The free version of Tailscale was crazy simple (unraid plugin vice docker container) with the only limitation being max 3 users. After that it's $5 / month for up to 6 users.
Random question for folks who've used Unraid.......
Any idea why there's a 4.5TB discrepancy between the Root and Data on the Array? (As reported by either Radarr or Sonarr).
Not critical, but it's a mystery that my Google-Fu is failing to come up with an answer to.
Any idea why there's a 4.5TB discrepancy between the Root and Data on the Array? (As reported by either Radarr or Sonarr).
Not critical, but it's a mystery that my Google-Fu is failing to come up with an answer to.
The root (/) partition (OS) is 60GB , and The /data (everything else) is 55.5TB ?
And me putting my left socks on my right foot. The usualYeah, that's it. Don't mind me constantly mixing up my GBs and TBs......
Yet another random question for folks who are familiar with Unraid.....
I've currently got a single 20TB + 4 10TB data drives and have been using the "High Water" setting for how to fill the drives. A couple of the 10TB drives filled up to 5TB and a third started filling before I added the 20TB which is now approaching 9+TB, and thus will roll over to filling one of the 10TB drives shortly.
So here's the question..... If I'm correctly reading how the high water setting works it calculates 50% of the largest drive and applies that to the system... does that mean it will attempt to fill my 10TB drives completely once it hits the 10TB mark on the larger disk?
The obvious solution to prevent that is to switch over to the "Most-Free" method once the 20TB hits the half way point, and that's probably what I'm going to do, but was curious if my thinking was wrong on the subject.
I've currently got a single 20TB + 4 10TB data drives and have been using the "High Water" setting for how to fill the drives. A couple of the 10TB drives filled up to 5TB and a third started filling before I added the 20TB which is now approaching 9+TB, and thus will roll over to filling one of the 10TB drives shortly.
So here's the question..... If I'm correctly reading how the high water setting works it calculates 50% of the largest drive and applies that to the system... does that mean it will attempt to fill my 10TB drives completely once it hits the 10TB mark on the larger disk?
The obvious solution to prevent that is to switch over to the "Most-Free" method once the 20TB hits the half way point, and that's probably what I'm going to do, but was curious if my thinking was wrong on the subject.
IIRC the watermark is percentage based, but capped at the size of the largest drive. So assuming the 10TB drives are all at 5TB used; once your 20TB drive gets to 10TB, then each of the 10TB will go to 7.5TB, then cut back to the 20TB to bump to 15TB, etc, etc. Each time the free space is halved by percentage.
Keep in mind that your 'split level' settings will impact this as well.
*EDIT* if you're using the NAS for media, I'd recommend you stick to high water mark unless you see issues. Mostly because as you copy TV series over, they will all end up on the same drive. (depending on your split level settings.) This means less drive spin up as you binge a series or flip through episodes of the same show. It also means the latest content that you've added, should all be on the same drive, also limiting drive spin up requirements if you're likely to be watching newly added content more than older.
Last edited:
Is that how it works though? That's how I initially thought the system would work in that it would fill each drive to 50% of that drive's capacity, and then up to 75%, but the way I'm reading the documentation of the high water mark is that it's a global TB across all drives based on 50% of the largest drive (as opposed to a global 50% of each individual drive) thus the 10TB level will be applied to all of the smaller drives regardless of whether or not it fills them up completely.
Maybe I'm reading the documentation wrong.
I'm pretty sure that's how it works. I know someone that I can ask for sure who runs a couple hundred TB across a variety of drive sizes. But he won't be available until later in the evening.
*EDIT* I just spoke to my guy and he's stating the oddity of documentation is correct as you mentioned. So in your example, the 10TB drives would completely fill before the 20TB gets used again. So, not great. His recommendation is to go with 'most free' and use your split levels to manage groupings of media.
My bad for misunderstanding. I have all identical drives, so it's not an issue for me, but now I think I'll go switch mine over as well.
Last edited:
I'm pretty sure that's how it works. I know someone that I can ask for sure who runs a couple hundred TB across a variety of drive sizes. But he won't be available until later in the evening.
*EDIT* I just spoke to my guy and he's stating the oddity of documentation is correct as you mentioned. So in your example, the 10TB drives would completely fill before the 20TB gets used again. So, not great. His recommendation is to go with 'most free' and use your split levels to manage groupings of media.
My bad for misunderstanding. I have all identical drives, so it's not an issue for me, but now I think I'll go switch mine over as well.
Thanks for reaching out to your friend for me. I had to ask as the documented process didn't make much sense to me, but it seemed pretty clear on how it would work.
I'll be switching over to "most free" once my 20TB hits the half way mark.
xentr_legal_notice_title
xentr_legal_notice_description