02-03-2019, 10:08 AM
(This post was last modified: 02-03-2019, 11:44 AM by flocke196.
Edit Reason: test result update
)
Hey nuumio,
thank you so much for this update.
I managed to update the controller firmware successfully using the following firmware:
http://ftp.assmann.com/pub/DS-/DS-30104-...181221.zip .
The one I flashed was 1.0.0.1027 bios + 2.3.0.1076 fw. The same version you are using.
It is NOT working with the newest firmware file i found, 1.0.0.1028 bios + 2.3.0.1078 fw. The discs are not recognized anymore and dmesg complains about the controller init going wrong.
So, downgrading the firmware was working for me.
What i have done:
1. Put the controller(mine is a DeLOCK 89395)in a x64/x86 machine
2. Prepare USB Drive with FreeDos and put the files from the archive, mentioned above, in its root.
3. Boot FreeDos from USB Drive
4. Execute "go.bat -y"
5. Wait for flashing to be finished
Attention: THESE STEPS CONTAIN NO BACKUP OF YOUR EXISTING FIRMWARE!
Even with the "go.bat" method, the backup of the SPI flash is not correctly working, so do it at your own risk.
Will do some stress testing and report here.
Edit: First stress test (2x cp from sw-raid1 -> both connected ssds in parallel, results in using all 4 ports of the controller) produced no errors in dmesg.
That was the test, that produced those ugly errors (see above) before on my side.
thank you so much for this update.
I managed to update the controller firmware successfully using the following firmware:
http://ftp.assmann.com/pub/DS-/DS-30104-...181221.zip .
The one I flashed was 1.0.0.1027 bios + 2.3.0.1076 fw. The same version you are using.
It is NOT working with the newest firmware file i found, 1.0.0.1028 bios + 2.3.0.1078 fw. The discs are not recognized anymore and dmesg complains about the controller init going wrong.
So, downgrading the firmware was working for me.
What i have done:
1. Put the controller(mine is a DeLOCK 89395)in a x64/x86 machine
2. Prepare USB Drive with FreeDos and put the files from the archive, mentioned above, in its root.
3. Boot FreeDos from USB Drive
4. Execute "go.bat -y"
5. Wait for flashing to be finished
Attention: THESE STEPS CONTAIN NO BACKUP OF YOUR EXISTING FIRMWARE!
Even with the "go.bat" method, the backup of the SPI flash is not correctly working, so do it at your own risk.
Will do some stress testing and report here.
Edit: First stress test (2x cp from sw-raid1 -> both connected ssds in parallel, results in using all 4 ports of the controller) produced no errors in dmesg.
That was the test, that produced those ugly errors (see above) before on my side.
