Going Ubuntu Linux

ubuntu-logo

I have been a loyal Microsoft advocate for a long time, everyone who knows me knows this.  I also was a early adopter of the Windows Vista beta program and did some extensive testing on our network with some positive results.  However, the final conclusion I arrived at was that there is really no compelling business reason to migrate to Windows Vista.  In fact I am of the opinion that Vista is really only attractive to gamers and people who are happy to work with immature products.  The only real benefit, if you can call it a benefit, is the attractive Aero Glass user interface.

As a network administrator Vista has introduced several obstacles that make installing and maintaining software an unpleasant experience.  This saddens me as I was hopeful that the new implementation of user access controls would improve that situation, not impede it further.

Additionally, I was very disappointed with Windows Vista pricing.  I am impressed that Microsoft can sell Vista at the current price points.

For some time I have been interested in trying out Linux.  Previously Linux had in my opinion only been appropriate in the server area, and more specifically in the web server area.  However I had heard some good things about the Ubuntu distribution of Linux and decided I would try it.  For my testing I decided to use the same Dell Dimension 8400 system that I have been using for my Windows Vista tests.

Ubuntu Linux is quite an impressive suite.  it includes the operating system and tons of software, including Open Office.  Open Office is in nearly every respect a Microsoft Office replacement.  If you have a typical Microsoft Windows and Office installation you probably have about $600 per seat invested.  If you compare this to the completely free Ubuntu system you can save a lot of money.  This can be particularly interesting to business users.

One of my early impressions with Ubuntu is the stability.  I am also impressed with the performance.  Ubuntu seems more efficient than Windows Vista, and perhaps even Windows XP Professional.
Ubuntu by default installed a virtual desktop system which is fascinating and should be very useful for power users who like to have a lot of applications running at the same time.  Switching between the desktops is as simple as clicking an icon at the botton of the screen.

I will be doing a more in depth report complete with screen shots in the coming weeks so if you have wondered what Linux, and particularly Ubuntu looks like check back again.

Dell PERC RAID Multiple Drive Failure

dell-perc-raid-array

This article is to help you get your Dell PowerEdge servers equipped with the PERC RAID controller back online if you experience a multiple drive failure.  A multiple drive failure will be indicated by flashing amber lights on more than one physical hard drive in your RAID array.

Background:  Some Dell servers equipped with PERC RAID controllers can experience multiple drive failures.  These RAID arrays can usually tolerate a single drive failure without any impact on the servers availability in your network environment.  However, if more than one drive fails the server will not be available on the network.  In this case you will usually see amber flashing status LEDs on the failed hard drives.

In most cases multiple hard drives do not fail at the same time so it is very likely that one of the drives is still good but may have gone offline when another drive failed.  In some cases this can be due to timing issues between the PERC RAID controller and the drives firmware.  As of this writing Dell has released a firmware update to bring hard drives in many PowerEdge systems up to level JT00.  If you have drives in your server with a lower revision level firmware you should consider this a urgent update.

Getting Back Online
These step require that you enter the PERC RAID controllers BIOS and making some changes.  We recommend that you leave this to experienced server administrators as you can cause permanent drive damage, or data loss.  As usual you should be backing up your server as by the time you have to perform these steps it is too late to do so.

Restart The Server
Power down the server, or perform a soft restart if possible.

Enter The PERC RAID Controller Setup
You will see the <CTL-M> message on screen.  This key combination will get you into the PERC controllers setup mode.

Force Drive Online
Choose a failed drive to force online.  This is a coin toss as you cannot be sure which drive (if not both) is actually failed.  Select objects and then physical drives from the menus.

IMPORTANT: Make a note of which physical drives are marked bad before making any changes.  Drives will be numbered starting with 0 so your first drive is not 1.  Example: If you have a 5 drive array they will be numbered 0-4.
Select one of the failed drives and select force online.
ESC out of all menus and quit the RAID controller setup by selecting yes.  Soft reboot the server with CTL-ALT-DEL.

Allow the server to boot completely.  If you see the operating systems startup logo you are probably ok.  If you see a message indicating corrupt data which does not allow the server to start you will have to go back into the RAID controller’s BIOS setup and force the drive you just forced online into a forced offline state.  Next you will have to repeat the above procedure forcing the other failed drive online and soft restarting your server.

Normally by following this procedure you will be able to get your server back online with only one drive indicating a failure mode.  You will be able to replace the failed drive with a drive of equal or higher capacity, but not lower capacity.  Dell, or your server manufacturer can ship you the replacement drive via overnight delivery.  you do not want to operate your server in a failed drive state for a prolonged period as it will not tolerate a second drive failure.

There have also been cases where the problem was not solved following these steps due to a defective backplane or controller card.  Usually replacing these components resolved the issue without data loss, however if the rebuild process is not completed successfully you can experience file corruption.  In these instances you will have to perform a complete system restore, or worse a complete re-installation of your server.

When you purchase a new server from any manufacturer you should be opting for the 3 year minimum full warranty.  Dell for example has been able to deliver us with replacement components the same day because the client had purchased the full warranty when the server was ordered.  In fact, on one occasion we had the parts delivered in two hours because Dell works with UPS logistics and they have caches of replacement parts.  In this instance the customer happened to be in close proximity to the UPS resource location.

We see most servers as having a three year life expectancy due to the technology advancement and the fact that many small and mid-sized businesses are not operating their servers in clean climate controlled environments.  Additionally most companies seem to be able to amortize their server investments sooner than 10 years ago.  If you intend to amortize your server assets over five years or more you should definitely opt for the maximum warranty during your purchase phase.

I hope this article helped you get your server back online and getting the angry users off your back!  If you have any questions about this article contact me.