Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Logs are filling up! New to UNraid and looking for assistance.

Featured Replies

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

Solved by Squid

  • Solution

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

  • Community Expert

Cache1 dropped offline, check/replace cables then post new diags after array start.

  • Author

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?

  • Community Expert
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.

 

  • Author

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?

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.