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.

[7.0.1] cache pool CRC error count on initial rebootafter upgrading

Featured Replies

Hello all, 

 

Well, I jinxed myself saying how reliable my Samsung drives have been.

 

This afternoon I updated my Unraid OS to 7.0.1. I noticed right after I rebooted that the cache pool had a status of not started, but I assumed I had just caught it the INSTANT it came back up. I ran through fix common problems, everything looks fine. 

 

Now I am seeing an alert that I had a SMART failure. I click into it, and one of the cache pool drives is showing CRC error count 199: raw value: 6.  So, I'm not TOO worried about this, 6 seems like a pretty low number (that being said, this server hasn't been moved in 4 years so I feel like the cables are pretty good, right?) 


I ran a short SMART test, and it passed. I am running the long test now.

 

I am more concerned with the pool device status, which if I am reading it right, suggests serious problems - but maybe I'm not reading it right. 

I looked at my current and previous syslog, which goes back 90 days, nothing in there about the CRC errors. I attached them but I don't think there is anything interesting in there, the only real errors are some of my docker containers are out of date (I know) and I sometimes let my cache drive fill up (I know).

 

1.) The device that has 6 CRC errors is under warranty until December. Should I RMA it immediately (it would be free), or would it be wiser to just monitor it for a while, make sure it doesn't increase, and then acknowledge the error and move on? Should I replace the SATA cable if I decide not to RMA it? 

 

2.) Does the pool device status indicate anything I need to be worried about?

 

Thanks!

unraid_cache_smart_fail.PNG

unraid_pool_device.PNG

min-syslog-20250314-0905.zip min-syslog-previous-20250314-0906.zip

Solved by JorgeB

  • Community Expert

CRC errors are connection related (typically cabling or power) and rarely indicate problems with the drive itself.  When they occur they trigger retries on the read or write operation to happen so can affect performance.
 

The value is never reset so even after fixing the cause the count remains non-zero but only stops increasing.   

  • Author

Sure, I get that (and thank you for confirming!).

 

What about that second part, with pool device errors?

 

Thanks again.

  • Community Expert

Those errors mean one of the pool devices dropped offline in the past, first, please post the diagnostics.

  • Author

Oops, sorry I didn't attach that initially. Here they are - and thanks again for the help!

 

 

min-diagnostics-20250314-0915.zip

  • Community Expert

Pool is still all raid1 profile, that's good, so run a scrub and post the results.

  • Author

Seems to be OK (attached). 

 

What now?

 

scrub.PNG

  • Author

Thank you so much 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.

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.