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.2.4] All drives spin up for parity checking, while the progress is always 0%, after unclean shut down

Featured Replies

My server has been stable for like 20-30days on 7.0.1. Someday, I decided to create a user under Docker Opencloud for my dad. Shortly after he starts using it, especially uploading files, the server becomes unresponsive to the point that I have to force shutdown as the GUI is no longer responding. Not long after the restart, I believe my dad is playing around with Opencloud (accessing it via Traefik + Cloudflare setup), then again leads to a crash again (this is highly related as I was away and not playing around with the stable server for a week).

Every unclean restart/force shutdown results in a parity-check. However, although all drives spun up, the checking stays on 0%, and I even cannot cancel such operation. The GUI is somewhat responive, but not fully, e.g. cannot download diagnostics, cannot cancel parity check. After that I decided to just do an upgrade to 7.2.4, the situation still exists.

Any help would be appreciated, thanks a lot.

Edited by PzrrL

Solved by JorgeB

  • Author
1 minute ago, JorgeB said:

Enable the syslog server and post that after the next crash.

Thanks, however, I now dont have a working server (meaning it is not possible to go on to the next crash), as after the unclean shutdown, it just do the parity check, which always stuck at 0% even though all drives spun up

  • Community Expert

Do you mean the server does' even boot now? If it still boots, you can enable the syslog server before starting the array. If auto-start is enabled and the server crashes right after array start, it can be disabled by editing disk.cfg on your flash drive (config/disk.cfg) and changing startArray="yes" to "no".

  • Author
On 3/27/2026 at 7:52 PM, JorgeB said:

Do you mean the server does' even boot now? If it still boots, you can enable the syslog server before starting the array. If auto-start is enabled and the server crashes right after array start, it can be disabled by editing disk.cfg on your flash drive (config/disk.cfg) and changing startArray="yes" to "no".

Thanks for the reply. It boots, it is just when I auto-start the array once boot up, the infinite parity checking goes on. The parity checking in safe mode is fine though (I got into the safe mode to enable the array to take my syslog back). Attached please fine the syslog, thanks

if I remember correctly, the first crash started around after 18th March.

btw it is weird that I can no longer drag and drop a file to here for uploading the file. (i can only add it through reply edit)

syslog.zip

Edited by PzrrL
adding file

  • Community Expert

I don't see anything logged that suggests the parity check is the problem; it just appears to be the result of the unclean shutdowns.

If it doesn't crash in safe mode, it suggests a plugin or other customization is the problem.

  • Author
4 hours ago, JorgeB said:

I don't see anything logged that suggests the parity check is the problem; it just appears to be the result of the unclean shutdowns.

If it doesn't crash in safe mode, it suggests a plugin or other customization is the problem.

Actually the parity itself didn't crash. The reason why I need to do unclean shutdown is that the GUI becomes unresponsive after I shared the use of Opencloud to my dad. The subsequent parity freeze is just some consequences. Do you see any possible reason why the GUI/server becomes unresponsive in the first hand?

  • Community Expert

And does that still happen in safe mode with Docker and VM services disabled?

  • Author
4 hours ago, JorgeB said:

And does that still happen in safe mode with Docker and VM services disabled?

There is no freezes in safe mode, even with docker and VM enabled. The parity check is completed successfully with 0 error too.

  • Community Expert
1 minute ago, PzrrL said:

There is no freezes in safe mode

On 3/29/2026 at 11:00 AM, JorgeB said:

If it doesn't crash in safe mode, it suggests a plugin or other customization is the problem.

Most likely a plugin, but you can also have something in the go file, for example, would need the normal diags to check, not from safe mode.

  • Author
1 minute ago, JorgeB said:
  2 minutes ago, PzrrL said:

There is no freezes in safe mode

  On 3/29/2026 at 6:00 PM, JorgeB said:

If it doesn't crash in safe mode, it suggests a plugin or other customization is the problem.

Thanks, sorry for being dumb, but what kind of customization are we talking about? Can you name some examples?

  • Community Expert
  • Solution

Typically it would be the go file, so if you changed anything there, try with a stock one, but most likely it would be a plugin, so try uninstalling them if there's nothing else changed.

  • Author
On 3/30/2026 at 9:58 PM, JorgeB said:

Typically it would be the go file, so if you changed anything there, try with a stock one, but most likely it would be a plugin, so try uninstalling them if there's nothing else changed.

Thanks JorgeB! I went through all the plugins one by one, and managed to find some deprecated one, which I was not aware of until explicitly looking in the support thread. While I am not sure if I am stable enough now, I will call it a day, thanks again!

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.