I have a data disk that is showing some poor SMART attributes, so I'm planning on replacing it with another disk of the same size that I have as a spare. My issue is that my server is slightly under-fanned (for noise) - so it gets pretty warm when doing array intensive tasks like parity checks and rebuilds.

 

Since this disk I am replacing is fully functional now - is there anyway I can just copy the old disk to the new one and not have to sit through the 6+ hour rebuild process with the box on my desk with an fan blowing into it.

 

I have searched the forums a bit because I suspect this has come up before.. but I haven't been able to find anything.

 

Can someone point me in the right direction?

 

Cheers!

I don't remember that specific set of conditions being addressed here before, but my gut instinct is that you could dd the drive from the old to the new, set a new config, tell unraid parity is already valid, and do a parity check just to be sure. HOWEVER... since I would recommend doing a parity check before you started messing with it, and a parity check afterwards, my gut instinct is that you would be better off temporarily putting a portable fan blowing on the server and going through with a normal rebuild, parity check before and after, and call it a day (or 3) 

 

How does the array handle a normal monthly check? If you are stressing it with normal activities, perhaps you need to rethink the entire thing. It would really suck to cook the server because a drive failed and it went into degraded mode, which spins up all the drives for any data activity.

I'm not really worried about it - I may see one or 2 drives get 45 degrees towards the end of a parity check with no extra fan. Hotter then I'd like to see for longevity, but not cooking. The plan is to put a fan in the top of the case (spot, but no fan presently) with a temp sensor.

 

I'll do the rebuild I guess - it just seems like a waste of drive crunching given that data is already intact on a disk.

 

Thanks for the help.