itimpi

I think you have misunderstood how the wait is used? It is the time to wait after starting this container before moving onto the next one. You therefore want a wait on the first container if you do not want the second one to start at the same time.

Was that after formatting with Rufus?

You want the flash drive set to boot using UEFI after doing this (I.e. no trailing ~ on the EFI folder).

One solution that seems to have worked for other users having boot issues is to use Rufus to format the flash drive.

Al you really need is the ‘config’ folder off the flash drive as that contains the licence file and all user settings.

A XFS check normally only takes minutes

I have been a bit lazy and not updated the Unraid/lang-en_US repo for some time so waiting makes sense. Over time mismatches will have accumulated. I am currently doing some local testing to try and make sure that all strings used in the current code are correctly reflected in the parity.tuning.txt file in my itimpi/parity.check.tuning repo (just found a few mismatches that will need correcting) before I upload the file to the Unraid/lang-en_US repo. That sounds as if it is more likely to be a genuine Unraid bug. I do not see how any plugin authors will have visibility or control over this (although I could be wrong)

If a memtest gives anything other than 0 errors you have a RAM problem. If it locks up while running memtest then you have a hardware issue such as CPU, cooling or motherboard.

It is an option on the Unraid boot menu.

If this is the version from the itimpi/parity.check.tuning project then I would be grateful if you mention them to save me trying to find them. If is the version of the file in the Unraid/langUS project (which is the basis for translations) then I know that one is badly out-of-date.

Click on the underlines links to get instructions. This is a standard technique in this forum where common phrases are automatically set as links to the relevant part of the online documentation.

It should not, although USB2 tends to be most reliable.

Not quite sure what you are saying? I think you are saying you get English even when the language is set to something else, or is the problem something else? If the problem is you are getting English regardless of the UI language then I am in the process of creating a push request for the English strings so up-to-date translations can be made. It is some time since the English strings have been updated so they are badly out-of-phase with the current plugin release.

I have pushed a release that I believe fixes all the issues reported against the last release: ### 2026-01-09 - Fix for version not being correctly set up for display on Settings page - Fix for permissions on the plugin path being changed during install - Fix for tidying up history file when restart being attempted which could stop restart working. - Fix for Pause and Resume notifcations not displaying correctly. - Change: Pause/Resume notifications displayed as warning if errors already found. Let me know if any issues appear to be still outstanding.

I have a question for anyone using the Restart option in the plugin and what it is desirable to show in the Parity History.. At the moment when you do a restart you end with a "Cancelled" entry in the History generated when the system shutdown/rebooted with a parity operation running and then an entry giving the array operation completion details. I am looking at simply removing this entry and only having the final entry on the operation completing. However I could instead change that entry to indicate that the system was shutdown/rebooted while an array operation was active (and perhaps indicate how far it had reached). Also what about an entry in the history if a restart fails - is this something that is desirable? If I added it I would also give the reason the restart failed (e.g. unclean shutdown, disk configuration change).

What do you get from ls -l /mnt/user

If you mean ZFS in the traditional Unraid type array you probably do not want this. In the Unraid array each disk is a self-contained file system so you would still need a parity disk for protection, and ZFS in the Unraid type array is know to not have good performance.

If you bring up the built-in help (by clicking on the text of that option) it tells you what formats are accepted.

Your problem with the cache giving this error is that you have not set a Minimum Free Space value for the cache (currently 0). Only when the free space falls below this value will new files bypass the cache. You therefore want to set this to be larger than the biggest file you want to be cached.

Your scenario is exactly what the parity swap procedure is designed for. If you were just upgrading a parity drive without a failed data drive you just do a simple replacement.

Looks mlike you have a lot of warnings from Fix Common Problems: Jan 9 21:24:30 SamsBay root: Fix Common Problems Version 2024.12.19 Jan 9 21:24:33 SamsBay root: Fix Common Problems: Warning: Share Media is an implied array-only share, but files / folders exist on the cache Jan 9 21:24:33 SamsBay root: Fix Common Problems: Warning: Share appdata set to cache-only, but files / folders exist on the array Jan 9 21:24:33 SamsBay root: Fix Common Problems: Warning: Share system set to cache-only, but files / folders exist on the array Jan 9 21:24:33 SamsBay root: Fix Common Problems: Error: disk3 (WDC_WD30EZRX-00MMMB0_WD-WCAWZ1396574) has read errors Jan 9 21:24:33 SamsBay root: Fix Common Problems: Warning: Plugin fix.common.problems.plg is not up to date Jan 9 21:24:33 SamsBay root: Fix Common Problems: Warning: Plugin unassigned.devices-plus.plg is not up to date Jan 9 21:24:33 SamsBay root: Fix Common Problems: Warning: Docker Application TinyMM-GUIv5 has an update available for it Jan 9 21:24:33 SamsBay root: Fix Common Problems: Warning: Share camera is set for both included (disk1,disk2) and excluded (disk3) disks Jan 9 21:24:33 SamsBay root: Fix Common Problems: Warning: Share Movies is set for both included (disk1,disk2) and excluded (disk3) disks Jan 9 21:24:33 SamsBay root: Fix Common Problems: Warning: Share mteam is set for both included (disk1,disk2,disk4) and excluded (disk3) disks Jan 9 21:24:39 SamsBay root: Fix Common Problems: Warning: NerdTools.plg Not Compatible with Unraid version 7.2.3 Jan 9 21:24:42 SamsBay root: Fix Common Problems: Other Warning: Mover logging is enabled Jan 9 21:24:42 SamsBay root: Fix Common Problems: Error: Share mteam has disk4 set in its included disk settings Jan 9 21:24:44 SamsBay root: Fix Common Problems: Warning: Share appdata set to use pool app, but files / folders exist on the cache pool Jan 9 21:24:44 SamsBay root: Fix Common Problems: Error: Old version of SSD Trim Schedule Not sure whether any of these are causing your problems but they should be taken care of to make sure. You certainly want to look to see if disk3 has an issue. Have you tried booting in Safe Mode to see if you get the same problems? If Safe Mode does not exhibit the same problem then a plugin is likely the cause of your issue.

I would think that using tmux can do as good a job, and there is a tmux plugin to give a GUI based way of managing sessions.

The process is covered here in the online documentation.

If the existing Licence is for Unraid Pro then there is no cost involved to move to the latest Unraid Pro on the latest Unraid release as all legacy licenses are entitled to free updates for life.

The green circle does not mean that the Unraid thinks the file is on the array. Instead it thinks that it is on redundant storage and is protected. At the moment Unraid is not taking into account the profile used on the pool and automatically assumes that a multi-drive pool is protected. I believe that a future Unraid release is expected to take the profile into account.