TimoJ

That option was well hidden... I cleared the status, Scanner very quickly rechecked the disk and returned the same file system damaged message. There appears system log VSS error every time I run Scanner recheck. I then removed my drive mappings from a folder in C-drive (I have removed drive letters from pool drives and mapped them under one folder), cleared status and now Scanner runs (much longer than when the error happened) without error and returns with healthy filesystem. I remapped the drives to the same main folder (with new subfolders) and Scanner still runs correctly. So looks like something had gone wrong with those mappings, it probably happened few weeks ago (and I just happen to have 14 days checkdisk schedule) when I had that another problem with Scanner (beta) and reinstalled it and Drivepool few times.

Suddenly I got file system damaged Scanner message from my server's boot drive. Still chkdsk finds no errors and /f or /f/ r/ finds nothing to repair. There are no smart or surface errors. The drive is an Intel SSD, 1% used lifetime. How can I rescan or reset Scanner's file system scan results from this drive? Looks like it's not doing a fle system rescan and just shows the same message. Scanner version is 2.5.1.3062. Application log shows 4 scanners errors and it has saved error reports. I have attached them. ErrorReports.zip

I have opened ticket/contact request 8710744.

I removed 3091 and reinstalled 2.5.1.3062 and it shows all disks as checked. I didn't delete any userdata etc. This is weird, looks like 3091 doesn't use the same data for disk check info?

Here's scanner log. I started a manual scan, waited few seconds, stopped scanner and copied the log. Scanner.Service-2015-04-06.zip

I reinstalled 3091 beta and again all disks changed to not checked (I put them earlier manually to checked state). And the same error appears when scanning disks with the LSI controller. Maybe it was this change that causes the read errors: [issue #13478] Use the sector count reported by IDENTIFY if the sector count reported by Windows is smaller. I'll upload logs soon.

Hello, What was changed in latest Scanner betas? I have used 2.5.2.3079 without problems and now installed 2.5.2.3091. After install I noticed that it had removed all disk check statistics i.e. disks switched to unchecked. And now when the Scanner runs, it's not able to scan disk sectors from drives that are connected to LSI 9650SE-4LPML controller. It just returns errors on all sectors, drives are 6TB. Drives (4TB and smaller) that are connected to mainboard Intel controller work without errors. I then unstalled 3091 and reinstalled 2.5.2.3079 and I still get the same problem. So I uninstalled again, removed all scanner's user data folders, installed 2.5.1.3062 Release and now surface scan works again. Actually I'm not sure when the change was made, maybe I had no surface scan runs during my usage of the build 3079 and the change happened earlier.