itimpi

Those messages are perfectly normal when docker containers start up. If you are getting it frequently then you probably have a container that is crashing - you can check the uptime for your containers to spot a culprit. You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs. 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 a crash. 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.

Handling of drives (emulated or not) that show as unmountable is covered here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The Unraid OS->Manual section covers most aspects of the current Unraid release.

If you do not know the key then any data on encrypted disks will be lost.

Not sure where you read this - it is definitely OK. What is NOT OK is copying mixing a User Share and a Disk share in the same command as if you are not careful this can lead to data loss. It will be. When copying directly to a disk share you are by-passing the settings on User Shares that control where files should be placed. For them to have kicked in you would have to have been using /mnt/user/Movies as the target (or the Movies share over the network).

You may have better success if you use the Manual method of creating the USB drive. Seems to often work where the tool fails.

Just a thought - have you checked the Export settings for the shares to make sure they are being exported and not exported hidden?

Note that if you have done that and have a parity2 drive you will now need to run a correcting parity check as parity2 will not actually be valid. If might be a good idea to do that anyway just to confirm everything is in sync.

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.

What parity disks do you have? Rearranging drives invalidates parity2.

The server name resetting to default suggests that Unraid was unable to read some configuration information from the flash drive. You might want to try plugging the flash drive into a pc/Mac to check it is ok.

A value of 0 is treated as meaning "set it to a value based on my disk sizes". Setting it to any other value than 0 should retain whatever you set. It used to default to 0 but so many people would have problems with that setting at 0 that a change was made at some point to change 0 to a calculated value.

You can always get the disk manufacturers tools for the drive. However one I like to have on my system is DiskCheckup which is much lighter weight. You mentioned already having Crystal Info - I do not have experience of it myself but would have thought that had such an option.

No - it was me. I think I looked in the wrong set of diagnostics 😬 Looking again now I cannot see what might be causing the issue you describe. As you say there appears to be plenty of space.

Not quite sure what you mean by this?

The syslog shows you getting read errors on multiple drives and this is eventually filling up the space allowed for logging. What do they share than can cause this (e.g. power, HBA, etc).

Do you have any molex connectors on the PSU? You are likely to get better results with molex->SATA connectors as the SATA splitters can not reliably split more than 2 way whereas you can normally get 4-way with Molex ones as the molex connector can carry more current without voltage sag.

Correct. Any app that can start the test and view the results will be fine. Note that the test can take a long time (~2 hours per TB) and that the progress is only reported in 10% increments so with a very large disk can seem stuck on the same progress point for hours.

I see no reason why ZFS becomes the future - just an option within Unraid for users who gave appropriate Use Cases. I see Unraid continuing to support a variety of file systems to suit different Use Cases. The main change I see coming is the current Unraid array becoming another pool type probably called something new like a ‘hybrid array’. It could simply be called a Unraid pool but I see this being confusing with Unraid also being the OS name. Within that hybrid pool it would continue to have each drive as a free-standing file system in any of the currently supported formats.

That is strange - there does not seem to be a User Share with that name mentioned in the diagnostics.

You might give the name of a share having unexpected behaviour so we can check it. i do notice that some of the shares I looked at had very large values for their Minimum Free Space values. You might want to check these and put them to values that match how you expect to use the system.

Trial licences cannot be transferred. Instead you would need to get a new trial licence for the new flash drive.

If you want to continue using macvlan then make sure bridging is disabled on eth0.

It definitely needs replacing. As well as the large number of reallocated sectors Bering worrying you also want the pending sectors to be 0 on a healthy disk. Probably the easiest way is to run an Extended SMART test on the drive to see if that can be passed. This can be done via a disk manufacturers tools or one of many 3rd party utilities. If connected to the Unraid server you could also use the Preclear facility to test it.

Weird - first time I have heard of something like this. Almost sounds as if it is something related to applying power to the drive. All I can think of to suggest is perhaps not monitoring that attribute for those drives.

No obvious problems in those SMART reports. The only one highlighted (CRC errors) indicates a connection issue and normally related to the cabling to the drive, and it never resets to 0, so as long as it is stable or very occasionally increments nothing to worry about it.