- NG Firewall firmware versions 4.2.x
- netfence firmware versions 4.2.x
The HP-Server with CCISS-controller doesn't boot from harddisk after the installation and the memory-stick isn't useable for another installation.
There is a known issue with the Bootloader after the installation. When installation is done, wrong CCISS parameters ware written into /etc/lilo.conf (bootloader-config-file). These has been fixed in Barracuda NG Firewall 5.0.x.
Workaround procedure:
- Create a installation-stick with the phioni and insert a post-installation script.
- Create a MBR-dump of your installaion-stick.
- Install your HP-Server.
- Recover the MBR of your installation-stick.
Additional informations:
If you tried already an installation of a HP-server with your stick, so you have to format your stick with the NG Install tool. Format your stick and delete the created files on your stick.
When you create the kickstart-file with the phion.i, you can edit the pre- and post-install-script.
Please insert the following lines into the Post-Install-Script:
*************** POST-Install-Script ***************
#PAPH
TARGET=/etc/lilo.conf
/bin/sed -e '
s,boot=/dev/sda,boot=/dev/cciss/c0d0,
s,root=/dev/sda,root=/dev/cciss/c0d0p, ' \$TARGET > \$TARGET.1
/bin/cp -f \$TARGET \$TARGET.2
/bin/cp -f \$TARGET.1 /etc/lilo.conf
chmod 0600 /etc/lilo.conf
/sbin/lilo
# do not change PARPATH and PARDEV
*************** POST-Install-Script ***************
These script will set the correct parameters into the lilo.conf file (at the firmware installation).
The "boot from harddisk" issue will be fixed by the installation, but the memory-stick is unuseable for another installation anymore.
It's possible to save the MBR of your installation stick, please perform these backup before you try the installation.
Connect your memory-stick to a Linux-Distribution (eg. a netfence box) and verify the address letter of your memory-stick (eg. /dev/sdc):
dmesg
scsi 12:0:0:0: Direct-Access Kingston DataTraveler II PMAP PQ: 0 ANSI: 0 CCS
sd 12:0:0:0: [sdc] 2014208 512-byte hardware sectors (1031 MB)
sd 12:0:0:0: [sdc] Write Protect is off
sd 12:0:0:0: [sdc] Mode Sense: 23 00 00 00
sd 12:0:0:0: [sdc] Assuming drive cache: write through
sd 12:0:0:0: [sdc] 2014208 512-byte hardware sectors (1031 MB)
sd 12:0:0:0: [sdc] Write Protect is off
sd 12:0:0:0: [sdc] Mode Sense: 23 00 00 00
sd 12:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
The memory-stick in our example has the address letter /dev/sdc. To backup the MBR, you need the first 512 bytes of /dev/sdc, please type in the following command:
dd if=*your memory-stick address letter* of=/tmp/disk_mbr.img count=1 bs=512
In our example:
dd if=/dev/sdc of=/tmp/disk_mbr.img count=1 bs=512
Mount you memory-stick:
mkdir /mnt/phion_stick
mount *your memory-stick address letter*1 /mnt/phion_stick
In our example:
mount /dev/sdc1 /mnt/phion_stick
Copy the MBR-Backup to your memory-stick and delete the backup-file from /tmp:
cp /tmp/disk_mbr.img /mnt/phion_stick/
rm /tmp/disk_mbr.img
Create a Script (fixMBR):
cd /mnt/phion_stick
vi fixMBR (or use another text-editor)
and insert the following text:
*************** fixMBR-Script ***************
#/bin/bash
dd if=./disk_mbr.img of=/dev/sda count=1 bs=512
echo "**********************"
echo "* MBR recovered. *"
echo "**********************"
*************** fixMBR-Script ***************
Make the script executeable:
chmod u+x fixMBR
The stick is now ready to install a HP-Server. Please unmount the stick from your linux-client:
cd /
umount /mnt/phion_stick
The stick-preparation is finished now, let's go to the HP-Server and start the installation. After the Installation is done, please disconnect the installation-stick from your server and boot the netfence. The installation-stick is still unuseable for another installation, to reuse the stick, you have to recover the MBR.
Please take a login as root (at the HP-server) and type in the following commands:
mkdir /mnt/phion_stick
mount /dev/sda1 /mnt/phion_stick
/mnt/phion_stick/fixMBR
umount /mnt/phion_stick
Disconnect your installation-Stick and reuse it for another installation.
Note:
If the controller is used for SATA, do NOT configure it as SATA-RAID!