Question *STABLE* NVMe - USB Adapter?

[Andalu]

It's an "M" key so, most likely, this is another wrong ID assignment or a bad recognition by the OS (but that's improbable).

 

[papapapapapapapababy]

strange. or mabye they use another chip, this guy

Francois Gervais

https://www.amazon.ca/QNINE-Enclosure-JMS583-Included-Samsung/product-reviews/B07JC2ZTNV/ref=cm_cr_othr_d_show_all_btm?ie=UTF8&reviewerType=all_reviews also bought an orico QNINE NVME SSD Enclosure and its reporting the same idhttps://www.amazon.ca/QNINE-Enclosure-JMS583-Included-Samsung/dp/B07JC2ZTNV/ref=cm_cr_arp_d_product_top?ie=UTF8

Device 015: ID 152d:0562 JMicron Technology Corp. / JMicron USA Technology Corp

 

[apoelistasaudi]

Already reported here

Confirmed. So this is what firmware 2.0.9 fixes.

So what I did.

went to friwmare app folder 2.0.8 Jeyi i9 with my previous customized published ini.
Changed the following parameter of ini:
FwFileName=JMS583_0209.bin
StandbyTimer=1
Added the bin file from firmware 2.0.9 as posted above and renamed that to JMS583_0209.bin

Flashed with jeyi i9 firmware 2.0.8 included app.

Did not want to flash with firmware 2.0.9 app because of more configuration settings.

My Orico now always stays cool and disconnect every 1 minute. Will do more tests tomorrow with 3.1 Gen 2.

At the moment I give it a 9/10 rating however can go to 10/10 if benchmarks with usb 3.1 gen 2 are also good.

Thanks for sharing.

 

[Andalu]

@papapapapapapapababy
I still think it might be a wrong ID. Here the features of the JMS562 chipset: https://www.jmicron.com/products/list/12

 

[apoelistasaudi]

That is why I flashed firmware 0209 with 0208 app. (same ID) I did not want to use JMS562 app. That solves my hesitation in flashing.

At the moment my enclosure is 44oC in standby. Goes to 47oC if waken and then reverts back to 44oC Seems better than firmware 0208 because it always disconnect if no use after a minute.

I prefer to keep this firmware at the moment.
I am reporting that my way app gives JMS583 ID same as before.

 

[Andalu]

That is why I flashed with firmware 0209 with 0208 app. (same ID) I did not want to use JMS562 app. That solves my hesitation in flashing.

the tool included in the 0209 firmware automatically detects the correct chipset:

 

[apoelistasaudi]

Only if one loads the correct ini file. Then both methods become the same. Dont try without. I still prefer my way.

 

[papapapapapapapababy]

whatever the hell it has inside i can confirm its working GREAT. could be better * disk is half full, plus i fumbled long in the background to find out the fkng temp software in the middle of the test, for reference the orico from an oline review at the bottom . the fideco first

 

[apoelistasaudi]

My write speeds are terrible. This firmware is not meant or designed for my orico enclosure. Will try to turn off bitlocker and recheck.
Any views?
read speed 934
Write speed 131

removing bitlocker is the same

 

[Andalu]

@apoelistasaudi
it seems the same degradation in writing performance which randomly occured in my tests up until a while ago and that maybe the latest firmware hasn't solved.

 

[Andalu]

Here my tests with the RTL9210 chipset (only pcb without brand to connect to USB port type 'A', no enclosure):


The standby mode is activated after one minute. No disconnection even if in idle. The safe-remove command does not work properly because its LED is always on (for one minute, then it goes into standby mode).
I'm still waiting for the orico enclosure with the RTL9210B.

 

[apoelistasaudi]

@apoelistasaudi
it seems the same degradation in writing performance which randomly occured in my tests up until a while ago and that maybe the latest firmware hasn't solved.

My tests were consistent low. Dont have a clue

 

[Andalu]

My tests were consistent low. Dont have a clue

just a month ago, the same happened to me after the firmware update to version 2.0.8, please see at #149
My latest tests for the JMS583 with the firmware 2.0.9 are good as never before but I'm not sure it will always be like this. Maybe next time I'll have the same problems once again.
A firmware downgrade would be a good thing but I don't know if it can be made. When I tried, I couldn't.

 

[apoelistasaudi]

What is

just a month ago, the same happened to me after the firmware update to version 2.0.8, please see at #149
My latest tests for the JMS583 with the firmware 2.0.9 are good as never before but I'm not sure it will always be like this. Maybe next time I'll have the same problems once again.
A firmware downgrade would be a good thing but I don't know if it can be made. When I tried, I couldn't.

What puzzles me even more is that I get the same write disk mark speed with my 3.1 gen 1 usb port (laptop). It is like it is locked at that speed. Tried another cable I have. ----- Same results.

However my read speeds with gen 2 usb 3.1 are not as good but not bad either at 950MB/S (fimrware 2.0.8 peaked 1050MB/S)

I think this firmware solves a problem but creates a new one. Will try to downgrade. Write speed is terrible.

 

[Andalu]

I think you have already compared the JMMassProd.ini used to update the firmware to version 2.0.9 with 2.0.8.
If it can be help, this is mine used in the updating:

Spoiler: JMMassProd.ini

