mathomas3

good advice here

without taking a good look at all the the hardware that you are using... You have tons of free space on your array... I would suggest that you move data to as few disks that you can... your array could live on 3 disks... and build parity... Also... check your SATA connectors... ensure that you have good connections... I currently have 23hhds running on a DAS that has 750 WATT PSU... your PSU should be enough for this setup, thus I dont think the PSU is at fault... are you using a RAID controller in this system?

Hello all, Current hardware - Dell r430 - HP DAS 24 bay with 2 HBA?s(two controller cards) I recently updated my server from an old HP ddr3 1u to a dell r430 chassis and while we were trouble shooting the system, it was suggested that I break the multipath(server-hba-hba-server) loops due to UnRaid not supporting this setup... I removed the cable connecting the two HBAs together but kept the server connected to both controllers thus breaking the loop... Since that time, none of the HDDs will spin down devoid of what time it is... I suspect that I will need to remove one of the cables to the Controllers but I would ask that someone confirm that this might be the cause of the HHD spinning 24h... Also I have 3 SSDs that are in the DAS that I would like to move into the r430 chassis... with the HP they were not recognized correctly, thus breaking the cache and app pools... What would be the best steps to attempt this? I suspect that the raid controller on the r430 will be a big reason as to if I can do this... the chassis RAID controller is a LSI MegaRAID SAS-3 3008 Thank you for considering these questions and have a good week/day

for anyone everyone else... there is a new ES setting that needs to be manually done... here it is

I am unable to view logs... I reinstalled the docker as a fresh install... and watched the logs... The last thing that I saw was that it was confirming access to ES and then right after that there are two new lines that flash and the log window closes... and after the docker is stopped... I can not view the logs even after it's stopped... I browsed to the appdata path and there is a single file there... db.sqlite3 file... feels like there should be more files/data there after a fresh install... Feels like this docker is half of what it should be... like it was taken down...

I did the force refresh on the main tube archive docker... that was the one that said and update was "not available" which is odd I did change the repo on the redisjson container and that didnt help anything... thus I tried the force update on the main docker

I tried to mimic the advice here... and blew up my entire setup... when I checked for updates for this docker it said there was "not available" in my panic... I forced an update... and blew up the whole thing... it wont start and on a fresh install it dies right away... suggestions?

The plugin changes how the Main page displays the Unassigned page... My Dummy Hat was earned today... Thank you dlandon

I was looking around a little bit more and noticed that on the Dashboard I have 2 unassigned disks... but the Main page still shows them as MIA... hmmm

tower-diagnostics-20230220-0751.zip

Thank you for that tip... been running it this way for a while and I have never come across this before... it's these little bits of knowledge that make you a god among us mortals

I did as suggested and the drive name/IDs have returned to what I would call normal and no longer have 4 digit names... I reinstalled the plugin and it now only shows the two drives and they properly ID the drives... dlandon, Should I still be able to see the two drives on the UD page? they are currently missing after installing the plugin again

I recently built the server chassis into what it currently is... the relevant hardware is listed below but basically it's a 1u server with a SAS card which is then connected to a DAS with two controller cards in the DAS(should one fail) Dell R430 chassis LSI SAS2308 SAS controller HP DAS

as requested tower-diagnostics-20230220-0621.zip

This was after uninstalling this plugin

Sorry... but what is a UD page?

Another interesting thing about this plugin is that I had to uninstall it to get the Main page to list the unassigned disks.

In the screenshot you will notice that I have 4 devices listed of which only two of them are clearable while I only have 2HDDs that are not currently in the array... The selected device is the "Dev 1" device and yet on this confirmation page it shows conflicting information for Dev 1 and sdg... You will also notice that SDG is not a drive letter for one of my unassigned devices...

I will not argue with the One Wise Man here... I would expect that you will end up recovering the data from the 'failed' disks and rebuilding parity... From your initial post it seems that you have a faulty SATA connector or controller... if you willing to rely on some of these 'failed' disks... I would expect that you could build a new array and copy the data from these disks that failed...

This plugin is very questionable... I had only 2 drives that were new to my setup... yet I had 4 disks listed... and while only 2 of them were clearable... the second clearable disk listed conflicting information as to which disk I would be clearing... I can provide screenshots should they be required... but I dont trust this current version of the software I stand corrected... It turns out that since I had 2 HBA cards in my DAS, conflicting information confused the plugin with strange data...

ah... so your saying that the minimum setting also applies to the cache drive(s)... interesting... kinda feels like that should be a separate setting imo... but ok

sound advice

long story shot... move EVERYTHING off the cache drive/s after that is done... remove the drive and start the array... stop it once more... add the new cache drive and start it...