  Hello Chris, What you will need to do is to go into the bios for the new SAS card and import the foreign configuration. Since you haven’t imported the configuration that is why you can’t see the virtual disk on your host. Once the configuration has been imported then let your host boot up normal and once logged into the host you should be able to see the virtual disks.  Please let us know if you have any other questions.    This has nothing to do with the foreign config.  The new SAS card has a different hardware address (World Wide Name (similar to a MAC address on a network card)). The MD3000 SAN specifically registered the server with the old hardware address from the bad card. You need to go into MDSM and go to the host registration and update it to use the new hardware address of the new card (if memory serves it has an option to replace the WWN/SAS HBA). After this you may need to rescan for hardware changes in the device manager (or 'rescan all' if it is a VMware host) or possibly reboot the server.
Hi All, Hopefully I'm explaining this correctly.  PE server connected to a MD3000+MD1000 which has worked fine for years.  The SAS5e card went bad on the PE host.  Replaced that card.  I can see the MD storage array with MDSM just fine, but I'm not able to see the volumes (would virtual disks be the correct term?) I'd created on the PE host within Windows...they are just not showing up as drives.  I can see my existing Host to Virtual Disk mappings in MDSM. I'm wondering if it has something to do with a HBA ID that was built into the old card which would be different on the new card but as of yet I'm not basing that on fact, just a hunch.  Any thoughts as to how I can regain access to my storage? Thanks!Chris
Replaced SAS5e card on host connected to MD3000