- Location
- Moncton NB
That's a sound advice, I do the same. Also, 22TB for parity? You are wasting 12TB![]()
It won't look like that when I add a 20TB drive into the mix.
That's a sound advice, I do the same. Also, 22TB for parity? You are wasting 12TB![]()
It won't look like that when I add a 20TB drive into the mix.![]()
I am not sure what you were thinking, but if you will replace 10TB drives with 20TB ones - your partitions would still be 10TB as that is the array size. Or if you add 20TB new drives, then that could work but only for new drives.
I am not sure what you were thinking, but if you will replace 10TB drives with 20TB ones - your partitions would still be 10TB as that is the array size. Or if you add 20TB new drives, then that could work but only for new drives.
I was under the impression that you could replace a smaller drive with a larger one, but even if that isn't the case it'd be for a new drive/replacement (clear the old drive of data, remove from the array, add the new drive).
Either way.... I grabbed the 22TB drive before I got the bunch of used 10's, I need to find a use for it, and I don't really have a spot for a single drive of that size if it isn't part of the array.
Now that I've got an idea of what a crazy big content library is going to take up, I could conceivably ditch the 8TB, grab a 10TB to use as parity and then bring the 22TB in outside of the array as a backup.


Thumbnails, intro, etc will not use the gpu in ny experience. It always uses the cpu.View attachment 44221
Not quite as heavy usage as I had during all-drive parity, but scanning a relatively full library for intro skip, and generating trickplay images puts a relatively heavy load on the processor.
I also went through my transcode settings to ensure I was offloading to the iGPU. I had the settings selected, but not sure I had the docker container configured so that it could access the iGPU. (Confirmed it's working now).
Thumbnails, intro, etc will not use the gpu in ny experience. It always uses the cpu.
Ok, It wasnt very clear to me in your post. I personally wondered why it never used the gpu to create thumbnails as it is going through the transcoding process to do it.Yeah, I'm aware that it's just the transcoding which will make use of the igpu, and in all honesty I don't think there's much transcoding going on. It's all pretty much direct play over my local network.
I have all of my tasks set to run on a schedule between 2 and 6am. That way it doesnt affect anyone watching my server, well at least its minimal. Even with a 14900k it can cause major buffering when people are watching. Proably because its a spinner issue.Yeah I ended up looking at both the igpu transcode settings and the two plugins based on a video. The video is how the two are related.
Scanning for trickplay (generates images for the position slider) should probably be done earlier rather than later when it comes to the size of a person's library..... 17+ hrs in and I'm still only at 25%.![]()
xentr_legal_notice_description