Power Edge 2800 - Problems replacing on board RAID with Mega Raid SCSI 320-2E

First, the memory/battery message CAN be harmless.  Was the LCD panel blue, or was it amber and scrolling an error message?  Were you still able to boot into the Operating System?  If the LCD was blue and you were able to boot into the OS ok, then you can ignore that message, and it will problably go away within a reboot or two.  This will also happen if the system was unplugged for some length of time, or if the RAID battery cable was disconnected from the PCI Riser.

If you are not able to boot into the OS, then the memory likely just needs to be replaced.  Dell doesn't stock this memory anymore, but you can still get it for less than the cost of a new controller.

http://www.impactcomputers.com/4d554.html

If the LCD was amber and scrolling an error message about the ROMB battery, then it is likely caused by a bad battery - you will usually be able to boot to the OS in this case.

Second, I'm not sure why they recommended you buy the LSI 320-2E and not the version that is guaranteed to work - the PERC 4/DC (or 4e/DC, depending on your PCI riser).  Sure the 4/DC is just an OEM version of that controller, but there can be show-stopping differences between them.

Third, in order to see the configuration on a new compatible controller, you need to go to CTRL-M, then Configure, View/Add.  You should be prompted between Disk View and NVRAM View.  Choose Disk View and save the configuration on exit.  If you are not prompted to choose and the drives are showing as READY, then you might be able to "retag" the array (don't try without instruction if you have never done it), but I wouldn't recommend it, unless you are at your last attempt before giving up and starting over.

If you do indeed have an LSI card (and not the PERC), I would use it only at your own risk.  If it were me, I would get the correct memory/battery (if needed) for the onboard (PERC 4e/Di) controller ... or get a PERC card instead of LSI branded.  Using the LSI ... it is the same hardware, but like I said, there can be differences in the firmware that can make or break what you are trying to do ... it may work, but it may not.  (Even different firmware levels on identical controllers can make a difference.)

Hey thanks Flash, just nice to know somebody could work out what the heck I was going on about :)

I cant remember now if the LCD stayed blue or was amber... But when I continued to boot up by pressing the button, I got an OS missing )or corrupted) file error (the file mentioned was ISAPNP.SYS). Guessing this was a fairly major fault....

I have lost all my data now anyway, which I dont mind, can re-install wondows pretty quickly and get back to where I need to be. Im not at the server now, I will be tomorrow, but I have a stupid feeling that the config was set to NVRAM view, so I will try Disk View and see where I go from there.

Not happy at being advised to get the LSI (well, my colleague was), if there is a more sensible alternative.... Will have to bite the bullet possibly and go for that memory.

Once again flash, big thanks, I was getting lost in that server, literally :)

Cheers,

Adam.

Usually when the RAID memory has gone bad and you start to see that Memory/Battery Problems Detected message, you cannot boot or use the OS until the memory is replaced.  It is a very unusual problem, as it should continue to operate with no cache - or the cache turned off - while the faulty memory is in.  The OS not booting can manifest itself in many different ways - missing/corrupt files, blue screens, hanging, cannot boot to Recovery Console, etc. - makes it appear as if something is wrong with the OS - and there might be too - but it is best to fix the memory/battery problem before attempting to repair the OS, as the memory can be the only cause of Windows not booting.

If getting a new controller, I would get - by name - the PERC 4e/DC (PCIe) or PERC 4/DC (PCI-X).

Good luck.

Hey Flash. So I went into the config and went for Configure, View/Add, but there is nothing there. No options for Disk View/NVRAM, and no drives at all showing. It just shows two empty RAID Channels.

This may sound like a crazy question, but in this setup, do I need seperate SCSI cables coming from this card to the hard drives? I didnt think so, as the LSI Bios can see the hard drives. I presumed the drives are connected to this card via the Riser?

Cheers

Adam.

:)

Yes, the other PCI slots will work if one is occupied by a RAID controller.  The SCSI cables that are in there probably aren't long enough to reach the card.  Just take a note of the connectors needed, as there are several types.

Ah right, we thought this might be the case but were not sure. Learning all the time here.... Other cards cards on the Riser will still work wont they? Better go source a couple of SCSI cables from somewhere....

Again appreciate the help flash, you are keeping me sane this week....

Cheers,

Adam.

No, bet they made them that short on purpose :) Im just having a look round for them now. You would have thought Dell would have told my colleague about these cables when he told him about the card.... but perhaps I assume too much, or the Dell guy thought that it would be so damn obvious :)

Thanks for all your help on this flash, all working great now with the new cable :)

Good ... glad to hear it :)