Announcements

If you're experiencing problems with the software, the best way to get ahold of us is to head to https://stablebit.com/Contact, especially if this is a licensing issue.
Issues submitted there are checked first, and handled more aggressively. So, especially if the problem is urgent, please head over there first.

See if the SMART Attributes option lights up (green check/tick mark next to it). If it does, click on the elipse button, and make sure it displays info (there should be a "table" type format that lists a bunch of values).

If it doesn't display this info, see if checking the Unsafe Direct IO option works. If not, then the drive isn't passing on SMART data.

If it is, then you may need t enable the setting in StableBit Scanner.

Share on other sites

I have the exact same problem. Checking the disk with the I/O Test Utility shows all smart values. But the Scanner does not. What setting do I need to change to show the values? Is a reboot necessary?

I am using version 2.5.1.3062.

Thanks.

Does it show the SMART Attributes without checking the "Unsafe direct IO" option?

If so, then let me know how the drive is connected and and what model it is. And on any drive that has the "SMART details" option, check the "Submit to BitFlock" option, and post the ID it generates here.

And in either case, could you install the latest public beta build and see if that helps?

Share this post

Link to post

Share on other sites

I have attached some screenshots to this post. With the Direct I/O Test tool all SMART values are read and shown (WMI and direct I/O) without checking the unsafe I/O option. The scanner shows an empty dialog. I have uploaded the data to BitFlock (see screenshot for ID). The drive is attached directly to a SATA-port on the mainboard. I have also attached a Samsung 850 Pro to a port on the mainboard and this one shows all values with no problems.

I have not tried the beta yet, but will do that as soon as possible. If you need more information, please let me know.

Share this post

Link to post

Share on other sites

I have installted the Beta of the scanner and it just went crazy! I remember that I have installed it before and removed it for that reason. Take a look at the screenshot. It reports sector errors for a couple of hard drives and DrivePool starts to evacuate the drives. The previous version did not report any errors even after multiple scans. I don't know what is going on, but I need to remove the beta to keep the system save.

PS: As you can see the "damaged" drives are connected to a RAID controller, but are configured as single disks. One of the connected drives does not seem to be affected. I also did a fresh reinstallation of the Scanner Beta, but it did not change. Scanner is still seen damaged sectors and while scanning on drive (see screenshot) and doing this very, very slowly, the number of unreadable sectors increases.

Share this post

Link to post

Share on other sites

I have installted the Beta of the scanner and it just went crazy! I remember that I have installed it before and removed it for that reason. Take a look at the screenshot. It reports sector errors for a couple of hard drives and DrivePool starts to evacuate the drives. The previous version did not report any errors even after multiple scans. I don't know what is going on, but I need to remove the beta to keep the system save.

PS: As you can see the "damaged" drives are connected to a RAID controller, but are configured as single disks. One of the connected drives does not seem to be affected. I also did a fresh reinstallation of the Scanner Beta, but it did not change. Scanner is still seen damaged sectors and while scanning on drive (see screenshot) and doing this very, very slowly, the number of unreadable sectors increases.

I'm not sure why it would be doing that. But clearly, it's erroring out during the surface scan. My guess is that the way it's reading it must have changed and isn't compatible with the RAID controller.

It's a 3Ware 9650 card, correct?

To clarify, this is only happening to drives on the RAID controller, correct?

And only happening to some of the disks? If so, could you right click on one of the disks and run a "burst test" and see if that completes fine.

And do you know specifically what build this started with?

I hate to ask, but if you could isolate which build this started with, that would greatly help to identify what is causing the issue.

Share this post

Link to post

Share on other sites

Ok. I have uninstalled the scanner completely, going to the registry and the folders on the system drives. After installing the latest beta the scanner now seems to work without reporting the drive errors. So I am not sure what was happening there, but maybe there was a problem with an older installation. Anyway, we can get back to the initial problem. Unfortunately the smart data is still not showing in the scanner window.

Update:

The problem with the error report and damaged disk remains. It does not show immediately a damaged drive, but as soon as you start a surface scan, damaged sectors are found. I have tried it only with one the drive connected to the controller. I have also found out that with scanner versions up to 2.5.2.3078 BETA the surface scan is ok. Version 2.5.2.3079_BETA shows errors on the first sectors scanned. Both versions are from February 15th this year. Going back to 2.5.2.3078 beta everything scans normally withour errors.

Share this post

Link to post

Share on other sites

That is correct. Version 3078 works properly. I am using the AMCC 3Ware 9650SE-8LPML controller card, which is listed in Windows 10 as "LSI 3ware 9650SE SATA RAID Controller" and has the Hardware ID "PCI\VEN_13C1&DEV_1004&SUBSYS_100413C1&REV_01".

Share this post

Link to post

Share on other sites

That is correct. Version 3078 works properly. I am using the AMCC 3Ware 9650SE-8LPML controller card, which is listed in Windows 10 as "LSI 3ware 9650SE SATA RAID Controller" and has the Hardware ID "PCI\VEN_13C1&DEV_1004&SUBSYS_100413C1&REV_01".

Thank you.

I've flagged this issue for Alex (the Developer) and he'll look into it soon.

Share on other sites

That is correct. Version 3078 works properly. I am using the AMCC 3Ware 9650SE-8LPML controller card, which is listed in Windows 10 as "LSI 3ware 9650SE SATA RAID Controller" and has the Hardware ID "PCI\VEN_13C1&DEV_1004&SUBSYS_100413C1&REV_01".

Could you grab the BitFlock ID from the system?

Open the SMART details on any of the disks (in stablebit scanner), and check the "Submit to bitflock" option. Post the ID it generates here.

Additionally, you'll need to enable an Advanced setting to get this working properly.

Click on the Settings button in the toolbar and select Scanner Settings. Enable the Show advanced settings and information option, and hit "OK". You will only need to do this once, from now on, it will always display this option.

Click on Settings, and select the new Advanced Settings and information option. Open the Configuration Properties tab. You will find a list of all the settings here, organized into section. Find the "DirectIO" section, and check the "DoNotCorrectSize" option. You'll need to reboot the system after doing this (or restart the service).

Click on the Settings button in the toolbar and select Scanner Settings. Enable the Show advanced settings and information option, and hit "OK". You will only need to do this once, from now on, it will always display this option.

Click on Settings, and select the new Advanced Settings and information option. Open the Configuration Properties tab.

Find the "Smart" section and check the "NoWmi" option.

Reboot the machine and see if that helps.

If not, try doing the same with the "Unsafe" option in the "DirectIO" section (and reboot).