Our SAN marked a disk as failed or physically removed a while ago.  I replaced the disk with a new one and am still getting the same errors with the new disk - it just keeps powering it off.  There appears to be a problem with the enclosure, not the SAN.  See the errors below and attached:

Date:01/17/2011
Time:10:26:24 AM
Event Code:0x7127897c
Description:Disk(Bus 0 Enclosure 0 Disk 9) failed or was physically removed.TLA Part Number is 005048582, Serial Number is 3KR3CG68.     00000400 06005600 d3040000 7c8927e1 7c8927e1 00000000 00000000 00000000 00000000 00000000 7127897c
Subsystem:FVZLZB1
Device:N/A
SP:N/A
Host:SPA
Source:Flaredrv
Category:NT System Log
Log:NT System Log
Sense Key:N/A
Ext Code1:N/A
Ext Code2:N/A
Type:Error

The disk shows green and orange LEDs.

Has anyone ever experienced this problem ?  Got any idea what I can do to resolve it ?  

As well as replacing the disk, which was working for several years before this happened, I've checked the logs and confirmed other disks are working ok.  Note we had no spare caddies, so I had to use the same caddy for the new disk.  We are not aware of any other external issues that happened at this time and the SAN is running off a UPS.

Any help would be greatly appreciated.
 

--
huddie

"Keep a cool head and always carry a lightbulb."

If the same disk failed again, you might have a problem with the plug within the shelf.  A call to Dell's support group will be needed to have them send out a new back plane and a support person to install it.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

Unfortunately we don't have support on it.  You might be right about that but I need know how to be sure whether it's the disk itself or something else like the backplane.  The logs just tell me the disk is being 'rejected' but not why.

A contact mentioned that it's possible that we should be using a registered drive.  That is to say the drive may need to be registered by EMC engineers, who would then follow their own procedure to remotely install the drive.  Obviously not an option.  That would be new to me but then we've never had to replace a drive in either of our SANs that I remember.

--
huddie

"Keep a cool head and always carry a lightbulb."

If you don't have support, how did you get a replacement disk?  The EMC array's don't support off the shelf disks.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

Ordered and paid for from the company that used to give us support!

It's a matched disk, I made sure of it.  Same manufacturer, model and part number.  However, I hear it may need to be 'registered' in some way for use in our SAN, is that true ?

--
huddie

"Keep a cool head and always carry a lightbulb."

It shouldn't need to be.  What version of FLARE are you running?

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

Not sure.  How do I check ?  Using Navisphere ?

--
huddie

"Keep a cool head and always carry a lightbulb."

Yeah, in Navi right click on the array and select properties.  Look at the software tab, and it'll give you the software version.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

OK.  Will check that when I'm back in work in the morning and let you know.  Thanks

--
huddie

"Keep a cool head and always carry a lightbulb."

OK, mrdenny, the FLARE software version is 2.19.300.5.034.  Any ideas ?

--
huddie

"Keep a cool head and always carry a lightbulb."

Wow, that's pretty old.  In the newer versions there is a utility which allows you to check disks when you put them in, and gives you more information.  On an older version like that, you might want to give a call to that support vendor that you bought the drive from.

Sorry.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

Thanks mrdenny.

My current suspicion is leaning towards a faulty disk.  I took the disk out and put it in a spare slot in our other SAN (a CX320) and it reacted in exactly the same way.  What do you think ?  Shouldn't the SAN report a more specific error if this is the case ?

--
huddie

"Keep a cool head and always carry a lightbulb."

I would think that it would, but that would depend on the reason that the disk is bad.  If the array can't do anything with it, it probably won't return a very useful error message.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

MrDenny,

I'm just back from holiday and while I was away I had a support company of ours check the disk in their CX300.  It accepted it, so what we now know is that neither our CX300 or our CX320 accept this disk, but their CX300 does.  It's therefore likely to be something to do with the way our SANs are configured.  Any ideas ?

--
huddie

"Keep a cool head and always carry a lightbulb."

The only reason that I can think of that the system would reject a disk, would be if you tried to put a SATA disk in a fiber shelf, of a fiber disk in a SATA shelf.

Other than that there shouldn't be anything you can configure that would cause it to reject the disk.

The array does track the serial numbers of failed disks.  Once it sees as disk as bad, it won't accept that disk again.  Best thing I can say is have them give you another spindle to try.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog