StableBit Scanner cannot read S.M.A.R.T. / temperature for two WD80EFPX drives behind Asmedia 106x SATA Controller, but another tool can

[MarcoTangerino]

Hello,

I am having an issue with StableBit Scanner not being able to read S.M.A.R.T. / temperature / age information for two specific drives.

StableBit Scanner 2.6.13.4088 shows both drives as Healthy, but temperature and age are missing. The lower panel says:

"The on-disk S.M.A.R.T. check is not accessible. Drive temperature and operating parameters are not available and will not be monitored."

However, another disk monitoring tool installed on the same server can read the missing S.M.A.R.T. information and temperature correctly from those same drives.

Affected drives:

- Drive E:
  Model: WDC WD80EFPX-68C4ZN0
  Serial: WD-RD2EU9HH
  Size: 8 TB / 7.28 TiB
  Windows BusType: SATA
  Windows HealthStatus: Healthy

- Drive F:
  Model: WDC WD80EFPX-68C4ZN0
  Serial: WD-RD3BEV6G
  Size: 8 TB / 7.28 TiB
  Windows BusType: SATA
  Windows HealthStatus: Healthy

Windows detects both disks as healthy SATA HDDs.

PowerShell Get-Disk reports:

Disk 6 — WDC WD80EFPX-68C4ZN0 — Serial WD-RD2EU9HH — BusType SATA — Healthy
Disk 7 — WDC WD80EFPX-68C4ZN0 — Serial WD-RD3BEV6G — BusType SATA — Healthy

PowerShell Get-PhysicalDisk reports both as:

MediaType: HDD
BusType: SATA
HealthStatus: Healthy
OperationalStatus: OK

Device Manager, using “Devices by connection”, shows both affected drives under this path:

Intel(R) PEG10 - 460D
 -> PCI Express Upstream Switch Port
 -> PCI Express Downstream Switch Port
 -> Asmedia 106x SATA Controller
    -> WDC WD80EFPX-68C4ZN0
    -> WDC WD80EFPX-68C4ZN0

The system has the following storage controllers:

Get-CimInstance Win32_IDEController:
- Standard SATA AHCI Controller — OK

Get-CimInstance Win32_SCSIController:
- Microsoft Storage Spaces Controller — OK
- Asmedia 106x SATA Controller — OK, multiple instances
- Standard NVM Express Controller — OK
- Covecube Disk Enumerator — OK

Other drives connected to other Asmedia 106x SATA Controller entries appear to report correctly in StableBit Scanner. The issue seems specific to these two WD80EFPX drives, this controller path, or the way Scanner queries S.M.A.R.T. for them.

The affected drives also appear in Windows as SCSI\DISK devices, even though Windows reports them as SATA:

SCSI\DISK&VEN_WDC&PROD_WD80EFPX-68C4ZN0\7&2EAFE890&0&000000
SCSI\DISK&VEN_WDC&PROD_WD80EFPX-68C4ZN0\7&2EAFE890&0&010000

There are also old phantom entries for the same model:

SCSI\DISK&VEN_WDC&PROD_WD80EFPX-68C4ZN0\7&76D6727&0&000000
SCSI\DISK&VEN_WDC&PROD_WD80EFPX-68C4ZN0\7&76D6727&0&010000

These old entries show:
Status: Unknown
Present: False
Problem: CM_PROB_PHANTOM

This looks like a possible StableBit Scanner Direct I/O / S.M.A.R.T. query compatibility issue with WD80EFPX drives behind an Asmedia 106x SATA Controller, because another tool can read the same S.M.A.R.T. data successfully.

Could you please advise what I should try?

Should I enable any specific Direct I/O option?
Should I try Smart / IgnoreChecksum in the advanced settings?
Is there any diagnostic log, troubleshooting report, or test build that I can provide?

Attached screenshots:

1. StableBit Scanner showing the two WD80EFPX drives without temperature / S.M.A.R.T. information.
2. Device Manager showing both affected WD80EFPX drives under Asmedia 106x SATA Controller.
3. Screenshot from another monitoring tool showing that S.M.A.R.T. / temperature can be read correctly from the same drives.

Thank you.