Good morning. I've been a longtime user of Driverpool/Scanner. I have a small home server used mostly for media throughout my home (Plex media server). One of my drives has periodically shown "damaged" sectors and in scanner it states "not predicting immenant failure....etc), I have everythign in my pool duplicated, so I hadn't worried about it too much. I had another drive that was overheating quite a bit, and eventually Scanner detected a problem and on that drive it did detect imminant failure and automatically started migrating the data off the drive by rebalancing. As a result, I purchased another 3 tb drive, removed the "imminant failure drive" from the pool. Placed the new drive in the system and added it to the pool. This is where things get weird. Once added to the pool, Drivepool "measured" and then rebalanced....and then I restarted the computer (normal Windows update stuff...I'm on windows 10 btw). When it restarted, the computer went to diskchk and got to 65% and stayed there forever. I eventually just restarted and told it to skip disk checking and it booted into windows. I went to scanner and told it to scan the new drive. It did, and it found damaged sectors on the new disk as well, with the same "not predicting imminant failure" message. Now, drivepool starts remeasuring and trying to rebalance again. I let the rebalance run for 16 hours and it only got to .05 percent. I'm not certain what is causing the problem (new drive that is "damaged" or older drive that is "damaged" or both. Furthermore, I'm not sure what to do to take the system out of the state of flux of rebalancing/remeasuring. Again, I have everythign duplicated, but have no idea how to proceed without losing anything. Please help!
Question
crankycowboy
Good morning. I've been a longtime user of Driverpool/Scanner. I have a small home server used mostly for media throughout my home (Plex media server). One of my drives has periodically shown "damaged" sectors and in scanner it states "not predicting immenant failure....etc), I have everythign in my pool duplicated, so I hadn't worried about it too much. I had another drive that was overheating quite a bit, and eventually Scanner detected a problem and on that drive it did detect imminant failure and automatically started migrating the data off the drive by rebalancing. As a result, I purchased another 3 tb drive, removed the "imminant failure drive" from the pool. Placed the new drive in the system and added it to the pool. This is where things get weird. Once added to the pool, Drivepool "measured" and then rebalanced....and then I restarted the computer (normal Windows update stuff...I'm on windows 10 btw). When it restarted, the computer went to diskchk and got to 65% and stayed there forever. I eventually just restarted and told it to skip disk checking and it booted into windows. I went to scanner and told it to scan the new drive. It did, and it found damaged sectors on the new disk as well, with the same "not predicting imminant failure" message. Now, drivepool starts remeasuring and trying to rebalance again. I let the rebalance run for 16 hours and it only got to .05 percent. I'm not certain what is causing the problem (new drive that is "damaged" or older drive that is "damaged" or both. Furthermore, I'm not sure what to do to take the system out of the state of flux of rebalancing/remeasuring. Again, I have everythign duplicated, but have no idea how to proceed without losing anything. Please help!
Eric
Link to comment
Share on other sites
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.