If you were bringing over two drives in RAID 1, and wanted to keep the RAID 1 array intact, using Import would be a good option. LSI MegaRAID Scan Foreign ConfigurationĪt this point, MSM will scan drives on the controller and say how many foreign drives it found. Then select Go To -> Controller -> Scan Foreign Configuration as shown below. Somewhat counter-intuitively (when managing one newly added foreign drive) one needs to click on the controller not the drive in MSM. The solution to our use case is to reset the drive’s configuration. The Solution to Fix a Drive Labeled as Foreign by a LSI/ Avago SAS controller Like our use case, we are going to clear the previous configuration (RAID 0 from the Samsung SM1625 200GB SSD RAID 0 testing) and make it usable as a data drive again. Other drives do not have the (Foreign) label nor the blue arrow on the drive. Here one can see our Samsung SM1625 SAS SSD is labeled as a foreign drive in MegaRAID Storage Manager. We recreated this in our lab using an onboard LSI SAS 3008 HBA. I was reading that LSI to LSI is supposed to work. When I try, I can see the drive in the LSI utility, but it doesn’t immediately register for me to pass-through like others. I’m trying to migrate my old VM store SSD to a ZoL on server. “STH I found info on my LSI 9271-8i and LSI 9300-8i here. The Foreign Drive ProblemĪlthough this question has been asked many times to date, here is the latest question: That is causing the drive to be labeled as foreign. What is happening is that the drive was previously inserted on another machine and a LSI/ Avago configuration was previously written on it. For years now this question has come up in various forms so today it is time to show the easy fix. Here is one from the mailbag about how to fix a drive labeled as foreign by a LSI/ Avago SAS controller when it is inserted into a system.

Avago megaraid storage manager 1068e