Christopher (Drashna)
-
Posts
11572 -
Joined
-
Last visited
-
Days Won
366
Posts posted by Christopher (Drashna)
-
-
Sorry, I meant that you should disable shadow copies on the Pool drive, not the drives in the pool.
Worst case, you'd have to take ownership of the folder, change the permissions, and then delete the file (for the future, if this happens again).
But if it's resolved, that is good.
-
That really depends more on how FlexRAID is implemented.
Installing it in a VM, it seems that FlexRAID mounts the drives to a folder path, but uses the drives "normally" otherwise.
So, DrivePool and Scanner should work great with FlexRAID. Both in monitoring SMART data, and in scanning the drives for errors.
I didn't do any testing out than cursory to see if it works. Just enough to see if "all the moving parts work right", and they appear to do so.
-
This is expected. DrivePool doesn't support Shadow Copies (aka "Previous Versions"). Or rather, Shadow Copies only supports actual volumes (not virtual disks, like what we use).
The reason that you did not see this on the Client Computer Backups is that it isn't a share and therefore doesn't check for this feature. All of the shares do, though.
But basically, this is expected, and nothing to worry about.
-
Otagolad,
It sounds like the server shut down unexpectedly. If that is the case, I would recommend following that up. But it could definitely cause this issue.
As for this folder, it would be on the pooled drive. Delete it there. Better yet, right click on the Pooled drive, select "Properties", open the "Shadow Copies" page, find and select the pooled drive's letter, and hit the "Disable" button. It will ask if you want to delete the shadow copies, hit "OK", and it should fix the issue.
-
Worst case, you could pull all the HDDs and just move them over. DrivePool should recognize the pooled drives, and "rebuild" the pool. And if you don't reattach all of the disks (like you don't move over the "bad" disks), you will have to remove them as it will mark them as "missing". Once done, you could reattach them, and copy the contents of the hidden "PoolPart.xxxx" folder into the pool.
This would be the quickest method.
-
It looks like you may have files in the recycle bin here.
Check that and empty it.
Worst case, you can format the drives while they are still in the pool. It will give you errors, as you will have missing disks. but that should do what you want. No need to even uninstall DrivePool.
-
Darkeuh,
Could you try resetting the settings for DrivePool?
instructions here:
http://wiki.covecube.com/StableBit_DrivePool_Q2299585B
Regards
-
If it makes you feel any better, I didn't notice that typo either, til you mentioned it.
Glad you got it all sorted out.
-
Okay, I just wanted to make sure.
And I'm assuming you mean the "DPI" setting. That could definitely make it hard to find.
-
Not a problem. There are a number of nice features that are kind of hidden (may be a good idea to really look at those balancers too, and check out the ones on the plugins page too http://stablebit.com/DrivePool/Plugins)
And no files should be lost in the removal. Worst case, they will remain in the hidden "PoolPart.xxxx" folder, for you to recover/move at your convenience.
-
Nope, definitely not.
If it was, then the "Skip duplicated files" option would allow you to remove it from the pool without issue.
And PerfectDisk shouldn't have caused any issues. I run it on my server as well, and I've not had issues removing disks. Though, you can stop any ongoing scan, if it's occuring.
Also, you can use the "file placement limiter" balancer, and uncheck both "Duplicated" and "Unduplicated" check boxes and the pool will try moving all the files off that disk. This would make it easier to remove the pool (or at least safer to just pull the disk and then remove it from the pool).
However, the reason I mentioned that log file is that it will log what files it errored out on. And there may be a damaged file that is causing it to hang on.
-
The License management stuff should be in the actually settings of the dashboard, just click that, and there should be a "DrivePool" section, and in that, a "Manage License" link.
However, I agree, the 2.0 UI is a lot better, and a lot cleaner. Thankfully, it works with WHS2011 as well.
Worst case for the license "release", is you can contact us and we can do it. (http://stablebit.com/Contact).
Regards
-
Logbit, copy the config file to your desktop, edit it there, and then copy it back.
Some times it does this. I believe it's an NTFS permission/security related issue, (as those can act funny some times).
If that still doesn't work, I'll see about uploading a copy of the modified file.
-
There should be a "force drive removal" option. This will skip any file that errors out (which is likely the issue). And then proceed to remove the drive from the pool.
You will retain files on the drive using this method though. You can access those files in the "PoolPart.xxxx" folder (may be hidden).
Worst case here, physically remove the drive, and then remove it from the pool. Then copy the contents of said "PoolPart.xxxx" folder back into the pool (it should mirror how the pool is laid out).
Also, you can check "C:\ProgramData\StableBit DrivePool\Service\Logs\Service\" for the logs and see what file(s) it is erroring out on.
Regards
-
When you remove the drive, it sets the pool as "read only", so you can't write to it. But you can still access the pool during this time.
However, because it is read only, any thing that relies on altering data will fail, such as client backups. But media streaming should work fine during this time. However, because one or more drives maybe written to during the removal process, it may make the system laggy.
If you want though, you could use the "File Placement Limiter" balancer to move the data off the drive in question, and once that's done, remove that drive from the pool immediately. And since there should be no pooled data after it's "balanced" the data, it should take minutes (if not seconds) to remove it from the pool.
-
Normal: That error could have been caused by the bad drive, or a crash. If you wanted to post log files (ideally to "http://stablebit.com/Contact"), I could look through them and see what is going on (or you could do so yourself, if you want). The directory in question is "C:\ProgramData\StableBit DrivePool\Service\Logs\Service".
And Shane is right, you should remove the bad drives immediately, or potentially risk data loss/corruption. Just add the other drives to the pool, and remove the affected drive. It will migrate the data for you. There is also an option to basically ignore duplicated files which makes the removal faster, but puts your data more at risk (as there will only be one copy in the pool.
Once the drive is removed, definitely check to see if it's under warranty still, so you can RMA it and get a working drive.
Regards
-
Sometimes the config file does that. Usually copying it to the desktop (or elsewhere) and back will help.
-
-
When you remove a disk from the pool, part of the removal process is to move all the files off of the disks. You can skip "duplicated" files which may be a good idea!
Given that you don't have the space to remove the drives *and* maintain duplication... That would be the bigger issue here.
If you have the money, opt for the "advanced replacement". It requires a credit card (or debit card), and they put a hold on the card equal to the amount they charge for the HDD. Then they send one out to you immediately and give you a window of time to return the bad drive. Once they get it back, they remove the hold from your card. Otherwise, if you take too long, the charge goes through.
I'd recommend this method to you, because you can get the two new drives, add them to the pool also, and then remove the bad drives from the pool.
Otherwise, you'll want to use the "skip duplicate files" option when you remove the disks, and disable duplication temporarily. Which isn't optimal at all.
-
Randomrage: I just want to cover all the bases.
As for the drive, I run Server 2012 Essentials and *all* of my pooled drives are 3TBs (all seagate), so that's definitely not the issue. I'd be more inclined to blame the USB hardware here (either the controller, or the enclosure itself,). Especially if it's USB3. Some of the chipsets are still very flaky as of yet (as USB3 is very new still).
But if you remove the external, and *still* have issues with the backups, then please do that log collection (linked above), as that is a very detailed log of what is happening.
However, if the issue goes away when that external HDD does, well, you know what the issue was.
-
Are you using the "/r" switch when running chkdsk? (you said you're on WS2012? have you tried "chkdsk x: /r /scan"?)
Also, have you tried installing StableBit Scanner? It grabs smart data, and does a file/surface scan.
And have you scanned any of the other drives?
And if so, have you tried resetting the client backup database?
Create a folder in that directory, move the backups to that folder, and restart the service. This keeps your old backups in case they are fine, and lets you create a new backup database, in case the old one is actually corrupt (it is possible). If that works fine, then that's the issue.
If it still has the issue, then it may be some interaction with DrivePool. And if that is the case, then do this:
http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection
Regards
-
yes, it should detect the client backup database. It may (most likely rather) will put all the disks in the "Archive" category, but they should be available. Just make sure you have the server all updated before doing this to avoid issues.
As for the disk passthrough, that is entirely possible. So no more issues after using the host?
-
... With my dying breath, it will be in there one way or another.
Alex has said that he is considering it. But to be blunt, he's been very busy with fixing bugs, and trying to get v2 to a "stable" build, so this isn't a priority right now. In the future possibly, but not at the moment.
But yes, I would absolutely love to see the dashboard integration back as well. And Alex knows how I feel about this.
-
And thank you both for the feedback.
WHS 2011 to WS2012E
in General
Posted
Philmatic is correct.
StableBit DrivePool 2.x will recognize the "old" drive pool and rebuild it. All your data should then be intact (assuming all the drives are present), and read to go.
As for upgrading, the license isn't for a specific version of DrivePool. It's for the product itself. No fee or anything to upgrade. But as Philmatic suggested, since you didn't release the license on the old system, you will need to contact us to get it reset. head to http://stablebit.com/Contact/, and ideally use the email that you used to purcahse the license for DrivePool with. And then we will see about resetting it for you.
Also, I'd recommend getting the "WSS Troubleshooter" utility. Use it to both "Reset NTFS permissions on the pool" option and "Rebuild DrivePool shares" option. That way, it wipes the permissions clean (so there should be no issues), and the second option will add the shared folders back to the dashboard, so you don't have to set that up manually, one folder at a time.
http://wiki.covecube.com/StableBit_DrivePool_Utilities