Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Try rebooting. If that doesn't help, try resetting the settings in StableBit DrivePool. https://wiki.covecube.com/StableBit_DrivePool_Q2299585B If that doesn't help with the missing disk, remove the disk in the UI, and then do this: https://wiki.covecube.com/StableBit_DrivePool_F1655 And the recycle bin should be the one on the desktop. It's a combined list of all of the drive's recycle bin.
  3. FAQ answers that, as did I, above. You can generate your own app API keys and use those, these are configured in "C:\ProgramData\StableBit CloudDrive\ProviderSettings.json" file. The Google Drive Provider will be marked as "expirmental"/"deprecated". This means that new installations, the provider will be hidden by default. You can enable it by enabling experimental providers. However, if you already have connected to Google Drive on a system, then it will stay visible. Fully outlined here: https://wiki.covecube.com/StableBit_CloudDrive_Q7941147
  4. Today
  5. Google Drive was an excellent choice when you were able to sign up as gsuite business (even the start of workspace entreprise) to get unlimited storage. But it was inconsistent, it was sometimes corrupting data. Now that they are enforcing limit and the pricing goes higher, there is no reason to not use something else. Will you let the option available to people that want to use it with the risk associated or you will remove it from the list of choice ?
  6. Not sure which Recycle bin to remove (the individual drive, or the pool itself)? I've cleared the individual drives, but there seems to be 16Gb in the pooled recycle that I am not sure that i want to remove/lose. Did a checkdisk and now have a weird issue where a disk is lost, but is able to be added. See screenshot below. I'm not sure how I can move forward with this without creating a new pool and moving data manually. If someone can give me a steer that would be a help.
  7. Where can I find instructions to get my own API Key to use?
  8. Yesterday
  9. StableBit DrivePool shouldn't move files from a non-poolpart folder into a poolpart folder. So that part sounds odd, and possibly that Windows re-assigned drive letters? And yes, the balancing does move the files from one PoolPart folder to another, on a different disk, if/when needed. As for stopping the files from being moved, a good question here is "why are they being moved". Most of the default balancers deal with edge cases, and shouldn't move data by default. That said, could you open a ticket at https://stablebit.com/contact
  10. I assigned drive letter Z:\ to my DrivePool drive. Yesterday I noticed that files were disappearing from the Z:\ drive. When I searched for them using Everything, I found that DrivePool had created a folder on Z:\ called PoolPart.5c7f2eb1-1b02-4f73-ae4b-beb3508b9723, and it was moving the files there. (I think it's moving the files as it's rebalancing the DrivePool.) Any suggestions about how to stop this? I don't think I can simply move the files out of the new PoolPart folder back to their original locations without causing havoc.
  11. Last week
  12. Simplest option? Just empyt the recycle bin. That will remove said file. As for the specific issue, I would recommend running a CHKDSK pass of all of the pooled disks, and then re-measure the pool. If the issue continues, then please open a ticket at https://stablebit.com/Contact
  13. Evacuating to specific drives? Don't panic, we can save your ISOs! Ouch, those spontaneous reboots sound rough! But don't worry, we can get your precious Linux ISOs off that suspect pool and onto safer ground. Here's the deal: You're right, there's no built-in "evacuate to specific drive" function in most storage pool software. But we can achieve the same result with a little work. Here's the plan: Grab a new friend: Get that fresh drive you mentioned. Prep the new recruit: Add the new drive to your pool. Copy, not move: Use good ol' fashioned file copying to transfer your ISOs from the suspect drive to the shiny new one. Most operating systems have a built-in copy function you can use. Drop the suspect: Once everything's copied over, remove the suspect drive from the pool. Scrub-a-dub-dub: Now you can safely reformat the suspect drive to erase any potential gremlins. The return of the king (or queen): If the reformat goes well, add the suspect drive back to the pool. Repeat and rejoice: Rinse and repeat steps 3-6 for each drive you want to check. Bonus tip: Since you suspect some of your drives might be failing, consider running a disk health check before reformatting. This can help identify any drives that might be on their last legs. Why not just evacuate everything? While evacuating all drives is an option, it can be unnecessary work. By copying to a specific drive, you only reformat the drives you suspect might be causing issues. Remember: This process might take some time, especially with 10+ TB of data. Grab a cup of coffee, settle in, and let your computer do its thing. By following these steps, you can isolate the problem drive, clean house, and get your precious ISOs safely stored on a fresh pool. Good luck!
  14. Drive Pool gives me the following error and I have no idea what to do to rebuild my pool.
  15. Just some more info, as the system rebooted itself just a couple of minutes ago. In Event Viewer under Windows Logs -> Applications, I've run across a few of these in red: Faulting application name: DrivePool.UI.exe, version: 2.3.6.1562, time stamp: 0x65e61092 Faulting module name: KERNELBASE.dll, version: 10.0.22621.3235, time stamp: 0x2b72307b Exception code: 0xc000041d I'm also still getting those notices claiming that I have duplicate disk id's. Finally, I'm seeing a fair amount of these and have no idea what it means: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.WscDataProtection and APPID Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Any help?
  16. It's definitely pool related. I installed another program which hits the pool fairly hard (NOT Scanner) and the restarts returned with a vengeance. I checked all the disk id's using diskpart's uniqueid feature and every one was different, so I don't know why Windows was complaining about clashing identifiers. I also chkdsk'd every single disk using Disk Management's tool tab and one of the pool drives had errors, which it fixed (I hope). I used DM's tool because I had to assign drive letters before a scan could be run. Oh, and >all< the drives are showing as gpt. Gremlins! I've also periodically seen file duplication consistency warnings from DP that have required manual intervention, but I don't have file duplication turned on, so I don't know what that's about. I don't know what to do from here. I could go back to the old cpu, but my instinct tells me that's not the culprit. Maybe something has gone wrong with the Sabrent, but that also seems unlikely given that everything was running smoothly before the cpu switch-out. I don't have a second Sabrent to try and buying another one when I don't know if my current one is going south is a financially risky endeavour (the damn things are $600). I suppose the only thing I can do at this point is go back to the previous cpu. It's just so odd and frustrating that the system runs normally otherwise. Should I try rebuilding the pool from scratch by removing all the disks, rebooting, and adding them back? Is it possible something has gotten corrupted in the pool's "config files"?
  17. For the MSR partiation, this depends if the drive is MBR or GPT, and sometimes, how it was initialized+partitioned. Either way, the presence/lack shouldn't effect things. My pool has a mix of these, and has for a long while. As for the non-GPT drive, it's possible that there was some partitioning error? Eg, if the system was unstable and rebooting/BSODing, any time that the disk is being written to, there is a chance of corruption/damage. You can use diskpart or powershell to fix this. IIRC. But it shouldn't be too big of an issue. And if you're using Windows Server, the Multipath I/O feature can "fix" this. Also, I would recommend checking the event viewer for disk, file system and controller errors. They may point to a specific disk. But Also, if you haven't, run a CHKDSK pass on *all* of the disks (except to pool)
  18. Glad to hear that you were able to get it sorted! As for fixing automatically, this one is tricky, because it can be complicated. And brute force fixes can be ... problematic.
  19. because it got bumped... I decided to look into defrag stuff again.... Diskeeper is now DymaxIO, with no real options or UI, and a yearly license. Raxco PerfectDisk appears abandoned. 2021 is the latest update, and the website has some pretty critical errors on it. Windows 10 support mentioned, but nothing about Windows 11. Defraggler is discontinued, last version is from 2018. Auslogic Disk Defrag is super spammy. O&O defrag, exists but haven't really tested it. Server version is separate and much more expensive. Seems like the era of defragging is dead. But given SSDs/NVMe drives, and large capacity HDDs, I can't say that I'm surprsised.
  20. Just to be clear from the instructions you supplied. After moving all files from, say, each disk of my mirror-1 PoolPart.GUID folder to outside of this folder (and deleting each PoolPart.GUID folder) should I then create a new single pool that will ultimately hold the contents of all my previous 5 pools ie you stated "Add the now unpooled disks to the remaining pool" could that mean "Add the now unpooled disks to the newly created single final pool". I hope this makes sense
  21. Thanks for the info Drashna. I'll give it a go shortly & let you know the outcome
  22. You can use the command dpcmd get-duplication object as an administrator, on the machine on which DrivePool is installed, where object is the full path of a folder or file in the pool (e.g. "p:\testfolder" or "p:\testfolder\testfile.txt") to check that the actual duplication matches* the expected duplication of the path, and it will also return which poolparts contain that object. *Note that due to the way DrivePool works, the actual duplication may exceed the expected duplication for folder objects; this is normal.
  23. Explorer relies on the underlying hardware's error-checking capability to indicate any problems when copying or moving a file. When dealing with a system that is rebooting by itself without explanation, I wouldn't trust that - let alone for anything critical or irreplaceable. You can use copier programs such as Teracopy or Fastcopy that have built-in checksum verification as an option when copying to a new target, or use syncing programs such as FreeFileSync or TreeComp which allow you to compare the contents of two existing drives/folders. I would also suggest checking and resolving the disk identifiers issue before proceeding.
  24. A final, I hope, follow-up to this. I have fixed the problems by simply going to the OS level and going to each drive and making "Everyone" the owner, with full rights, to each of the PoolPart... directories on the drives. That seems to have cleared everything up and the duplicating functioning is restored. I probably made this more trouble than it needed to be but I plead age and poor health that influenced my decisions to the more complicated side. I lost a few files but at least i did not need to rebuild my entire pool. I wish there was a tool available that will fix this kind of issue automagically but doing it manually is not too bad as long as the correct choice is made early on. Unfortunately some of my early decisions led me down the wrong path so it took me several times longer than it should have. Again, I plead old brain syndrome.
  25. Well, I don't think DP in and of itself is the problem. I just think the disks themselves have gotten themselves into a degraded state for whatever reason. When I did the cpu switch-out, one of the drives dropped-out of the pool. I was really irritated and exasperated at the time, so I just shoved the drive back into its bay, made sure the door was 100% shut, and it seemed to stick, but it was one of those shucked drives, so it may (or may not) be actually healthy. Another reason I suspect the pool has become problematic is because, when I reinstalled Windows, I noticed that some disks had the MSR partition and some didn't. Also, one of the drives didn't have a gpt volume, which is hellaciously odd because I always use gpt volumes. These sort of inconsistencies play havoc with my OCD. Combine that with these intermittent restarts and I don't know what to do other than to try to get the pool back to a "baseline" state. Oh, to make matters even worse, I took a look at event viewer and saw a bunch of these: "Disk 9 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue." So, something has definitely gone awry. I was hoping to get lucky and let DP do the evacuations itself, which I know contradicts my suspicion that DP may in some bizarre way causing the restarts, but at this point I'm willing to sacrifice a goat if it'll make these problems go away. I'm at an age where these things are no longer neat things to track down, but are real obstacles to my mental well-being. If I do have to do things manually, I was simply gonna let Explorer do all the work. Does it not verify file operations? Thanks for the quick feedback!
  26. Earlier
  27. Regarding the reboots, given you strongly suspect it's DrivePool-related then I would recommend opening a support ticket with StableBit. Though with any use of Scanner increasing the reboot frequency I'd suspect some kind of load/conflict trigger; I'd be giving your new CPU dubious looks too. Evacuating follows the same rules as placing files on the drive - for example it will default to evacuating to the drive(s) with the most free space at the time - so it should thus be possible to force it to use a specific drive via the Ordered File Placement balancer, but I'd want to test that first. However if your machine is often rebooting whenever you're using the pool then I'm not sure how you plan to successfully evacuate a drive via DrivePool's Remove function; you may have to do so manually: Add the new drive. Stop the DrivePool service. Copy your content from the hidden poolpart folder on the old drive to the hidden poolpart folder on the new drive. Don't include system folders (e.g. recycle, sysvol, covefs). I'd also suggest verifying the copy afterwards (e.g. using FreeFileSync, md5deep, et cetera) if your copy method doesn't include its own post-copy verification. Format the old drive. Start the DrivePool service. Amend any balancers or placement rules that specify the old drive. Remove the "missing" old drive.
  28. I think I've got a real problem on my hands. A few days ago, for unrelated reasons, I swapped-out my CPU for another. SOMETHING happened after the swap, as my Windows 11 install became corrupted to the point that I had to perform a complete reinstall. And it's been downhill since then, as my system will spontaneously reboot. Doesn't crash or otherwise BSOD, but just does a fast reboot. It's driving me crazy and, for possibly mystical reasons, I suspect my pool is the culprit. Why? Because whenever I do anything with the pool, a reboot seems to follow. Sometimes it doesn't happen immediately, but it WILL happen and it's the only commonality I've seen, as I can go all day without seeing one of these reboots just so long as I don't touch the pool. Now, I know that doesn't make much sense, as obviously DP is reading and writing stuff to the pool in the background, but it's the only thing I've been able to deduce. I also suspect this because, when I install Scanner, the reboots really start to kick in. I'm using a Sabrent 10-bay enclosure for the pool. I have raging mistrust issues when it comes to this stuff, so the only thing I know to do is to completely rebuild the pool. Fortunately, I have a spare bay I can use for this process, which I know is going to be a long and painful affair, but I'd really, REALLY like to save the 10+ TB of Linux ISOs I've amassed over the years. My plan was to buy a new drive, put it into a spare bay, add it to the pool, evacuate drive 1 to the new drive, drop drive 1 from the pool, do a long reformat of drive 1, add it back to the pool (assuming it passes), then re-evacuate the files back to drive 1. Rinse and repeat. Problem is I don't know of a way to evacuate a drive to another user-defined drive. I know I could simply evacuate each drive, drop it from the pool, reformat it, and add it back, but I don't know if the other "old" drives might also have problems, so I want to do the evacuations to a brand-new drive one-by-one. Some of my drives are cheap shucks from several years ago that might be failing in ways that Windows can't handle. In the end, I want to long format the entire damn lot to be 100% certain they're good to use. So, is this possible?
  1. Load more activity
×
×
  • Create New...