itimpi

It looks like the disk dropped offline so there is no SMART information for the drive. It might be worth power-cycling the server to see if the drive comes back online and then post new diagnostics.

It gets created if the repair process finds files and/or folders for which it cannot locate the directory entry so does not know what the name of the file/folder should be.

With the fact that the NerdPack plugin is now deprecated then the warning from FCP probably needs updating so that it only issues the warning if the packages are not from Nerd Tools plugin.

CRC errors are connection errors that are normally caused by the SATA or Power cabling rather than faults with the disk itself. When such an error happens it normally causes a retry to happen so that the write eventually succeeds so the net effect is simply to slow things down. On that basis a small number of such errors happening occasionally is not really a cause for concern but it is more of an issue if they occur with any frequency. It is also worth noting that the count never resets to 0 so if you click on the orange thumbs down icon and select the Acknowledge option then Unraid will only notify you again if the count increases again.

@agonza The section 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 seems reasonably clear to me? Is there a suggestion for improvement?

The top level is the folder that is equivalent to the share name and is level 1.

Unraid insists on having at least 1 drive in the main array, but for your Use Case you could make this a small thumb drive which is not intended to store data and have 2 pools with the actual data.

No. Unraid will only attempt to read the SMART information if it thinks the drives are NOT spun down.

If you rename the .plg file in the ‘config’ folder on the flash drive to have a different file extension and reboot then the drivers will not be loaded.

The SMART report for the drive.

I think because everyone seems to have it I assumed it was in the base I wonder what proportion of users do NOT have the UD Preclear plugin?

It might be worth mentioning that Unraid 6.11.x includes as standard the tmux package that can be used instead of screen.

Do you mean bits or bytes? If you mean bytes then that is normal as a write to the Unraid array involves multiple I/O operations as described 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.

There is no connection to your Unraid server unless you install the MyServers plugin. The only slight exception is if you are running a Trial version of Unraid when a temporary outward connection is made to check the Trial licence when the array is started. The Unraid server can only be accessed remotely if you have installed the MyServers plugin AND enabled that feature.

Not sure what is going wrong for you, but you should be able to get the server side running irrespective of whether you actually have the Alexa skill installed on a echo device. In particular you should be able to get the server to show up in the Servers page. You can try asking on the MyMediaForAlexa site to see if they have any suggestions. The docker container is exactly the same one that is deployed on other platforms - the only Unraid specific part is the creation of the template that provides the parameters that would otherwise to be provided via a docker run command.

The links for the last 3 stable releases are at the bottom of the Download page - the same one that has the USB Creator tool download.

You can only use ECC RAM if the motherboard supports it.

Are you trying to boot in legacy or UEFI mode? For UEFI mode the Unraid flash drive needs the trailing ~ character removing from the EFI folder name.

A disk is disabled when a write to it fails, but often this is due to a factor external to the drive. Once a drive has been disabled then it needs to be rebuilt to get it out of the disabled state. This applies regardless of whether it is a data or parity drive. The process for rebuilding a drive onto itself 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.

The delays are probably occurring when flushing RAM buffers to physical disks. you can never achieve anywhere near the native write speed of a drive as under Unraid a write operation always involves multiple I/O operations. This is described 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.

Do you expect the data on the internal drive to survive the transition from internal to external? If so then you cannot simply add it to a parity protected array as Unraid would clear it to zeroes during that process, so alternative/extra steps become necessary to keep the data.

Fair comment: I will see about at getting links added from some of the other sections of the documentation to make it easier to find.

It 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 probably your very restrictive value for the shares Split Level setting that is causing your problem. The Split Level setting will over-ride the Allocation method and Minimum Free Space setting in the event of contention between them as to what drive to use (as 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).

Have you tried the process described here for handling unmiountable disks 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?