itimpi

I would not bother replacing the flash drive just because it is old! Now that transferring the licence to another flash drive is automated and quick it seems needless. what you might want to do as ‘just in case’ are: ensure that you have a backup of your current flash drive so that you can easily transfer all your current configuration to a new one. The backup would be done either by putting the flash drive into another machine to copy its contents, or by clicking on it on the Main tab of the Unraid GUI and selecting the option to download a backup as a zip file. This is the important thing to have and you should update such a backup any time you make a significant change. it might be a good idea to have a spare empty flash drive available. However if you could live with your server being down while you got a replacement delivered even that may be overkill.

It will This is in fact one of the easy ways to proceed with the new security in place on the flash drive.

Disk2 also started showing some read errors so should probably have the extended SMART test run on it as well.

It is primarily a transposition of the original guide into the wiki with some minor tidying up. Should probably update it based on the latest guides, plugin feedback and plugin screenshots and to give more examples .

You can read about it here in the online documentation or in the Guides forum area.

You can do both at the same time but you would then not be protected against an array drive failing until the new parity has been built on both drives. if you do them separately then you remain protected against any other drive (including the other parity drive) failing while building new parity onto the drive. This takes longer but you have protection throughout. both the above statements assume that you do not already have a problem on a data drive before starting the upgrade process.

You can always re-install a container with its configured settings intact by using the Previous Apps option on the Apps tab.

Memtest supplied with Unraid will only work Id booting in Legacy mode. If you want a version that works when booting in UEFI mode you need to download it yourself from memtest86.com

This does not seem to be an issue with the LSI based chipsets. Lots of Unraid users have more than one in their system.

This is probably the way to go if you want to remain parity protested throughout. You have got that backwards If you only have parity1 present then you can reorder the disks without affecting parity. This is not true if parity2 is present as the calculations for parity2 take disk position as one of the inputs.

In step 1 it is simpler if you use the option to keep the current assignments when using New Config as that means you will not accidentally make any error with the parity disk or disks 1-4 assignments. You can then make the desired changes for disks 5 and 6 before starting the array to commit the changes.

Yes. Pre-clearing happens before you add any disk being pre-cleared to the array so does not touch your data.

The steps are not quite right as you cannot change the parity drive and add a new data drive at the same time. What you want to do is to follow the procedure for Upgrading a parity disk and then when that completes follow the procedure for Adding a data disk using the old parity disk as the one to add.

The two actions are not equivalent and you should expect writing to the array to always be slower than a parity check. You might want to read this section from the online documentation to get an insight into why this is the case. The speeds you quote are not atypical for writing to the parity protected array Do you have the “Turbo Write” mode active as this may well give faster write speeds (albeit at the expense of keeping all drives spinning).

Some small tiny cosmetic points about the Settings page for this plugin: the drop downs for selecting the release you want are not immediately obvious as they look like text links at a quick glance. Changing the colour of the background and/or text colours might make them stand out a bit more. it would be better if the releases offered were sorted in the reverse order so that the most recent release is at the top. The vast majority of the time I would expect this to be the release that most users want?

A parity check could definitely cause this sort of issue as it will be causing contention for the disk drives if you are trying to stream at the same time. You might want to look into the Parity Check Tuning plugin as a way to only fun a parity check in increments outside prime time to improve the user experience?

Did you realize that you can over-ride the global setting for individual drives by clicking on the drive on the Main tab. That would allow you to set different values for the 1TB and 10TB drives.

Have you installed the SMTP plugin (available via the apps tab)?

A rebuild always rebuilds to the same file system type so cannot be used as a method of converting to XFS. The standard conversion process always involves copying the data off the disk so that is can be reformatted to XFS (wi-img any existing contents) and then copying data back. in your case I would be tempted to do the following variation on the standard process: Use Tools >> New Config to reset the array (using the option to keep current assignments) Go back to the Main tab and change the assignments for the disks that are in ReiserFS to be the 3 new disks. At this point make sure that they are set to be XFS (if necessary clicking on the drive to get to the option to explicitly set the format). Start the array to commit the new assignments and start rebuilding parity based on the new assignments. All disks with existing data will come up as normal and the 3 new disks may show as unmountable (but may not if formatted under UD). At this point the unassigned reiserfs disks will show up under Unassigned devices. Format the new disks to XFS if needed. Make sure that the disks you are formatting are the ones you expect as you do not want to accidentally format the wrong disk losing its current contents. This can be done while parity is being built or you can wait until that completes. It is quite a quick process so do it when it is most convenient. mount the reiserfs disks in Unassigned Devices and copy their data back to the array at the location you want. In theory you can do such a copy while parity is being rebuilt but I would suggest waiting as copying while building parity severely affects the speed of both the copy and the parity rebuild. the downside to the above is that you are unprotected if one of the reiserfs disks actually fails while doing this and you could lose it’s data (do you have backups?). The upside is that it will be by far the fastest approach and puts the least strain on the reiserfs disks during the process. If you do not want to take the risk of being unprotected then you can follow the standard process as documented in this forum thread.

If you want any help it is always a good idea to post the system diagnostics zip file (obtained via Tools >> Diagnostics). That allows for informed feedback rather than just guesses. just a thought - have you checked under Settings >> Global Share Settings that you have User Shares enabled?

Those are two different views of the same file! The /mnt/user location is looking at the virtual file system used to implement User Shares, while /mnt/cache is referring to the physical device holding the file.

You can’t easily get the address from the Unraid level for a VM, but it should be easy enough from inside the VM to ask it what IP address it has.

As long as the VM is set up to use a bridged network rather than the default of virbr0 then you should be able to use RDP successfully. I personally prefer to use NoMachine rather than RDP as it performs better.

Nothing obvious in the logs, but from your description I would suspect a LAN cable (or port) is dodgy. A 1Gbps connection requires 4 twisted pairs in the to be functional while 100Mbs ( ~ 10MBps) only requires 2 twisted pairs to be operational. With a dodgy cable/port it is not unknown for the LAN connection to silently degrade from 1Gbps to 100Mbps or lower. Because the LAN keeps working a cable/port issue is often not diagnosed.

Go to the Apps tab and search for it.