xdriver

I am thinking I may move the data from the "virtual?" 3TB disk onto the array since I have space, get a large 20-22TB drive and install it and have the parity get rebuilt on that new larger drive and save the 14TB as a spare. Thanks Larson

I have a failed 3TB drive, a parity of 12TB, and a replacement drive that I had sitting and just shucked that is 14TB. I think it would be wisest to purchase a new 20-22TB drive and replace the parity with it, then add the parity as a drive in the array and save the 14TB as a spare drive, or transfer the 3TB of data to one of the other drives, let the parity rebuild and wait till a deal no a larger drive. I am also thinking of putting in an SSD for audio/music. Any good reason to do something else? Suggestions on when these larger drives go on sale or should I just put a deal alert on slickdeals or some other website? Thanks for helping brainstorm and work through this.

I have a 3TB drive that has errors and unraid has taken offline and emulated the data. I have 15TB free over my other drives. What is the easiest way to just remove the drive and let unraid do its thing? Is there a "better way" than the easiest way, other than just replacing the drive? Thank you

How would I find out what is being written and where? Any idea what set of logs? Also, I added a shot of the confit file for Plex above, is that the one you were referring to? Thank you Sent from my iPhone using Tapatalk

It just has chapter thumbnails, not the whole video, so I don't think that's it.

This one? /mnt/user/appdata/plex (image attached)

Would this matter if nothing is being transcoded? These full docker messages come up at the same time 3 times a day even when not in use/watching anything. On that same note, does it make sense map the transcode folder to my cache drive or to the array?

While my docker container is on the smaller side, 15GB, I have recently run into an issue of it getting full multiple times a day. These events happen at 12:23am, 10:19am, 12:28pm and they do not happen when I stop the Plex docker container. I believe this started when I enabled the Sonic feature for music in Plex. I have attached the paths I have in hopes that someone can tell me what I have set wrong, or where I need to look in order to fix this issue, maybe a path in the Plex docker itself? I posted about this before, but lacked adding some extra detail. I get the alert emails: Event: Docker high image disk utilization Subject: Warning [TOWER] - Docker image disk utilization of 75% (then a few other full warnings within a couple of minutes - 87%90%/100%) Description: Docker utilization of image file /mnt/cache/docker.img Importance: warning Event: Docker image disk utilization Subject: Notice [TOWER] - Docker image disk utilization returned to normal level Description: Docker utilization of image file /mnt/cache/docker.img Importance: normal Thank you in advance. Please help me set my paths

Anyone able to help me figure out what path is not mapped properly? Diagnostic file attached. Thank you in advance for your assistance tower-diagnostics-20230607-0817.zip

So unmapped paths are stored in the docket instead of the array? Why would this just start all of a sudden? Hmm, actually I set up the audio imprint sonic thing fairly recently, maybe that’s it. Sent from my iPhone using Tapatalk

Screen shot attached. This keeps going back and forth between high usage and normal levels. Nothing is downloading, so I am unsure what I should be looking for or where. Thank you

This seems to be correct, so thank you for putting any of my concerns to rest. Thanks again.

Just looking for some information on the uses and support for a Bluray/DVD reader/burner. I have an LG WH14NS40. I saw the Make MKV app right off the bat and have used it on my desktop to rip all of my DVDs and Blurays for use in PLEX, but the drive doesn't fit in my new desktop. I am wondering if there is full support to read and move data from discs to UNRAID, and if it has the capability of burning to discs as well. Thanks.

I am replacing my parity with a larger drive after a different drive failed, and am putting the old parity into the array. I am currently around 78% into the process and at some point during the night, fix common problems gave the "error" disk6 (WDC_DRIVE SERIAL HERE) is disabled. Is this normal, or is there a real error? In the fix common problem app, it says "Begin Investigation Here" with a button that just goes to the unraid MAIN page. It appears the process is still moving forward, normal or not?

I removed the dGPU for now. I will need to look into deleting the boot config, but for now, I am happy it is up and running. Now to try rebuilding the parity.