squazify

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by squazify

  1. I think I have it figured out now, thank you. Just removing a single splitter seemed to have fixed the issue, but I don't want to mark it as solved quite until I've done more testing. Thank you so much! I think at this point I'm looking into getting a new PSU that has more molex handoffs for my drives. Once again, thank you.
  2. It's Molex to Molex, then Molex to Sata. I have enough spare Molex to at least remove that first splitter.
  3. I've replaced the cable for disk 3 and now I'm getting read errors on the disk. I set it to rebuild 3 (and 4 since it was knocked offline at the same time). It seems it didn't make it far into rebuilding at all. Here are the new diags. prometheus-diagnostics-20240321-2114.zip
  4. I have had two drives (2 and 4) both drop pretty frequently from my unraid server. It seems like especially if I do a parity check it will drop 4 for sure and 2 sometimes. I can rebuild with different drives, and using different connections which leads me to believe it's not an issue with my LSI controller, or my motherboard as I've used each. I'm a little confused as to where to go from here. prometheus-diagnostics-20240318-1057.zip prometheus-syslog-20240318-1642.zip
  5. Apologies, that was an older file, here is the correct one. syslog-192.168.1.25(2).log
  6. So I've been having two hard drives kick switch kicking off each time they're rebuilt, but so far as I can tell there's no issue with the hard drives themselves, that may explain some of the errors, I'm troubleshooting that now, but that issue is new, and I'm hoping unrelated. I'm troubleshooting that one myself. My may concern is the random crashes. I've cleared out the log and have rebooted with a clean reboot. Here is the log for that. For the two drives I've tried swapping one with a new drive and am seeing the same behavior, I have also ruled out the sata cables at this point too. I'm just not sure if that issue is related or not. syslog-192.168.1.25(1).log
  7. I have done that, however I'm not sure if the file is too large or what, but I keep getting an error when I try to upload it. ~100Mb
  8. My Unraid instance has been freezing and becoming completely unresponsive. I've tried everything I can going through logs to see if I can find anything in common before the gaps where it stops working, replacing CPU, Mobo, and RAM. Tried different versions of Unraid, different BiOS versions, removing plugins that I think may be suspect and I'm just at the end of what I can do. It's hard to pin down as it can sometimes be within 4 days, and sometimes can be about 4 weeks. I tried getting the log file to tail on the monitor so I could see what the last command was before the server became unresponsive but the screen would just freeze on a black screen. The only solution I have found is a hard shut down and at this point it's kicking off drives and I just lost about 3TB or so of data, so I'm just really defeated right now. I can't upload my logs as I'm getting error -200, but I can try and upload with another method if possible. I just can't have more data be lost. I can't have my server continue to crash regardless of what I've done. I'm just at the end of my rope and really don't know what else to do. prometheus-diagnostics-20231107-1545.zip
  9. Little late on the party, but I was running into a similar issue. Don't rename your config to /config/no-ip2.generated.conf, that'll break it. But for me I was running into an issue as I had multiple domains. There should be an error further up. Putting it here in case you're running into something similar, but you may need to do "-.domain.ex" if you're running into this.