hypermog

Reinstalling Windows 10 appears to have fixed the problem. My drives are back and working perfectly... thanks Chris.

I've decided to reinstall Windows 10 to try to fix the problem. This is what I will do: Disconnect the two external drives used for DrivePool Reinstall windows Install DrivePool Connect the external drives Chris, my reading indicates that DrivePool will then recognize the drives and the DrivePool will appear – mapped and all. Is that right? Do I need to reconfigure or import the old drives somehow? And most of all, will the data be preserved? Thanks

I have wanted this to work for so long and it finally works now. I had to do pretty much every single thing Christopher suggested in this thread, but it works. Thank you!

Thanks for your replies. I am on 2.2.0.903. Will post back with any new developments.

First, let me say I searched this forum for 'KB2267602' and did not see any results. Issue: Windows Update KB2267602 fails to install and Windows Defender cannot run. It appears as though Covecube is aware of this issue based on the following comment in this code change: Is there an update to when this issue will be addressed? I don't like having Windows Defender unable to run on my PC, and it seems like Windows Update has stopped searching for new updates as well. Thanks.

Right you were. Both drives now show 'Healthy' after a full scan. Thanks very much for your help!

After I installed the new version and restarted, it forgot that it had scanned those drives before. That's fine because I want to see how this version does with a full scan anyway. So it's scanning the drives right now -- it'll probably take until tomorrow to finish. Thanks for your fast replies Chris. The model number is Western Digital WDBCKA0080HBK-NA. These are external drives... someone on reddit opened one, here's the best picture they had showing what's in it: https://i.imgur.com/TzmZUfX.jpg. Looks like WD80EFZX

So after the full disk scan completed, I marked unreadable sectors as unchecked and ran the check again. They show as damaged still. It's the very last sector on both disks. I'm not storing any data on these disks. How can I resolve this problem? Do I need to format the disk?

I don't understand why the scan doesn't start when I press Start check. Is that a known issue? No matter how much I press it, even with the drive selected, it won't start scanning. Nothing happens actually. Pretty disappointing for a program called Scanner. edit: I left it and came back an hour later and the start check button worked this time (...but had not started already, i.e. it was not a delayed start from earlier). There should be some kind of message or indication letting you know what's holding it up. Anyways, full scan continues.

Hi Christopher, thank you for the fast reply. I went ahead and ran the burst test for 24 hours, came back successful. I'm going to let it finish scanning the drives, then mark unreadable blocks as unchecked and scan again. Do you think that's a good idea? Also, is it possible to have it just rescan the unreadable blocks?

I just bought two identical 8TB WD Reds, and ran StableBit Scanner on them. I'm using StableBit.Scanner_2.5.2.3103_BETA.exe on Windows 10. It says that both disks are damaged and it appears to be the same sector on each. Is this possible? Am I reading this right? For what it's worth, I'm also running DrivePool. (screenshot.png) P.S. the FireFox security warning for this website is kind of bothersome, please take a look at that (insecure.png).