jsmid6

I've disabled the global c-states on the motherboard and so far it has been running for over a day which is far longer than before, so fingers crossed

I'm trying to move my server over to new hardware. On the new server I installed unraid 7.0.0, I re-used a motherboard and cpu that I had left over from upgrading my desktop pc, initially I had some issues with hard crashes but that seems to be resolved by switching out the memory for memory that was being used in the desktop. I installed the OS created the shares started moving data over from the old server installed containers to start taking over the hosting from the old server It will randomnly hang after running for a few hours. Sometimes it makes it all through the night and other times it will happen again after a few hours. I can't ssh to the server and the WebUI is also not reachable. Forcing a restart works but eventually it locks up again. I followed the guides to enable the syslog server but I'm not seeing any glaring issues. Any suggestions on what else to check? tower-diagnostics-20250221-0929.zip syslog-192.168.1.71.log

I've used that tool to move all of those files and clean up some old directories as well, I had some old data from dockers that aren't used anymore. The tool worked perfectly to move everything

After the file system repair I ran a parity check and that has just finished, so here's the new diagnostics. jmedia-diagnostics-20240319-1028.zip

I did that and it seems to have resolved the issue for now, but considering the issues I've had lately, the filesystem will likely go bad again in a few weeks. Is there anything that could be causing this?

In that case, is it possible to reset the filesystem?

Ok, I'll give that a shot. Any idea what would cause the filesytem to have this issue? because this is the same issue I had with the old drive

Thank you, here's the diagnostics. jmedia-diagnostics-20240318-1111.zip

I recently replaced disk 2 in my array after it had been giving me problems for several months. The new disk has been in about 2 weeks now and it's already giving me problems. I did a 'Check Filesystem Status' and I'm seeing lots of these messages: Metadata corruption detected at 0x438a03, xfs_inode block 0x87a0/0x4000 bad CRC for inode 34720 bad magic number 0x86c5 on inode 34720 bad version number 0x69 on inode 34720 inode identifier 8206885521470191829 mismatch on inode 34720 imap claims inode 34720 is present, but inode cluster is sparse, would correct imap I'm not sure anymore what it could be. Is it possible the disk controller is bad?