Doremi IMS1000 - Manual (Page 290)

IMS.OM.002949.DRM Page 290 of 320 Version 1.7
Doremi Labs
A hardware issue with FPGA or its associated component can also trigger a FIPS lock, and the
following message will be seen on the serial log:
IMB: loading firmware: IMS-FW 4.1.3-3.
IMB: Firmware CRC is GOOD.
IMB: prog_fpga(6589/3609899), FPGA_CONFIG_STATUS
IMB: load_firmware(), Can't load FPGA firmware, reason: 1
IMB: clarity_dev_ioctl(), Can't load firmware.
...
[Jan 1 00:00:01 2009][INFO ]: firmware integrity seltest succeeded.
[Jan 1 00:00:01 2009][ERROR]: FPGA AES selftest failed.
[Jan 1 00:00:01 2009][ERROR]: FIPS lock
...
17.10.3 Solution
This issue was fixed in BOM revision E4 . The solution for a customer would be to RMA the
unit.
17.11 No power
17.11.1 Description
There is no power on the IMS. All LEDs are off.
17.11.2 Identification
No errors in the logs.
17.11.3 Solution
This issue was fixed in BOM revisions E9 and E10. The solution for a customer would be to
RMA the unit.
17.12 Unit Not Booting When Drives Are Installed
17.12.1 Description
The IMS unit will not boot up completely when the HDDs are installed. Unit only boots up
completely when HDDs are not plugged in.
17.12.2 Identification
If you have access to the CPU serial logs, you can see that the unit does not boot
completely and is stuck after the filesystem is mounted on md0/md1.
17.12.3 Solution
To recover the unit, boot the unit with one drive only, then hot plug the two other drives and
re-init the RAID:
1. Boot with only one drive inserted.
2. Wait 5 min for unit to boot completely.
3. Insert the other 2 drives.
4. SSH into IMS1000.
5. Run ‘mount -o rw,remount /’.