fmjets11

I got it figured out. No idea how this happens (especially when I am not home) but somehow in the bios Advanced - PCI Subsystem setting - LSI onboard Oprom - was set to disabled. Once I went in and enabled this it detected all of the drives right away with no issues. Hopefully this helps someone else.

I just looked at how everything is wired in and this is the breakdown: 2 SATA onboard connections go to the SSD drives (the two that are showing up) There are 3 SAS connections on the board - These connect to 7 Hard Drives and one CD ROM / BluRay Drive (cd/dvd HL-DT-ST BD-RE WH16NS40) 2 SAS connections go from the motherboard to the expansion card (which then connect to 7 hard drives in total 1 of the connections from the motherboard has a SAS to SATA connector cable (with 4 SATAs connections on it - 3 have always been disconnected and still are) but one of the four connects to the CD ROM drive that is showing up successfully (cd/dvd HL-DT-ST BD-RE WH16NS40) Not sure if this means there is possibly something that has gone bad with the SAS part of the motherboard, or if something has happened relating to SAS BIOS (I originally followed this tutorial here: https://www.serverbuilds.net/flashing-onboard-sas-2008 ) Additional Info: Motherboard Specs - https://www.gigabyte.com/us/Enterprise/Server-Motherboard/GA-7PESH2-rev-10#Support-Manual Original Server Guide Used to Build- https://www.serverbuilds.net/anniversary

Confirmed the expansion card is in PCI-E slot one and it is enabled. There is another open PCI-E slot, I moved the expansion card there and nothing changed.

Not sure I understand exactly what you mean, but the SAS Expander Card is connected into the motherboard via two separate Mini SAS 36-Pin to SFF-8087 Cables then SATA connections from the expander card go directly to the hard drives.

Through an HP 24-Bay 3GB SAS Expander Card 487738-001.

I just got back from being out of town and my server is in shambles it seems. I have never had any issues since I have built this thing a few years ago. When I powered it on the main message is that 7 of the devices (not the two cache drives - see screenshot) are all missing and the array is unable to be started. I hope I can get some help as far as where do I even start. They are not showing up in un-assigned devices that I can tell. I am no Unraid expert but this feels to me like it could be hardware related but I do not know what to do to even begin to figure that out. I checked all connections twice, re-seeded everything and confirmed the drives have power so my gut goes to, is this the SATA expansion card? Hoping someone can guide me here and see something in the logs that gives me a path forward. Would the hardware profiler be helpful here to help diagnose a potential issue? I appreciate any help in advance. tower-syslog-20240315-1732.zip tower-diagnostics-20240315-1331.zip

Updated to the most recent OS and get this message when I try to restart the plex docker app. I searched around and some say just be patient and it fixes itself but its been 6 hours and still the same message. I restarted the server, restarted the container still same error. "MAINTENANCE" STATUS="PMS IS CURRENTLY RUNNING STARTUP MAINTENANCE TASKS." Is the next best thing to try to revert the docker to an old version, if so what does that entail/is it the right move. Thanks all for the help and patience in helping explain and troubleshoot.

I just updated to Unraid 6.9 but now when I try to start plexnvidia it throw "Bad Parameter" error. Everytime I have updated in the past, I would also update the plugin "Unraid Nvidia" and choose correct drivers etc. Upon looking into this plugin it appears that this has been deprecated (some sort of drama it appears). What do I need to do to get this back working again?

It is interesting that when I did the upgrade something similar happened to me....my cache drives were both unmourned and taken out of the array but data wasn’t lost. Maybe 6.9 isn’t stable? Sent from my iPhone using Tapatalk

Great that worked! Thanks so much! Now back to the updating question. Did I do something wrong before? I just hit update to update to 6.90 and when it restarted thats when all of this happened. Do I need to do something differenT?

Got it : What am I looking for here? Is this just to see if they were both caches in a pool together?

How do I do run that command? I am trying to run it in terminal but it just says no such file or directory. Do i replace "Name of the ud mountpoint" with something else? @trurl@JorgeB

That doesnt seem to tell me if it was a cache drive before it got taken off of the array etc though. Unless I am missing it.

Yes i think so but not 100%. I setup the server like two years ago and havent had to do anything like this to it since setup so problem is I dont remember. I am not 100% they were both cache drives either. Is there a way to see what they were before and then should I reslot them and start the array?

Hello, Today I went to update my OS and when I did all of my docker's disappeared completely. So I rolled back to the previous OS and realized the reason the dockers disappeared might be because I have 2 drives that were completely unmounted now (assuming one was the cache drive, I am not sure what the other drive was though). I remounted them but not sure what to do from here. These are my SSD drives. Is there a way to figure out which drive should go in which slot to re-start the array without losing data? I am worried about trying to put the array back together and it rebuilding and I lose everything. Logs attached. Thanks tower-diagnostics-20210303-1141.zip