During the recent update from IEOD 1.27 to 1.28, we uncovered a critical boot issue affecting systems configured with RAID1. Here’s what you need to know to keep your operations running smoothly:
What’s the Issue?
Some devices with RAID1 may get stuck in an endless reboot loop after the update - even though the RAID array itself remains healthy and synchronized.
What Happened?
Our investigation revealed a tricky interaction between the boot process, RAID configuration, and disk boot order. Under certain conditions, the system might try to boot from the "wrong" disk during firmware activation, causing an inconsistent update state and blocking a successful startup.
Current Status
The issue has been reproduced, analyzed, and a workaround has been validated on affected customer systems.
Good news: Devices were recovered without reinstallation and all customer data stayed safe!
Quick Fix / Workaround
If your RAID1 system won’t boot after the update:
This workaround has been tested and confirmed to restore affected systems.
Our Recommendation
Before updating any RAID1-configured systems:
Huge thanks to everyone involved in the rapid root cause analysis, validation, and customer support. Your teamwork helped avoid reinstallations and minimized downtime for our customers. 💪🏻🚀