Christopher (Drashna)
-
Posts
11573 -
Joined
-
Last visited
-
Days Won
366
Posts posted by Christopher (Drashna)
-
-
sspell, there were some changes to the Remote Control code, so that could definitely be the cause.
Though, have you tried to add a "static peer" for that client?
From the block post (about 345)
Remote Control UpdatesRemote control allows you to easily connect to and manage another system running StableBit DrivePool on your LAN.
Simply select which computer you want to connect to from the drop down at the top.
List Computers
This by itself is not new, but we have 2 new remote control features in the latest build.
Reconnect to the Same Computer Used LastThis was a user feature request and is now implemented in the latest build.
If you were connected to a remote computer when you closed the UI, the next time that you open the UI it will automatically connect to that computer (provided that it’s still online).
It’s a very small change, but actually makes a big difference if you only have one DrivePool server and tend to manage it from many clients. We now save you 2 clicks every time you start the UI.
Static PeersBy default StableBit DrivePool uses multicast UDP packets to discover other peers to connect to. Sometimes, due to your network configuration, multicast packets can be dropped by your router.
Now in the latest build the Remote Control system can connect to static peers specified by you.
The installer now places a new XML file in:
C:\Program Files\StableBit\DrivePool\RemoteControl.default.xmlYou can edit it and define your own DrivePool peers using IP addresses, Windows computer names or domains. For further instructions just open the XML file in a text editor like notepad.
-
DrivePool 2.x supports WS2012E officially. But it is still in beta at the moment.
And I'm not sure you can do an in place upgrade with Server 2012 Essentials. (I'd love to be proven wrong, but I'm pretty sure about this).
Though, what are you running currently?
And worst case here, the pool is "portable". Meaning that you could install to a new HDD, install DrivePool and reconnect the pooled drives and it will read the pool right away.
-
I chatted with alex a bit about this, and:
It is possible that the firmware on the drive is not reporting Advanced Format properly.
On that DirectIO test app, click on the "..." button next to "Identify". Look for "Logical sectors / physical". That is what we look for when reporting advanced format or not. If it's 1 (0x4000), then it's not advanced format (or just not reporting it). If it's 8 (0x5000, or 0x6000) then it means it's reporting advanced format.
-
Ah, okay.
And yeah, it's grabbing the info from scanner, but not it's settings.
-
And just to make sure, it says it's reporting the sector size as 512, and "not reporting as advanced format"?
-
Yes, this was added a while ago. Make sure you've updated StableBit Scanner.
And the setting, open the UI (either the dashboard on the WHS version, or the stand alone app). The "Start/Stop/Automatic" toolbar at the top, click the arrow next to the "Scanner Settings" box, and select "All Settings". Then open the "Heat" tab. You'll be able to choose which setting from there.
-
Are you using the "Disk Details" section to determine this?
-
Sorry if I wasn't clear.
For the situation you described, there was no real need to change the drive letter. But there is absolutely no issue with changing the letter, if you want to do so.
And yes, it's not important how the drives are connected, or what letters they have. The disks are identified by the PoolPart folder, and some very hidden metadata (it is done this way, specifically because it is much more resilient to change, and very unlikely to break to the pool)
-
Glad to hear,
If you have any other issues, don't hesitate to contact us.
Though, hopefully, you won't have any other issues.
-
Glad to hear.
-
Does resetting the DrivePool settings help?
-
Try resetting the DrivePool settings, and see if that fixes the issue.
-
There is no need to change the drive letter of the pool, especially if you're moving to a new install. And the "WSS Troubleshooter" utility will map the shared folders to the "new" pool's drive letter without issue.
I think that answers everything you asked/wanted to know. If it doesn't please ask.
-
You can switch between the versions interchangeably.
It will immediately recognize the existing pool and "rebuild" it. No need to do anything to the disks. And you could move the pool to a different system and it will be recognized as soon as you install and activate DrivePool.
-
I'm goign to have to double check DrivePool, but I swear it would..... I could be wrong.... it's be one of those sorts of weeks.
As for the mount path, we try to be as "hands off" as we can with your drives. That way, you can use them however you choose.
If you really do want the drives mounted to a path, head to http://stablebit.com/Contact and submit a feature request.
Otherwise, you could definitely do it manually (in fact, this is what I do, it allows for the system to be very organized, and the drives to be completely accessible).
As for migrating....
http://wiki.covecube.com/StableBit_DrivePool_Q5463715
That's a guide on how to do it, without moving all your data around. Would take less than 30 minutes to do all of it (give or take), instead of days...
-
Instead of removing the drive letters completely, I'd recommend mounted the drives to NTFS folders, that way you can easily run chkdsk on the drives if/when you need to.
http://wiki.covecube.com/StableBit_DrivePool_Q4822624
This is basically what you want, but it is a bit more manual... (but simple)
As for the Add disk, if it's not initialized or formatted, DrivePool will do that automatically, actually. And the Virtual Disk Service assigns a new drive letter automatically.
-
That definitely sounds like an issue with the drivers for the USB3 port, if I had to make a guess.
There should be details in the event viewer. If not, then could you upload the crashdump?
There is a widget at the bottom of this page to upload the dump (zip it first though):
-
Once the pool is reactivated.... grab the "WSS Troubleshooter" utility, and run the "Rebuild DrivePool shares" option, and that will fix your issue with the server folders:
-
Do you mean you want to break the FlexRAID array? Or add the array to the DrivePool?
Could you open a ticket at "http://stablebit.com/Contact/" and attach the ErrorReports?
-
StorLib Virtual Storage is the FlexRAID volume, IIRC, actually.
And the "file system damaged" message is from a "chkdsk" pass. I'm not sure if the flexRAID volume is compatible with chkdsk, so that may be the cause here. You can disable the file system check on this volume, if you want. Right click on the drive and select "Disk Settings" and check the "never scan file system automatically"
-
What version of DrivePool are you using?
Also, have you reinstalled or otherwise migrated the pool from another "system"?
-
Lee, that is odd that it would be set to 0MBs. But glad you found that and fixed it.
-
Sauberli,
I'm glad you found the solution.
But just FYI, it does reset all the settings (including balancer settings).
-
Saiyan,
Thanks for going to all the trouble to track down the issue.
DrivePool does use the uniqueID to track the disk, IIRC.
I'm flagging this for alex, to let him know about it. (though, yes this could be an issue with VMPlayer, but I'm not sure about that).
Upgrading to WSE 2012
in General
Posted
yeah there definitely isn't an upgrade path from 2011.
you'd basically have to install over it, and move the HDDs over. But once you had DrivePool installed, it will immediately recognize the "old" pool.