Mick Mickle

Regardless of the quality of the software, this isn't helpful nor constructive, and provides nothing to the conversation. 
 

The problem is that you were still on an affected version 3216. By upgrading to the newest version the Stablebit Scanner Service is forcefully shut down, thus the DiskId files can get corrupted in the upgrade process. Now that you are on version 3246 which fixed the problem it shouldn't happen anymore on your next upgrade/reboot/crash.
I agree wholeheartedly though that we should get a way to backup the scan status of drives just in case. A scheduled automatic backup would be great. The files are extremely small and don't take a lot of space so don't see a reason not to implement it feature wise.

Mick Mickie:  Thanks for jumping in Mick! Christopher just said "Crashes", so I thought the "Fix" might not help me. I don't usually upgrade to Beta versions of anything, but in this case I think I might make an exception. I was just upgrading to sort of get away from the built-in wssx versions in preparation for my upcoming move to Server 2016 Essentials.
Again, thanks!
Gary
 

Well, a number of others were having this as well, and I've posted this info in a number of those threads, so hopefully, confirmation will come soon.  

The cause of the issue is fixed with Beta 3246. Since my machine is not frequently crashing, maybe once per month, it will take a while to verify it on my side.

I've had it happen with normal reboots as well, just not as often as with crashes. It just depends on the timing. Imagine what happens on a reboot. Windows is forcefully shutting down services, including the Stablebit Scanner Service. So if this service gets shutdown at the timeframe where it is writing new DiskId files the files can end up corrupted, thus after a reboot the Service creates new DiskId files meaning all previous scan status is lost.
Now the DiskId are not written literally every second anymore (which increases the risk that the service gets killed at the time of writing files significantly) but instead 20-40 minutes (don't know the exact interval now) . That's a reduction of a factor of 1200 to 2400 so the risk that you reboot at the exact time the files are written should basically be zero now.

Thanks, Christopher.  I agree.  Currently, I have a SMART warning just for LCC, so I did permanently ignore it. 

@Mick Mickle Unfortunately, there isn't a way to handle multiple settings at once.  
But honestly, if you are seeing multiple SMART warnings at once, you should replace the drive.  LCC by itself is fine, but with other errors.... it's time to replace. 

It's probably related.  Though, this should hopefully be resolved in the 3220 beta:
http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3220_BETA.exe

My two ST5000DM000-1FK178's are going strong but they do that annoying cruch/chirp sound that I posted about months ago all the freaking time, it's driving me up the walls.  
 
Dave, did you get the HDAT2 software to work on a 5TB seagate?  I can go in and disable the APM, but when I go into the DCO menu in step 11, all five items there are red, and when I select modify per step twelve, it just chirps and says command aborted.  So I got nowhere because that's the hack that makes the APM setting stick.  
 
I'm so sick of these Seagates, if I had the money I'd toss them and get greens, at least you can control them.  I'm also a little ticked that apparently these are SMR / Shingled drives and I could find nowhere in the product documentation that mentions that.  I thought they sucked performance-wise, and I guess that's the answer. 
 
when the seagates are internal to my computer, I can use CrystalDiskinfo to disable the APM, but when they're in my Mediasonic Probox eSATA enclosure where they belong, the commands using CDI or StableBit Scanner are not honored.  And I should add, that using HDAT2 I had it hooked up internally. 
 
Sorry if I sound grumpy, I just spent the better part of the last two hours dinking around with this, the thread got it back into my head again that I should finally mess with it, I thought I had hope, and my hopes were, alas, dashed.  

If you've already moved them, there's probably no need to do it again. Umfriend was describing in "Wrt step 4" how to move the location address of the files within each individual drive (E: then F: then G:) rather than physically copying and deleting the files themselves. 
As you probably know, if you move a file, no matter how big it is, from one folder to another using Windows/File Explorer, the action is almost instantaneous since Windows simply points to the new location -- like changing the page number in the table of contents or index.  You can do the same thing by moving files between the PoolPart.* folder  (that represents the DrivePool pool) and another folder outside of the PoolPart.* folder on the same drive (e.g., E:).
So if folder PoolPart.xxxxx represents Pool A on Drive E: and folder PoolPart.yyyyy represents Pool B also on Drive E:, you can move the files between those two folders quickly, since the operation would just change the address of the files. The long alternative would be physically moving the files into the drive letter that represents Pool B.
Again, if you can confirm that the files are now in Pool B, you completed the race but didn't take the shortcut.
I guess "upper" and "lower" PoolPart folders is how they are sorted in Windows Explorer, and PoolPart for Pool A is named closer to "A" in the alpha sort, maybe because it was created first?

Just upgraded two different machines running different Operating Systems (W7 Pro and W10) from 2.5.3.3191 to 2.5.4.3216.  Didn't have any issues - all settings and data retained perfectly.  I will note that I've gotten used to stopping the Scanner service prior to manual upgrades, but that's just me being cautionary.

Sorry to be negative, but I doubt if 3198 fixed it. I uninstalled 3191, copied my previous folders for 3062 back in place and reinstalled 3062:  all disk settings and data were then back to normal. Then I went directly to 3204, since that has the new settings backup and restore feature, bypassing 3198. The result was that no settings were retained (except for 1 of 11 disks, oddly) and all disks needed to be scanned for the first time.
(This time, however, I did a printscreen of my names & locations, and re-entered everything into 3204. I'll let Scanner rescan everything and just move on to the future.)

Also, you may want to check out the newest beta.
http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3204_BETA.exe
 

Okay, good news everyone.
Alex was able to reproduce this issue, and we may have a fix.  
http://dl.covecube.com/ScannerWindows/beta/download/StableBit.Scanner_2.5.4.3198_BETA.exe
 

Edit:  moved suggestion to other topic..
 

The import/export feature would be nice. I guess right clicking on the folder and 7zip'ing it, is the definitive solution, for now, until an automated process evolves.
According to Christopher's answer that it seems to be an isolated incident, I'm wondering what is it about our particular systems that is causing this purge? 
I have it running on both W7 and W10 and it purges on both. Both OSs are clean installs. Both run the same EVO500...alongside a WD spinner. Both are Dell. It seems to me that the purge is triggered by some integral part of the software once it's updated. Like an auto purge feature.
I'll be honest, I think most people are too lazy to sign up and post the issue, which makes it appear to be isolated incident, but I believe this is happening more often than we think. 
I'm on a lot of forums, and it's always the same people that help developers address bugs, by reporting them. Unless it's a functional problem, it goes unreported.
All of you...know how lazy people are. With that said, I like the idea of an integral backup and restore of the settings. 

Well, I don't mean to minmize the issue, at all.... but this generally happens to only about 5-6 people (or at least, that's how many report it).   So, it's no a huge thing. 
That said, 
We've looked into this issue in the past, with little success Alex is planning a "deep dive" to look into this issue ( @Mick Mickle, I believe Alex mentioned that to you in the ticket, actually), and we've talked about this The new JSON format for the setting store (located in "C:\ProgramData\StableBit Scanner\Service\Store\Json") should be much more resiliant. 
in fact, I tested out copying the folder elsewhere, nuked the settings, and restored the JSON folder.  I did this on my production server, and can verify that it works.  So, if you backup the folder in question, you setting should be safe, from here on out.  

Might be a nice option to have an import/export function for the settings in the various products.  Primocache and Primo Ram Disk have it, and I use them when re-creating configs all the time.  It has saved my bacon more than once.  Just bundle the JSON folder into a .zip and allow the user to specify export destination.  On import, unbundle and write (with optional overwrite verification).  Just a suggestion.   

Well, I don't mean to minimize the issue, at all.... but this generally happens to a small group people (or at least, that's how many report it).   So it doesn't seem to be a wide spread issue.  Which ... means it's pretty rare, and ... that it's not as easy to track down. 
That said, 
We've looked into this issue in the past, with little success Alex is planning a "deep dive" to look into this issue ( @Mick Mickle, I believe Alex mentioned that to you in the ticket, actually), and we've talked about this The new JSON format for the setting store (located in "C:\ProgramData\StableBit Scanner\Service\Store\Json") should be much more resiliant. 
In fact, I tested out copying the folder elsewhere, nuked the settings, and restored the JSON folder.  I did this on my production server, and can verify that it works.  So, if you backup the folder in question, you setting should be safe, from here on out.

