February 22, 20242 yr Hello, I need some help with my system, it is running a parity check after the system crashed and it is running at 241.8 KB/sec which will take 382 days to complete. This is a new system I build about a week ago, I added a new drive 2 days ago and ran parity then, it took 14 hours to finish (I had help here to add the drive). The system rebooted out of nowhere. I attached the diagnostics. nasty-diagnostics-20240222-1432.zip
February 22, 20242 yr Author I stopped the server, reseated all the sata cables and power cables, started up and still the same. Started the array back, started the parity check and it is still running very slow. any help will be appreciated.
February 22, 20242 yr Community Expert Problems communicating with all HDD. How exactly are these connected to power? Any splitters?
February 22, 20242 yr Community Expert Should be OK, but maybe not. In any case, power would be the main suspect. I assume all are connected to motherboard SATA ports?
February 22, 20242 yr Author Yes they are connected to sata ports. No hardware change, unraid crashed earlier today and the server rebooted, since that reboot the problem occurred. Do you see on the logs which hdd is the problem? Do you see in the logs the root cause of the crash?
February 22, 20242 yr Community Expert 20 minutes ago, Chelun said: which hdd is the problem? 1 hour ago, trurl said: Problems communicating with all HDD
February 22, 20242 yr Author What do you think the next steps should be? Should I start changing/replacing/removing parts?
February 23, 20242 yr Community Expert Solution 2 hours ago, trurl said: power would be the main suspect
February 23, 20242 yr Author @trurl I just got around to work on this (homelab is always second or third on my daily list, LOL), I removed the splitter and connected the drives directly to the power supply, this seems to fix the issue! But not completely, as soon as I brought it up and started the array, the CPU went to 100% and the system crashed!! After came back up, started the array again and it started the parity check automatically, now it is going at 238.8 MB/sec, which is what I expect and the check should finish in 8 hours, which is 4-5 hours faster than before!! I am attaching new logs here, would you be able to tell me the reason for the crashes from the logs? nasty-diagnostics-20240223-1215.zip
February 23, 20242 yr Community Expert The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot. It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.
February 23, 20242 yr Author I see, let me setup the syslog and start preserving the logs, then if it crashes again, I will create a new post and upload the logs. Thank you all for the help!
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.