I have rebooted my server (S2008 R2) and the message in the Drivepool window is :"Drivepool starting..." it sits there for a very long time (+20mins) and never loads.
I tried to restart the service, no luck. I have tried to repair the install... no luck. I have uninstalled it and now I am trying to install the beta release and is it sitting at about 25% and has been for about 30mins..
Am I missing something? All drives are fine and the server is running fine. Just not Drivepool
I have attached a screenshot of the log info...
Hi all. I'm testing out a setup under Server 2016 utilizing Drivepool and SnapRAID. I am using mount points to folders. I did not change anything in the snapraid conf file for hidden files:
# Excludes hidden files and directories (uncomment to enable). #nohidden # Defines files and directories to exclude # Remember that all the paths are relative at the mount points # Format: "exclude FILE" # Format: "exclude DIR\" # Format: "exclude \PATH\FILE" # Format: "exclude \PATH\DIR\" exclude *.unrecoverable exclude Thumbs.db exclude \$RECYCLE.BIN exclude \System Volume Information exclude \Program Files\ exclude \Program Files (x86)\ exclude \Windows\
When running snapraid sync it outputs that it is ignoring the covefs folder - WARNING! Ignoring special 'system-directory' file 'C:/drives/array1disk2/PoolPart.23601e15-9e9c-49fa-91be-31b89e726079/.covefs'
Is it important to include this folder? I'm not sure why it is excluding it in the first place since nohidden is commented out. But my main question is if covefs should be included. Thanks.
Setup is DrivePool + SnapRAID under Server 2016.
I've been testing in preparation for actual setup. I have two drive set up in DrivePool with a File Placement setting so that data placed in a particular folder is preferentially placed on a specific drive. To simulate a lost drive, I take it offline from Disk Management first, then DrivePool says a drive is gone so I remove it there (have to do it this way so DrivePool doesn't move files around when removing a drive). Then I add a new drive and remount it to a folder in Disk Management. The new drive shows up and I added it DrivePool. Then after tidying up snapraid.conf I run snapraid fix to restore the bad drive that was removed. If I head back to DrivePool I have to set up File Placement rules again. It sounds like this is what should normally happen, but is there any reason to have some way to save or restore File Placement settings?
I'm using the latest beta (2.2.0.802) and I've discovered a bit of an issue when running pools of pools. My current structure is:
Pool A: 2x CloudDrives
Pool B: 21x Phyiscal Disks
Pool C: Pool A + Pool B
Because I have Pools of Pools, there are 2 PoolPart hidden folders, each consisting of what looks like 45 characters. So for both of these folders we're at 90 characters of the 255 size limit before we even start with any other files/folders. Most of my files are OK but I'm still running into many that are hitting this limit and causing all kinds of problems.
This is less of an issue and more of a discussion if this is a feature that will be released in the future. Do I have any options for reducing the size of the PoolPart folder names?
Drashna, can you explain how I can tweak the setting that Drivepool uses before they mark a disk as "missing?"
I have a few Seagate disks that seemingly take forever to spin up and after a very short while, then Drivepool marks them as missing which of course puts the pool in read only mode.
The only way I can get them live is to unplug the SAS/SATA cable while they've been powered up for a while, then plug it back in. Assuming there's activity, I don't have a problem, but I suspect once they spin down and Drivepool tries to write data again and they don't respond fast enough, then missing!
I remember a tweak somewhere that can make this much longer before marked as missing.
Additionally, do you know of a tweak - perhaps via scanner that doesn't allow these troublesome drives to spin down?
I have a mysql database set to be duplicated real time but I keep getting warnings that \ServerFiles\MySQL\user.MYD File is in use.
I thought drivepool supported duplication in real time for files in use? I am on the current beta 2.2.0.798
So, I'm about a month into my DrivePool based file server, and it is going well :-)
As discussed, it is an old i7 HP with an 250G SSD and eight drives connected via USB.
Some questions:
1. I'm struggling to have the SSD used as a write cache. In ui1.png, the red arrows imply that new files will go to the SSD/C: But when I copy files across the network to the pool drive, they go directly to one of the USB drives (i.e. H:\ in the image)
2. It reports Unduplicated of 1TB. That is higher than unexpected on a pool set to full duplication. What should I check?
(See ui2.png. Recycle Bin is empty)
3. Not sure why it reports 1.5TB unusable for duplication, but this only started after I added an 8TB drive a few days ago so it probably needs a few more balancing runs (originally reported 4TB unusable)
4. The raw size of a single copy of all my data would be less than 7TB. Is there any easy way to ensure there is at least one copy of every file on my 8TB hdd (would this be a file placement rule to put everything on just that hard drive?)
5. I'm using Beta 812, because I was having unresponsive UI issues in an older beta. CPU usage is surprisingly high with the DrivePool UI. >50% on my the file server. 28% on my whizbang dev system (connected remotely).
Hi,
I have installed the 822 beta version, however, after restarting my machine DrivePool displays the following:
The background server failed to start, try to restart the computer.
I have restarted twice with no success. The EventLog displays the following error:
Hi,
DP 2.2.0.651
Win 7 SP1 x64
Scenario;
I have a pool with two 4TB drives and 2x duplication. The drives were nearly full (~213GB free on each) so I was going to replace both with larger 10TB drives. I shut down the computer, removed one of the drives and replaced it with an empty unformatted 10TB drive. I turned the computer back on and created and formatted a partition. I removed the missing drive from the pool in DP and added the new empty drive. DP started balancing. At the end of the process a half day or so later, the 10TB drive is reporting as expected in DP, but the 4TB drive I did not remove and the one being balanced from is now reporting 6.86 TB of Duplicated files and 213GB free. There is something in parens after the duplicated space amount but it is clipped by the window boundaries.
If I mount both drives and look at them natively The total number of bytes, files, and folders match, so I believe all is ok "under the covers", but for some reason DP is reporting double the amount of duplicated space for the 4TB drive an amount larger than the actual physical drive).
I tried rebooting but that did not correct the problem.
Screen shots attached.
I did not have an extra free internal drive bay to have both the old and new drive online at the same time. I didn't want to do this externally over USB or eSATA.
As the first 10TB drive seems to have received a good copy, and as I will save the 4TB drives for a while as backup, I am going to go ahead and replace the other 4TB drive with a 10TB and have the files balanced back in the opposite direction. Just wanted to report this as I couldn't see something like it in a quick forum search. It might all be explained by the part of the message cut off in parens.
Thanks,
David
With larger pools the difference between the balance ratio of 99% and 100% actually equates to a large amount of data. In my case 664GB
This leads to the pool not balancing for potentially a long period and leaves the ssd drives with significantly reduced space - so a new copy of a large amount of data to the pool can lead to issues.
So can we have a more granular control of the % at the top end - can't think anybody uses anything less than 90-95% on the balance ratio - so 0% to 100% is a bit overkill
Now both my pools are showing "Duplication Inconsistent" message in the UI.
I think that was true on both the 2.2.0.651 I was running before I upgraded for this thread;
as well as 2.2.0.823 now. The pool automatically re-measured when I rebooted post-install.
The drive sizes look ok now, but both (even the pool I did not work on) show duplication inconsistent. They showed green/ok before I replaced the first drive under 2.2.0.651. DI message has not been an issue for me before.
I ran chkdsk on all drives in both pools and no errors were found.
I ran the troubleshooter program and sent you all the data.
I was looking for a solution to get past windows' 26 letter limitation for shortcut then i read about dfs.
Any known problem using both dfs and drivepool?
I read this and was wondered about the bug status now
http://forum.covecube.com/discussion/comment/888/
Also..anyone know if dfs the best way if we want to work with kodi and more than 26 drive letters?
I know this is a very minor thing, however for pools that I am basically using as RAID 1, where the data is cloned between the two drives, is it possible to have the drive size and storage usage reflect this?
i.e. for a 2x 3TB pool, it currently shows in Windows as "3.16TB free of 5.45TB", however it would make more sense if these values were halved as this is the usable space.
Sorry if the wording isn't great
Thanks!
Hi,
Is there any way of getting API access to at least the balancer API ?
I am thinking of 2 examples I'd like to code;
1. Snapraid trigger
As soon as a Balancing activity has ended, start snapraid check
2. File placement "list"
As soon as a Balancing activity has ended, create a folder á la https://blogs.dropbox.com/business/2016/04/announcing-project-infinite/ symlinking to the "real" folder.
Coincidently, this removes the need to rebuild the driver as you stated in another thread.
This can also mean that a tiered storage can be achieved by moving less-acessed files to slow storage, and often-accessed files to SSDs.
Thanks for checking in 
Anyone find out if the REFS driver still causes a Memleak?
I'm asking because I plan on getting DrivePool and using it with SnapRAID so I get data protection. One problem I have though: Does DrivePool write data across disks like RAID-0, or does it just fill up each disk in turn? Thanks!
DrivePool is telling me I have 753GB of files that cannot be moved because it can't satisfy the file placement rules.
For the life of me I can't find what the conflict is, I didn't change anything...
I added a new drive and set up some rules for it - those rules worked because I have the data I wanted on that new drive.
Is there a way to see exactly what the conflict is?
A way to see which files this message is referring to? Or which rules this is referring to?
It would make it a lot easier to get this sorted out...
In a log file somewhere?
Thanks.
In Windows Explorer I want to see the OS drive and my Pool only, not all the drives comprising the pool.
I went to delete the drive letters for those drives, but it warns me some programs may not work.
If I do this will DrivePool still see the drives, or will it cause issues?
I didn't want to try it and mess things up.
I don't know how to apply the correct terminology for this issue, so I'm not certain if it has been discussed before or not. Please forgive me if it has. I have looked for almost an hour and I can't find anything relevant.
Please refer to my Signature for my System Description. It is up to date.
About 80-85% of my 35TB Pool is duplicated, but there are some files that just don't warrant the space allocation. That doesn't mean I don't care if those files are lost however, the're just not critical files and I'm trying to be somewhat reasonable. A few of my Drives are starting to get some age on them, like 5+ years. HD Sentinel and Scanner are not reporting any problems at all, but I would like to minimize my risk with these drives if I can. What I would like to do is tell DrivePool to not put any NON-Duplicated files on drives I so designate.
Is this possible? If so, how would I do it. I have looked DP over and I can't see how.
Thanks for your help,
-Gary
