Lake

I'm using Windows 8.1 Pro 64-Bit I'm using DrivePool version 2.1.1.561 I'm running Webroot SecureAnywhere v8.0.8.76 File System Filter Drivers: C:\Windows\system32>fltmc Filter Name - Num Instances - Altitude - Frame -------------- ------------------ - -------------- ------------ WRkrn 329998.99 <Legacy> WRkrn 20 321611 0 luafv 1 135000 0 npsvctrig 1 46000 0 FileInfo 20 45000 0 Wof 0 40700 0 I submitted my Service.zip file through the contact form. I stopped the error logging as soon as I could after the error occured, so the actual error should be near the end of the file.

Every time I write data to my Drive Pool the Pool Organization bar goes yellow and starts checking... Once the check finishes, it always goes back to normal.... until I write data to the pool again. I have 6 internal drives connected to SATA ports, and 8 drives in a Mediasonic Probox that are connected through USB 2.0. Reading data is fine. I just cannot write any data without the drive pool going into "checking..." mode.

Yes, Real Time Duplication is enabled. It took several minutes, but after the pool was remeasured, it did start.

Sorry if this question has been asked and answered before; I looked around and didn't see anything. I just had a drive in my drive pool start giving read and write errors. So, I shut the PC down, removed that drive, and upon reboot Drivepool alerted me to the missing disk, as it should. Then I selected "remove missing disk from pool", and then selected "re-measure". When the process was complete, the Pool Organization bar was at 100%, and I had 2.08TB of un-duplicated data, which is exactly the amount that was on the disk I removed. (so, everything is perfect.) My question now is: when will Drivepool start to duplicate the data which is currently un-duplicated? -- Does this process start automatically if given time?

Done.

All disks are initialized and simple partitioned. The "disk details" for each drive reports a string of numbers and letters. (not all 0's) I found that if I manually "stop scan" before restarting, that saves the progress of all disks. However, I only had the problem happen once, and I haven't tried rebooting without manually stopping the scan first since then, so it could be one of those fluke problems that only happens once. I'll make another post if something similar happens again.

I'm using a Mediasonic 8-bay JBOD usb enclosure via USB 2.0 with 8 3TB hard drives. Yesterday night one of the drives was being scanned automatically by the scanner in the background, and I noted before rebooting the computer that the progress was at 44% complete. Then I checked the progress after rebooting, and the drive showed up as "not checked". I looked at the disk sectors map and all of the blocks were grey. (I checked all 8 of the drives to make sure I was looking at the right one.) The scanner program did save the status of the other drives in this JBOD enclosure, though. One of them was fully complete and showing up as "Healthy". The other was about 1.5% complete and "waiting to scan" before I rebooted, and after the reboot it still showed up as 1.5% complete. The remaining 6 all show up as "this drive has never been checked for problems", which is not true. But the drive that was being scanned when I rebooted lost all of it's progress. (about 12 hours worth of scanning.) I should also mention that there are an additional 6 hard drives that are connected to my motherboard which are scanned, and all are showing up as "healthy" even after reboots. It's just the drives in the JBOD enclosure which are currently being scanned which is losing it's progress upon a reboot. I'm afraid to reboot again for fear of losing the progress on the drive that's currently being scanned. What can I do?

What happens if I move and delete files while the scanner is checking a file system on the disk for problems?