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.

Shoutdown of system issue and conseguent Parity-Check.

Featured Replies

ENOVO 1030 , Version SDK0J40697 WIN 3305038539247
LENOVO, Version S01KT63A
BIOS dated: Tuesday, 19-02-2019

2xIntel® Xeon® CPU E5-2650 v4 @ 2.20GHz

RAM 96 GB

2x14 Tb WD Gold + 8Tb WD Gold + cache SAMSUNG SSD 512 Gb

I have installed UNRAID version 7.2.5 , and when I shoutdown the system it will sort of not complete the shutdown..... I wait something like 1hour and I had to force shoutdown and consequently at switch on parity restarted (meaning 14-16 hours waiting). What I'm doing wrong? How to proper shoutdown the system?

Moreover when doing PARITY the APP are not working, and already PLEX and KRUSADER also give error message once Parity completed. I need some help.

Thanks

See if you can stop the array normally; if you cannot, disable Docker and VM service and reboot in safe mode, start the array and see if it stops, if yes, retest again after booting in normal mode to rule out a plugin issue, leave the services still disabled, if still OK enable one of the services and retest, then the other, note that if the issue happens with the docker service enabled only, you may need to try enabling one or a few containers at a time to find the culprit.

  • Author

@ConnerVT Now I have manage to get the Diagnostics file , while with parity ongoing I need to find a proper way to download it.

I want wait for this parity to terminate , and then I will follow @JorgeB suggestion.

  • Author

Not sure if mean anything , if I see the LOG is constantly writing :

May 5 17:25:21 PeppeRAID emhttpd: error: get_key_info, 722: Invalid argument (22): stat: /boot/config/Trial.key

May 5 17:25:22 PeppeRAID emhttpd: error: get_key_info, 722: Invalid argument (22): stat: /boot/config/Trial.key

This means that the key is invalid, assuming you are no longer using it, you can just delete it:

rm /boot/config/Trial.key

  • Author

I got definitely some issue in simply shoutdown the server with UNRAID.

Not sure if at Workstation level , maybe some configuration missing in BIOS?

At UNRAID level , maybe I'm too amateur to understand what I'm doing wrong?

Maybe simply too many things run at same time , Krusader copying while Plex scanning ? I got 3 of the CPU constantly at 100%...... that seems weird.

I hope someone can give a support on what is the issue here.

Screenshot 2026-05-07 at 08.30.08.png

pepperaid-diagnostics-20260507-0826.zip

  • Author

I had to force restart again, and again the PARITY CHECK ...... 15 hours to wait.

APP during parity are NOT working.

I leave down also the DIAGNOSTIC after the restart , with PARITY ongoing.

pepperaid-diagnostics-20260507-0852.zip

You need to figure out what is preventing the clean array stop, I posted some steps above that may help.

  • Author
28 minutes ago, JorgeB said:

You need to figure out what is preventing the clean array stop, I posted some steps above that may help.

Yes, you are right. Asap finish this Parity, I will follow your previous recommendation, and let you know if something change.

Thanks again

  • Author

@JorgeB I did as you suggest.

The array started and I was able to start the array in normal mode without any Parity check.

At same the issue with APP still persist, Plex and Krusader says :

PLEX : Looks like there’s a problem with this site

Firefox can’t connect to the server at 192.168.2.222:32400

Krusader : Failed connect to the server

Note sure what is the best to do ......

pepperaid-diagnostics-20260508-1132.zip pepperaid-safemode-diagnostics-20260508-1107.zip

2 hours ago, pepprom said:

Plex and Krusader says :

PLEX : Looks like there’s a problem with this site

Firefox can’t connect to the server at 192.168.2.222:32400

Krusader : Failed connect to the server

For app issues, you can look for their respective support thread:

docker support.JPG

  • Author

I keep having an issue where sometimes the whole system gets stuck during shutdown. Even if I start a proper shutdown process, it does not power off, and I end up having to force the shutdown by holding the power button. When I turn it back on, Unraid always starts a parity check.

At the moment it is running another parity check that will take about 16 hours, and I am worried that, once it finishes, I might face the same issue again with Plex not being accessible.

I have also noticed another problem: when I restart the server and there is no keyboard or mouse connected, it does not seem to boot automatically.

Is there any specific BIOS setting that would allow the server to start correctly even without any input devices connected?

pepperaid-diagnostics-20260513-1524.zip

I posted above what you can do to try and find out what is causing the array to not stop cleanly.

  • Author

Done as I wrote above too.

Now the problem come back again.

What I note that there is a link on when I got CPU at 100% working .........

Edited by pepprom

  • Author

I believe there is an issue with my Unraid configuration.

After multiple parity checks since I first set up the server, I completed another one yesterday. As soon as it finished, I again had the same problem: my containers failed to start, so I had to reinstall Plex and rescan my entire library.

This morning, when I checked the server, Plex had disappeared from the Docker tab. I decided to stop the array and restart the server, but the array would not stop and kept showing the message “Retry unmounting disk share(s)”. In the terminal I could see the same message repeating.

Eventually I decided the shutdown of the server and restart, and now I am once again in an automatic parity check, which will take another 24 hours.

pepperaid-diagnostics-20260515-0644.zip

May 14 17:30:18 PeppeRAID kernel: ntfs3(nvme0n1p1): MFT: r=38, expect seq=1 instead of 7!

May 14 17:30:18 PeppeRAID kernel: ntfs3(nvme0n1p1): MFT: r=1877, expect seq=36 instead of 2!

May 14 17:30:18 PeppeRAID kernel: ntfs3(nvme0n1p1): MFT: r=49, expect seq=32 instead of 31!

May 14 17:30:18 PeppeRAID kernel: ntfs3(nvme0n1p1): MFT: r=19de, expect seq=1 instead of 1b!

There are filesystem issues with the cache pool, you should not use NTFS with Unraid, Linux support is limited for that. Back up the pool and reformat it with a Linux filesystem.

  • Author

Perfect.

While I see only the CACHE disk is in such format type.

What would you recommend? Format the CACHE in other format will NOT delete any data, correct?

Thanks

For single pool, you can use XFS, btrfs or ZFS.

38 minutes ago, pepprom said:

Format the CACHE in other format will NOT delete any data, correct?

It will delete all the data on the cache pool, nothing else.

  • Author

Dear @JorgeB I have done the parity.

Before restarting the ARRAY, I have also format the CACHE (now xfs) and also upgrade the firmware of the BIOS.

I already noted that the scan in Plex is better distributed on the CPU and seems a bit more responsive.

I hope I don't get any other weird problem.

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.