itimpi

You can rebuild each disk in turn if that is more convenient. After the first rebuild succeeds then the array will be back in a protected state.

@unusername if trying to use a ‘move’ rather than a copy/delete you have to be very careful folders/files do not end up on an unexpected disk as described here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at he top of each forum page.

The correct handling of unmountable disks is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at he top of each forum page. I suggest you keep the disk you removed with its contents intact as it may prove an alternative recovery option for any data.

My suggestion is that you start by posting your system's diagnostics zip file so that we can see the current state of things. Then pick one specific issue that you are having problems with that you want resolved and we can then see if we can guide you getting that done. After that work on the next issue. I suggest concentrating on a single issue at a time so that the feedback you get at any point in time s focused on that one issue rather than scattered across different ones.

Sounds like it If the cache drive was assigned then Unraid would have automatically picked up the files for those shares from the cache drive (regardless of any of you share settings) so deleting the shares would be deleting from the cache drive.

Have you ensured that the folder for the Time Machine share does not exist on disk8? You might need to manually delete it if it does.

Are you sure your PSU is up to handling that many drives? Do you have any splitters used in the power supply cabling to the drives?

Just to check the obvious, do you have the ‘isos’ share setting set to be visible on the network. The default is for it to not be visible.

Why do you say this? This is the default (and recommended) setting.

Do you have an ad-blocker installed in the browser? If so you should make sure your Unraid server is white-listed in the ad-blocker.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.

You can use the New Config tool to change the assignments to what you want and then rebuild parity based on those assignments.

At the moment Unraid should be emulating disk3 using the combination of the other disks plus parity to act as if it were still present. If you replace the missing disk3 then Unraid will rebuild the contents of the 'emulated' disk3 on to this replacement. If you try to do anything else this will invalidate parity (and parity will need to be rebuilt) and thus the contents of disk3 become irretrievably lost so be aware of this.

I have added a mention of these steps to the online documentation so thanks for the feedback.

If the appdata share is also on the array then make sure they are configured to use separate drives. Each disk in the main array is a self-contained filing system so you would be unlucky to get a failure that caused simultaneous corruption of multiple drives.

If when you got the original failure once you had described your problem and posted diagnostics so we could confirm there was nothing else obviously wrong we could have given you the steps to get Unraid to accept the original parity disk so that you could then probably get an error-free rebuild of disk3. In principle it is a good idea to ask for help before letting Unraid do anything you are not sure about.

In most cases sorting out a lost+found folder is more effort than is worth it. The items in there are ones where the directory information giving their names is what was lost. Sometime using the linux 'file' command to determine what type of content is in a file can help - but in your case it sounds as if that might not be much help. It just emphasises that you still need backups of anything that you deem important as things can go wrong that are outside your control. Just as a check are you saying that the drive is NOT disabled (i.e. has a red 'x') against it. Just asking as if it was disabled the repair would have run against the emulated drive, and if that is what happened a repair of the physical drive might be more successful.

It is possible for RAM, CPU and motherboard to go wrong so a failure does not pinpoint the failing item. My guess is it happens more frequently with RAM but that guess is not based on any hard evidence. It can sometimes be worth simply reseating the RAM in its motherboard slots in case it has worked slightly loose. It is possible for each RAM stick to test out fine individually but you still get failures when you have multiple sticks plugged in due to overloading the motherboard memory controller. Carefully check in your motherboard manual the maximum RAM speeds your motherboard+CPU combination can support and remain stable - it is often lower than the rated speed of the RAM sticks, and can vary according to the number of sticks you have plugged in. Anything other than 0 failures means the system will be unreliable. In terms of how long to run the test the general answer is at least for a complete pass, and ideally for longer (e.g. overnight) as long as you are getting 0 errors. No point in continuing a test once you start getting errors reported other than perhaps seeing if it points to a particular RAM sticks/slot.

It looked to me as if you only did the short SMART tests on the drives. Drives can easily pass this test and still not be reliable. You should carry out the Extended SMART test on any suspect drives and any that do not pass this should be replaced. Note that when carrying out the Extended test it can take many hours (with progress only reported in 10% increments) and you should temporarily disable any spindown on the drives being tested.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.

One way you can get the symptoms you described is mentioned here in the online documentation accessible via the 'Manual' link at the bottom of the GUI. If this was the problem, though, it would not be as a result of the upgrade.

were you replacing the drive as part of an upgrade process or because you thought it had failed? in other words do you think the contents of the drive you removed are intact?

Sounds as if you are seeing a manifestation of the behaviour described here in the online documentation accessible via the 'Manual' link at the bottom of the GUI. If you are on Unraid 6.10.x or later you could install the Dynamix File Manager plugin and use that to move files instead of Krusader. This plugin is aware of the issue and will use a copy/delete strategy to avoid it.

From the description you give it sounds like has to be something in your laptop or router that is limiting the speed. You have confirmed that Unraid can getter speeds when the laptop is not in the equation.