Christopher (Drashna)

In this case, yes. Or create a rule that bypasses it. But you can also just turn it off temporarily.

That's ... very odd. But for reference, you can manually add "peers": https://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings#RemoteControl.xml

Have you tried the beta version of StableBit Scanner. IIRC, there are some improvements that should help with false positives in the file system scanning.

Yup, they run on Windows 11 just fine (Also Server 2022 looks to be Windows 10 based, 21H2, specifically). And yes, you can use 2x SSDs for cache, just download and install the SSD Optimizer balancer plugin. StableBit DrivePool Balancer Plugins

we've run into a few people that have had issues with the HFS driver for windows causing BSODs, and a good number of people using primocache with StableBit DrivePool without issues.

I think you opened a ticket for this as well, and that one of the poolpart folders is showing up a file. If so, then data recovery, or wiping the drive and letting it reduplicate the data is the best option here.

Yup. But I would recommend deactivating all of the StableBit products before moving over to the new hardware, that way you don't run into any activation issues.

Use powershell, and "remove-item". It should be able to do this. Otherwise, this should work. And if it's not, could you open a ticket at https://stablebit.com/contact

Not currently, but I definitely do keep on bringing it up.

The simplest option would be to use the file placement rules to exclude the SSD drive from being used.

Just a heads up, though, DrivePool doesn't have a concept of original and duplicate for files. So if you limit the duplication space, that's limiting where both copies of the files can reside.

Yup. https://stablebit.com/Support/Scanner/2.X/Manual?Section=Disk Settings And you can control the frequency of the scans, here: https://stablebit.com/Support/Scanner/2.X/Manual?Section=General

Well, this is unrelated, but I highly recommend not using the B: drive letter for the pool, as Windows has some hard coded behavior in this regards. Eg, it treats A: and B: as floppy drives, and constantly pings the drives. That said, torrents on the pool can be tricky, given the way that the torrent files work. I would recommend storing the torrents outside of the pool, to be honest.

well, I'm glad to hear that. And yeah, it probably updated something "behind the scenes" that got the driver working again. (this can happen with certificate root stuff, for instance).

Yes! https://wiki.covecube.com/StableBit_DrivePool_F1655

If the other drives have more than 10% free space, then this is normal. It doesn't rebalance data to use the new drive, by default. However, you can use the Drive Space Equalizer balancer plugin to force this to happen. StableBit DrivePool Balancer Plugins

That's the drive for stableBit Drivepool. If you upgraded Windows, it can sometimes cause issues. Uninstall, reboot, reinstall, and reboot again. That should fix the issue.

Yeah, that looks fine. But you may want to run a CHKDSK Pass on the G:\ drive, just in case.

it depends on what you're moving to, but basically it's removing the files from the pooled drives, and migrating to the new solution. All of the drives are NTFS drives, so you can easily get the data off of it. As for snapraid, this may get you started: https://community.covecube.com/index.php?/topic/94-drivepool-and-snapraid/

Yes, it should be. Their docs should cover everything you need to get it set up: https://www.idrive.com/cloud/faq#s3-credentials Just select the Amazon S3 provider, and select the S3 compatible provider option.

I'm sorry that I missed this. Are you still having this issue?

That's definitely not typical. That sounds like the settings aren't being written to disk properly. If you could, open a ticket at https://stablebit.com/contact, please.

Are the bad sectors showing up under the sector/surface scan part? If so, the only way to permanently clear them is to write to those locations, which should force the disk to remap/reallocate those sectors. However, StableBit Scanner doesn't have that ability, intentionally. We activately avoid writing to the disk, to fix issues, as it can prevent data recovery from working properly. That said, a "chkdsk /b" pass may help here... but worst case, a full (non-quick) format will get the job done (and possible find and fix other sectors that havent been identified as bad, yet).

Yup, shouldn't be any issues with running it.

Not through the UI, aside from manually, which may be very, very time consuming. However, the "dpcmd" utility should have an option to do this.