• i7 2600K
• Gigabyte P67A-UD4 B3
• 8GB DDR3-1866hz 9-9-9
• 1TB Samsung F3 drives
• Intel Gigabit Network card

Now, the issue here is that after a clean install of VMWare Sphere 5, boot-up would take at least 5-9 min to complete from a clean power-on. Compared to an upgrade from VMWare Sphere 4.1U1 which will load all the necessary drivers right away after a restart/power-on. It seems like its not detecting the HDD at all at first glance but soon found its way. Further tests, experiments and research yielded that this is a side-effect on how VMWare handled their installation process in VMWare Sphere 5 compared to 4.1U1. In 4.1U1, it uses the MBR for the boot process by default, while in 5.0 it uses GPT. You can fixed this if you force the installer to use MBR during the installation phase.

A developer from VMWare confirmed this and posted a way to fix this. You can find the thread here.

To quote him…

By default ESXi 5.0 uses GPT based partitions tables and not MBR like it did previously. This allows you to have disks which are greater than 2TB in size, but some systems are incompatible with it (possibly including yours) or need to have the correct BIOS setting.

You can try changing your BIOS to see if it’s compatible with EFI or will work in “legacy/compatibility mode”. Alternatively you can reinstall and use the “formatwithmbr” setting at the boot prompt which will cause the partitions to be set up the way they were in ESX 4.x. Just add it in the same way you would to tell the machine to do a scripted install.

To make things short, as written by wdbarker….

the boot prompt appears after you hit Shift-O during the boot process. You will see runweasel already in the boot prompt. Right arrow to the end, add a space and formatwithmbr and press enter. The prompt will look like: runweasel formatwithmbr

So, there you go. Hope this helps.

This was in collaboration with a friend of mine (Earlz) for setting up the box and helping me debug.

sudo aptitude install acpi acpi-support apm

This will install the power-button-power-off feature in you server.

1. Download the driver source from Intel driver webpage here, or the latest one they have. Double check if the driver supports the version of the network card, the one I have is 82579.
2. Ready the Ubuntu server, install make gcc g++ and linux headers

   aptitude install make gcc g++ linux-headers-`uname -r`

3. Un-pack the src driver that you just downloaded, compile and install.

   gunzip [filename].tar.gz
   tar -xvf [filename].tar
   cd [folder_name]/src
   make install

4. If everything goes well, no error should come out, then enable your new ethernet card.

   modprobe e1000e

5. You can check your new network card via ifconfig
   Enjoy!

Note: If you update your kernel or linux image via aptitude safe-upgrade or dist-upgrade, you need to remove the e1000e module, re-compile the driver and install the newly compiled driver again.

1. Login as root, you can also use “su” though I prefer to login as root.
2. apt-get install sun-java5-jdk
• This will install Java 2 SDK (1.5), ubuntu will start downloading packages that are not found in your system.
3. apt-get install tomcat5.5 tomcat5.5-admin tomcat5.5-webapps
• Of course jakarta-tomcat 5.5, I’m using 5.5 since this supports java 1.5
4. Now here’s the tricky part, location for Java and jakarta-tomcat
• Java’s location is in /usr/lib/jvm/java-1.5.0-sun
• Jakarta-Tomcat’s location is in /usr/share/tomcat5.5
• We will need these location for the export configurations to be written in the .bashrc
5. Now, open .bashrc in your favorite text editor, I used vim
6. At the end of the file add these:
   
export JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun
export CLASSPATH="/usr/share/tomcat5.5/common/lib/jsp-api.jar;/usr/share/tomcat5.5/common/lib/servlet-api.jar"
export CATALINA_HOME=/usr/share/tomcat5.5

7. Now save the file and exit, then log back in. This is required for the export script to be set.
8. Before starting the server, the default port the installer set is 8180 instead of the 8080 port that Tomcat uses. To change this, go to /usr/share/tomcat5.5/conf/ and open the file server.xml. Locate the line:
   
...Connector port="8180" maxHttpHeaderSize="8192"...

   and change 8180 to 8080. Save and exit. Now your ready to test the server.
