drumstyk1

bump, i am really stuck here...

I have been using the Plex docker from limetech since forever without an issue. I brought my server down for some maintenance and changed a lot of things including replacing/rebuilding a drive, updating unraid, updating several plugins, etc. I am not sure how i broke it but I could not get PMS to run. It appears to run fine from the docker screen but when i log into server:32400/web it just spins on "looking for servers" forever. I have this line in my plex log: Error in command line:the argument for option '--serverUuid' should follow immediately after the equal sign After about a week, I got desperate and deleted the docker image and the config files and tried to start fresh using the binhex-plexpass release but I get the same result. Any clue on where to start with this? Any tips would be appreciated!

Thank you so much for the help. Per your suggestion, I restored a backup to a new flash drive and it worked like a charm.

I'm not sure of where to start on this issue. Here is the sequence of events: Parity disk got a red X I added a docker for Home Assistant and played with it (probably irrelevant) I ran smart reports on my parity disk which all passed I decided to preclear the parity disk (3 cycles with built-in tool) I got a notification that cycle 1 passed Went to check on cycle 2 and couldn't get a response from the tower at all (waited several days) Rebooted Now all of my disks are missing completely. there is no longer a version number in the top right of my dashboard. If memory serves, a diagnostic saves to the root of my flash which i can't seem to mount. Where should i start on troubleshooting this?

Perfect! This is an old archive drive that i know hasn't been touched in a long time. I will give that a go. Thanks for all the help. I truly appreciate it.

Whoa, I just followed your instructions through step 3 but my disk5 is now showing up as green... Do i need to disable/enable disk5 after all? Thanks so much for the help!

i popped out and re-seated my parity drive and rebooted my server. Now it has a warning "ALL DATA ON THIS DISK WILL BE ERASED WHEN ARRAY IS STARTED" i am scared to do this because I don't understand how unraid could rebuild my parity when my disk5 is already being emulated. Any suggestions on how to avoid data loss would be much appreciated...

Would I take the array offline before messing with it. My dashboard says that mover is currently running so I don't know if I can force a spin down.

Hey guys. My disk5 had an issue so I disconnected it, started/stopped the array, and then re-added it. I asked it to rebuild the drive but it has been stuck at 0.0% for 2 days and now my parity drive is red. I'm not really sure where to start now. My disk 5 has data that I would prefer not to lose but my main concern is really the remainder of my array being unprotected. I just ordered 2 more drives just in case. If someone would point me in the right direction, I would greatly appreciate the help. Thanks! Unraid Version: 6.3.2 Diagnostics and smart reports are attached jarvis-smart-Parity.zip jarvis-smart-Disk5.zip jarvis-diagnostics-20170812-1121.zip

I promise not to clutter up this thread with help requests. I have read through the majority of this thread and I'm pretty certain that I am suffering from the marvell related red-ball and data corruption issue (not sure about the parity check speed issue). I would like to volunteer to be a guinea pig if you guys are still searching for a solution. I have posted logs and info in my own thread here: http://lime-technology.com/forum/index.php?topic=43746.0 but please let me know if there is anything I can provide or try that would help you guys out at all. Other than that, keep up the good work!

If anyone has any ideas, i'm kinda desperate here. I feel like a sitting duck without a valid parity...

My power supply is the SeaSonic X Series X650 Gold (SS-650KM): http://www.newegg.com/Product/Product.aspx?Item=N82E16817151088 If memory serves, I think it's all coming off of a single 12v rail. Thank you for the help!

Any suggestions on how to troubleshoot this? I greatly appreciate your time.

Ok, I rebuilt the drive in a different hdd bay with a different SAS cable. It said it was successful and stayed up about a day before redballing again. This is the brand new replacement drive that passed 3 preclear cycles. The drive failed in the middle of a non-correcting parity check. I'm not sure if that's related or not. I am attaching a new log. Any insight or troubleshooting suggestions would be greatly appreciated! jarvis-diagnostics-20151103-0820.zip

If the breakout cables go to a hotswap cage, then it's not an issue. But if they go directly to the drive, you've got to make sure that the breakouts are to spec. http://lime-technology.com/forum/index.php?topic=36065.0 Ok, i checked my connections and they all seem to be solid. I have a sas cable servicing parity, disk1, disk2, and disk3, and then a separate sas cable for disk 4 and 5. Here is a photo: https://drive.google.com/file/d/0BxKMUqtDPm-yLTQtYnBhZTB3dDg/view?usp=sharing For kicks, i moved my faulty disk3 to another slot on a different sas cable and it still shows up faulty. Im guessing this is because unraid is remembering the drives ID as redballed?