itimpi

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

Tmux is a good alternative to screen and is already installed if you have the UD plugin (as most users do). There is even a tmux plugin to make it easy to handle tmux sessions.

That is a major new feature and therefore not to be expected in a bug-fix point release. I would not expect it any earlier than the 7.3 releases.

Probably worth pointing out that the dependence on the flash drive is scheduled to shortly be removed.

In particular never split a PSU SATA connector more than 2-way or you are liable to get current dropouts. You can normally split a molex->SATA 4 way as the Molex connector can handle more current.

Do you by any chance use Power Splitters on the PSU cables to the drives?

That script could definitely cause a problem as mkdir with the -p option creates all folder levels in the given path. You need to start by checking that /mnt/user/Backups already exists before running the remainder of the script.

What happens if you boot in safe mode in case you have a plug-in causing your problem?

Now there’s no option in the web UI to assign it back to its original IP, There should be as long as you first stop the array.

The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot. It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.

Only if you do not want to run a confidence check on the old drives before using them in the new server.

This can happen if the device drops offline and then reconnects (which then gets a different device id allocated). Unraid is not hot-plug aware and as a result does not handle this tidily.

The question is whether you still have the old parity drive unchanged from when it was in the array? It is possible to force Unraid to accept the old parity drive without doing a parity sync. Have you written any new data to the array since trying to first replace the parity drive?

It should show up as an unassigned device. Do you have the UD plugin installed?

Unraid never automatically moves files/folders between drives in the array so if this is actually happening then you must have started something else doing this. The diagnostics may show what but not necessarily.

There is a plugin for testing memory on a live system. It can only test unused memory but it can still be worth trying as if it produces any failures you know you have a RAM issue.

If something ends up in the lost+found folder then that means the repair process could not find the directory entry to give it is original name/location. Unfortunately sorting out the lost+found folder is a manual process.

Which ever method you go for, no need to delete anything from old drives as both methods overwrite existing data. Option 1) means the drives are available immediately after the array is started, but you had to take the time to preclear the drives before doing the add. Option 2) means that when you add the drives then Unraid needs to clear the added drive(s) before they can be used. While the 'Clear' is running the rest of the drives are available so the array downtime is the same as 1) as long as you do not need to immediately use one of the new drives for data. Clear is faster than pre-clear so total elapsed time is shortest with option 2), but option 1 checks out the drives before trying to add them which you might want to do.

Questions: The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

It is worth pointing out that the Unclean Shutdown notification from the parity check tuning plugin is just information from the plugin that Unraid has detected an unclean shutdown. The idea is to save you having to look through the syslog to find this out. It is Unraid (not the plugin) that automatically starts a parity check after an unclean shutdown.

The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot. It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.

note that the SMART short test is not really meaningful (unless it fails). Only passing the extended test is a good indication that the drive is in good shape.

You need to contact support to get any licence related issues sorted. BTW: if you have a legacy Pro licence this is functionally identical to the new Lifetime licence.

If you are copying files to your server over the network they should not end up there. However if you have docker containers running (e.g. the ‘arr’ suite) they may not be respecting User Shares settings when moving/renaming files which can mean files end up on the cache unexpectedly.

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.