Dell Powervault MD3000 lost configuration H800 adapter

Hello tferlaak,

Is the drive that is failing in your R710 or in your MD3000?  Is your MD3000 connect to your PERC H800 or a SAS HBA?  Are there any error lights on your MD3000?  Can you login to MDSM, and see what errors are listed if any?

Please let us know if you have any other questions.

I really believe the issue here is the H800 Controller card. I purchased a new one off amazon that should be arriving today and then will import the config to this one. 

the reason i believe this to be an issue with the card itself, is that last friday i power cycled the SAN cabinets, and now none of the drives came in, they all say foreign config, and it wont import the config. There is another H800 card attached to the same storage and that brought in the configs just fine. 

So i will replace the card today or tomorrow and hopefully be able to import the config and all will be happy again. 

Ive replaced the H800 Card, but it will wont import the foreign. 
Upon reviewing and matching the PD Mgmt tab with the foreign view tab i believe 2 drives may be causing this as they are present in PD Mgmt but not in Foreign view. 
So here is what my next steps are that i believe. 

First is to power down the san for about an hour, to let it "Cool Down". After that i will remove the 2 drives that are in pd mgmt but not in the foreign view to make sure those drives arent causing a mistake in the import. 

Next which seems to be the most risky would be to clear the foreign config (risky because the controller currently has no config). Then attempt to rebuild it on the controller just how the config is in the foreign view and not initialize the disks. this will hopefully allow the OS to see the drives but keep the data in tact. 

Anyone have any other suggestions: 

Here is what is currently in the PD MGMT and Foreign view. 2 enclosures Raid 50

PD MGMT

00:00:07
00:00:08
00:00:09
00:00:10
00:00:11
00:00:13
00:00:14
01:00:07
01:00:08
01:00:09
01:00:10
01:00:13
01:00:14

Foreign View:

Span: 0
00:00:07
00:00:08
00:00:09
00:00:10
00:00:11

span: 1
missing
00:00:13
00:00:14
01:00:14
01:00:08

span: 2
01:00:09
01:00:10
missing
missing
01:00:13

Drives in PD but missing from Foreign:
01:00:07
01:00:14

Hello tferlaak,

If you are connecting your MD3000 to your PERC H800, that will not work as you have 2 raid controllers connected to each other.  With an MD3000 you need to connect it to a SAS HBA.  You can login to MDSM and you should be able to see your raid configuration on your MD3000.  You will use OMSA or PERC bios for your drives that are internal to your server. 

Please let us know if you have any other questions.

what is MDSM? is this like openmanage?

Hello tferlaak,

If you don’t have a network port on your controllers then you don’t have a MD3000.  Here is the link to the users guide and if you look on page 15 there is a picture of the controller that is in an MD3000. https://downloads.dell.com/manuals/all-products/esuprt_ser_stor_net/esuprt_powervault/powervault-md3000_owner%27s%20manual_en-us.pdf

To me it sounds like you might have a MD1000 that is connect to your PERC card.  If that is the case then you will need to use OMSA to manage to manage your MD1000.  With an MD3000 you mange it using MDSM (Modular Disk Storage Manager).

Please let us know if you have any other questions.

also.... the back of the storage enclosures do not have a network port. there is just some round service port that i have no idea what connects to it. 

So if this is a MD 1000 would i need to connect to OMSA from the storage controller or a omsa install on a device near it?

Hello tferlaak,

Thanks for the pictures as it helps to see that you have EMM’s.  You can try the steps list in the user’s guide to try to recover the virtual disk.  However, if this doesn’t work then you will need to contact a data recovery company to try to recovery your data.

Please let us know if you have any other questions.

Hello tferlaak,

Does your controller in your MD3000 look like the picture in the user’s guide on page15 or no?  If your controllers don’t look like the ones on page 15 then you don’t have controllers in your MD3000 you have EMM (Enclosure Management Modules) which here is a link to thoses look like on page13. https://dell.to/37T4dgQ

Please let us know if you have any other questions.

when i enter the service tag number into support it detects as a MD3000. 

so Oddly enough i did see on your last MD1000 document something rather interesting and was part of my "Last Resort" option. 

So currently where i am at, is that i shut everything down, then restarted. and i now have 1 or less failed drive in the spans (which should be enough for raid 50.). But all of the drives are showing foreign, the controller shows that there is no configuration. But there is one drive that shows offline so its not allowing me to import the foreign config to the controller. 

On page 44 and 45 of the MD1000 troubleshooting section where it says if there is a Failed virtual disk, to record all of the raid information and the steps to rebuild (but done initialize) the raid. 
see pic. 

yeah they look like an MD1000 controller. 

I guess i thought it was a 3000 based on the service tag. sorry for the confusion. 

Hello. I am trying to get openmanage on my poweredge r710 for this, however im having trouble figuring out why the dell repo is not pulling in srvadmin-all When i do  yum install srvadmin-all it gives no package available. 

i am following this https://linux.dell.com/repo/hardware/DSU_20.01.01/ and its not working. I can do a "dsu --inventory" and it works fine. but the omsa wont install as the repo seems to be missing the package.