tcz06a

Yeah, ReFS doesn't support pinning, at this time.  
 
The problem is... we have to know the file system's data structure so we know what we need to pin.  
 
This means that we need to find GOOD documentation, source code, or reverse engineer the file system. 
 
The plus side.... we'll have ReFS Support in CloudDrive, Scanner and DrivePool (full support) at about the same time. 

In my opinion, I think a drive with such a measly SMART attribute set is not necessarily any more or less suitable for most people's needs. It does pose, I think, a greater liability, insomuch as you have fewer attributes to indicate the drive's health and overall fitness. Had I known beforehand, I would have chosen a different drive. I left feedback expressing this with WD. If it is working alright for you now, you will simply need to remain extra vigilant of its health yourself. Fortunately, StableBit Scanner's core scanning features can be leveraged for this easily.

I have recently purchased a new USB drive, and StableBit Scanner is using non-manufacturer specific interpretation rules for it.
I have also found that Scanner cannot read from 1705 sectors near the beginning of the disk, although 4 other utilities are reporting able to read and write to those sectors.
I am using Scanner Beta v2.5.2.3103
I noticed that Scanner is not able to read how old the drive is, when it could on an older model of WD My Passport 2TB drive.
If I can provide any further information, please let me know. I am attaching several images to detail the disk.

The included attachments have information from:
CoveCube DirectIO Tool
StableBit Scanner
CrystalDiskInfo
 
 
I wonder if Scanner is somehow incorrect about those 1705 sectors being damaged, perhaps due to not communicating with the disk correctly.
For example, DirectIO seems to think this is an SSD when it is not.
 
-Tomas
CrystalDiskInfo7_0_4.txt
direct.txt

I believe I have found a solution to this problem of mine. When I had CloudDrive destroy my drive, something, somewhere, had a hiccup. The folder on Google Drive wherein the chunks resided was deleted, but somehow the chunks themselves were not. Google forums indicates such files are called orphans, as they have no parent structure (folder). These orphans can be viewed by searching for 'is:unorganized owner:me' and deleted from there. As the Drive GUI produces 'server error occurred' when trying to delete more than 100 files at once, I looked for a script to automate their removal. I finally found one which worked. I found the code snippet at https://medium.com/@tashian/the-workaround-300ac8f05bb7#.vc41xsuwdalthough I am unsure if I can post a hyperlink in my comments. I can testify that it is deleting the orphaned files, while not touching anything else.

Good catch. Submitting official feature request to Alex:
https://stablebit.com/Admin/IssueAnalysis/2175
 
 
Preliminary support for ReFS has been added to the software. It is present in the beta versions, but may change. 
 
We need to investigate exactly how to implement ReFS, and what we can do with it specifically. There are some serious opportunities for advanced handling of the file system, and we want to make sure that this is done right.  For instance: 
Checking the integrity streams when accessing files or running a duplication pass Replacing a file that has failed the integrity check with a known good copy on another disk, when duplication is enabled Showing the pool as ReFS instead of NTFS (more for Scanner, but) run regular integrity checks on the disks. Other, unforeseen complications or features that could be added.   
Needless to say, this isn't as simple as just turning on the ability to use ReFS and will definitely take some time to investigate. 
 
Unfortunately, we are a small company, and our resources are limited. That means that this won't happen until we have an RC or release version of StableBit CloudDrive (which we hope is soon). 

I believe I have found a solution to this problem of mine. When I had CloudDrive destroy my drive, something, somewhere, had a hiccup. The folder on Google Drive wherein the chunks resided was deleted, but somehow the chunks themselves were not. Google forums indicates such files are called orphans, as they have no parent structure (folder). These orphans can be viewed by searching for 'is:unorganized owner:me' and deleted from there. As the Drive GUI produces 'server error occurred' when trying to delete more than 100 files at once, I looked for a script to automate their removal. I finally found one which worked. I found the code snippet at https://medium.com/@tashian/the-workaround-300ac8f05bb7#.vc41xsuwdalthough I am unsure if I can post a hyperlink in my comments. I can testify that it is deleting the orphaned files, while not touching anything else.