Jump to content

Christopher (Drashna)

Administrators
  • Posts

    11573
  • Joined

  • Last visited

  • Days Won

    366

Posts posted by Christopher (Drashna)

  1. On 11/30/2021 at 9:29 AM, moskeale said:

    In hindsight now I believe my conflict was actually "HFS+ for Windows", (besides the point).... so trying to reimplement my Primocache usage now.

    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. 

  2. 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. 

  3. On 8/6/2020 at 6:12 PM, bitfidelity said:

    I just restarted my machine after adding a drive to my JBOD (not sure if that has anything to do with it) and was greeted to an unknown "COVECUBECoveFs" listing under the "non-pooled" category in DrivePool. I also noticed that Disk Management was showing me two unallocated partitions: 1) Covecube Virtual Disk (2 TB) and 2) Microsoft Virtual Disk (8 GB).

    I think the latter has something to do with Windows Sandbox or Windows Update, but how did that 2 TB partition get there?

    That's the drive for stableBit Drivepool.  If you upgraded Windows, it can sometimes cause issues.

    On 10/7/2021 at 11:23 PM, Drivepoolguy said:

    I have the same problem after updating to Windows 11. I am getting a bit worried now because no one replied to you for more than a year. 

    Please see my post about the same issue: 

    Did you end up fixing it and if yes, how? 

    Uninstall, reboot, reinstall, and reboot again.  That should fix the issue.

  4. 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). 

×
×
  • Create New...