Blacksmith24 Posted January 24, 2022 Share Posted January 24, 2022 Hello all, I am looking for some assistance. My log file is filling up and I am not quite sure why. New to the field and we have an unraid server running a few apps for our company. Any feedback would be greatly appreciated. Log files attached, we are running Unraid 6.9.2. ucs-unraid-diagnostics-20220124-0823.zip Quote Link to comment
Solution Squid Posted January 24, 2022 Solution Share Posted January 24, 2022 Can't see where it all started, but a ton of write errors to the cache pool. But, the one drive (...3042) isn't showing as being online in the SMART reports, so you might want to check cabling etc (or maybe it just died). @JorgeB will be able to assist in any recovery operation Quote Link to comment
JorgeB Posted January 24, 2022 Share Posted January 24, 2022 Cache1 dropped offline, check/replace cables then post new diags after array start. Quote Link to comment
Blacksmith24 Posted January 24, 2022 Author Share Posted January 24, 2022 Hello all. Thank you for taking the time to review the logs and provide feedback. I disassembled the storage bay, removed all drives, and went through the unit with compressed air (quite a bit of dust had built up.) I've now reassembled and restarted the array and I am still getting the same error on that cache drive. We have two cache drives in our array, I think the next step might be to copy the contents onto the back up cache drive and then replace the drive that is throwing the errors? Unfortunately there is no cabling to replace, all of the drives are plugged into a SAS card and it appears as though all of the other 12 drives are functioning properly. Thoughts? Quote Link to comment
JorgeB Posted January 25, 2022 Share Posted January 25, 2022 11 hours ago, Blacksmith24 said: I've now reassembled and restarted the array and I am still getting the same error on that cache drive. Do you mean it's still not being detected? Or just 14 hours ago, JorgeB said: post new diags after array start. Quote Link to comment
Blacksmith24 Posted January 25, 2022 Author Share Posted January 25, 2022 Looks like that cache drive had gone bad. I shut down docker and then the array, replaced the drive and started everything back up. Looks like everything is running smoothly now. Thank you for the input! Hello all. Thank you for taking the time to review the logs and provide feedback. I disassembled the storage bay, removed all drives, and went through the unit with compressed air (quite a bit of dust had built up.) I've now reassembled and restarted the array and I am still getting the same error on that cache drive. We have two cache drives in our array, I think the next step might be to copy the contents onto the back up cache drive and then replace the drive that is throwing the errors? Unfortunately there is no cabling to replace, all of the drives are plugged into a SAS card and it appears as though all of the other 12 drives are functioning properly. Thoughts? Quote Link to comment
Recommended Posts
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.