On-disk SMART check is not accessable. Etc. Etc.

[gratch]

So DirectIOTest is working, and can read the device through scsipassthrough but fails with ata passthrough and stablebit scanner log says online tells it to use atapassthrough which fails, do you really need me to pull the log where it says to do so?  Anyways, because of atapassthrough failing period, unsafe methods and no wmi do not effect this issue.  From my understanding of how this all works this is something you have to fix on your end and then let me know and then I restart the service?  Controller is a 8 bay syba jbod usb 3.0 beyond that I don't know.

Amazon Link, IDK

HDDs are just a mix of Western Digital Hdds.  4x HGST HUH721010ALE600 and 4x HGST HUS728T8TALE6L4

[Christopher (Drashna)]

Have you tried the unsafe Direct I/O setting, as well as the "nowmi" option?   Both of these are in the advanced settings:
https://wiki.covecube.com/StableBit_Scanner_Advanced_Settings#Advanced_Settings

[gratch]

“Anyways, because of atapassthrough failing period, unsafemethods and no wmi do not effect this issue.”

As reported in the initial post that option has no effect because the online call the program does for identification either doesn't have a reply or says to use ata passthrough.  These options do not change the proceedure in the log, and seemingly have no effect.

 I actually have 2 of these jbods with different controllers but the older one correctly chooses to use scsi passthrough and as such I get smart data from that jbod, its just kinda fristrating I know the point of failure and cannot do anything about it but wait on replies and hope you add this controller to the database (and if you need more info to do so I am happy to provide, I just assume having the VID/PID is enough) the program uses so I can get the data or accept learning to live without it.  It just seems odd to me that there isn’t a user option as a final backup solution to simply let us choose the method of communication manually.  I mean lets be real here, no one using covecube software is a below a poweruser on computing.

 

Scanner.Service.exe    Information    0    [DiskInfo] Creating '\\.\PHYSICALDRIVE8'...    2024-10-09 05:57:38Z    20762143840335
Scanner.Service.exe    Information    0    [Cloud] Looked up USB pass-through method for 'VID=152D, PID=0578, REV=0114'. SmartIoctl (Cloud:SmartIoctl)    2024-10-09 05:57:38Z    20762144563972
Scanner.Service.exe    Information    0    [DiskInfo] Querying disk identification via. ATA...    2024-10-09 05:57:38Z    20762144567896
Scanner.Service.exe    Information    0    [DiskInfo] Could not query for disk identification via. ATA.    2024-10-09 05:57:39Z    20762151279852

That would seemingly be my point of failure right there.  I just don't really know, I just know that if it did this,

Scanner.Service.exe    Information    0    [DiskInfo] Creating '\\.\PHYSICALDRIVE15'...    2024-10-09 05:57:15Z    20761909593001
Scanner.Service.exe    Information    0    [DiskInfo] Querying disk identification via. ATA...    2024-10-09 05:57:15Z    20761910155646
Scanner.Service.exe    Information    0    [DiskInfo] Got disk identification (PassThroughMethodUsed=ScsiPassthrough). Comparing disk signatures...    2024-10-09 05:57:15Z    20761910760425
Scanner.Service.exe    Information    0    [DiskInfo] ATA query accepted. Disk signature ignored.    2024-10-09 05:57:15Z    20761910766119
Scanner.Service.exe    Information    0    [DiskInfo] Starting performance sampling...    2024-10-09 05:57:15Z    20761910774444

I would have smart data. The second c/p is from the older jbod.