Reset to device, \Device\RaidPortXX, was issued

Thank you. I can see the problem now and will try to fix this in the next (Beta) build.
 
Ok thanks

My ASM225CM shares the same firmware as ASM235CM but USB 3.x Gen2 is disabled at the silicon level via some factory lockouts
I have updated its firmware and am going to changed its PID i dont like that it uses a 105x pid and id's its self as such
Should i use ASM235CM PID (i dont know ASM225CM PID) to make sure the fix is applied with HWiNFO?
I would think yes

I hadnt done it yesterday so you got the actual PID and such
 
Yes, according to my analysis some of those controllers don't properly handle certain ATA pass-thru commands and instead treat them as a reset (ehm).
So HWiNFO has to skip some commands (e.g. ATA ID or ATA Statistics LogPage) for those controllers.
I have put all such known controllers on an internal black-list and this requires knowledge of the USB VID/PID for each of them.
 
I just remoted into my N100 that has a Realtek 9201R plugged into it
no errors

and plugged in the Orico NGFF to Sata ASM225CM (With ASM235CM PID and firmware)
on the pc im using atm also no errors

next time i go upstairs i will grab a few drives test it more to make sure
 
I have just noticed another problem :)

MY JMS583's dont read the smart data for some reason
and show in scsi instead of nvme see images

1.png2.png3.png4.png5.png6.png7.png
 

Attachments

Should be fixed in:
 
Hi yes the smart data is pulled now thanks

there seems to be some bugs though
hwinfo seems to think drive a usb stick is a partition on some drives
also SCSI show's up for two of the three JMS583's with bad info
 

Attachments

  • 1.png
    1.png
    357.3 KB · Views: 9
  • 2.png
    2.png
    108.2 KB · Views: 8
  • 3.png
    3.png
    112.2 KB · Views: 6
  • 4.png
    4.png
    109.2 KB · Views: 5
  • 5.png
    5.png
    150.9 KB · Views: 4
  • 6.png
    6.png
    152.8 KB · Views: 4
  • 7.png
    7.png
    152.2 KB · Views: 6
  • 8.png
    8.png
    123.2 KB · Views: 6
  • 9.png
    9.png
    117.8 KB · Views: 9
Thanks Martin

When closing sensor status the last two builds stall when clicking x for about a second
and crash about 50% of the time

Drive letters are correct in nvme and sensor status now
still wrong in SCSI
only two of 3 JMS583 showing in SCSI

the debug file it didnt crash that time
 

Attachments

  • 0.png
    0.png
    202.4 KB · Views: 4
  • 1.png
    1.png
    118.7 KB · Views: 3
  • 2.png
    2.png
    115.8 KB · Views: 3
  • HWiNFO64.rar
    HWiNFO64.rar
    100.1 KB · Views: 3
Debug file with crash had to open Sensor Status twice whilst HWinfo was running to get a crash

Opened HWinfo opened Sensor Status and closed Sensor Status = no crash
Opened Sensor Status and closed Sensor Status = Crash
 

Attachments

  • HWiNFO64.rar
    HWiNFO64.rar
    100.6 KB · Views: 3
  • Untitled.png
    Untitled.png
    474.7 KB · Views: 3
It looks like access to the JMicron controller becomes blocked sometimes.
Are you perhaps using some other application that's also monitoring those drives?
Can you please enable the Profiling Time column and check how much time the JMicron SMART sensors take?
 
Last edited:
I dont think there are any processes blocking access

My install is very clean without breaking anything (I would like to clean alot more out but dont want to break os features)

No VBS
Minimal Microsoft Chaff
No Edge or webview2 etc (official removal GPDR)
No Defender etc.. (Policy + DISM /online /disable-feature /featurename:Windows-Defender-Default-Definitions -NoRestart)
No startup background processes and such

Im not sure what is causing the crashes and lockups monitoring is delayed sometimes
when the JMS583 goes into low power mode and power's the drives down (10 Min Power management in the JMS583 Firmware Light goes from green to blue when the drive is powered down)
when the drive is accessed they wake back up

HD Sentinel doesnt lockup/crash/slow down when probing them when they are asleep (It will just fail to pull the smart data until the drives are accessed)

The lockup's/slow opening seems to be debug mode related
the Crash seems build related

03:50 JMS583's Plugged in
06:10 First HWiNFO64 Crash


Ok after some further testing
the JMS583 being in low power mode isnt cauing the crashes
that just stops SMART being able to be accessed the same as HD Sentinel which im fine with i can always wake them myself

When the drives are sleeping HWiNFO no longer crashes randomly when closing the sensor panel..

First 11:55 is me testing what does and doesnt cause issues
First Crash at 11:55 ish

 

Attachments

Last edited:
Thanks for the detailed analysis. I will try to resolve this in the next version which is planned for today.
Please try new v8.14.
 
Last edited:
Thanks im not on that pc atm as im upstairs
so will test later and report back

I had something interesting turn up just now that you may or may not be interested in

Its an AXE Speedy+ 1TB USB Stick which is a turnkey Phison USB drive (made by phison and sold badged to oem's)

I have older models of this AXE Speedy 128GB x 2 & AXE Superb 128GB x 1

USB\VID_13FE&PID_6000
with the older gen id as Model: USB DISK 3.0 PMAPPMAP1234
USB\VID_13FE&PID_6500
the one that arrived today was Model: USB DISK 3.2 PMAPPMAP1234
Drive Firmware Revision: UHFM00.5

AXE Speedy & AXE Superb
Model: USB DISK 3.0 PMAPPMAP1234
Size : 118409 MB
Controller : PS2308 (from firmware) (PS2251-08)
Bank00: 0x98,0x3c,0x98,0xb3,0x76,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die

AXE Speedy+
Model: USB DISK 3.2 PMAPPMAP1234
Size : 953869 MB
Controller : PS5017 (from firmware) (PS2251-17 Phison U17)
Bank00: 0xad,0x89,0x29,0x53,0x0,0xb0,0x0,0x0 - Hynix 3dv6-128L TLC 16k 2048Gb/CE 1024Gb/die

The older AXE Speedy & AXE Superb which use the Phison PS2308 Controller support trim which is neat
The AXE Speedy+ which use the Phison PS5017 support uasp + trim + the nvme feature set so you can nvme se it pull smart data nand writes temp etc

HWiNFO64 pulls the data just fine

71NCKf1mb+L._AC_UF1000,1000_QL80_.jpg
 

Attachments

  • a.png
    a.png
    440.7 KB · Views: 6
  • b.png
    b.png
    360.1 KB · Views: 6
  • c.png
    c.png
    209.1 KB · Views: 6
Last edited:
I have just tested JMS583 with the latest build
all is working great no crashes and such detection 100% also

With regards to the USB sticks in the last post i was mistaken they dont share the same pid

USB\VID_13FE&PID_6000 = Phison PS2308 (PS2251-08)
USB\VID_13FE&PID_6500 = Phison PS5017 (PS2251-17) Also known as Phison U17
 

Attachments

  • Untitled.png
    Untitled.png
    217.5 KB · Views: 5
Thanks for your feedback!
I will add those USB IDs into database, so the devices will be properly recognized.
 
Back
Top