ncage

Thanks, Drashna. I might ask in a year or so to see if the status has changed any but for now i, of course, will go with your recommendation.

Hi, everyone. I just got a warning from stabilebit scanner that my reallocated sector count has got worse. I got a warning sometime back that the drive has some reallocated sectors and I just told stablebit to let me know if the count got worse. Now I got another warning they hate have in fact got worse. I have two of the same type of drive and they both have reallocated sectors. The drive type is
Seagate 1.5 TB (ST31500341AS). There were all kinds of problems with these drives when Seagate released them (only time in my life when i had to update the firmware on a hard drive). I ended up having to get them both replaced under warranty but haven't had any issues with them other than when I first started using stablebit scanner that I was telling me both drives had reallocated sectors. Unfortunately i don't remember what was the previous reallocated sector count. Here is the email:
 
ATA ST31500341AS SCSI Disk Device - 1 warnings
There are currently 36 reallocated sectors on the hard disk. A reallocated sector is created when a sector cannot be read or written to. In such a case, the next time the sector is written to it is swapped in for a good one from the spare sector pool. Having reallocated sectors decrease read/write performance and indicates drive trouble.
Realize the drive is not under warranty anymore. I'm not in a habit of throwing drives away. Would you just tell stablebit again to tell just tell me if things get worse? Is there any general rule on the # of reallocated sectors when you need to get rid of the drive?
 
thanks,
Brent

Looks like the error isn't being properly handled here.
 
 
Specifically, the second message is the correct one here, and .... what is the problem:  That files are still in use on the pool.  We cannot move "open" files (at least in this version), so it errors out.
 
 
That said, please grab this version:
http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.798_x64_BETA.exe
 
There are a bunch of changes in this version that may fix a wealth of issues, but specifically, the drive removal code was rewritten, and should handle this sort of issue MUCH better.  
 
Install this version, reboot, and then re-attempt the removal.
If you still have issues, make sure you select the "force" options (both of them), as well.  This should help with removing the disk.