danimal86

is it normal for the second parity drive rebuild to go slower than the first?

That makes total sense! Thanks for dropping some knowledge on me! It is decreasing as time goes. I was hoping it was going to be done by the time i go to sleep, but might have to do it in the morning, or stay up.

I think you are right. It seemed like it was going to be close, and i dont want to be rushed. I'll get the parity drives swapped (second one should be done tomorrow evening) then i'll swap drives 1/2 with new ones and rebuild and call it. I can try to move data when i get back. Its interesting, its current position on the parity rebuild is 8.54tb, and its running at about 175mb/s, i think it was running faster at the start (around 200)

When i swap the #1 & #2 drives with 14tb drives, it should only write what is on those drives to the new ones right (not like a parity rebuild where its going to take a full 24hrs)? I'm just trying to figure out how to get all of this done in the next 4 days before i head out of town. I'm fairly confident in my drives health. The only time i've had any errors on the drives was when a sata cable died on me, it was a quick fix. They are pretty old though. Should the parity check after the parity build be done after both parity drives is swapped, or do 1 then parity check, then do the other then parity check

My data drives are in xfs, i wasn't planning on changing formats, but is it something i should do now? You are right, i dont need to move data off the drives first, i can just physically swap drives 1 and 2 with the new ones and re-build. Can i do 2 at once or should i do one at a time?

I read through it....a lot to take in and try to process. Copying seems like a good idea, so i would still need to unbalance 2 drives to be able to install the new ones, then i would be able to copy data one drive at a time to the new drives and if the data is identical then i can remove the drive from the array and then physically from the server? Is there any way of doing this without the command line? I've used it before, but not the most comfortable with it.

Now were talking. I'm liking the looks of the unbalance plugin! I guess i'll have to do it in two steps, i'll move all the data off of two drives that have the least amount of data written to them currently and add the new drives in....and then move the rest of the data over to the new drives and remove the old ones from the array. sound reasonable?

I was doing reseach last night and came across the wiki page on Shrink Array. Thats where i read about the New Config option. Ultimately i want my array to be 2 14tb parity and 2 14tb storage drives on the array. Those 2 and 3 tb drives are pretty old and well beyond their rated hrs. So i can shut down, pull drives 1 & 2 install the new drives, select those for the array, and then rebuild and it should be good at that point. I would have 42tb at that point. I guess i could just leave those old drives still installed i guess, or is there an easy way to transfer data off those onto the new drives.

I just want to get these old 2 & 3tb drives off the array and use the new 14tb'ers, without loosing any data. Not moving any data outside of the array.

Thanks. I set my rebuild to start last night and its just chugging along at about 200MB/s. It 11hrs in and looks like its got just over 12hrs to go. I'll swap the second drive over before i go to sleep and let it run over night again. I'm always scared to mess with the array, but its been pretty straight forward. Is the New Config going to be the best way to be able to remove a few drives so i can put in 2 14tb drives?

Thanks for bringing that to my attention, I'll have to set it to not autostart My array will be active during the rebuild?

Thanks @squid I'll skip the preclear. So I'll remove 1 parity, plug a new drive in, I'm assuming it will not Auto start the array, and I should just have to select the new drive from the drop down and click start the array? Ultimately, I'd like to move my 10ish tv of data to the new drives and not use the (very old) 2&3tb drives, what's my best course of action to get data off the old and on the new

i'm at my drive limit using a hodge podge of small drives and i want to consolidate my drives to 4 14tb drives i just got. I added 2 drives and they show up as unassigned drives, but i cant start my array because its at my license drive limit. I really dont want to pay 50 bucks when i wont go over 12 drives just to be able to preclear them. I'm running an lsi 9211-8i card along with my motherboard ports (the 14tb drives are on the lsi card). How do i go about pre-clearing these? I cant seem to find out if its safe to just plug the drives in after the array has started. My other option is to just not pre-clear them. If thats the case, then i would just remove one of the 3tb parity drives and assign one of the 14tb drives and let it rebuild? Then do the same with the remaining 3tb?

I didn't know i needed to do that until i had deleted my docker image. Now that everything is back up and running, and tdarr isn't filling up the image, i'll go in and delete those extras.

