itimpi

That is standard. It is the space used to create the file system structure that will later be used to hold files.

You can end up with files on the wrong drive if using ‘move’ at the Linux level rather than a copy/delete strategy (this also applies to Krusader) to move files between User Shares. If using Unraid’s built-in file manager it will handle this correctly. The easiest thing is to leave the pool as Primary Storage and the array as Secondary Storage and let Mover handle transferring the files to the array. This was clearly documented in the online docs before the recent reorganisation. I looked and could not find it in the current documentation. You will not encounter this behaviour if you are moving the files between disk shares rather than User Shares.

You only get this option if the array is NOT primary storage. If you have a pool as primary storage then you can set the array as secondary storage. You do not mention what volume mapping you have set up for that container. Perhaps a screen shot of the container settings will help.

Both of these are OK. What is not OK is disk to share or vice versa

I notice the the Plugins section of the forum says it is for support for Unraid 6 plugins. Only cosmetic really but it should be amended to something that also caters for Unraid 7 (or later).

You can have as many data drives as you want up to the max allowed in the array (currently 28) as long as none of them are bigger than your smallest parity drive.

Looking at the description of the rmapbt option it looks like like this might reduce the chance of files ending up in the lost+found folder in the event you get file system corruption and have to run xfs_repair to fix it. Is this correct, and if so maybe it is worth the overhead? If not what is the purpose of that option?

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. It might also be a good idea to post a screenshot of the Main tab so we can see w hat you are seeing.

No. The only way to clear an unmountable state is to fix the file system level corruption (assuming it can be fixed).

That would result in a User Share called ‘cache’ and according to your diagnostics you do not have a User Share with that name. In addition the Unraid GUI should stop you from creating a user share with that name. The Unraid ‘cache’ functionality is something you set at individual User Share level and can be directed to use any pool (and can be different pools for different User Shares). The pool name is irrelevant in this case. It just a legacy issue that the default name of the first pool is ‘cache’.

This normally means you have made an error in the scheduling of it. I suggest you post a screenshot of the Settings->Scheduler->Parity check settings page.

It will only be that size if that is what you set under Settings->Docker. The default is 20GB which is enough for most users.

Not sure what happened but none of your drives are being detected at the hardware level, so this is not related to the upgrade. Are you sure you have not disturbed anything? Losing all drives sounds like either a disk controller or a power issue.

Not sure what you are asking for that is not already covered by the combination of the Unassigned Devices, Unassigned Device Plus and Unassigned Devices Preclear plugins.

User shares are not available on Unassigned Devices. User shares can exist on pools, but not span multiple pools directly. For pools this is not normally an issue as pools can inherently be multi-drive. Having said that any pool can be used for ‘caching’ new files for a User Share regardless of where the main body of the User Share is located.

No - only single devices are supported. What it saying is that if a disks is already formatted in one of the listed formats then it can be used in Unraid. In addition you can format new drives in Unraid to ext4/ntfs, but not to ext2/ext3. Note that in the main Unraid array although each drive is a single file system you can have User Shares that span multiple drives (even if they are not all the same format) as the User Shares system is independent of the underlying file system formats.

If you restart the array in normal mode you can look at what is now showing on disk5. If there is a lost+found folder that will be where the repair process puts any files/folders for which it could not find the correct name.

Unfortunately it is a manual process. If you have decent backups normally much easier to restore files from them. The Linux ‘file’ command can at least be used to tell you the content type of files with numeric names so that you can give them the right file extension to help with loading them into an appropriate program to look at their contents.

In the special case of a the main array having 1 data drive and parity1 then the answer is yes.

There should be a file '/boot/config/share.cfg'. Try going to Settings->Global Share settings and check there that the values there are what you want. If necessary make a dummy change and then hit Apply and the required file should be generated. If things still do not work you are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread and mention a share you expect to be moved that is not being moved. It is always a good idea to supply diagnostics to allow us to see the current state of your system and so we can see logs.

Another point to note is that you should not rely only on parity to protect your data. For important files you also want another copy as a backup, ideally not kept on your Unraid system.

Not something I have seen reported before so not sure where to look. 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 as it may supply dome glued as to why you see this behaviour. 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.

These might cause issues - we recommend never splitting a SATA power connector more than 2 ways as the source SATA connection might not be able to carry enough current for 5 drives.

This once both are replaced (may need to reboot - not sure).

When you get a link capped at 10MBPS this typically means you have a LAN cable (or port) that is not connecting on all 4 twisted pairs required for 1Gps (or higher). In such a case the link will fall back to 100Mbps (which is effectively 10MBPS).