itimpi

The file you posted is empty! With errors trying to build parity it will be invalid anyway so no point in continuing. Do what you suggest, and if that does not work post the diagnostics.zip file for your system to your next post in this thread.

OK - just wanted to make sure that there was no issue. Getting off reiserFS is getting more urgent as support from it will soon be removed from the Linux kernel, and thus any future Unraid release using kernels without reiserFS support.

@gnollo What is the issue - that process looks correct (as far as the bit you have listed goes). You do not mention the other steps given that allow you to reformat the drive you have just emptied to a supported file system.

Did you remove the trial licence .key file? Did not think this was necessary but maybe it is.

Not spotting anything obvious that should stop mover operating. - maybe someone else may have better luck. Noticed some things about your share settings: appdata and system shares are configured to only be on the array. Normally you want the opposite - to only be on a pool to maximise performance of docker containers and VMs (if any) and to allow array drives to be spun down more easily. You then typically use the Appdata backup plugin to make regular scheduled backups to the array. You do not have a Minimum Free Space set for the cache pool. You want this to be set to be larger than the biggest file you expect to store there so that when the free space falls below this value Unraid will start by-passing the pool for shares configured for caching. This will help with avoiding with running out of space on the cache pool. You do not have Minimum Free Space configured for your shares. You want this set so that when the free space on an array drive falls below this value Unraid will select another array drive for the file (other share settings permitting). Have you actually rebooted since noticing this issue? If not then that might be worth doing on the off-chance it rectifies things.

The standard version (cheapest) should be enough for array drives where each drive is a free-standing file system. You would need the RAID variant if trying to recovery files from a multi-drive RAID pool. The Free trial versions can show you what it could recover before you commit to paying for the selected version.

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You could 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.

I suspect that your issue was a side effect of adding the NVME drive as that could cause the hardware device IDs to change. Any time you add new hardware you need to be aware that this could happen and any pass-throughs need redoing.

This is expected to be a 7.3 feature.

According to the diagnostics disk1 is formatted and mounted. You only get the Format button if Unraid thinks there is an unformatted drive. What makes you think it now needs formatting? Your screenshot is cut off on the right so cannot see what shows there.

You must NOT ever format a drive in this scenario as you will lose the data as a new empty file system will be created and parity updated to reflect this. You simply need to let a rebuild put back the contents. When you select the format option you get a popup dialog warning you about this.

Normally switching hardware is simply plug-and-play as long as no RAID disk controllers are involved - and even that can be worked around. Having said that if you pass any hardware through to VMs the hardware IDs will be different so remove any VFIO assignments and then set them up again on the new system.

Any time you add new hardware it can potentially change the Hardware Id's so you need to check/redo any VFIO pass-throughs or you may be passing through a device you did not intend.

Do you by any chance have a pool defined called “Test” with no device defined? The latest Unraid does not allow you to have pools with empty slots.

What does unraid say is the problem (next to the Start button). It might be worth providing a screenshot of your Main tab.

As a safety measure make sure you have made a backup of the 'config' folder from the flash drive before doing anything. With that available it should be easy enough to revert to the current position if necessary.

The 'type' is meant to be omitted from the command. It is just an indication that you need to type the command in at the console level.

I see you have some additions to the config/go file that are not part of standard Unraid. Perhaps one of them is the culprit.

Not sure. I can see that when you stopped the array that restart information was saved. However I see that something went wrong later as there is an indication that restart information was no longer present. I have some thoughts on what could cause this but I will need to do some testing to be see if my idea is a possibility.

Nothin springs out in the diagnostics except that suddenly the flash drive seems to become inaccessible. Maybe the new flash drive really has failed? Have you tried reading it in another system to check? You make it sound like more than getting a replacement flash drive and doing a licence transfer? The only complication would be that you might need to contact support to help with the licence .key file if the automated transfer does not work.

To stop the cache filling up you need to make sure you have set a suitable Minimum Free Space value for the share. Changing a share to be array only does not cause any existing files to be moved. For them to be moved you need ‘cache’ pool as Primary, Array as secondary, mover as cache->array.

In Unraid v5 if I remember correctly (it was along time ago😀) the Basic licence was a free one allowing up to 3 devices (as opposed to the v6 Basic licence which was paid for and allowed up to 6)? You need a paid-for licence from an old release to avoid having to buy a new one.

Both ‘powerdown’ and ‘shutdown’ commands stop the docker and VM services and stop the array. Each of these have their own timeout setting for those whose requires more time for that step.

The drawback is that any writes to the array requires all drives to be active so they are much less likely to spindown thus potentially increasing power consumption of the server.

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.