Jump to content

Search the Community

Showing results for tags 'Bad Cluser'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Covecube Inc.
    • Announcements
  • StableBit Cloud
    • General
  • StableBit Scanner
    • General
    • Compatibility
    • Nuts & Bolts
  • StableBit DrivePool
    • General
    • Hardware
    • Nuts & Bolts
  • StableBit CloudDrive
    • General
    • Providers
    • Nuts & Bolts
  • Other
    • Off-topic
  • BitFlock
    • General

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Hi there, I saw a previous thread about putting a damaged disk back into the pool, but my question is slightly different... I have a disk that StableBit Scanner says has some damage. It's a small amount of damage vs. the whole disk, but of course, it's part of a big file, so that's likely toast. What happens now? What happens with DrivePool when a bad file is either "fixed" or becomes corrupt? Does the bad file get replicated to other pool members? Or does DrivePool figure out the disk has damage and overwrites the bad file? Should I leave the bad file in place (rename it so it stays put over the bad disk area) and copy a good file over to that folder? I've run chkdsk /f /b on the drive a few times (it takes around 18 hours), and Scanner is trying to "recover" the file - but I think that's going to fail. If chkdsk has done its process on some bad sectors, is the drive OK for a while? Or will DrivePool keep trying to write back to those sectors? Thanks...
×
×
  • Create New...