I was thinking about a Debian install on my server, but in the end, I thought I’d go with Ubuntu server.
Ubuntu server install
I’m not going in to all the details about installing Ubuntu server (debian would be similar), but I thought it would be worth noting the steps I made to get the RAID device partitioned ready for installing xen or KVM.
When booting the server, you are able to access the MegaRAID configuration. As my server came with 2 unregistered drives, it was simple to create a new RAID1 configuration with those two 146Gb drives, creating a virtual 146Gb RAID1 drive.
I ummed and ahhed a bit about whether to use the RAID controller, but it looks like it might be ok kit.
I usually use inetbootin to create a USB memory stick with the OS I want to install. In this case, I downloaded the 64bit Ubuntu image and used it to create the bootable USB stick.
Expert install followed.
Grub2 gotcha 1
Oh dear, I had a number of failed installs until I asked an expert (@wilbatron) for some help. The grub2 installation in to the MBR kept failing because… The grub2 installation doesn’t fit in the MBR does it? I wish it told me that rather than just failing.
Ah well, got it sorted in the end, here is how I set up my partitions.
Partition set up
During the install, do manual partitioning. We’ll set up 2 physical partitions, one of which will be a Logical Volume Manager (LVM) Physical Volume (PV)
At this point, the menu will show your USB stick (still mounted) and your 146Gb virtual RAID drive. The Hardware RAID is hiding the fact that you’ve actually got two hard drives there and the installer just sees one.
- Select the Raid array - in my case, it was labelled 146.0Gb LSI MegaRAID 8708EM2
- Once selected, create a new empty partition (and table) for this device
- Choose GPT as the partition table type (not MSDOS!)
- Now select FREE SPACE 146.0GB and create new partition
- Set new partition size to be just 10Mb, this is where the installer will put the rest of grub2
- Set to be at the beginning of the drive
- Set type to be used as Reserved BIOS Boot area
- Create next partition to use as Physical Volume (PV) for LVM
Now we configure the LVM
- Configure LVM (option at the top of the partitioning page)
- When prompted, write partition changes to disk
- Create volume group, give it a name and select the PV.
- Create logical volume, call it ROOT or whatever, mine was 15Gb - this is where the OS will be installed. You could create all the separate partitions if you like of course.
- Create swap volume, I chose 6Gb, although the server has 12Gb of server memory, I didn’t want to give it swap of that size. We’ll see how we go.
- Finish up and head back to partition page
- Set root partition to be root (ext4), doesn’t need to be bootable partition.
- Set swap to be swap
- Down to the bottom of the page and write changes to disk
- Back to main menu and install!
Installing grub in MBR - gotcha 2
Just another slight gotcha, if your USB stick is mounted as /dev/sda & your RAID array as /dev/sdb you might have to tell it not to install to the MBA, but instead to where you want it installed, i.e. /dev/sdb
BMC (Baseboard Managment Controller)set up
To get the BMC up and running properly, I needed to do a few things, first, is to ensure that it is set up correctly in the BIOS.
Enter the BIOS and in the server management section, ensure it is set to use the correct LAN port, either Dedicated if you are using the single port on the back of the server, On Board for one of the 4 built in LAN ports. I used the latter with DHCP. Make a note of the IP address which is given to the BMC and fire it up in your web browser. All being well, you should see the log in page:
Default authentication log in
Apparently the default is either admin/admin or ADMIN/ADMIN so give that a go first of all to see if you get in. If not, we will have to do some jiggery pokery on the server.
Resetting BMC credentials from the server
The tool, ipmitool is required to access the BMC from the server. I just did apt-get install ipmitool to get it up and running. However, before I got it working properly, I had to load some kernel modules
Kernel modules for ipmitool
First, I’d see whether it is working straight after install:
if you get
1 2 3
Then try manually loading the kernel modules with
1 2 3 4 5
You can add these to
/etc/modules for permanent loading.
Now try again, you should get some results
Get correct channel
(where the latter 1 is the channel, so if 1 doesn’t work, cycle through)
1 2 3 4 5 6
which showed that Channel 1 was the one I needed.
should give you a list of users, then you can reset the passwords. I ended up setting all I could to password then, once I was in the web admin, I deleted the users I didn’t need and set all the passwords to be more secure ones!
Hmm, not sure I got this right, but I tried
(the 1 here is the channel)
for the various users until I could log in to the console!