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.

parity errors caused by plugins?

Featured Replies

I have sickbeard , sabnzb and also transmission running off my unraid server.

 

I have them installed on disk 15 of my server.

I am getting parity sync errors since I done this. Will having these running off an array drive instead of a cache drive do this??

No. Issue must be elsewhere. Post Smart reports on the drives and a syslog.

I have sickbeard , sabnzb and also transmission running off my unraid server.

 

I have them installed on disk 15 of my server.

I am getting parity sync errors since I done this. Will having these running off an array drive instead of a cache drive do this??

No, but forcing the server to power down when unable to cleanly stop it will cause errors, since data in the disk buffer cache cannot be written to the disks.  (some of the plugins are not written to cleanly terminate when stopping the array, which might result in a non-clean shutdown)
  • Author

that maybe it then. I installed ram and just powered it down without stopping the plugins.

 

 

Always use the powerdown command from the webgui (unless the webgui is dead ofcourse). If the array will not shutdown you need to terminate processes by hand from commandline..

 

If you powerdown unclean at that point parity will not be changed, because that happened the server starts a parity check to correct this  So a parity check that finds stuff after an unclean boot is a good thing, it is the server acting on a situation it recognises as a situation that needs a parity check.

  • Author

I did power down from the webgui. But I didnt stop the plugins before doing so.

 

 

I did power down from the webgui. But I didnt stop the plugins before doing so.

 

You do not need to stop the plugims, of they are built right they should stop automatically.

 

 

Sent from my iPad using Tapatalk HD

I did power down from the webgui. But I didnt stop the plugins before doing so.

 

You do not need to stop the plugims, of they are built right, they should stop automatically.

 

 

Sent from my iPad using Tapatalk HD

You do not need to stop the plugins, IF they are built right they should stop automatically.

 

Many are NOT written correctly... and do not stop automatically, or start even if the array is not yet initialized and prevent the array from starting on a reboot. 

More recent versions of plugins are getting better, as the developers learn more, but please TEST stopping and rebooting your server AFTER each installation of an add-on.

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.