Many people losing settings on updates recently.
 

I wish the install stated that it would erase your settings so I could have opted out of the update or at least copied my settings down first.

Christopher, thanks for your extensive reply. Maybe showing up as a removable drive is why My Movies logs continue to reference the DrivePool drive letter as well as the UNC. I'll update to the DrivePool beta you referenced and see if that changes things.
 
My initial problem with My Movies General Service runaway memory stopped with a corrected erroneous path on one TV series title. That General Service continuing to parse the DrivePool letter rather than just the UNC path could be an efficiency/overhead (or other) issue, though. If the beta doesn't fix it, I'll upload a dump of the My Movies process. I must say, you guys would be going above and beyond to take a look at that. My hat's off to you for offering.
 
I hope you're feeling better after your recent illness!

Well, I see what you mean about every platform supporting RDP. I just discovered the free Microsoft Remote Desktop for Android in Google Play Store. It might replace TeamViewer as my favorite way to access my server and my other computers remotely from my phone and tablet. (It wasn't available when I got my Samsung Galaxy S3.) You can switch between mouse cursor and touch control of the remote desktop, so you can actually put the - ugh - Modern Start screen and apps in Win 8/2012 to practical use with an Android device.

(Tried to post this as a support contact, but the contact web pages produce only an error right now.)
 
With Scanner v 2.4.0.2929 in Essentials Experience VM of Windows Server 2012 R2 Essentials, Scanner completes a scan of a 2TB Seagate drive with no errors, including a file system check, then it starts scanning all over again, and the status still erroneously says that portions of this disk have never been checked for problems. The same outcome occurs when scanning with v 2.4.0.2928 on the host.  Currently, that particular pass-through drive is working okay in DrivePool, and there are not SMART errors or warnings.
 
Earlier, a couple of days ago, the VM started to boot slowly and everything became wonky until I set the DrivePool service to manual.  With DrivePool service off, all seemed speedy and normal again.  But I brought all the DrivePool drives online on the host and ran a chkdsk on each.  On the particular drive in question, chkdsk /f couldn't complete and produced Windows event id 153 warnings.  Also, SMART showed 2 Current Pending Sector Count and 2 Uncorrectable Sector Count. I then ran the Scanner scan on it in the host, and after completion, it said that the file system was damaged and needed to be repaired.  Of course, Scanner then relies on chkdsk to do that (unfortunately, there's little feedback to chkdsk when you go through Scanner, whereas, you do get appropriate feedback when using the cmd line).  (Whatever happened to the Scanner feature to salvage data from damaged sectors or to state that there's no data on the damaged sectors?)  After hours of no feedback and the repair process still looking like it was underway, I stopped the process.  Since then, no performance issues with that drive, no SMART warnings (SMART even shows 0 Reallocated Sectors Count), but Scanner continues to loop the scan as described above.
 
I know the drive is "iffy", but why isn't Scanner working correctly on it?
 
Could use a little improvement in the repair interface through Scanner, which currently leaves the user in the dark as to its progress.
 
Edit: Since the Contact webpage is working today, I created a ticket on this.