JorgeB Posted July 26 Share Posted July 26 You can delete the new one from cache, as for the old one, you can leave on disk1 or move it cache, important thing is to always have a current backup of that file. Quote Link to comment
Tundraboy44 Posted July 26 Author Share Posted July 26 49 minutes ago, JorgeB said: You can delete the new one from cache, as for the old one, you can leave on disk1 or move it cache, important thing is to always have a current backup of that file. Never thought to do that. Appreciate it a ton, Thanks! Quote Link to comment
Tundraboy44 Posted July 27 Author Share Posted July 27 (edited) On 7/26/2024 at 9:46 AM, JorgeB said: Thanks for the beer money! Always! Looks like you may have to earn it..... Came back home to see the server in a null state again. Console was working (Via KVM) but all nics were down, no coms to it and required a hard reboot again. Noticed upon bringing it back up that the array worked fine, no errors this time, (running parity check as we speak), but that the VM i nuked before is now back. Certainly feel something is wrong with it, but not sure if it's hardware or software. Would be curious your thoughts - Edited July 27 by Tundraboy44 Removing diag Quote Link to comment
JorgeB Posted July 27 Share Posted July 27 Regular syslog starts over after every boot, enable the syslog server and post that if it happens again. 1 Quote Link to comment
Tundraboy44 Posted July 27 Author Share Posted July 27 (edited) 10 hours ago, JorgeB said: Regular syslog starts over after every boot, enable the syslog server and post that if it happens again. Sounds good - Will make this change and monitor. Seems like it only happens under load. Been trying to migrate about 10tb of data to the array over the past week and it's been having a ton of issues because of it. Really strange. Will report back on next crash with the data. Should I rotate the syslog? Edited July 27 by Tundraboy44 Quote Link to comment
JorgeB Posted July 27 Share Posted July 27 2 hours ago, Tundraboy44 said: Seems like it only happens under load. That suggests a hardware issue. 2 hours ago, Tundraboy44 said: Should I rotate the syslog? Should not be needed. 1 Quote Link to comment
Tundraboy44 Posted August 5 Author Share Posted August 5 (edited) @JorgeBUnfortunately woke to a rebooted server...... Logs attached, would appreciate any help you have. Running a memory test right now. Edited August 5 by Tundraboy44 Removing attachment Quote Link to comment
JorgeB Posted August 5 Share Posted August 5 2 hours ago, Tundraboy44 said: Unfortunately woke to a rebooted server Server rebooting on it's own also suggests a hardware issue, and unfortunately there's nothing relevant in the syslog, which is typical for hardware issue, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM. 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.