itimpi

All top level folders will be treated as part of a User Share of that name regardless of whether the Share settings actually mention that drive. In addition the command you give mixes a User Share and a physical device in the same command. This is dangerous and can lead to data loss if you are not very careful.

This is normal. You might gain a few seconds during boot in the time to load the bz* type files but the gain is very small. During normal running the system is running from RAM and therefore not constrained by the boot drive performance. That is one of the reasons why it is often recommended that if you can use a USB2 flash drive instead of a USB3 one as the performance gain is relatively small, and USB2 is far less prone to failure. The only real reason for wanting to boot from SSD is that it might be less prone to failure than a flash drive.

The rebuild process uses the combination of parity plus other drives to work out what to write to the drive being rebuilt. This means that if there were no errors during the rebuild then parity is automatically in sync.

This would normally be done as two separate steps. Did you do it some other way (e.g used the New Config tool).

Technically ‘cache’ is a capability linked to User Shares where you can use a pool to ‘cache’ writes to User Shares. It is just a legacy detail that the default name for the first pool defined is ‘cache’. I assume what you mean is use all the drives in pools and do not bother with the Unraid type array.

Just checked on my system and there appear to be multiple unraidd# type processes running where # corresponds to each of my array drives. Does your system have disk22 configured?

The boot runs in several stages as described Here. You can get the Linux level loaded without the later stages being successful.

It might also be worth checking that the volume mapping for the Plex container has the relevant location mapped using a ‘slave’ access mode.

This implies that Unraid has either been unable to mount the flash drive, or it has dropped offline.

Yes. Normally if you have any options that are not standard with Unraid you need to add them to each of the boot options you want to use.

The information you posted is enough to show that the restart failed for the same reason I found locally. I am testing the fix and it appears to be working although I want to test a bit more to be sure. I am also fixing another long-standing bug where allowing mover to pause checks can cause a notification that is not quite right to be generated.

Not sure why it only shows that update. You can go directly to 7.2.3 if you use the Manual upgrade method.

As long as you achieve a clean shutdown then this plugin should allow you to restart from the point previously reached as long as you set that option in the plugin settings. Having said that I have introduced in the release I made a few days ago a bug that can stop the restart working correctly. I have a fix for this under test and will release it in the next day or so assuming no other issue identified.

Note that the current stable release is v7.2.3.

There could be, but not clear what it might be. If the plugin cannot restart a check when the restart option is enabled then it is meant to display a notification saying why. I will see if I can recreate the issue at my end, but if it is possible to enable the Testing mode logging in the plugin settings and recreate the issue then the syslog might give me a clue why this is happening. EDIT: I have found a reason that a restart can fail and will work on fixing that. I would still be interested in the Testing mode logging to confirm that it is failing in the same way for you although you may prefer to wait to see if the fix I have already found fixes it for you.

Looking at the SMART information for this drive: 5 Reallocated_Sector_Ct PO--CK 161 161 196 Reallocated_Event_Count -O--CK 073 073 000 - 127 197 Current_Pending_Sector -O--CK 200 200 000 - 793 Based on these I would think the disk is not in a good state and should not be used in the Unraid array.

Not sure what you mean? Nothing stops you getting a paid for licence for the new flash drive immediately, and if you do that you can copy the ‘config’ from the old drive to bring across the setup from that trial. The alternative is you start a new trial for the new drive, but then you have to set some things up again.

If you are on the latest Unraid release (currently 7.2.3) then formatting to NTFS is a standard feature. If on earlier Unraid release then the Unassigned Devices plugin supports it (as long as you have enabled Destructive mode in its settings).

Is there a EFI folder on the flash drive without a trailing ‘~’ character? If so the flash drive is set to boot in UEFi mode, and if it will not it is a BIOS issue.

You cannot transfer a trial licence to a new flash drive (one of the limitations of trial licences) which is what I think you are trying to do. What you CAN do is set up a new USB drive with a paid-for licence, and then copy the ‘config’ folder from the old drive to the new one (less the trial licence .key file) to bring across the setup from the trial.

Just pushed a new release. Does not change basic functionality but has lots of small fixes/changes: ### 2025-12-29 - Changes to comply with security guidelines for plugins - Updated Unclean shutdown notifcation to separate crashes from array not stopping - Correct some spelling mistakes in notification messages - Added some debugging to track reports of history lines going missing. - Added pause reason to Pause notifications. - Improved/updated some of the built-in help text. - Handle built-in parity checks being disabled. - Fixes for conformance to Unraid 7.2 Responsive GUI requirements - Hide options in GUI that are not relevant at the moment. E.g. - if no parity disk installed - Cumulative mode set at Unraid level - if appdata backup not installed. - Options not relevant unless another option set to Yes - Fix for notifications for mover/backup being displayed when option set to not do so - Fix for array operations allowed to restart even after a disk change. If you spot any issues or encounter any problems then please let me know.

It is just that Unraid has just got a bit stricter on the checks it makes - earlier releases ignored case.

Yes. Rewriting the files can mean they now get read without errors.

Look into the config/shares folder on the flash drive and check that all the .cfg files have the same capitalisation as the folders on your disks for the share.

It can be worth trying downloading the zip file for the Unraid release and extract all the bz* type files overwriting the ones at the root of the flash drive. It sometimes helps with this sort of issue.