itimpi

What is the emulated drive in Unraid showing? Whatever appears there is what would appear if you rebuilt the drive. when you say the drive is ‘empty’ is that looking at in Unraid array or somewhere else? You are likely to get better informed feedback if you attach your system’s diagnostics 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.

Has anyone seen any suggestion that it might be possible to run "iCloud for Linux" in a docker container rather than needing to be done in a VM? The closest I have seen so far is a container that gives partial integration with iCloud Drive rather than the more complete integration given by "iCloud for Linux". If there is a suitable base container to which it could be added I might try to do it myself but not sure if so what base container I should use. I suspect if not possible that it might be because of the requirements around GUI support but thought it worth asking as it would be a great application to have in a container.

It is always possible it temporarily dropped offline for some reason and is still OK. Unraid does not handle this well although the "Flash Remount" plugin can rectify this sometimes. It could be worth plugging into a PC/Mac to see if it can be read there. Ideally you want the 'config' folder as it has all your configuration information and licence.

I have often thought the documentation should be made far more prominent in the GUI. On my own system I have used the Custom Tab plugin to add a 'DOCS' tab to the main GUI which is far more obvious than the little icon in the bottom status bar of the GUI. This makes the documentation feel far more integrated than the current approach.

When you say the flash drive appears to have no file but does have space used how was this checked? The flash drive is formatted as FAT32 so should easily be readable on any PC/Mac Do you have a backup of the flash drive in case it has failed and needs replacing?

That is a feature of a parity protected Unraid array. When a drive is disabled it is ‘emulated’ using a combination of the other data drives plus the parity drive(s) and the system acts as if the drive is still there. Moving the data off the disabled drive is/was probably unnecessary - just a rebuild being needed to get the drive back to its normal state. The diagnostics might help if you want feedback on that.

Note that the link you give puts to legacy documentation - not the current online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release. You may find this section useful as it describes the process in much simpler terms. You may also find the Dynamix File Manager to be of use when moving the data around. It did not exist when the link you give was created so not mentioned there.

The fact a disk is disabled does not necessarily mean it has failed - just that a write to it failed. More often than not this is dies to an external factor such as cabling or power and the disk is fine. This section of the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page discusses this and actions that can be taken. You are likely to get better informed feedback if you attach your system’s diagnostics 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.

The correct process for adding new disks is documented here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. As you will see the last step was to format the drive which you said you did. The fact that the subsequent rebuild resulted in an empty file system suggests that the format succeeded so at that point you should have been good to go without the rebuild. there was definitely no need to Preclear the drive which is why it is not built into the core Unraid system. The link above discusses Clear v PreClear. In this case of an old parity drive being reused as a new data drive a preclear just wastes time.

This is NOT anything to do with the pool you have called ‘Cache’. It is that somehow you have also ended up with a User Share called ‘cache’. If you look you probably have a folder called ‘cache’ on one of your drives. You definitely want to fix this and not ignore it.

For anything to do with licence keys you normally need to contact support to get it resolved.

You can always set the access permissions on any mapped drive used by a container to be read-only for all users so it does not matter what user is used inside the container. Would that work for your cases?

The process is not really that complicated and is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. It is mainly a case of being methodical as one works through the drives to avoid accidents. What is useful is suggestions on improving the documentation from those who have tried to use the documentation but find the current documentation insufficient or confusing. it might be worth Limetech starting to emphasise the need to move away from ReiserFS in release notes as I am sure that there are many users who have put off the conversion because they were short of time and did not consider it urgent. However the time when reiserfs support is likely to be dropped from the Linux kernel is starting to get a lot nearer.

It is probably best (and safer) to leave it set to /mnt/user and use the Exclusive Share option that is now part of the 6.12.x releases. That gets the same performance advantages as would be given by /mnt/cache and is less likely to be something you might overlook in the future when making changes.

My memory being what is I do not either 😊

There does not seem to be a parity check running when those diagnostics were taken. Would need some taken while you were experiencing the problem.

Not familiar with that container, but you have given no container path for the 3D Prints mapping to make them visible inside the container - is that intentional?

I wonder if there is a good case for changing things so docker containers and/or VMs are not auto-started if you select Safe Boot. I would think the fact you have chosen Safe Boot means you are troubleshooting so it seems a good idea to me but there may be a downside I have not thought of.

Yes. You need to carefully define the start time so it can only occur once during the lifetime of a check. if you use the parity check plugin then you also get control over other types of long duration array operations. It will still, however, expect you to get the start conditions right for scheduled parity checks.

True, but it defers the cost which may matter for some people, particularily if they are not treating it as expected to be a multi-year buy.

The last few 'fast' copies will be because the copy is not actually going across the network as you think but is running locally within the server as Windows has triggered server side copying. The iperf results suggest you have a networking issue in one direction. What the cause is I do not know, but that is what you need to be concentrating on solving.

It does not fix the error, but if you click on the orange icon against the drive and select the Acknowledge menu item then Unraid will only notify you again if one of the values increases. As mentioned I would not be worried about the CRC error as that is a connection issue external to the drive and not an issue unless you get a lot. The others are more concerning.

I am confused. In you list of steps it was assigned in the second last step and then formatted in the last one. Why are you trying to do anything after that?

Are you sure it was not previously $59?

According to your diagnostics the check is doing exactly what you set it to do. Start at 4:00 am and pause at 8:00am until the next day! I think you settings are wrong for when it should be started as you do not want to start it again every day during the first week. You might want to consider using the Parity Check Tuning plugin to give you even more control over the checks.