Jump to content

Christopher (Drashna)

Administrators
  • Posts

    11549
  • Joined

  • Last visited

  • Days Won

    365

Everything posted by Christopher (Drashna)

  1. Ah, okay. And yeah, it's grabbing the info from scanner, but not it's settings.
  2. And just to make sure, it says it's reporting the sector size as 512, and "not reporting as advanced format"?
  3. 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.
  4. Are you using the "Disk Details" section to determine this?
  5. 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)
  6. Glad to hear, If you have any other issues, don't hesitate to contact us. Though, hopefully, you won't have any other issues.
  7. Does resetting the DrivePool settings help? http://wiki.covecube.com/StableBit_DrivePool_Q2299585B
  8. Try resetting the DrivePool settings, and see if that fixes the issue. http://wiki.covecube.com/StableBit_DrivePool_Q2299585B
  9. 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.
  10. 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.
  11. 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...
  12. 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.
  13. 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): http://wiki.covecube.com/StableBit_DrivePool_System_Crashes
  14. 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: http://wiki.covecube.com/StableBit_DrivePool_Utilities
  15. 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? StableBit DrivePool 1.x Error Reports StableBit DrivePool 2.x Error Reports
  16. 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"
  17. What version of DrivePool are you using? Also, have you reinstalled or otherwise migrated the pool from another "system"?
  18. Lee, that is odd that it would be set to 0MBs. But glad you found that and fixed it.
  19. Sauberli, I'm glad you found the solution. But just FYI, it does reset all the settings (including balancer settings).
  20. 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).
  21. First of all, very nice find. It would seem that this UPS doesn't have a USB connection for management. So you may need to make sure you have a serial/com port on the server/computer to be able to interface with it. And you'd definitely want to install the software It shouldn't change the consumption much. It will consume a bit more, but not drastically. (like maybe, *maybe* 10% more). There are devices to monitor the consumption, if you are really concerned (and the software should let you know how much power is being consumed through the UPS, I believe). Otherwise, just make sure you configure the shutdown/standby functionality. And that you test it. It's no good if the battery only lasts 30 seconds....
  22. Thanks. I've forwarded to Alex, and I'm sure he'll add it to his to-do list.
  23. otispresley, Thanks for the clarification. I'm not as familiar with ESXi, as I'm a hyper-V user.
  24. You do mean other than the drive must be a certain percent free to defragment it? And a number of other operations (such as backups) need a certain amount of free space (for backups, for the snapshot). Those are both good reasons... Also, there is the persistent rumor/report that NTFS suffers performance issues when ~90% full or more (I'm not sure about this one... though I have seen a lot more issues when the drive has less than 1GB free...) Otherwise, you are pretty much spot on.
×
×
  • Create New...