Hadders,
What is the PBA and serial number of your controller?
We have seen this issue, but the module we saw this with was a very old hardware version. So far, our engineering suspects it to be a combination of earlier SROMBSASMR and latest firmware (1.40.232-1007) . We are investigating. The customer expereincing this issue with the SROMBSASMR rolled it back to an earlier firmware (1.40.32-0580) and it was fine. 1.40.92-0746 is the previous release if you want to try that.
Regards,
John
Hi,
Thanks that has indeed sorted it (rolling back to the version specified). 1.40.92-0746
Not sure what you mean by the PBA? 0x8086, 0x3508?
The serial number is SV10804634
It's a SROMBSASMR with 128MB.
Let me know if there's anything else I can supply you to help diagnose the cause...
I had also flashed the enclosure to the latest firmware that was available for it too.
H
Hadders,
Just to confirm, with firmware 1.40.92-0746 you can now set your virtual disk size and complete the setup?
The PBA (Printed Board Assembly) number consists of nine (9) alphanumeric characters in the following format:
XXXXXX-XXX
The serial number precedes the PBA number on the sticker.
I couldn't find the serial number you provided in our database. Is there a different one present on the PBA sticker?
John
Yes, once I flashed it back using the -NoVerChk option to force the downgrade, it worked as expected.
It even "prefilled" the container size, when it initialised.
The other version, simply left that field blank and no matter what value you plugged in, would not accept it.
I got that Serial Number from the BIOS screen on the RAID controller, under "Controller Properties".
I'm in Australia if that makes any difference?
I have some install work on Saturday, so I'll take a look in the system then and see if I can spot the sticker and its numbers.
Thanks.
