itimpi

As far as I can see that does not cater for moving files from an UD location (which is not part of the User Share system) to a User Share or vice versa. Have I missed something? I can see why you need to be very careful about mixing User Shares and Disk shares, but I would not have thought a UD location should count as a Disk Share in the Unraid meaning of the phrase?

The advantage of installing packages via Nerdpack is that it tries to install a version compatible with the release of Unraid you are running.

There is also the possibility of plugging the Unraid flash drive into any machine that DOES have internet access and booting off it to get the licence installed (simply booting Unraid will not affect anything else on that machine). Since the licence travels with the flash drive you can now plug the flash drive into the machine that has no internet access as once the licence is installed internet access is no longer required.

The NerdPack plugin includes screen as one of the packages it can install.

Small wording issue? If I go into the Apps tab without the array started I get a notice displayed reading Docker Service Not Enabled - Only Plugins Available To Be Installed Or Managed This is slightly misleading in that the Docker Service IS enabled in Settings - it is just that it is not started since the array is not started. Should the message reflect this?

The plugin I mentioned to handle open putty sessions is Dynamix Stop Shell. It could be worth you installing this?

Yes. It is a requirement that the flash drive have a unique (unchangeable) GUID to satisfy the Unraid licensing requirements. you mentioned the global Id changing - did you mean the GUID or something else? Do not see how the GUID could be changing as it is built into the hardware of the flash drive.

This would stop Unraid stopping the array cleanly if the putty session has an array location as its current working directory. I seem to remember a plugin that helps with closing such sessions tidily during a shutdown sequence (but I am not near my Unraid server to look for its name).

When you explicitly specify a drive you are bypassing the user share system and forcing the data to the drive in question. you are right that in one sense they can be different views of the same files, but The user share path includes all drives with a ‘Media’ folder at the top level whereas the drive level path is restricted to that drive only. You might find it worth reading the description of how User Shares are I’m-lamented in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI.

Unraid will be attempting to do a clean shutdown but not necessarily succeed. You may find this item from the online documentations accessible via the ‘Manual’ link at the bottom of the GUI to be worth looking at. Yes - you would need to reboot again to gather the relevant information as a normal syslog of the sort included in the diagnostics is RAM based and only covers the boot sequence - not the earlier shutdown one. Note that You do not want to leave the option to mirror syslog to flash enabled all the time as it can cause a large amount of writes to the flash thus potentially shortening its lifetime. The option is primarily intended for troubleshooting issues like the one you describe.

You say it is a clean reboot, but an automatic parity check suggests that Unraid thinks it was not. What makes you think the shutdown was clean and none of the shutdown timers took effect? Have you tried stopping the array before doing the reboot to see if you get the same symptoms? I would suggest you enable the syslog server with the option to mirror to flash drive and post your diagnostics and the syslog server file that is generated so we can get a better view of what happens during the reboot sequence

I would suggest you post your system’s diagnostics zip file and mention the name of the problem share do we can see how this is all configured.

Sounds as if the safest thing to do is plug the drives into a Windows system and then copying the contents to Unraid over the network? Might be slower but sounds less risky.

Should be same speed (unless you happen to have a very slow CPU that struggles with the more complex parity calculation used for parity2).

Have you checked that Unraid is set to the correct time zone?

This

That router only has 100Mb ports as it says 3 10/100Mbps LAN Ports, 1 10/100Mbps LAN/WAN Port in the description.

You are likely to get better informed feedback if you post your systems diagnostics zip file (and mention the share)

If you want a memtest that will work with UEFI boot mode you need to download it from the memtest86.org site. The one shipped with Unraid only works in legacy boot mode.

You are likely to get better informed feedback if you post your systems diagnostics zip file. Since the default profile is RAID1 (for redundancy) you should have ended up with 1TB of usable space. Your symptoms suggest one of the 0.5TB drives did not get added properly, and this would show in the diagnostics. If you want all the space usable then you need the 'Single' profile.

You did not say exactly which error If you are talking about the FCP one mentioning rootshare then ignore it as FCP needs an update to stop flagging this.

How about adding an option to edit text files? Having said that maybe that functionality should be left to the Config File Editor plugin?

No - it requires 6.10.0-rc3 or later.

I have found that sometimes simply downloading the .zIp file for a release and then extracting all the bz* type files and overwriting the ones on the flash fixes such issues. It is as if the upgrade process does not always write these out error free. If you want to try this then the zip file can be downloaded via this link

It IS mentioned in the docs under Split Level where it says: IMPORTANT: in the event of there being contention between the various settings for a share over which array drive to select for a file the Split Level setting always takes precedence. This can mean unRAID chooses a drive which does not have enough space for the file so that an out-of-space error subsequently occurs for the file.