9. Now try the server if it starts, /usr/share/tomcat5.5/bin/startup.sh You should see something like this:
   
Using CATALINA_BASE: /usr/share/tomcat5.5
Using CATALINA_HOME: /usr/share/tomcat5.5
Using CATALINA_TMPDIR: /usr/share/tomcat5.5/temp
Using JRE_HOME: /usr/lib/jvm/java-1.5.0-sun

10. Shutting down the server is just /usr/share/tomcat5.5/bin/shutdown.sh
11. Now, during installation of tomcat, Ubuntu automatically adds a startup and shutdown script for ubuntu to use as it starts up or shutsdown in /etc/init.d/ folder. Filename is tomcat5.5. As the server finishes starting up, you will notice tomcat isn’t running at all. One possible problem is that the script didn’t use the correct path for the java 2 sdk. You can check the boot log in /var/log/. Check if during boot up, tomcat5.5 encountered problems. For the problem stated above, you can fix this by going to /etc/default/ and edit the tomcat5.5 file. Locate the line:
    
    #JAVA_HOME=/usr/lib/j2sdk1.4-sun

    remove the ‘#’ and change it to…
    
    JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun

    or wherever your java directory is.After that, restart the server and see if tomcat was successfully started.
    
    /etc/init.d/tomcat5.5 status

Edit: Problem encountered:

• Tomcat does not load in Ubuntu 8.04

Found a little problem loading Tomcat 5.5 under Ubuntu 8.04, it either fails or white screen just appears. I don’t know what happened from 6.04 to 8.04 but once I compared the init.d/tomcat5.5 startup script from 6.04 and 8.04, there WERE changes to the scripts. I replaced the new tomcat5.5 script in 8.04 with the old one from 6.04 and the server started properly after a server restart. I don’t know why but this may have something to do with permissions and I have yet to trace the script.

• java.lang.ClassNotFoundException: org.apache.jasper.tagplugins.jstl.If

• The problem here is that the above name is incomplete… what it should have been is org.apache.jasper.tagplugins.jstl.core.*
• Now, to fix the problem, locate /var/lib/tomcat5.5/webapps/jsp-examples/WEB-INF/tagPlugins.xml and open it with your text editor… I used vim. Now edit each line of code that has org.apache.jasper.tagplugins.jstl in it and add “.core” after jstl. What you will see after editing the code will be…

org.apache.taglibs.standard.tag.rt.core.IfTag

org.apache.jasper.tagplugins.jstl.core.If

org.apache.taglibs.standard.tag.common.core.ChooseTag

org.apache.jasper.tagplugins.jstl.core.Choose

org.apache.taglibs.standard.tag.rt.core.WhenTag

org.apache.jasper.tagplugins.jstl.core.When

org.apache.taglibs.standard.tag.common.core.OtherwiseTag

org.apache.jasper.tagplugins.jstl.core.Otherwise

org.apache.taglibs.standard.tag.rt.core.ForEachTag

org.apache.jasper.tagplugins.jstl.core.ForEach

• SEVERE: The scratchDir you specified: [folder_path] is unusable.

• Sidenote: took me 2 days to figure out why this was happening (X_x)
• Based from the Catalina logs, the folders under webapps was not accessible by tomcat5.
• Now looking under all processes running ( ps command ), most bootup services were running under root (mysql, apache, etc ) but tomcat5 was not.
• If I start tomcat5 when I logged into the console as root, the problem disappears. This lead me to believe this might have been the Tomcat5 user was not given the correct privileges.
• Work-around 1: Elevate Tomcat5 user to root access level.
• Work-around 2: Go to /etc/init.d/ and open Tomcat5.5 under any text editor ( I used vim ). Locate the line TOMCAT5_USER=tomcat55 and change it to TOMCAT5_USER=root . Restart your server or you can also execute the restart command for Tomcat5.5 in init.d folder

sources:

• Ubuntu/Drapper Remaster
• linux journal
• Ubuntu Install Tomcat
• Net Admin Tools