Hello all, I have a question that I couldn't find an answer to when I searched the forums.

 

I recently performed some cleanup on my unRAID server and now have 2 disks in the server that are completely empty.  Should I disconnect the power cables from these empty disks to prevent them from spinning up and down each time we use the server?

 

Just wondering if disconnecting them will save them from unnecessary wear and tear since they aren't needed at this time.

 

Thanks!

If they are part of the array, they will spin down with the spin down timer. There is not much harm leaving them plugged in unless you don't plan to write to them until months from now.

 

If they are NOT part of the array, they will not spin down and will always be on.  For those, you should unplug or write a script that spins them down.

I would advise to leave remove the drive from the array logically (not physically), make sure it is nice and clean (possible do a preclear cycle), and then leave it in the system as a hot standby, the moment a disk fails you then only need to logically remove the failing drive from the array and add the hot spare.. You will be protected again then at the shortest possible interval (the time it takes to restore the missing drive).

I would have never added them to the array to begin with...

 

Even when spun down they are consuming watts, 24x7.  (ok probably ONE watt each, but still it's useless until you need them, and when you do it takes only minutes to add the drive if you are using a 5in3 or something, where the power and signal cable are already wired)

Depends on where you have your server physically.. If you have it snorring under your desk this is true, but if it is tucked away somewhere it might be usefull.. But I agree: cold standby will work also, worthwhile to have it physically in the system and precleared ready to go though.

Just wanted to post a follow up since I have now completed this "unplug empty disks" project.

 

It wasn't as easy as I thought it would be because unRAID doesn't like it when you unplug a disk that is part of the array - even if the disk is empty.

 

To remove the unused disks I did the following:

• Run a parity check
  
• Take a screen shot of current disk configs in case something goes wrong
  
• Stop array
  
• Un-assign empty disks from devices tab
  
• Run initconfig from command line to refresh disks configuration
  
• Start array
  
• Wait nervously while parity rebuilds again
  

In the end I was successful in removing the unused disks but I was a little nervous running without parity protection during the time it took to rebuild parity.

 

Maybe this thread will help others in the future who may have this same question about removing empty disks.