BYUSinger84
-
Posts
42 -
Joined
-
Last visited
Posts posted by BYUSinger84
-
-
Since there seems to be a problem with the 1.3 version, I tried the 2.x beta and magically everything started working again. This leads me to believe that something was very messed up with my installation of the prior version. Given that now I have lost dashboard integration, I'd like to not stay on this version. If someone from StableBit could let me know what I can do to get back to normal (with Dashboard integration) at some point that would be great.
-
Anyone know what this means and how I can re-install?
Product: StableBit DrivePool -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action DashboardLockingFixInstallCustom, location: C:\Program Files\StableBit\DrivePool\, command: C:\Windows\system32\sdbinst.exe /q "C:\Program Files\StableBit\DrivePool\DashboardLockingFix.sdb"
I've redownloaded it several times.
-
Before DrivePool was uninstalled I tried that too, didn't work or make a difference. The thing is, this server has been ROCK solid for over a year (perhaps two). Right now I JUST need to get the drive pool software working again.
-
-
At this point I think I'm royally screwed. The server will NOT let me re-install the drive pool software. I've thought about reformatting but the problem is that my backups were on the pool and so I'm not sure how a format and reinstall of the OS will affect those. They are absolutely CRITICAL that I do not lose those...I don't know what to do at this point. If anyone has ANY ideas, please, by all means.
-
This is the error I get:
Product: StableBit DrivePool -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action DashboardLockingFixInstallCustom, location: C:\Program Files\StableBit\DrivePool\, command: C:\Windows\system32\sdbinst.exe /q "C:\Program Files\StableBit\DrivePool\DashboardLockingFix.sdb"
and this:
Windows Installer installed the product. Product Name: StableBit DrivePool. Product Version: 1.3.7556. Product Language: 1033. Manufacturer: Covecube Inc.. Installation success or error status: 1603.
-
I managed to uninstall the DrivePool software, but after multiple reboots I cannot re-install. It errors out saying that the add-in cannot be installed. Help?
-
I'm starting a re-install. Unfortunately upon rebooting and going directly to uninstall the software, it's frozen...I'm going to pull my hair out. What the heck is going on? This server was working PERFECTLY find a few days ago!
-
I've rebooted the host server too. No dice. Is my installation messed up? Would re-installing help?
-
More and more I'm convinced it's not a drive issue. When it gets stuck, it's in different places each time. This time on a completely different drive.
-
Looking at the Event Viewer I get several unexpected failuers from the VDS Basic Provider. Exact message is:
Unexpected Failure. Error code: 490@01010004
-
Nothing in the error logs at all. That last error looks like it was back in March. I don't know what is going on, but now I'm worried that things are really messed up.
-
I've already rebooted, a few times. No change. Works great and then gets stuck again.
-
** Update ***
I did have a SMART warning on a drive, but after removing it, it remeasured and seemed to get stuck in the same place. That drive passes all the tests, so I don't know what's going on...based on the behavior though it seems to me that one of two things is happening:
1) That drive is actually going bad but it's just not showing up on SMART tests
or
2) There are so many small files on that drive that it's taking longer to measure. Could this be the case?
-
I'm having an issue with my server that hopefully someone here knows what I can do to resolve it. Background information:
WHS 2011 - Core 2 Quad 9400, 6 Gigs of RAM, ten hard drives most of which are 2 tb and 1 3TB. Duplication is enabled on all folders.
A few nights ago I thought I'd give StableBit's Drive Scanner a try. I'm glad I did because the next day it alerted me that one of my drives had bad sectors on it. At that time I had about 500 gigs free on the pool with the bad drive being a 2 TB drive. Because the data was all duplicated, I thought well...let's just take it out and replace it. I already had a 3 TB I had been meaning to put in anyway so this seemed like as good a time as any. I removed the damaged 2 TB drive from the pool, shut down the server, added the new drive, and then booted back up. I was able to add the 3 TB drive without any issues at all. Duplication began and once that was complete, the measuring process started (rather quickly I might add). It went through the first drive, no problems, then the second (the 3 tb), then as it got about 1/5 of the way through the 3rd drive everything starts running really slow and I can barely click on anything. Measuring got to about 15.8% when it started freezing. The dashboard freezes as well as the task manager. The last reported CPU utilization was about 25% and the RAM usage was down around 30%. Now I'm at a point where I can't even log back into the server after having logged off thinking that may help me out. My shared drives still work but it takes several minutes to open a folder. I don't even want to know what will happen if I try to open a file. Because this is running in Hyper-V (which I've been doing for years now without issue), I can still see that the CPU Usage bounces between 22-24% which indicates to me that something is going on. My question is, do I just leave it here doing it's thing for the next 24 hours? Does anyone have any idea what the deal is? I'm running the latest DrivePool 1.3 that's out at the time of this writing. Thanks for any thoughts in advance.
Server Stuck on Measuring After a Completed Re-Balance
in General
Posted
Spoke to soon. It finished the rebalance and then at the measuring again it's now completely frozen. It's obviously doing stuff because the CPU usage on the Hyper-V server is bouncing around between 70-75%. Help!