Database can not start after reordered hard drives
Details
| Detail name | Value |
|---|---|
| Changelog Number | 17673 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 7.1.0 |
| Fix Versions | Exasol 7.1.23 |
| Resolution Date | 2023-09-11 |
Background
The Exasol data node boot process recognizes when hard drives appear in a different order than the one configured for the node in EXAoperation. This can happen any time a node is restarted, e.g. due to changes in the underlying hardware or even random chance.
Description
In node configurations with a dedicated OS disk (as per Docs: Storage Overview), the cluster might fail to boot correctly depending on the specific order in which the disks are enabled during boot. In these cases, the database is not able to start.
This is generally indicated by the message HDD mount failed in the EXAoperation monitoring log.
Workaround
Contact support for a workaround.
Fix
In this scenario, the nodes are able to boot correctly, and the database is able to start.
