loady

Ok, that i will try, so is it pointless me just leaving the server with the disks unmouted to see if it crashes like this ? I do actually want to upgrade the board to one with two .M2 slots...any recommendations ?

I have been running on this equipment, mobo etc without issue for a good few years, this all started about 18 months ago, i use the server quite a bit so trying to get to bottom of it is frustrating, i am at the point of throwing money at it now

warptower-diagnostics-20240506-1308.zip

Wow..have i been bumbling along like this for a year ! My server is still crashing constantly, daily if not left in safe mode, in safe mode i might get longer between crashes, parity usualy hangs at a certain point pretty much all the time, i have checked the BIOS for the C states but as far as i can see they are not enabled, couldnt really find the exact field to look as described in the thread for it, as you can see C states were off and had been anyway, restore AC power loss was set to power off. Now some of the drives have errors, i have spare drives to replace them and i actually want to change my parity drive to a 10TB disk, however, i am not sure if it wise to do this whilst its crashing like this ?, if it crashes whilst replacing parity i think i might be up the creek without a paddle, its been said it is 'probably' hardware issue, i had done memtest and looked at all the other suggestions, would the hard drives cause this crashing ? should i boot the server to get GUI but NOT mount the disks and leave for a few days, if the disks were causing the issue then not being mounted would they be out of play for the cause ? i am even looking to see if replacing the motherboard will resolve the issue but where do start with these kind of problems, the power supply was replaced very recently when it was found to be dropping out and causing disk error, the new psu resolved this. The attached syslof is the server booted without the drives mounted. warptower-diagnostics-20240506-1308.zip

So, it was up for over six days in safe mode and crashed again last night.. if this is hardware related where would the logical place be to start ? I have a 10TB drive i want to use to replace my parity drive, im guessing its not wise to do so whilst it is exhibiting this behaviour ? syslog (1) warptower-diagnostics-20230425-1348.zip

Thats going to be a headache if it is hardware related... where do you even start looking, i suppose i could remove the memory and just start with one stick and see if it persists, adding a stick at a time. Would be good if it was the mobo because i am looking at upgrading that to one with two .m2 slots

Ah, sorry, i forgot i had enabled this, is this syslog of any use ? it should show the times i have had to hard reboot the server syslog

warptower-diagnostics-20230318-1326.zip warptower-diagnostics-20230321-1744.zip warptower-diagnostics-20230403-1235.zip

The server has been in use so i have not been able to do what you said yet, however, whilst in safe mode gui mode (no plugins) it has still been crashing, it just takes a longer time to do it. syslog warptower-diagnostics-20230114-1305.zip

Right, its been up for nearly 20 hours now, parity check has completed and no errors. All dockers are functional but no plugins installed, i chose safemode GUI no plugins. syslog

im still trying to find fan regulators for the 3 fans that face the drives, its like sitting next to a jet engine if they are just plugged in without any speed control

so i started it in gui mode no plugins, should i still start the array though or just leave it like that ?

the only thing i can think that is different..i set up next cloud, but recently i created a link for someone to upload files to me, about 40gb.... would this cause the server to crash ?

Well its crashed again, less than 30 mins uptime..i took it out before restarting this time and its populated now... syslog

I followed these instructions.. Go to Settings->Network Services->Syslog Server You can click on the 'Help' icon on the Toolbar and get more information for all of the options. Mirror to Flash: This is the simplest to set up. You select 'Yes' from the dropdown box and click on the 'Apply' button and the syslog will be mirrored to the logs folder/directory of the flash drive and is appended to on a reboot. There is one principal disadvantage to this method. If the condition, that you are trying to troubleshoot, takes days to weeks to occur, it can do a lot of writes to the flash drive. Some folks are hesitant to use the flash drive in this manner as it may shorten the life of the flash drive. The advantage of this approach is that it captures everything from the start of the boot process which can be important if trying to diagnose boot problems. Have i missed something ?...i hard shut down the server as it had crashed and then removed the flash drive to get the file off.