[QUOTE=tkindig;23085]I am configuring a pair of servers as a High Availability extensions using the SuSE HA-X addon downloaded from OpenSuSE (as directed by SLES support). After configuring iSCSI and installing the appropriate drivers for mutipath &ct. I mounted the iSCSI volume on my SAN. I rebooted the server to get to the the DRAC/IPMI settings in BIOS to enable IPMI for STONITH. Having done this, I rebooted again and the boot failed stating that it could not write to /var and offered repair mode.
Long story short, I ran Automatic repair at one point and it suggested there was a problem with the bootloader and offered to repair it. Another thing that popped up is a conflict with the catalogs because I was reportedly not using the same installer CD as the installed system. The Versions were identical, but the installer was SLES and the system SuSE. This is not true. The only SuSE components I installed were the HA Extensions as an add-on product.
The bootloader now only shows:
Failsafe – SUSE Linux
The other server shows:
Xen – SUSE Linux Enterprise Server 11 SP3 - 3.0.101-0.29
SUSE Linux Enterprise Server 11 SP3 - 3.0.101-0.29
Failsafe – SUSE Linux Enterprise Server 11 SP3 - 3.0.101-0.29
As a consequence, I cannot boot this repaired server into the Xen kernel. From Patterns. I can see that XEN is installed. Am I going to have unistall Xen and reinstall it, or is there a way for me to (un)fix the bootloader?[/QUOTE]
sounds like you have some work ahead… but let me get one thing out of the way first: I’ve never heard of the “HA-X add-on”, especially not one from opensuse. What I know is the SLE HAE add-on, which can be downloaded from SUSE, and is what would have expected the SUSE support to direct you to. Could you please let us know what exactly it was that you installed?
Depending on how much work you invested in the installation, it might be easier to start with a fresh, clean install - using SLES11 SP3 and SLE HAE SP3 - rather than trying to undo the installation of Opensuse parts by surgically removing products, packages and configuration, without certainty that no malicious left-overs remain.
As a consequence, I cannot boot this repaired server into the Xen kernel. From Patterns. I can see that XEN is installed.
Could you please provide the output from
“zypper pd” to see which products and add-ons were installed
“zypper lr -d” to see which repositories were added, and from which URL their content is fetched
"zypper se -i -r " for (each of) the non-SLES repositories, to see which packages were installed from non-SLES sources (if the list / the lists get to long, just mention that - no need to spam the forum )
“rpm -qa| grep kernel” to see which kernels are installed
and please check via "rpm -qi " for (each of) the installed kernel(s), to see which kernels are installed that are not from SLES sources (see the line starting with “Distribution:” in the corresponding output)