itimpi

Nothing obvious in the screen shot. Are you saying that when you stop the array you cannot add that device as disk7. If so, perhaps you can post diagnostics taken after attempting this so we can see why it is failing.

Note that although Unraid allows for ZFS format on array disks, these can only be single device pools as each array disk must contain a free-standing file system.

Normally rebooting would cause this to restart from the beginning (unless you have the Parity Check Tuning plugin installed and you have set it to continue from point reached).

You do not mention which share you are talking about, but looking at the diagnostics the likely shares have a Minimum Free Space setting of 1.5TB and the pool does not have this much free space. Having said that is debatable whether it is worth caching a share that is on a SSD pool in the first place.

Removing disk is covered here in the online documentation. The New Config tool is covered here. Note in particular that New Config does not touch the existing data on drives - it just rebuilds parity to match the new drive set.

Not quite sure why you are having a problem with this. It is normally just a case of assigning it to a new slot in the array. Perhaps a screenshot of the Main tab might clear up what is your problem? After it has been added you then control at the Individual user share level what drives the share is allowed to use.

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.

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.

If you have the key file have you put into the ‘config’ folder on the flash drive? If so I suggest 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.

For mover to do anything you need to have both Primary=pool, Secondary Storage=array, and the mover direction pool->array to achieve getting the files moved off the pool and onto the array. You should also have Docker and VMs disabled in Settings as they can hold files open and stop them being moved..

The sector is logged so you can at least see if you keep getting the same sectors reporting errors. However it is not specific to any drive, and it is also not easy (and thus practical) to try and work out what files(s) that sector might belong to. If you want to be able to check for file level corruption then you need to have checksums for your files. BTRFS and ZFS formats have this built in, but for XFS you need to use additional software such as the File Integrity plugin. With checksums then you can identify exactly which (if any) files are corrupted.

Not using standard Unraid features. It is just possible that disk recovery software such as UFS explorer on Windows might be able to recover something. That software is not free, but it does have a free option that shows what (if anything) it would be able to recover.

No. It is on the location you specified for the Docker container files to be stored on. It does not use up RAM space.

No. Unraid has no idea which drive caused the problem. This is why a parity check was automatically started. I believe these automatic checks are always set to be correcting. After an unclean shutdown it is perfectly normal to have a number of errors needing correction. The correction is always to make parity match the drives. The normal Unraid write process updates the data drive before the parity drive so if there was any sort of crash it is most likely to be the parity drive that was out of sync. I would just let it run to completion. Is the error count still increasing? Just asking as after an unclean shutdown most error are likely to be near the start of the check.

What you have done is not necessarily wrong but I think it leaves room for confusion at times. I think having a physical device (the pool) and a logical device (the share) having he same name can be confusing. I would just rename the pool to something like "Downloads_Pool" so that you never get any mix-up between the pool name and the share name. If you do this you would obviously then need to adjust any references to the pool to match your change.

I am surprised Unraid even lets a pool and a user share have the same name! Seems a recipe for potential user errors 😊

Not sure how this ever worked for you then. Unraid has always tried to copy to the pool being used for cache as long as there was at least the Minimum Free Space left, and then failing with out of space if the file subsequently did not fit. I can only think that in the past you copied directly to an array drive and not to the User Share.

You need to run the Extended SMART test to get a meaningful result. Passing that normally means the drive itself is OK and it was some other factor that caused the dtive to be disabled. I would carefully check the power and SATA cabling to the drives as it seems unlikely they would actually really fail simultaneously. Note that to clear the disabled state you will have to rebuild parity.

According to the diagnostics the PLEXMEDIA share does not have any files on the ‘cache’ pool.

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.

Stop array Unassign disk3 Start array to make Unraid ‘forget’ current assignment Stop array Assign disk3 Start array to begin rebuild.

Just to clarify, ANY storage devices that are plugged in at the point the array is started count towards the licence limit even if not configured to be used by Unraid. Drives plugged in afterwards on a temporary basis (such as removable drives used for backups) do not count.

Yes.

That is the easiest way.

As was said you cannot have two flash drives with the label ‘UNRAID’ plugged in. If you want to use one in a VM it has to be labelled something else as described in the documentation for running Unraid in a VM here.