Sneh

Added more RAM and that fixed the issue, thanks

Ok, I will try all of these things when I get home. I have 32GB ram on the way, so I'll let you know if that fixes it. Thanks for the help

Made a crash happen again by trying to update a container, rebooted into safe mode and downloaded these. clinton-diagnostics-20250807-1151.zip syslog-192.168.1.10_new.log

syslog server is active, I've posted the log above.

Unraid crashed, I hard rebooted and then downloaded diagnostics. Since the UI freezes theres no way for me to download it during the problem so I'm not sure how to get more "up-to-date" diagnostics. Im gonna attach another earlier diagnostic, maybe something will show up in that one. All these downloads were after a crash. clinton-diagnostics-20250806-2351.zip syslog-192.168.1.10.log

Been having this issue for the past month or so. Starting unraid without docker seems to work fine (have not run it like this for an extended period). Starting docker is where the problems start. There hasnt been a pattern I've recognized but a few (2-3) containers will work fine but the more containers I start, the more unraid starts slowing down and feels sluggish until the whole system will hang and crash. Can't access the gui locally via ssh or webui, and cant access it directly through the computers output at that point. I ran 2 x Memtests for 10 hours each (~20 passes) and found 2 out of 4 ram sticks were bad (2 separate kits, one kit went bad together). I ran the remaining two sticks for another 10 hours and no errors but the problem with unraid is still happening (I think something to do with corrupted data from my googling). I did get a "crc error count is 1" after removing the two faulty sticks on my cache drive but nothing since then. diag.zip

I’ve ran the long test and it checked out until the drive starts giving read errors and eventually drops out. If that’s my only option then I’ll just have to return it. Thanks for the help.

Is there no way to verify with 100% certainty that it’s the disk? It’ll cost me $100 to return it also on the Amazon page, it seems one guy had to cover one of the power pins for the drive to spin up, would something like that be my problem?

Running 6.12.3 LSI 9223-8i - https://www.ebay.ca/itm/142161306210 Using Mini SAS Cable SFF-8087 to SFF8482 - https://www.amazon.ca/dp/B09F6BXLNQ?psc=1&ref=ppx_yo2ov_dt_b_product_details Been using SATA drives with no problems and saw a deal on SAS drives, felt a little overconfident and here we are. I initially just added them to the array after creating a new config and they were working fine. I started a read-check over night and it gave 34 million read errors by the morning... I cleared the drives and removed them from the array. Checked and reseated all power cables. One SAS drive seemed to be working fine so I swapped the power and data cables with the faulty drive and faulty drive still failed while 2nd SAS seems to be fine so far. At one point the faulty drive went missing and unraid couldn't find it, did a power cycle and it eventually came back online. I ran the extended S.M.A.R.T test on each drive and attatched it below, both showed no errors. At that point, i installed the pre-clear plugin and decided to run it overnight, it was working fine until the same faulty drive is throwing errors again. I'm fairly certain I've tried everything and think its a faulty drive but I'm not 100% sure since this is my first time encountering this type of problem. The weird thing is the SMART test succeeded for the faulty drive but dissappears once the read failures start happening. I've attatched both versions and preclear logs as well. Good drive is still running the preclear. preclear_log_faulty.txt SMART_faulty_drive_after_read_fails.zip SMART_faulty_drive_before_fail.zip SMART_maybe-good-drive.zip tower-diagnostics-20240109-0150.zip