So I woke up to my the unraid computer on, but nothing on the attached screen (total black - said no cable connected) and the web GUI on my house computer not pulling it up. Restarted the unraid, worked fine and started a parity check then 12 hours later same thing happened. My motherboard has a digital readout with error codes and said that the RAM was bad.

 

So I just replaced the RAM cleared my MOBO CMOS and fired it up. It's working and again running a parity check.

 

Here's my log file if anyone can let me know if there's any indication of what went wrong I'd appreciate it. Thanks.

tower-diagnostics-20240318-1917.zip

6 hours ago, Cartierusm said:

Here's my log file if anyone can let me know if there's any indication of what went wrong I'd appreciate it.

Syslog starts over after every boot, also it usually won't have anything logged for that kind of issue anyway, just see if the server runs stable now.

W

12 hours ago, JorgeB said:

Syslog starts over after every boot, also it usually won't have anything logged for that kind of issue anyway, just see if the server runs stable now.

with me has been the same problem , it has been more than 1 week that the server crashes every 2 or 3 days of use, and sometimes it still occurs that the dockers stop alone, right now it occurred that the dockers are all showing that they were active , but in fact they were all stopped, I tried to restart the dockers manually and presents error message: 

Execution Error:
Error Code 403


In the error log here appeared this:

Mar 19 17:38:11 ROGERSERVER kernel: BTRFS error (device loop2): block=21414051840 write time tree block corruption detected
Mar 19 17:38:11 ROGERSERVER kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction)
Mar 19 17:38:11 ROGERSERVER kernel: BTRFS info (device loop2: state E): forced readonly
Mar 19 17:38:11 ROGERSERVER kernel: BTRFS warning (device loop2: state E): Skipping commit of aborted transaction.
Mar 19 17:38:11 ROGERSERVER kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1992: errno=-5 IO failure
Mar 19 17:40:30 ROGERSERVER kernel: docker0: port 3(vethed82632) entered disabled state
Mar 19 17:40:30 ROGERSERVER kernel: docker0: port 8(veth41669a3) entered disabled state
Mar 19 17:40:30 ROGERSERVER kernel: vethb24fb11: renamed from eth0
Mar 19 17:40:30 ROGERSERVER kernel: veth12a7133: renamed from eth0


From what I saw other people here in the forum with the same problem , referring to the CACHE this damaged, a friend of mine who also uses unraid had exactly the same problem, and he had to delete all content from the cache, format and recreate to solve the problem.

Just finished parity check. All seems good. Zero errors. Well I guess it was the RAM.

10 hours ago, Krypto5 said:

write time tree block corruption detected

This usually means bad RAM, start by running memtest.

Sorry for not closing this topic, but I never get notifications anymore. Anyway, it was ram. Didn't run a memtest, but replaced the RAM and it's been up since I posted this. Thanks for all the help.