loady

Doscker image can just be deleted and remade ?..

Phew, it has rebuilt, still showing lots of error now though, im concerned for the other disks showing errors, i thought UNraid would tell me to replace them which is why they are still sitting there, if you say they should be replaced i will happily do so, should i replace those and what order should i do it in ?, i am going to have 2 x 10TB for parity so also need to factor that in warptower-diagnostics-20241216-1215.zip

Thank you. I will try to rebuild again and report back, my parity is 4TB but i have a couple of 10TB i will put up for dual parity once this is resolved

so how can i get drive 6 rebuilt so i can then go and replace drive 2 ?

Pretty sure if a disk was not good that UNraid would red ball it ? thats whats happened before, when its alerted me i have put in a new drive. i Have drives to replace, whats the best foot forward ?

So when i clicked start yesterday it started straight at 10%, i assumed it was doing its business, i got in this morning and it seems it never got past 10%

sorry i was on auto pilot and trying to do it on disk 6, disk two is now performing extended test, ill report back. Thank you

Doesent seem to want to start the test, i have disabled spin down by setting to never, when i click start it just reverts back to a clickable button like its done nothing, is it because the disk is disabled, if so how do i perform extnded test ? also worth mentioning the array is running in safe mode, i was ironing out some hardware issues but the array has been up for a few months without issue

I was doing some dusting and accidently clicke a drive door open enough for it to spit it out and is now disabled with contents emulated, i stopped the array, unassigned the disk, started array, stopped it again and then reassigned the disk, it started to rebuild then after a day i noticed a read check was paused, i let it resume and seems to have perofrmed the read check but the drive is still disabled. Any ideas please. warptower-diagnostics-20241204-1149.zip syslog

i see, they are not called RAID cards then ? so just put it all in and fire up

the cards were genuine pulls from a server and not the chinese knock offs, they are flashed to IT mode, guess i can only try, i have the hardware to put back in if it doesnt work properly

I has a thread running about constant UNraid crashes, pretty sure it was the memory or the slots themselves but decided i wanted to have nvme/.M2 drives as the cache, the reason being i run nextcloud and wanted to keep it on the cache to stop the drive being spun up when someone accessed files on it. So i now have a new board/CPU/RAM and two nvme drives (i think) i will be taking screen dumps of drive allocations and other settings made just in case and also a back up of the flash, i have done this before and was just a matter of transferring and turning on but since then i added RAID cards to run the drives so i could have a proper server case, can i also just transfer them in with everything else and switch on ? im also thinking let it start up then add in the nvme drives and get them going, is it then just a matter of making them cache drives and transferring the data from the existing cache ?

its very old and its a lexar, so i should be able to get a replacement and transfer my license to it ? any recommendations on reliable flash drives ?

Whats the possibility of a faulty flash drive that unraid boots from causing the issues ? twice now it has been removed as the first boot device and today when i tried to boot it wasnt even showing up in the BIOS, i unplgged it and checked it came up in windows (complained it wanted to fix it) which i didnt, plugged it back in to server and booted and set it as first boot device again.

so running in normal mode, the drives remain spun up contantly, if i spin them all down, within 2 minutes they are all spun up again

Well, i shouldnt have, this case has three fans in it but i cant even have one as it is like a rocket, i have been looking at some can of regulator i can put directly inline but not had any luck finding anything. It is something i need to do

so array seems fine in safe mode, will stay up, if i let it start in normal mode it gradually degrades, usually through the parity check, when i came in today it is unresponsive but you can hear all the drives chattering and can literally fry an egg on it. I have hard rebooted the server into normal mode and stopped parity check, see if it stagnates again, seemed to be fine once i had removed one stick of RAM, i have moved it to a different slot now. syslog syslog-previous warptower-diagnostics-20240622-1234.zip

Running fine in safe mode, no activity, all drives spun down

ideally i dont want to run in safemode constantly ? i just spun down all the drives and they have all spun up again, it was never doing this, three of the drives have errors though they are not red balled so i assume they are just warnings. Is it being caused because i only have one stick of 8GB RAM in it ?

Well its been up and fine for well over a week and running in normal mode with no crashes after removing one stick of RAM... however, i started to notice the drives were chattering away by themselves and the GUI become less and less responsive, its not crashed like it was doing before but its not usuable and pressing power wont shut it down, the drives are going mad, have had to hard shut down and started up but stopped parity check this time, syslog and diags attached. loading things is painfully slow and just gets slower syslog syslog-previous warptower-diagnostics-20240602-1047.zip

Well, that would be a bummer and about my luck...at least i have stability for now, running on one stick of 8GB

So, popped the lid, removed one of the two RAM sticks, fired up server in safe mode and left all dockers running, been up for two days now, started a parity check yesterday and has finished, do the diags look better ? next i will swap sticks over, could it also be the RAM slot and not the actual RAM ? warptower-diagnostics-20240521-0902.zip

so i started in safe mode GUI no plugins, there were no VM's running (stopped) and i stopped all the dockers, parity check started but its just hung at 2.3%, it never completes parity check, it either hangs or the server crashes and have to hard reboot...safe to say its not the dockers or anything ?...time to start testing the RAM sticks ? warptower-diagnostics-20240512-1545.zip

testing RAM sticks is my next move, i have done memtest previously and found no error, when you say start in safe with dockers disabled, is that to say i start safe mode with GUI but no plugins and then disable the dockers manually one by one ?

warptower-diagnostics-20240511-1535.zip syslog So GUI is unresponsive and i hooked up a monitor to the server, thats just a black screen, i tried to SSH into server and it prompted for my user/pass but just hung when i entered password, shares were still working and showing in windows and i fired up a few files, i had to hard boot the server so the diags are from after that, i had enabled syslog server some time ago so i added that too.