Can anyone please provide some guidance regarding the following?
I currently have five hard drives within my drivepool, housed in a microserver, totalling 16TB.
However, I have received an alert via Drivescanner warning me that one of them, a 3TB drive, might be heading towards failure - let's call if Drive F.
When I try to remove Drive F from the pool it gets to the stage of migrating the files before telling me it cannot proceed due to an I/O device error. However, the content of Drive F *has* dropped down from 2.72TB to 700GB, so some migration appears to have occurred.
I know that I can force Drive F out of the pool if it comes to that, but I don't know what happens to the files on it. Are the files self-contained, or shared across the other drives in the pool? Would I be left with only parts of a file - both on Drive F and in the remainder of the pool?
Drive F is currently showing as having about 700GB of material on it.
Across the rest of the pool, I've freed up 2.74TB of free space. And what I've started to do is look to remove the files which are listed as being on Drive F out of the drivepool and onto non-drivepool areas of the remaining four hard drives.
Is this the best approach? Once all those files are moved by me, should I then be able to force Drive F out of the pool without losing anything? I guess one of the issues might be that the files listed as being on Drive F may only be *parts* of a file? Would 2.74TB be enough to take the parts off Drive F as well as the remainder of those files which are spread across the rest of the pool?
One further quirk which has developed is that one of my shared folders is coming up as not being accessible either in the general Drivepool Drive or via Drive F, but I can get into it on the other drives in the pool.
Any advice very gratefully received.
Best,
Desk