[setting]
USBWritePerformance=0
USBReadPerformance=0
ShowRWPerf=1
WriteFileName=test.bin
ProductModel=JMS583
WRLoop=0
RWDataSize=100
EEPROMOnly=0
SupportODD=0
CheckMaxSn=0
MPVersion=1
MPSafeRemove=0
MPEEPROMToLog=0
PerfShift=1
MPPassLabel=1
MPAutorun=0
MPResetWait=30
MPSnAToZ=0
MPPortReset=0
EnBarcodeMode=0
EnKey0SafeRemove=0
EnEPPTypeC=0
EPPPowerGPIODelay=1000
EPPPowerOnDelay=30000
EPPPowerOffDelay=1000
SCSITimeout=30
[JMEXECUTE]
CapacityCustomize=0
Capacity=0
FreeSpace=3998735138816
FreeSpaceRange=0
EnFreeSpaceCheck=0
EnPartition=0
EnFormat=0
EnRWTest=0
EnEEPROMUpdate=1
EnFWUpdate=1
DiskFormat=0
DiskLabel=NVME
FwFileName=JMS583_0209.bin
FmtSecPerClus=-1
EnVenderCheck=0
EnUSB30Check=0
EnSWCopy=0
SwImgPath=
SwDstFolder=
EnFWCheck=0
EnFolderCompare=0
bAdvenceCompare=0
EnCloneProduct=0
EnUSB31Gen2Check=0
nPartitionTblFmt=0
[JMEEPROM]
TableType=3
MapToHDName=1
StrBFromHDSN=0
VenderID=152D
ProductID=0583
StringA=JMicron
StringB=USB to NVME Bridge
StringC=JMicron
String3=DD56419883893
StringAInc=0
StringBInc=0
String3Inc=1
FlashType=-1
StringMaxSn=0
EEPROMRetry=0
JMB509REU=0
JMB509WDHDD=0
StandbyTimer=5
JM539PWMode=0
ProductRevsion=0000
ODDSize=0
EnMultiSec=0
EnOver2TBMulLun=0
EnManuProdStrSourceCtl=1
EnInquiryStrSourceCtl=1
EnJMS561StandbyTime=1
EnSNfromHDDSN=0
BarcodeLength=16
[JMEEPROMVERIFY]
VenderID=152D
ProductID=0583
StringA=JMicron
StringB=USB to NVME Bridge
DiskName=JMS583
EnCheckDiskName=0
VolumeLabel=UsbDisk
EnCheckVolLabel=0
HDDFwRev=01.01V01
EnCheckHDDFwRev=0
[576PDswitch]
EnPD=0

 

[apoelistasaudi]

The two differences we have are the
1. Serial number
2. StandbyTimer=1

reverting back to firmware 2.0.8 did not solve the write speed. Back to 2.0.9

The way I see it I have 3 steps:
1. either I should reformat the disk
2. Change standbyTimer to 5 mins and a similar serial as yours.
3. Flash firmware on USB 3.1 Gen 2 (used gen 1)

so will try tomorrow step 3 and leave step 1 as last option. Step 2 did not help.

 

[papapapapapapapababy]

My write speeds are terrible. This firmware is not meant or designed for my orico enclosure. Will try to turn off bitlocker and recheck.
Any views?
read speed 934
Write speed 131

removing bitlocker is the same

that blows i have better numbers with my sata case 573.98 read n 532.20 write * sata 2 sata, and a bit better sata to nvme, edit using the original cable i got shit write speed with the via chipset, great numbers with a super short and fat one, maybe is the cable. edit, updated bios and now it works with both cables, it seems this is all infancy tech...

 

[Andalu]

Just as a little note: I have updated the firmware using a USB3.1 Gen.1 port (see image at #210).
There would be a fourth possibility (if the previous ones didn't help) that you have not tried: update the firmware using the tool included in the 2.0.9 firmware package. It's the only difference between our update operations. But, be very careful to avoid taking a bricked device.

How did you downgrade to the 2.0.8 version?

 

[apoelistasaudi]

I did all my today downgrades and upgrades using the tool in the 2.0.9 folder.
To downgrade you need to use the ini I have posted in a previous post (I think your ini is similar to mine so I dont know why you cant downgrade).

So this step was also tested.

 

[Andalu]

I did all my today downgrades and upgrades using the tool in the 2.0.9 folder.
To downgrade you need to use the ini I have posted in a previous post (I think your ini is similar to mine so I dont know why you cant downgrade).

So this step was also tested.

Thanks for the info. Most likely I have to re-edit the ini file.
Sorry for asking the obvious: have you checked that the trim is actually enabled? I can't think of any other suggestions.

 

[apoelistasaudi]

Yes trim/optimize works. I also check/repair drive but did not help.

Thanks for trying to help.

 

[apoelistasaudi]

I believe that bitlocking the complete drive caused this issue (even after removing) so formatting drive should resolve my issue. Will need to do some online search to verify this
-------------------
Correct.
Formatting solved my issue.
NVME now performs as it should on Gen 1 usb 3.1 Happy now with firmware 2.0.9. Back to 1min standbytimer to keep my enclosure always cool.

My rating has just been updated to 10/10 for firmware with 1min standby customization.

This will be my last firmware update unless there is a problem with bitlocker which most probably corrupted some of my nvme data

Thanks again @papapapapapapapababy for providing the latest and best 2.0.9 firmware.

To Orico support: Thumbs down.

 

[Andalu]

Glad to know it works fine now

As for updating the firmware, I think it's always attractive
even if it doesn't always mean improvement.

 

[papapapapapapapababy]

it was andalu initiative really, initially i was 2 chicken shit 2 try out again and with good reason, almost bricked mi case XD, but it worked fine, glad to help!

 

[apoelistasaudi]

It was a Gem find and the test resulted to a Gem. Thanks @Andalu for testing and confirming compatibility.