UNSOLVED

networkcloset

updated

15 years ago

0

61448

December 27th, 2011 13:00

MD3000i - Array is non optimal - 3x Out of Compliance Errors

I pulled one of our MD3000i's off a shelf and decided to set up a new ESXi environment using a couple of PE1950 servers.  I reset to factory defaults and now I am getting the following 3 errors in the Recovery guru:

1) Storage Partition Premium Feature - Out of Compliance (0 of 64 used)

2) Remote Virtual Disk Mirroring Premium Feaure - Out of Compliance

3) Feature Pack out of Compliance

I'm pretty sure that no premium features were enabled on this device when it was in production.  I was unable to access the device for performing the factory reset, so I cannot confirm that 100%.

Under premium features, nothing is listed.  And there is nothing configured under any of the host, virtual disk, groups, mappings, etc.

Any idea how to bring this puppy online?

  • 2155

    0

    Posted December 27th, 2011 13:00

    EDIT: I was unable to access the device *BEFORE* performing the factory reset, so I cannot confirm that 100%.

  • 2155

    0

    Posted December 27th, 2011 16:00

    Apologies, I wish I could edit my thread...

    ADDED: I just added an MD1000 expansion chassis tot he MD3000i.  If I slot in any drives at all - anywhere in the MD3000i or the MD1000 (even ones that have never been configured in either device) I immediately go from optimal to non-optimal and the same three errors appear!

    This is nuts...  am I missing something obvious?

  • 2155

    0

    Posted December 27th, 2011 16:00

    ADDED: If I remove the 15 x 300GB 15k.5 SAS drives and reboot the system the status goes to optimal.  As soon as I slot a drive, the SAN returns to non optimal with the same 3 problems.

  • 2155

    0

    Posted December 27th, 2011 16:00

    ADDED: Firmware update while optimal:

    [Dec 27, 2011 7:35:58 PM] [Unnamed] [pre-upgrade tests] [check spm database]

    An error occurred while checking the spm database on RAID controller module 0.

  • JOHNADCO

    2 Intern

    •

    847 Posts

    2155

    0

    Posted December 28th, 2011 08:00

    I'd flash it with the current FW and see what happens.  

    07.35.39.64

    is the current version....   The update is trickier if the controller(s) are not on the second gen FW.

    So what is actually wrong with it?     I would expect non of those messages to actually impair it's operation.

    Is it not allowing you you see the physical drives?     On the summary page dose it list anything under Disk Groups and Virtual Disks?

    Have tired to add your host(s) and map storage to them?

  • 2155

    1

    Posted January 2nd, 2012 10:00

    Answer above.

  • 2155

    0

    Posted January 2nd, 2012 10:00

    I was unable to do anything.  I couldn't add physical disks, groups, nothing.  But I did manage to speak to a Dell rep who gave me some tips.  Last night I finally got it fixed!  It turns out I had the original 8 x SAS drives mixed up with another  7 x SAS drives from an MD1000.  This confused the unit completely to the point it wouldn't run with even 1 drive installed.

    1) Took 2 drives at a time and connected to Perc 5i

    2) Created RAID 1, start init, stop init

    3) Delete Virtual Disk

    4) Slot each drive in one at a time, slowly, waiting for it to become visible as a physical disk on the  MD3000i

    Using this method I was able to bring up all 15 drives and create a RAID10 with hot spare.

    My new problem is that no matter what I do the system times out when trying to configure the default iSCSI IP addresses and brings up a generic error message.  I am going to attemp a 6.X firmware to newest and then a 7.X firmware to GEN2 and see if that helps.

  • netasp

    18 Posts

    2155

    0

    Posted January 9th, 2013 06:00

    hey,

    I am getting the same error: (An error occurred while checking the spm database on RAID controller module 1)

    I can't do anything, any command I issue to the SAN I get an error about no physical disks are present in the SAN or can't communicate with the disks.

    This started to happen after a failed upgrade to GEN2. All controllers are in optimal state and no errors.

    any idea?

    thanks