thepregnantgod

Latest beta. Maximize duplication - meaning: change it to a foreground task vice background task, increase priority, give it as many cores as possible, as much RAM as possible.

I saw a wiki article on DrivePool's advanced settings. Can someone who has experience with this advise me? I want to maximize duplication across all 22-24 drives. I have 16gb RAM and an i73770K (so 4 cores/8 threads). What do you guys recommend?

I was using the x483 beta. But for some odd reason my pool became "unable to access" - no permissions? So I uninstalled the beta and reinstalled. I can now access my pool but I can't change the name of the virtual drive - from the default letter (D). I could before... Any ideas?

I put in my 1000watt PSU today and spread the drives among different rails coming out of the PSU. Hopefully no more problems.

Lee - I suspect what you say is happening. I have ordered a 1000 watt powersupply to deal with the issue. I have lost two drives already. Pain in the arse. In your opinion, how many green drives can be connected to one molex/sata connector coming out of the PSU? (mine have 3 different connectors on one cord coming from the PSU which I then have branched out to manage all 24 drives).

What's the cause of this? Is there something I'm doing on the hardware end to limit this? My setup: Supermicro SAS2LP-MV8 cards (x3) connected to: 15 3TB green drives 7 4TB green drives If there's something I can do, let me know. This happened a few days ago and one drive completely crapped out. I'd rather not have that happen again.

Philmatic, see my post in the scanner forum. I managed to clean it completely. It's now marked as healthy - I wrote zeros three times. Took a while but seems to have worked.

Happy to report, the two pass zero fill above seemingly fixed it. Scanner reported it healthy and the SMART attributes have changed as well.

Drashna, thanks for the quick response. The chkdsk /r /scan seemingly did not remove the bad sectors/remap them, do anything. I'm going to try format g:/fs:NTFS /p:2 (a 2 pass zero fill from an elevated command prompt). It's a 3TB drive so not sure how long it will take. After it completes, I'll scan it again with your scanner and report back.

I starting to enable duplication on my folders. I enabled it on one folder - a Bluray rip of a movie. The .iso rip was 34gb. Within the same folder is a file of the same exact size, partial name, and ends with copytemp extension. I'm assuming that's the duplicate of the .iso. But...is it stored in the same directory? I recently migrated from Drivebender and they stored their duplicates in a separate folder. If it is indeed the duplicate - is it located on a different drive but appears in the same folder? Just trying to understand how it works.

Drashna, I'm double posting to both forums unfortunately. But since you responded here first... I did run chkdsk /r /scan. The 16 sectors remained.

1. Drashna and others - you are very helpful. Quick responses - enjoying your product(s). 2. My concern is what to do with a particular drive (and future drives like below) where it has 16 uncorrectable sectors. It is out of warranty so no chance of RMA'ing it. - I have formatted it (quick) - I have chkdsk /r /scan overnight - I then rescanned it and the 16 sectors are still bad 3. Is the drive useless? I was under the impression that if the sectors are uncorrectable they'd be swapped out. Thus, I can assume that there are actually many more bad sectors on the drive but they have been remapped already? 4. Thanks.

I did a full quick format. Drive is empty. Marked everything unchecked. Scanned. Still came up with a measly 16 sectors bad.

I noticed this. However, it only allows me to mark unchecked blocks good or bad blocks "unchecked." What I want to do is use this drive but also still have scanner integration flag bad drives...etc.

I have a 3TB Green drive that had 16 sectors marked as damaged. I wiped the drive but now would like to use it in the Pool. However, I still want the scanner integrated option to not put files on damaged drives, etc. The rub is that I can't mark the drive as "undamaged." Any ideas?

Thanks!

I have 24 drives currently - but a few of them have come up "damaged" with unreadable sectors. I've moved all my data from them, formatted them, and then RMA'd those still under warranty. However, I have a few 3TB drives that are marked damaged but the warranty has expired. In your experience, when should I not risk using them? Note, I will be using them in a 24 drive pool with triple duplication. In other words, how many sectors are too many sectors bad? Will using chkdsk /r (overnight because it takes so long) - make this a useable drive again? I've posted a screen shot of the SMART details for a Seagate marked as damaged.

Thanks, didn't consider the preceding 0. I'll do that.

I have about 26 drives. Currently, I have them named Disk 1 through Disk 26. However, when I sort them by the name column, it goes Disk 1, Disk 11, Disk 2, Disk 21, etc. Is there a better naming convention to use so I can sort by name? I thought using Disk A, Disk B, Disk C, but for some reason that didn't work either. I know this is OCDish...but I like to keep track of the drives and sorting by name is a good way for me.

I have a pool built - and clearly some configuration files are stored because when I uninstall and reinstall a new beta the pool reappears as previously built. However, because of some balancing issues and damaged drives, I'd like to rebuild the entire pool from scratch - then copy over the files to the new pool. How should I do this?

As the screen captures show, I am using the latest beta, have 9 pooled drives, and one of my drives (an empty 3 TB) will not take any files at all despite balancing options set to equalize. I've left it this way for two days, with balancing options set to immediate and three reboots in between. Any help would be appreciated.

Just loaded the latest x64 beta (468) and the problem above is fixed (I have 9 drives in the pool and 9 are listed) To date: pleased with your product and it's brother Scanner. Of the 20 disks in my previous Drivebender pool, I had 7 damaged disks and no way to know this unless I accessed the data. Not sure where to post this either - but I'm finding that Drivebender's way of duplication (via hidden folder with folder.duplicate.something) makes the file name often way too long to copy over. Win8.1 throws fits at a number of my nested folders deep inside these duplicates forcing me to go all the way down, find the file, and then manually copy it over. Not sure how you guys do your duplication...just throwing that out there.

Yes, they are all different disks. I have 23 individual green 3 -4 TB discs attached to two Supermicro SAS2LP controllers along with onboard SATA ports. I'll put this on my to - do list. Headed out for the weekend. So likely Monday (Tokyo time).

I've attached a screenshot. I have 8 drives in the pool, but the pool is only reporting 5. Am I doing something wrong or is this a bug?

I have my DrivePool set up for duplication x2. Just for clarification does that mean each file is then duplicated twice (i.e. three copies of the file)? If I only want one other copy of the file do I set duplication to x1? Additionally, if I've already set duplication to x2 (and it's the two additional copies as questioned above) and THEN I changed duplication to x1 - what happens? Does Drivepool delete the third copy? Thanks.