Jump to content
Covecube Inc.

Search the Community

Showing results for tags 'damage'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

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 3 results

  1. Hi Guys, this week i got my first damage error via launchpad notification from my system SSD (Kingston 60GB). There were not much free space on it since months, so i was planning to swap it with a bigger one (WD 240GB) in any case. After file scan there was only one file damaged, which was not important, so i deleted it, run chkdsk /f on it and clone the whole partitions to a newer bigger SSD. Actually everything is working fine but the damage message is still present in launchpad's notification window and the old kingston drive is unplugged lying in the cubboard. I know from o
  2. I recently had Scanner flag a disk as containing "unreadable" sectors. I went into the UI and ran the file scan utility to identify which files, if any, had been damaged by the 48 bad sectors Scanner had identified. Turns out all 48 sectors were part of the same (1) ~1.5GB video file, which had become corrupted. As Scanner spent the following hours scrubbing all over the platters of this fairly new WD RED spinner in an attempt to recover the data, it dawned on me that my injured file was part of a redundant pool, courtesy of DrivePool. Meaning, a perfectly good copy of the file was sitt
  3. 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 st
×
×
  • Create New...