Link to home
Start Free TrialLog in
Avatar of tsaico
tsaicoFlag for Afghanistan

asked on

Inherited a server that is showing a RAID problem

I just picked up a new site and one of the old-ish servers (about 3-4 years old) is an Chartec server based on the Intel RAID controller SROMBSASMR.  It is showing "SAS topology error: Device not addressable", but the strange thing is it has no SAS drives.  There are 4 SATA drives in a RAID 6 container and all show online and the container itself is not degraded.

I googled the error message, and found many LSI chipset manuals that have the same error code, and error message, but it doesn't say what the error means or how to go about correcting it.  So other than reading in the manual it is a possible error, I don;t know my next move.

The RAID log shows this as far back as the beginning of the log, which is earlier this year back in Feb, so I am guessing it has been throwing this for quite some time.  Anyone have suggestions how to resolve this?

Anyone
ASKER CERTIFIED SOLUTION
Avatar of David
David
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of tsaico

ASKER

Yeah, I am thinking the same.  As long as I can wait out a couple of years, the issue will go away since it has to be retired anyhow...
Avatar of tsaico

ASKER

Just in case anyone reads this old post,

By chance I had noticed one of the SATA drives had a different speed.  (8 of the drives were showing 3 GPs negotiated 6 actual) except for one.  It was showing 3 and 3 respectively.  I pulled the drive and replaced it with a 6 like the others and the error went away after the rebuild happened.  Of course still SATA and still negotiated at 3 GPs, but at least one less error message.

My guess is all of the original drives had failed at one point and been replaced with this one being the last.  Why that would throw an error like this though, who knows?