Alevi,

With a drive being shown as Foreign, what that is saying is that the virtual disk configuration info on the controller doesn't match the configuration info on the drives. That being due to there not being any configuration data on the controller. With Importing a foreign configuration, you are telling the controller to Import the configuration info from the hard drives. With Clearing a foreign configuration, you're telling the controller to clear the hard drive configuration information and to use the controllers configuration data. A good rule of thumb is if the data/OS is accessible, then you would clear the foreign if unable to boot to the OS.

In your case you would need to IMPORT the Foreign Configuration data, seeing as there isn't any configuration on the controller currently. 

Let me know if this helps.

Hi Chris,

Thanks for the detailed explanations.

I will then IMPORT my array configuration (foreign) in the new H730p PERC.

A few more questions for my information regarding CLEARING, though.

You wrote :

A good rule of thumb is if the data/OS is accessible, then you would clear the foreign if unable to boot to the OS.

I am not sure I understood this well.

If the data/OS is accessible, what's the point of CLEARING the foreign IN the drives ?

In which case example would you actually do a CLEARING and what's generally the step NEXT after a CLEARING ?

 If the OS is bootable and data is ok, then the VD information on the controller is correct, as it wouldn't boot without the correct config. So you clear the foreign in order to continue using the controller data, which is working. 

Got it ... that's now crystal clear for me !

Thanks.

If I can I suggest something, I would remove the drives and power on the system.

Then clear the config on the new RAID controller just in case there is some other config on it. You never know.

Then I would proceed to connect the drives and import the foreign config.

Apart from that you can always view the foreign config before importing it by pressing C to view the controller configuration.

Another very important thing is to have a good known backup before swapping.

Hi,

you're welcome.

when you receive the 

Foreign configuration(s) found on adapter.
    Press any key to continue or ‘C’ load the configuration utility,
    or press ‘F’ to import foreign configuration(s) and continue.

you can press 'C' here. This will take you to the configuration utility where you can check the current and foreign config.

Thanks alot @BriFar

That's quite a sound recommendation, especially because I have purchased a USED H730p card !

I will definitely CLEAR its possible config with no drive attached, beforehand.

Apart from that, when do you have to press CTRL-C to view the foreign config ... is it during PERC BOOT/POST when the foreign config message is displayed ?

Got it, thanks !

I haven't received my PERC H730p yet, that's why I haven't seen this message so far ... 

I'm seriously considering doing exactly the same.

Did you complete the swap? If so, did the OS boot, did it recognize the new controller?

-James

Hi James,

Yes, I have just completed the swap.

Here's my report/remarks :

#1  First installed the PERC H730P with no drive connected then cleared the config thru the Perc Mgt Interface (CTRL-R at boot time) as recommended by @BriFar

#2  Then installed the latest H730p F/W version thru the LifeCycle Controller (F10 at boot time) from the appropriate F/W version DL from Dell site and recorded at the root of a USB disk

#3  Then connected my 3x RAID drives to Port-A of the H730p and booted the machine

#4   At this point, it did not detect a foreign version at boot (did not have to 'IMPORT' a foreign version as I expected) but instead it booted straight in my RAID5 array, the windows boot blue windows appeared but soon after got a BSOD :-(

#5  Tried another time, same BSOD :-(( (not quite sure it was a REAL BSOD but a transient blue alert screen looking much like a BSOD) 

#6  At some point, it gave me an option to boot in SAFE MODE, selected it and the machine booted properly in Safe Mode (relief... !)

#7  Shut-downed the machine and rebooted, this time it booted right normally in WS2012R2

#8  Launched OMSA and checked F/W version, driver version and Storport driver version. The second one had an exclamation mark. Downloaded the latest available on Dell site and updated my Perc H730p with it

#9  Rebooted the machine, checked again versions in OMSA -> no more exclamation, everything's updated 

#10  In OMSA selected Perc/Virtual Disks then 'Change Policy'/Execute and selected 'Anticipated Reading', Write-Back' and 'Cache Activated', then 'Apply Changes'

#11  Checked my IOPS with CrystalDiskMark, now Read and Write performances are quite similar and reasonable (>350Mbps, whereas my write performances were WAY below read perfs with the former Perc H330 !)

To make a long story short : a bit of chill when I got a BOSD-like but eventually everything now works like a charm !