JorgeB Posted May 12 Share Posted May 12 14 hours ago, loady said: is that to say i start safe mode with GUI but no plugins and then disable the dockers manually one by one ? Starting in safe mode disables all plugins, you can then also disable VM and docker services, and if stable, start enabling one by one, including individual containers and VMs, if that's not practical, you can try the other way, that is, still in safe mode, but only disable on VM or one container, if still issues enable that one and disable the next. Quote Link to comment
loady Posted May 12 Author Share Posted May 12 6 hours ago, JorgeB said: Starting in safe mode disables all plugins, you can then also disable VM and docker services, and if stable, start enabling one by one, including individual containers and VMs, if that's not practical, you can try the other way, that is, still in safe mode, but only disable on VM or one container, if still issues enable that one and disable the next. 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 Quote Link to comment
JorgeB Posted May 13 Share Posted May 13 18 hours ago, loady said: time to start testing the RAM sticks ? That's a good place to start, start by running memtest, but note that memtest is only definitive if it finds errors, if you have multiple sticks you can also try with just one, if the same try with a different one, that will basically rule out bad RAM, next suspects after that would be PSU, board, CPU. Quote Link to comment
loady Posted May 21 Author Share Posted May 21 On 5/13/2024 at 10:06 AM, JorgeB said: That's a good place to start, start by running memtest, but note that memtest is only definitive if it finds errors, if you have multiple sticks you can also try with just one, if the same try with a different one, that will basically rule out bad RAM, next suspects after that would be PSU, board, CPU. 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 Quote Link to comment
itimpi Posted May 21 Share Posted May 21 1 hour ago, loady said: next i will swap sticks over, could it also be the RAM slot and not the actual RAM It could be. It could also be simply the fact of having the extra RAM module installed where each one checks out fine individually, but you get failures when both installed. Quote Link to comment
loady Posted May 21 Author Share Posted May 21 3 hours ago, itimpi said: It could be. It could also be simply the fact of having the extra RAM module installed where each one checks out fine individually, but you get failures when both installed. Well, that would be a bummer and about my luck...at least i have stability for now, running on one stick of 8GB Quote Link to comment
loady Posted June 2 Author Share Posted June 2 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 Quote Link to comment
JorgeB Posted June 2 Share Posted June 2 Try booting in safe mode and/or closing any browser windows open to the GUI, only open when you need to use it then close again. Quote Link to comment
loady Posted June 2 Author Share Posted June 2 (edited) 10 minutes ago, JorgeB said: Try booting in safe mode and/or closing any browser windows open to the GUI, only open when you need to use it then close again. 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 ? Edited June 2 by loady Quote Link to comment
loady Posted June 2 Author Share Posted June 2 Running fine in safe mode, no activity, all drives spun down Quote Link to comment
loady Posted June 22 Author Share Posted June 22 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 Quote Link to comment
trurl Posted June 22 Share Posted June 22 3 minutes ago, loady said: literally fry an egg on it Do you have a cooling problem? Quote Link to comment
loady Posted June 22 Author Share Posted June 22 18 minutes ago, trurl said: Do you have a cooling problem? 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 Quote Link to comment
loady Posted June 22 Author Share Posted June 22 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 Quote Link to comment
loady Posted July 1 Author Share Posted July 1 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. Quote Link to comment
loady Posted July 1 Author Share Posted July 1 43 minutes ago, JorgeB said: It's a possibility. 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 ? Quote Link to comment
JorgeB Posted July 1 Share Posted July 1 It may be worth a try, personally I like the Sandisk Cruzer Blade 32GB, one of the few USB 2.0 flash drives still available, and in my experience they tend to be more reliable. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.