alright, its done. I was able to redownload all my apps. the only hiccup was that under the apps tab and "previous apps" there were ones that i had downloaded before but had removed. Example: there was a plex official and linuxiso version of Plex on there, so i had to figure out which one i was using. Advice to anyone looking to do this: make a list of the apps you are using and their developers. all my dockers popped back up just fine.

Alright, i read about that....even though they say its an "easy process" ....im scared. Lol Doing an appdata backup right now in case things go south, and i'll delete the docker image and re-install apps. Following this for the delete:

I was having a problem with Tdarr where i had an path incorrect and i believe it was writing data where it shouldn't be. I THINK i have solved that problem, but my docker size still shows almost full I've tried restarting tdarr and tdarr node. I tried restarting the docker engine. I left the docker engine off and restarted unraid. I was hoping that that would flush out what had been written in the wrong place, but no go. I see there's a "scrub" under the docker advanced settings, but i dont want to go being all click-happy and mess something up I've attached diagnostics. Thoughts? tower-diagnostics-20210930-1512.zip

I restarted both tdarr and the node, didnt flush it, restarted the docker engine, didn't flush it. Left the docker engine off, restarted the server and then restarted the docker engine, didn't work. Still sitting at 96% Any other ideas? Looks like with the docker engine off, i can just resize the image allocation from 20gb to something else, but i'd rather fix it than band aid it.

I may have figured it out. On one of my libraries (within tdarr) i had the transcode cache set to /tmp not /temp. I bet that was it. I'll update as it goes. How do i get my docker image size back down to normal

I'm having the same issue, i've tried moving my transcode folder to a spot within /media. It was working fine for about 8hrs (docker image wasn't rising in size), but when we started watching plex and it shot up to 99%

This doesn't seem like it would fix my problem with the docker image getting too big. I'm not sure whats going on with it, it ran for a solid 8hrs and my docker image was around 63%, then all of a sudden when we started watching plex, it skyrocketed to 99%

I ran through the spaceinvader one tutorial and am running into a file path issue (at least i think it is) My docker image is filling up. I'm getting critical errors: I'm guessing that its re-encoding to somewhere where it shouldn't, but i cant figure out why. I did make a new share called "temp" and set it to Prefer for the cache settings. here's the tdarr template: tdarr node: in tdarr under libraries (for my movies library) Edit: So i've got the dockers running right now, and not getting any big errors, but docker memory is still high:

Well, i just tried to point the /transcode to /mnt/cache to see if that would work, and it seems like it does. Anyone know why the unassigned drive m.2 with about 90gb free wouldn't work, but my cache with 500gb free would? Does the transcodes really need that much room?

Sorry if its the wrong place to post this, i couldn't find a support thread for the Official PMS support. I'm trying to record the Olympic coverage using HDHomeRun Quatro and plex. I tried to play a recorded file on the web player (on a windows machine) and it says Not enough disk space to convert this item. I can go to the file itself on the download directory and can play it using VLC just fine, but not through plex. I have my transcode path set to /tm/ i have a feeling that that may be the issue. I have 16gigs of ram on the server and the recorded files are around 7gigs (i'm sure those files get big when converting?) I've tried changing the /transcode directory on the docker from /tmp/ to /mnt/disks/Transcode (an unassigned m.2 with about 90gb free) and that didn't work. Any advice? Not sure if it matters, but there are recordings happening (but not trying to play the file that is in the middle of recording) while i'm trying to play the past recordings. Here's htop Here's what the log says: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 40-plex-first-run: executing... Plex Media Server first run setup complete [cont-init.d] 40-plex-first-run: exited 0. [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing... [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0. [cont-init.d] 50-plex-update: executing... [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done. Critical: libusb_init failed

I thought i'd follow up with myself, maybe it will help others out with the same issue. Here's how i solved my problem: Shut down the server, and pull the flash drive. Plug the flash drive into another computer and in the "config" folder there is a file named "go" Open that in notepad and add "nvidia-persistenced" to the bottom. Eject the usb and put it back in the server and boot. Upon reboot, my P2000 goes straight into P8 and also my cpu usage went from 6-8% at idle to 1-2% at idle