Ignite-UX and SAS white paper

7
A problem happens if you were to re-install or recover this system
8
, as the hardware paths would
change to become:
SAS Enclosure Bay # Old Hardware Path New Hardware Path
4 0/4/1/0.0.0.4.0 0/4/1/0.0.0.0.0
5 0/4/1/0.0.0.0.0 0/4/1/0.0.0.1.0
6 0/4/1/0.0.0.1.0 0/4/1/0.0.0.2.0
7 0/4/1/0.0.0.2.0 0/4/1/0.0.0.3.0
8 0/4/1/0.0.0.3.0 0/4/1/0.0.0.4.0
Since Ignite-UX (prior to version C.7.5) is driven by hardware path and device files are driven by
hardware paths, during a non-interactive recovery if the old hardware path was 0/4/1/0.0.0.3.0
(Bay 8), it now would attempt to use the device in Bay 7 instead since that bay is now associated
with the old hardware path.
As of C.7.10, devices under the sasd driver will have their hardware paths correctly mapped:
SAS Enclosure Bay # Old Hardware Path New Hardware Path
4 0/4/1/0.0.0.4.0 0/4/1/0.0.0.4.0
5 0/4/1/0.0.0.0.0 0/4/1/0.0.0.0.0
6 0/4/1/0.0.0.1.0 0/4/1/0.0.0.1.0
7 0/4/1/0.0.0.2.0 0/4/1/0.0.0.2.0
8
0/4/1/0.0.0.3.0
0/4/1/0.0.0.3.0
Important:
An unattended recovery or a reinstallation of a system (using Ignite-UX
releases prior to C.7.5) might overwrite the wrong device causing data
loss unless you take care to use the SAS device in the appropriate bay.
8
Using a version of Ignite-UX prior to C.7.10.