Hello usfwalden The errors reported on the front panel are pulled from the hardware log. You will need to clear the hardware log to get rid of the errors. You can boot to the BMC via CTL E or use OMSA to clear the hardware log. There is a log category in OMSA. Under that category is an option for system or controller logs. You should have an option to save or clear the log in that menu. The hardware log may also be referred to as the system or system event log, but it is no related to the Windows system event log. Thanks 
First off.....  Hello, this is my first post in the forums.  I'll post my whole story--you may want to skip to 4th paragraph.... I got tired, dissapointed, and fed up with the really poor storage options out there for the home user after first running out of space on a NAS and finding out there is no reasonable path to migrate to something bigger and then finding out the intel raid stuff on my desktop motherboard doesn't support things like online expansion or volumes over 2tb.  I also have small business server 2003 running on an old PowerEdge 400SC which I must give props to Dell for since it's still humming along reliably but it  will have to give out eventually, right?  I figure it's time to have something else to start replicating the services I use on the small business server over to for when it does give out. So now I've gotten myself a Gen3 PowerEdge2950 with PERC 6i with SAS backplane and 6 caddies.  I installed a 60 gig ssd into one of the caddies using an alienware ssd to 3.5 adapter and installed to position 0 0 and configured as a single disk raid 0.  I also initially installed 3 2tb sata drives on which I configured a 500 gig raid 5 volume with 64k elements and a 3.2 terabyte raid 5 volume with 1024 elements.  I partitioned the raid volumes with gpt using gparted.  I slipstreemed the perc6 drivers into a Windows 2003 Server Enterprise Edition installation cd and installed onto the ssd.  I got up and running and turned off the paging file and everything worked great.  The lights on the drive 0 caddy didn't light but everything worked great. After I got my data off the various NAS devices and workstation drives and onto the raid volumes on the 2950 it was time to install the freed up 2 tb drive into the 2950 and expand the raid volumes.  To expand the raid volumes online I found I needed to install Open Manage Server Administrator Node to get the storage manager which I did.  After doing so it told me I should update my perc6i firmware, the backplane firmware, and the storport driver. I updated the perc6i firmware using the dell update package to 6.3.1-0003.  This required a restart which I performed remotely and the server came rigth back up.  Then I updated the backplane firmware using the dell update package to 2.50.00.  This did not require a restart.  Then I updated the storport driver using the MS hotfix to 5.2.3790.4173.  This required a restart which I performed remotely but the server didn't come right back up so I went down to the garage where I have the noisy beast and the front display was indicating a hdd0 fault.. I didn't pay attention to the exact code at the time I just held the power button till it shut down and then turned it back on.  It booted up fine and is working fine but it still indicates an E1810 hdd0 fault and the lights on hdd0 are flashing amber. In the open manage server administrator no fault is indicated.  The server is still functioning fine.  In fact I've gone on to delete the 500 gig vd to allow me to expand the main virtual disk, reconstruct the 3.2tb vd to 4.8tb and add a 732gb vd disk to replace deleted 500gig one.  Everything seems great but I figure I better ask for help to clear up the reported error.  Anybody have any ideas?
E1810 hdd 0 fault on good ssd after updating perc6i and backplane firmware and 
storport