Hi,

 

I was copying data to my unRaid Server and didn't notice that the cache ran full. I meanwhile changed the setting on the share to not use the cache and cancelled the copy-process. When I checked the unRAid dashboard I saw a lot of notifications that the cache was full andsomewhere in between that a drive was disabled.

A parity check was running the past hours and still is.

I attached the diagnostics file.

The mover is running (I assume, as I can see space getting freed up on the cache drives).

This  is my Main dashboard:

 

How come the drive was disabled? And what can I do now?

I'm still very new to unRaid and still  in the process of setting it up bit by bit.

 

Many thanks!!

 

Odom

 

diagnostics-20190501-2002.zip

It's better to not cache anything for a large initial data load, since cache will not have the capacity. And it would also be better to wait until the initial data load is complete before setting anything else up, such as dockers.

 

You will have to rebuild disk6 after checking all connections. You may have to reformat cache and install your dockers later.

 

Do you still have the source data you are trying to load on this system?

If you mean what I copied today yes, not the other 30TB. Disk 6 is the latest I added to the array, I"m only copying some copies of backups onto it.

How do I only rebuild disk 6?

Edit:

Do you mean following this procedure?

https://wiki.unraid.net/Replacing_a_Data_Drive

Edited May 1, 20197 yr by Odom

13 minutes ago, Odom said:

How come the drive was disabled? And what can I do now?

A disk being disabled means that a write to it has failed.    When that happens Unraid stops using the physical drive and instead ‘emulates’ it using the combination of the parity drive and the remaining data drives.    Since writes can still be made to the ‘emulated’ drive this means that the physical drive is no longer in sync with the ‘emulated’ one.

 

Very frequently there is nothing wrong with the drive itself, and the write failure was caused by an external factor (cabling, power, controller).    The recovery process is to rebuild the ‘emulated’ drive back onto a physical one.    If the drive has really failed this will be to a replacement drive.    If it is determined that the disk has not really failed then it is possible to rebuild back to the original drive to bring it back into line with the ‘emulated’ one.

2 minutes ago, itimpi said:

  The recovery process is to rebuild the ‘emulated’ drive back onto a physical one. 

How do you do this? Is it the procedure of replacing a data drive and simply re-use the same one?

The parity check is still running. Is it advisable I wait until it is finished before doing anything else?

SMART for disk6 looks OK.

 

Your screenshot shows a lot of writes to both parity disks. Did you have valid parity before adding disk6?

I think so. I did a pre-clear on disk 6.

I had a USB drive attached and was using Krusader to copy data and at the same time I was copying data from my PC to it as well. I enabled the cache on a folder without considering that there wouldn't be enough cache free for the data I'm copying.

I ran a quick SMART test and it also came back fine. Maybe it was too much for the drive and it bailed.

 

How can I get it back enabled?

OK, I guess those writes to parity are just updates due to writing disk6. You say it is doing a parity check currently? Why?

 

Post a screenshot of Array Operations.

The parity check was running because I had it scheduled to run on the first of every month. It just finished now:

 

 

 

 

The Main screen looks like this:

 

 

 

The SMART for disk 6 looks like this:

 

 

The free disk space on the cache stabilised. When I check the scheduler settings it doesn't show as the Mover working

 

Is there another way to show you what the array operations are?

What can we do about disk 6?

 

Thank you very much for the help so far, it is really appreciated!!

 

4 hours ago, Odom said:

What can we do about disk 6?

The wiki link you posted earlier has the correct procedure for rebuilding to the same disk.

Thanks very much!

I removed the disk and replaced it with another WD Red 6TB I have. The array is now rebuilding.