Jump to content

Shane

Moderators
  • Posts

    724
  • Joined

  • Last visited

  • Days Won

    62

Everything posted by Shane

  1. I'm... not sure? Having checked my own installs I still get the normal Notification settings but it seems like they might also be stuck in an expired trial of Cloud plus. But it wouldn't feel right that linking to the Cloud would reduce the individual functionality of the desktop app either. @Christopher (Drashna) is Bazzu85's issue "functioning as designed" or "not as planned"?
  2. Try re-adding your email address in the app and using the Test button?
  3. I was using Chrome when I checked. Interesting, Chrome is still good but I get your page when I try Firefox instead. Doing some digging... at least on mine, looks like ad blocking is tripping things up. Specifically, stablebit.cloud makes a call to https://stablebit.cloud/lib/sentry/bundle.min.js with a build number and "/sentry/bundle.min.js" is denied by default by uBlock origin (due to that script being in the EasyPrivacy filter list that ublock origin makes use of); permitting that script allows the page to load. stablebit.cloud also makes a call to q.stripe.com/csp-report that uBlock origin denies by default but stablebit.cloud still completes loading. So if you wish to access the site you could try disabling ad-blocking for stablebit.cloud or, if you're using ublock origin, you could use advanced filtering to specifically allow just 1st-party scripts or that script call in particular on stablebit.cloud. Pinging @Christopher (Drashna) regarding this.
  4. Just tried, seems to be working here? You can also check https://status.stablebit.cloud/ if it happens again for you to see whether the problem is at StableBit's end.
  5. Note that if "File placement rules respect real-time file placement limits set by the balancing plug-ins" is not checked then any file that triggers a File Placement rule - even if the rule just says "this can go to any disk" - will be ignored by OFP. Given your 2nd edit however, it looks like Ordered File Placement isn't working properly. I'd recommend opening a support ticket with StableBit.
  6. Something to try #1: Ensure that Balance Immediately is selected, Automatic Balancing - Triggers is set to 100% / 1 GB and enable only the Duplication Space Optimizer balancer (plus Scanner is okay if you've got that). Re-balance; DSO having complete priority should get DP back on track and you can then return to your regular preferences. Something to try #2: In the GUI, from the Cog icon go to Troubleshooting then Reset all settings... and then set your preferred configuration and try #1 again. If that doesn't work, it's possible the balancing metadata for the pool might have somehow borked. At this point I'd recommend opening a support ticket with StableBit so that they can investigate/fix the problem. Alternatively, you could try replacing the pool. The following instructions presume that (1) you have a current backup in case something goes (more) wrong, (2) you don't have or don't want to use spare drives to copy your data from the problem pool to a new pool, and (3) you are not using any symlinks, junctions or third-party system-attribute content to/in the pool (if you are, you will have to resolve those appropriately): If disabled, enable hidden (but not system) folders viewing in Windows. Stop the DrivePool service and close any open programs/files in the pool. Rename the hidden poolpart.uidstring folder on each drive in the pool by prepending "old" or similar (e.g. rename "poolpart.1234" to "oldpoolpart.1234"). Start the DrivePool service. In the GUI, the drives should all show up as missing. Remove the "missing" drives until the pool is gone. Create a new replacement pool with those drives. Set up your preferred balancing, placement, duplication, etc. Stop the DrivePool service again. On each drive, move the contents of the xpoolpart folder to the newly created poolpart folder (do not move system folders - if it asks, skip them). Start the DrivePool service again. In the GUI, Manage Pool -> Re-measure and Cog Icon -> Recheck Duplication. Once you're happy that everything's showing up in the "new" pool, delete the "oldpoolpart" folders (do NOT delete the new "poolpart" folders) and optionally re-disable the hidden folders viewing in Windows. If you do that and it still didn't work, please lodge a support ticket with StableBit as something is messed up.
  7. Checking the OFP plugin's notes, you've got the right settings. Has your DrivePool version updated between when OFP was working and when you noticed it isn't anymore?
  8. If you've got a catch-all (i.e. "*") in your File Placement rules, remove that? Regarding SnapRAID, I don't recommend adding parity drives to a pool. Parity drives should be dedicated to providing parity.
  9. There might be something else involved. If you open a Command Prompt as an Administrator, you can use dpcmd list-open-files with the appropriate parameters (e.g. "dpcmd list-open-files *") to see what is keeping it from being ejected. Open directories aren't usually an issue but any open files/streams can prevent ejecting. Note that this will only show files open inside the pool, not anything else that might be on the docked drives outside the pool. You could also try editing the "C:\ProgramData\StableBit DrivePool\Service\Settings.json" file to change the Override from null to true for "CoveFs_IsDiskRemovable" and reboot to see if that helps, but be aware this will affect all pools.
  10. Yeah, to keep both read and write you'd have to go with RAID 1 (software or hardware based) to mirror a pair of drives. If your choice of RAID doesn't come with its own remote notifications but still allows per-drive SMART (e.g. Windows Pro software raid) you may wish to use StableBit's Scanner software so that if either drive dies or starts going bad it can send an email, app notification or SMS to let you/whoever know.
  11. Just delete the old folders and remove the letters. Don't format the drives. DrivePool stores a pool's files inside a hidden "PoolPart.UID" folder (where each UID is a unique, dashed alphanumeric string) in each drive that's part of the pool, so formatting any such drive would erase that drive's hidden folder and any data in it.
  12. No idea, sorry. If you're happy with just using the All-In-One plugin then I'd say keep going with it, otherwise you could try lodging a support ticket with StableBit regarding the weirdness with the SSD Optimizer plug in.
  13. DrivePool works by creating hidden poolpart folders on one or more drives (e.g. in your case C and D) and pooling them as a single virtual drive (e.g. P), so if the DB needs to be kept on literally C drive you wouldn't be able to directly go "hey DrivePool duplicate C:\PointOfSale to D:\PointOfSale". You could however create a pool drive P from drives C and D, move the database to P:\PointOfSale and then in Windows create a directory symlink so the database still seems to be in C:\PointOfSale as far as your software is concerned. Potential gotchas: If you have to use a symlink because your database has to be in C:\something, some really old software doesn't work with symlinks. It's rare but something to test. You'll need to use DrivePool's real-time duplication and not its scheduled-time duplication as the latter won't duplicate in-use files, but I gather the former is what you're wanting anyway. Personally I would also make sure read striping is disabled, some old software doesn't play nice with that and I wouldn't risk it in a production environment without extensive testing first, but disabling it is as easy as unticking it in the Manage Pool -> Performance menu (if it's ticked in the first place). Note that DrivePool's response to "a drive that's part of the pool has failed" is for the affected pool to go read-only until the failed drive is replaced or at least removed , though that's easy to do. You might also want to look at backup software that supports VSS - i.e. able to take backups of files, folders or drives even when in use. Note that while VSS is not compatible with DrivePool directly it does work on poolpart folders, so if a 2x duplicated pool consisted of 2 poolpart drives then you'd only need to backup one of the poolparts.
  14. The default settings should be emptying the files to the drive with the most free space (in bytes, not percentage) at any given time. So if you have drives A and B with free space A>B then it should be putting the files in A until A<B at which point it should begin putting the files in B until A>B again (and so on)... note that over time this naturally will result in a roughly even spread of files across A and B (assuming the drives are of similar size). Is this not happening? How much free space do you have on each of your archive drives? Also if you're using snapraid or similar parity tool on your archive drives then you'd need to be careful to not have any balancers or placement rules enabled with settings that would move existing files within those drives. Do you have any other Balancers or Placement Rules active?
  15. That's roughly 120 MB/s, which (checking) is about the same as what I get on an internal 12TB SATA HDD that benchmarks at roughly 250 MB/sec sustained, so magic 8-ball says it seems likely?
  16. Both are "Mini-SAS" but the SAS9207-8E requires SFF-8088 cables (rectangle-shaped ends) while the SAS9300-8E requires SFF-8644 cables (square-shaped ends). So the latter is no good to you unless you also buy an adapter. I haven't used the card with Windows/Drivepool however, so if anyone has please do chip in with any tips!
  17. You're welcome! If the backup software does not do so already, you may wish to exclude the hidden system "$RECYCLE.BIN" and "System Volume Information" folders from your backup to save a bit of space there. If you're not using reparse points (symlinks, junctions, etc) inside the pool you could also exclude the ".covefs" system folder.
  18. I haven't used that provider myself; does the tooltip from resting the mouse cursor over each account give any useful distinguishing detail?
  19. Are you familiar with the VHD, VHDX, etc type of file formats that allow a virtual hard drive to be stored as a single file whose actual size expands with the used space of the virtual hard drive it represents? Clouddrive does something similar but instead of a single file it uses multiple files (called chunks, with each chunk roughly equivalent to a number of in-use sectors of the virtual drive). If the clouddrive is kept on local storage (i.e. a physical drive pooled alongside the existing physical drives physical drive or replacing one of them) and you're using backblaze's software to back that up, then it's only going to back up the 1.5TB of the files in the clouddrive. If the clouddrive is kept on blackblaze, then there will also be overhead from the virtual drive metadata plus the cost of any "sectors" that have been used but not (yet) cleaned. Also if clouddrive data duplication (not to be confused with drivepool duplication) is enabled when the clouddrive is created then the storage requirements will be doubled. I hope that's clear? P.S. If your pool consists of four physical drives with 4x drive duplication enabled (i.e. every drive is an exact copy of every other drive) have you looked at whether it's suitable for your situation to have the B2 backup software use the poolpart folder on any one of the drives (which are VSS-compatible) as its source instead of the virtual pool drive?
  20. TLDR is stick to the GUI unless you have an urgent reason to do it manually. DrivePool 2.x expects every poolpart to have a unique UID (the dashed alphanumeric string after the dot in the hidden PoolPart.* folder name) so you'd have to: either pull the old drive and clone the entire volume to the new drive on a different machine before putting the new drive into the drivepool machine and wiping the old drive's poolpart before putting the old drive back in or turn off any automatic and immediate/forced balancing, add the new drive to the pool first, stop the service, use robocopy (making sure to include directory timestamps) as an administrator to copy the content - excluding .covefs and any protected system folders - within the old poolpart to the new poolpart, and then start the service, remove the old drive, turn on balancing (if desired) and do a re-measure (and maybe a duplication check if you're using that). Basically there's good reasons to use the DrivePool GUI to add new drives and then remove old drives. It's slower but can be as simple as just using the GUI to add the two new drives and then remove the two old drives (you can queue multiple drives) and then let DP take care of everything inbetween - which has much less chance of something going wrong and you can keep using the pool in the meantime; this can be particularly handy if the pool is being shared on a network with other people. (Incidentally, I have tested copying a poolpart folder itself on a machine that had two pools, and the result after I ejected the old drive and rebooted was the new drive showing up... as part of the wrong pool - so I really don't recommend trying that).
  21. Yes, that's the pool drive letter. So if the hidden poolpart folder in the root of your bad drive is named "PoolPart.654e1b5c-05b8-44a2-8b6b-a0251f2ec7d6" then the command you would use to tag that particular poolpart to be ignored would be: dpcmd ignore-poolpart n: PoolPart.654e1b5c-05b8-44a2-8b6b-a0251f2ec7d6
  22. In the DrivePool GUI, at the very top where it lists your pool(s) - NOT the Disks section below that - what is the string inside the first set of parentheses? E.g. on mine: "DrivePool (P:\) - (39.1 TB)"
  23. Hmm. Just checking, you are using the pool's drive letter and not the bad drive's letter, confirm? If the pool itself is mounted as a path (e.g. "c:\mounts\poolP") instead of a drive letter (e.g. "p:"), try the path. If it's not mounted as either a path or a letter, try mounting it as either first and use whatever you've assigned.
  24. Try the following command from a command prompt run as an administrator where pooldriveletter is the drive letter of the pool itself and poolpartname is the hidden folder beginning with "PoolPart." on the bad drive: dpcmd ignore-poolpart pooldriveletter: poolpartname This should tag the relevant poolpart to be ignored by DrivePool at the system level, which will effectively make it "missing" as far as the pool is concerned; the pool will become read-only until this is reversed or the "missing" drive is removed from the pool - which you should be able to immediately do as DrivePool should treat it just like removing any actually-missing drive and drop it without attempting to retrieve anything from it.
  25. Updating shouldn't make things worse but if the drive's at the point where it's generating BSODs then I doubt updating would make things any better either. Personally I'd physically remove the drive from the server altogether (it'd then show up as a "missing" drive in DrivePool and can be safely removed from there); if I still needed to (try to) get any remaining data off the bad drive I'd use a separate test machine so any further BSODs wouldn't interfere with the server.
×
×
  • Create New...