cypres0099

That I don't know. I never assigned it manually. All I did was plug it in and turn it on and it showed up in unassigned. Initially I think it gave me the option to mount, but when I refreshed the page it had changed to unmount.

When you say copy those files somewhere, you mean you think they are fully intact somewhere? Which drive(s) are at biggest risk here? Just disk 2 or more? Between the diagnostic and that screen shot I stopped the array, turned off the external hard drive (9RHWXDWC ), rebooted, and then turned the external hard drive back on.

Wholeheartedly agree with this. Diagnostics posted. The contents of Disk 2 seem accessible the files I tried open. There are a couple empty folders that I'm not sure if they were empty on disk 2 before. Is there a better way to tell than just randomly opening files that are present to see if they work? I don't have great backups. A lot is backed up on the cloud, but there are some personal photos and videos that I would be pretty sad to lose. mongo-diagnostics-20210727-1707.zip

This is what my current situation looks like. The unassigned drive (that i thought had failed) is accessible in my windows network folders and it's about the same size as Drive 1. So maybe I got confused about which drive was having the errors and replaced the wrong drive? So the unassigned drive is actually a still good version of drive 1 and I can just put it back in place of the red x Disk 1?

I just didn't think through the problem very well. Saw a failed dis and thought "I have another disk to pop in there" so that's what I did :-/ I just hooked up the drive that I thought had failed to an external sata enclosure. It's now showing in unassigned devices.

Yes

Oh boy, I think I'm losing track of what disk went bad when. A disk (pretty sure it was disk 2) went offline last week and I replaced it with a spare disk I had in case of this situation. While it was rebuilding, Disk 1 started throwing errors.

So I just want to be sure about something. I had Disk 2 go down last week, so I replaced Disk 2 and started a rebuild. However, during the rebuild Disk 1 started throwing errors and I couldn't access files on that disk. But the rebuild supposedly completed on Disk 2 (says lots of errors). If I now try a rebuild on Disk 1 and the Disk 2 data is corrupted, will I lose the data on both drives?

Will have to do that after I hopefully get it sorted!

@JorgeB the rebuild of Disk 2 did finish (not 100% sure if finished correctly). I hope I didn't screw myself by doing that I only had one spare SATA cable so I replaced it on Disk 1 (which was the one throwing the errors). I rebooted and Disk 1 is showing disabled. If it was a bad cable that did it, how do I get the array to pull Disk 1 back in? mongo-diagnostics-20210727-1755.zip

Most recent diagnostic mongo-diagnostics-20210725-1700.zip

Disk 1 started throwing millions of errors during the disk 2 rebuild. Am I going to lose 20+ TB of data?

Ugh, now it's saying that Disk1 can't be written too. Disk 2 is currently being rebuilt.

I'm doing a disk rebuild on that disabled disk, so I guess if that works fine, it's not that big of an issue. Mostly just the mover not running now.

Thanks for chiming in @ChatNoir That folder doesn't really have anything in it. I think it was setup just for pre-roll in plex for some reason. I've had this cache setup for like 6 years without issues, but all of a sudden after upgrading to 6.9.2 it's stopped moving files every night. Now there's another new issue popping up, it says my disk 2 is disabled and stuck in read only or something. I've attached the zip diagnostic mongo-diagnostics-20210725-1448.zip

Looking at it now, it seems my cache drive is completely full.

Fix common problems showing these issues.

I upgraded unraid last week and have been running into issues with a few dockers not starting and not upgrading and then this happened. Can't get the docker service to start anymore. What can I do?

DOH! Was there some specific way I was supposed to get the diagnostics to make sure it was included? Any tips on getting rid of the bad docker mount? Here's the screenshot of the run command for plex

It took a lot longer than it usually does, but I just captured the log while the RAM was at 100% usage. mongo-diagnostics-20200211-1957.zip

ok, thanks for checking into that. I'll keep an eye on the usage and grab the log the next time I see it full.

Attached run command & transcode directory below. It looks like DLNA is off, if that's what you meant.

Hey all, I'm still having problems with Plex filling up the RAM to 100% then locking the server up every other day. A reboot of the plex docker fixes it temporarily. I've attached my sys log here, but I rebooted the docker before I downloaded the log. Hopefully it's helpful. mongo-diagnostics-20200129-1744.zip

Would love to start trouble shooting this. It's locking up every other day.

Well the problem happened again. Plex went up to 100% RAM usage this time and totally locked up the clients. Server was running super slow too. Once the Plex container was manually restarted, everything went back to normal. Any ideas how to fix this? It's very frustrating.