Jump to content
Covecube Inc.

Christopher (Drashna)

Administrators
  • Content Count

    10667
  • Joined

  • Last visited

  • Days Won

    292

Christopher (Drashna) last won the day on September 9

Christopher (Drashna) had the most liked content!

1 Follower

About Christopher (Drashna)

  • Rank
    Customer and Technical Support
  • Birthday 06/25/1983

Contact Methods

  • MSN
    drashna@live.com
  • Website URL
    https://drashna.net/blog/
  • Jabber
    christopher@covecube.com
  • Skype
    drashnajaelre

Profile Information

  • Gender
    Male
  • Location
    San Diego, CA, USA

Recent Profile Visitors

5220 profile views
  1. You can lose any number of drives, and any remaining drives will still keep their data in the pool. However, any data that is just on the failed drives will no longer be in the pool. For the most part, it's straight pass through, basically. So you should see performance equal to the underlying disk's performance. Well, it uses normal NTFS volumes, and places the files in hidden "PoolPart.xxxx" folders. As for accessing over the network, you can use the HaneWin NFS Server. Well, as long as we're open, we'll support the software. However, if we closed our doors, the plan basically would be to remove the licensing components from the software and release them. That way, you could use the and there would be no phoning home. Also, even without a license, our software will still work. This applies to the software right now, as is. The pool would go into a semi-read only mode, but you'd still be able to read data from the pool, without any issues. Either. As above, the files are stored in hidden PoolPart folders, so you could access them that way. But ideally, you'd want/need to install StableBit DrivePool. Once it's installed, it will look for pooled drives and automatically rebuild the pool with the available drives. This depends on what you mean. Linux supports Samba/SMB/CIFS (windows file shares), and there are some NFS servers that would work well with linux. So over the network, no issues, at all. You mean like a system case? If so, a rackmount server chassis will probably be your best bet, actually.
  2. First, I'm sorry to hear about that, as that is never a pleasant experience. Try restarting the service. If that doesn't help, check to see if the files show up, and specifically, PoolPart.xxxx folders.
  3. Have you enabled the "do not query more often than" setting in the SMART tab?
  4. Could you open a ticket at https://stablebit.com/Contact
  5. You may want the "CoveFs_SynchronizeDirectoryTimes" Setting. http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings#Editing
  6. Do you know what version of StableBit Scanner that you're using, and how the drives are hooked up?
  7. @mayorville It won't necessarily scan right away. You can start a scan by clicking on the "Start". If that doesn't work, double click on one of the drives, and click on the "Start" for that drive specifically.
  8. Unfortunately, no, there really won't be an update on this. Google Team drive is limited on the number of files that can be hosted. And that limits the size. That would be ~10TB normally, or 5TB if duplication is enabled for the provider. Additionally, because it's a shared drive, it's a potential issue too.
  9. No, it doesn't. Well, mostly. If the data is duplicated, and you're reading the data, it will prefer internal over external drives for the reads. But as for what ports that they're on, that doesn't matter. You can move them around with no ill effect.
  10. I'm glad to hear that!
  11. Unfortunately, there isn't a way to get that to happen. The scanning is a slow process that can take roughly 5 hours per TB. That said, there are a few things that may help. Try disabling the throttling settings.: https://stablebit.com/Support/Scanner/2.X/Manual?Section=Throttling Also, there is an advanced setting that will allow StableBit Scanner to scan multiple drives on the same controller at the same time. http://wiki.covecube.com/StableBit_Scanner_Advanced_Settings#Advanced_Settings It's the "maximum concurrent" setting. Try setting that to 0.
  12. I think we pulled it real quick due to an issue, and have a fixed version out. Is this still an issue?
  13. Check both the share permissions, and the NTFS permissions. Also, do you mind posting the name of the folder?
  14. That's really odd, that that happened! That said, I would recommend remeasuring just in case.
  15. Sorry for the delay. Yeah, this is completely harmless and an artifact of how the pool driver works. Basically we don't block LBA address requests, but we do return errors for them. LBA requests are actually requests for a block of data on the drive, rather than a file request.
×
×
  • Create New...