itimpi

Have you tried writing a fresh install to the flash dtive to see if that can be booted on case there is something corrupted in your configuration information.

You also need read/write access at the Linux level. Across the network you only get the subset of permissions that are set at both the share and Linux levels. Docker containers set their own permissions independently of Unraid do it is not unusual for you to not have full permissions via the share across the network. You should be able to edit configuration files using Dynamix File Manager which is built-in to Unraid v7.

You do not mention exactly what v6 release you are thinks off (and why you need v6 rather than v7) but possibly not. You need a version of Unraid that was released after the new Licencing model was implemented so only the later v6 releases will work. Having said that v6.12.15 should be OK.

Have you made sure that the credentials in Windows Credentials Manager match what you have set in Unraid.

You need to run a check filesystem on disk9 as there is file system corruption for it being reported in the syslog.

Anything put there is because the repair process could not find the directory entry to give it the correct name. If you can work out the correct name/location you can put it back where it belongs, but it is a manual process.

The ‘fuse’ system is what Unraid uses to manage User Shares. That message is therefore suggesting increasing the number of files that can be opened at the User Share level.

No diagnostics provided 😒 Running the New Permissions tools should not cause this sort of issue. Can you see the files if you look directly at the drives? If so then most likely cause would be file system corruption and you should run a check filesystem on all your drives. Providing the diagnostics will help us see if this is the likely cause.

Go to the Settings tab and it is the User Utilities sub-section.

A disk rebuild should only happen if replacing an existing drive. If you are getting this when just adding a drive then it implies something else happened. If adding a new drive and the preclear signature is not recognised then Unraid will carry out a 'Clear' operation to ensure the drive is all zeroes so it does not affect parity.

Step 1 is a bit pointless as step 2 promptly overwrites all sectors on the drive to zeroes eliminating the results of the format. Any formatting needs to be done after adding a drive to a parity protected array.

You really should have backups held off the server for anything that is important to you. Parity protects you against a drive failing but does not protect you against anything going wrong at the software level that might lead to a file system being corrupted.

@Kilrah suggestion makes sense. You do not seem to have many drives so perhaps having 2 parity drives is overkill especially if you have a good backup strategy. The other possibility would be to use the Parity Swap procedure to upgrade parity2 to a larger size and rebuild the failing drive onto the old parity2 drive.

Yes. Legacy licences are valid for all Unraid releases. A point to note is that no plugins from the earlier version are compatible with v7 but as you will be starting afresh that should be no issue. Strongly suggest you back up the contents of both flash drives before trying anything. They are in standard Windows compatible FAT32 format so this is easy to do. Failing that at least backup the license (.key) file first as that is what ties the licence to the GUID of a particular flash drive. Nowadays that is the ‘config’ folder on the flash drive - not sure if that was the case with 4.7 or if that allowed it in the top level of the flash drive. You can then use the USB Creator tool to put 7.1.4 release on one of the flash drives and after doing that put the licence file for that flash dtive from your backups into the ‘config’ folder. When you boot that it will show as a licenced copy. Not sure how big the flash drives you were using are? It is possible they may be a little small for current Unraid, but if so you can use the online licence transfer process to move a licence to a larger drive.

Strictly speaking no reason to Preclear drives that are going to be used for a rebuild other than carry out a stress test before using them.

Actually Unraid will automatically create a User Share corresponding to each top level folder on the drives. However this share will be created with default values which may mean the SMB Export option will be set to No so it is not visible on the network. If you want it visible on the network then you nead to set the appropriate Export setting.

The share behaviour has NOT changed although some of the terminology did change a few releases ago. Perhaps you need to carefully read the online documentation about User Shares That might help you understand how to set up any caching and whether files should be moved between cache and array. Regarding the shares ending up on the cache rather than the pool then make sure the Caution (which is not new) does not apply to your case. If you are still getting unexpected behaviour then post your diagnostics zip file giving the name of a share you think is misbehaving so we can look to see why.

If that is one PSU cable with 6 SATA connectors I would think you are OK as that PSU cable should easily be able to handle the current. I was talking about splitting an existing SATA connector on the PSU cable more than 2 ways potentially being an issue as such a SATA connector has limited current carrying capability. Is that clearer?

Thanks - that clears that up. I had not noticed that change had happened in the 7.1 release because I never had a scenario where it was relevant.

The answers given recently here suggest that there is no longer an 'Unraid' type signature on the driven for the new file system types? If so are we liable to get some support issues when disks that have previously been used elsewhere are used in Unraid either as a new install or via New Config? I need to set up a Unraid 7.2 test environment so I can answer such questions for myself if the answer is not already known 😊

Earlier you did say that you had moved all data off the drive so what you are seeing sounds sensible. Is there any reason to think differently?

Check that it not disabled in the BIOS. If you post new diagnostics we can see if it even being detected as present at the hardware level.

If you go into the mappings for the sonarr container then check that the access permissions are set to allow read/write for the mapping (you may need to click on the Edit option for that mapping to see). Alternatively posting the docker run command for sonarr will allow us to see it that way instead. Unfortunately nothing about docker container settings are included in the diagnostics so cannot check from there. Having said that I think that file system level corruption is a more likely suspect although I saw no sign of it in the syslog included in the diagnostics that you posted. To make it easier I have attached a simple script I use with the User Scripts plugin to run xfs_repair against all drives - it is easier than doing them one at a time if you have a lot. It does assume that all drives are in xfs format which does seem to be the case for you? I must admit though that I am trying to guess at what might be wrong as there is nothing that stands out from your description. BTW: You seem to have a lot of .cfg files on the flash drives under config/shares for shares that I think no longer exist. Using the Clean Up button on the Shares tab will remove unused ones which will make it easier for anyone looking at the diagnostics. CheckFilesystems.sh

You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs. It might be worth running a check filesystem on all your drives as file system corruption can cause this sort of issue. I assume that "Plex TV Shows" is a User Share? If so check that in the Sonarr mapping that /tv which you have mapped to /mnt/user/Plex TV Shows/ has its access set read/write?