I just got my build up and running.  I have been copying my data (3 tb ) to the server.  During the process I was watching the web interface and the green lights started flashing green to white and back to green.  I lost the temp readings of the disks.  What I ended up doing was stopping the copying, stop and restart the array.  This seemed to fix the issue.  So has anyone ever bumped into this before? Should I be concerned about this?

I just got my build up and running.  I have been copying my data (3 tb ) to the server.  During the process I was watching the web interface and the green lights started flashing green to white and back to green.  I lost the temp readings of the disks.  What I ended up doing was stopping the copying, stop and restart the array.  This seemed to fix the issue.  So has anyone ever bumped into this before? Should I be concerned about this?

Yes...

 

The "green" indicators flash when the disk drives go to sleep and spin down.  It is an indication the disk is sleeping. (spin down)

 

The temperature on most disk drives cannot be read without them spinning.  Therefore, you'll see no temperature reading when the disk is not spinning.  (A side effect of reading the temperature spins up the drive, therefore, when not spinning no temperature reading is attempted so it remains sleeping)

 

You should not be concerned.  If you always wish to always see the temperature you can set the disks to never spin down.

 

 

This was strange because I was copying files to the server.  When this happened it seemed like it stopped copying files to the server.  So I stopped the copy process and and started copying again, just in smaller chunks.  I was trying to use teracopy standalone to copy 3 tb to the server.

I just got my build up and running.  I have been copying my data (3 tb ) to the server.  During the process I was watching the web interface and the green lights started flashing green to white and back to green.

Did this happen to all the disks in your array at once or did just a few of them switch? 

 

Also, if you are starting with an empty unRAID server then it would be much faster (~ 2X) to copy the files over to unRAID if you removed your parity drive from the array.  Once you've copied all the files over then you can add the parity drive to protct the data.  Since the files exist elsewhere there is no benefit to having parity protection while copying them over - it's just slows down the process.

I realized that after I started copying.  SO can I temporarily remove the parity drive, then readd the drive after I am finished copying everything?

 

I realized that after I started copying.  SO can I temporarily remove the parity drive, then readd the drive after I am finished copying everything?

Yes, just unassign the parity drive on the devices page.  Then when you are finished copying over the data you can reassign it and your array should automatically begin to calculate parity.

Thanks for the help