This is getting more and more confusing but at least the drive imported
fine when I stopped specifying the Foreign Configuration # in my MegaCli
args... (check the difference between the two -Import commands)
# MegaCli -CfgForeign -Dsply 0 -a0
Foreign configuration 0 on controller 0:
Number of DISK GROUPS: 1
DISK GROUP: 0
Number of Spans: 1
SPAN: 0
[......]
# MegaCli -CfgForeign -Import 0 -a0
FW does not have Security key, create Security key first.
Failed to import foreign configuration 0 on controller 0.
FW error description:
The requested command has invalid arguments.
# MegaCli -CfgForeign -Import -a0
Foreign configuration is imported on controller 0.
Grumble..
Vincent
On Wed, 3 Jan 2018, Patrick Boutilier wrote:
On 01/03/2018 07:48 PM, vinc...@cojot.name wrote:
On Wed, 3 Jan 2018, Patrick Boutilier wrote:
Did you try using the Ctrl-R interface during boot instead of MegaCLI
after boot? I have always had success importing foreign configs that way.
Hi Patrick,
No, I did not try that. I'll do on the next iteration (tonight).
Would storcli have worked any better? Perhaps that'd be a reason to ditch
megacli since it has not been updated in ages..
Rebooting a host to import RAID LD's in a hot-swap config is quite a pain,
IMHO. This worked just fine for me in the past using LSI HBA's (9271-8i)
but it seems these PERC are a little more touchy..
Vincent
Oh, didn't realize Server 2 was booted when you moved drives over. Not sure
about storcli but there is a perccli from 2015 available from Dell. Might be
able to do something with that.
[root@vs07 plugins]# /opt/MegaRAID/perccli/perccli64 -v
PercCli SAS Customization Utility Ver 1.17.10 October 21, 2015
(c)Copyright 2015, AVAGO Corporation, All Rights Reserved.
Exit Code: 0x00
[root@vs07 plugins]# rpm -qf /opt/MegaRAID/perccli/perccli64
perccli-1.17.10-1.noarch
_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
