Topic
  • 3 replies
  • Latest Post - ‏2013-03-15T12:56:34Z by SystemAdmin
SystemAdmin
SystemAdmin
3234 Posts

Pinned topic SNA hang on RAID controller error : " 4005 : No media tray detected"

‏2013-02-21T19:28:48Z |
Hi all,

I can not use Start Now Advisor because it report that my bladecenter S system is not healthy.
when I check for error I see a critical alert

Alert code: 4005
Description: No media tray detected
Date/Time: 20/02/13 00:28

and I can not guess what to do with.
I am able to access my blade serveur (esxi 5.1) connect with though ethernet, configure storage on Bladecenter S with telnet and "IBM Storage configuration manager 2.20.0", but I don't want to deliver a solution with logs reporting critical status.

does one of you known what to do to clear or circumvent this alert.

thank for your time.

greeting for Tahiti / french polynesia
echo qbzvavk@znvy.cs | perl -pe 'y/a-z/n-za-m/'
Updated on 2013-03-15T12:56:34Z at 2013-03-15T12:56:34Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: SNA hang on RAID controller error : " 4005 : No media tray detected"

    ‏2013-02-21T19:32:25Z  
    Forgot to say that this error is not documented (or I didn't found it).

    greeting for Tahiti / french polynesia
    echo qbzvavk@znvy.cs | perl -pe 'y/a-z/n-za-m/'
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: SNA hang on RAID controller error : " 4005 : No media tray detected"

    ‏2013-02-21T19:38:01Z  
    Forgot to say that this error is not documented (or I didn't found it).

    greetings from Tahiti / french polynesia
    echo qbzvavk@znvy.cs | perl -pe 'y/a-z/n-za-m/'
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: SNA hang on RAID controller error : " 4005 : No media tray detected"

    ‏2013-03-15T12:56:34Z  
    If you check the media tray from the command line or the web interface of the AMM is it actually in a fault state? SNA is notorious for not functioning currently. Especially if you upgrade your AMM firmware to any of the 62x revisions. Basically, the 62 levels break SNA. Here is a list of issues we have found with the current SNA version. There may be more, but this is just what we know about.

    1. Lack of CIOv support for SAS expansion cards they are not recognized in Blade Servers. HS22, HS23, HS23, and Power 7
    a. Stops configuring onboard storage.
    b. CFFv is no longer used on current blades blades and SNA only supports CFFv
    2. No HS23 and HS23E Blade Server support at all.
    3. No RSSM firmware update support.
    4. Pre-req checking should be done Before user enters all information into multiple screens, rather than at the end.
    5. SNA BC-S Chassis discovery takes too long to discover.
    6. Unable to access SAS RAID Controller Modules randomly for no valid reason.
    7. If SNA uses xml files for firmware updates, some updates are missing these files on the IBM Fix Central Support website.

    I would recommend that you do not use SNA and instead use SCM, the AMM Configuration Wizard, or the command line interfaces to configure your BC-S.

    Good luck.