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.

Unresponsive/Crash Followed by Slow Parity Check

Featured Replies

So yesterday around 12:30pm (ish, should have noted it down) my entire unRAID server went unresponsive. It was apparent since I run a 2x GBE card on it  with pfSense...kinda easy to take notice when your internet goes down with it lol.

 

Went to my home rack and tried to login via the GUI, which was frozen and wouldn't accept any inputs. So made the tough call to power off. Upon powering on the array started smoothly, all dockers, all vms on...no problems/everything seemed fine. Unfortunately there was no way for me to retrieve my syslog prior to rebooting 😪

 

However as of lastnight/this morning my CPU (AMD 2700X has been going wild doing the parity check, so much so that I can't stream anything from plex. Based on this I powered off or paused most if not all VMs/Dockers/etc that could be writing to the array. CPU usage/temps went down but no improvement on the plex front. It was then I noticed that the parity check has been running for over 18 hours with 2+ days estimated remaining...speed crawling along at around 16mb/sec. Pretty big yikes there.

 

Hit pause on the check, turned all my dockers and resumed and speeds stayed the same. Decided to take this as a bad omen and reach out for some second opinions on possible causes here. Diagnostics attached.

It should be noted that there is 1 drive with some SMART errors and its "Parity 1" a 4TB WD drive, it has a Reallocated sector count of 8 and a Reported uncorrect count of 24. However when I manually run the extended test it comes back as having no errors...which is strange. This has been the case for almost a year and I've never had parity problems before after a shutdown/reboot be it clean or unclean. I'm not saying that's not a candidate for the cause...just saying that it seems unlikely when its been like that for so long.

 

Any and all help/pointers appreciated.

ibstorage-diagnostics-20210111-1307.zip

  • Author

The original diagnotics I posted were from straight after the crash/shutdown and it just occurred to me that a recent set might be more useful (attached).

ibstorage-diagnostics-20210112-0922.zip

  • Author

A restart and a BIOS update seems to have fixed this. After running benchmarks it looked like the controller on my ASUS TUF B450 was having issues, hence why I decided to try a BIOS update.

Archived

This topic is now archived and is closed to further replies.

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.