On 12/15/11 16:40, Andrew Boyer wrote: > I'm not sure it would even be possible to come up with a worse interface. It > boggles the mind. > > I recommend you always run with this configuration: > > # MegaCli -AdpSetProp AutoEnhancedImportEnbl -aALL > # MegaCli -AdpSetProp MaintainPdFailHistoryEnbl -0 -aALL > > AutoEnhancedImportEnbl will bring the foreign disk back in on a reboot. LSI > recommends turning off MaintainPdFailHistory when using single-disk RAID0 > configurations. >
Any gotchas with this enabled? I'm thinking putting in a disk from another card, which is part of a raid, in this server, for instance. > To bring in a foreign disk without rebooting: > > # MegaCli -CfgForeign -Scan -aALL > # MegaCli -CfgForeign -Import [x] -aN (where x is the config number listed in > the scan, and N is the adapter number) > > Adding these capabilities to mfiutil is on my list of things to do, but it's > not ready yet. > > Has anyone managed to get the real JBOD mode working on this controller? It > advertises support in the firmware but doesn't seem to do anything. The > documentation only lists JBOD mode as a feature of the lower-end controllers. > > Hope this helps. > > -Andrew It does help - thanks! For the same disk being removed and then reinserted, the provided commands brought the disk/volume back to mfiutil show drives/volumes output, and after a zpool clear, ZFS has no complains. For recovery from a software-induced fail (mfiutil fail eX:sX), I couldn't perform a recovery using just mfiutil. MegaCli -PDOnline -PhysDrv[eX:sX] -aN did it, in that case. For the still-untested case of an altogether new disk being inserted, I guess mfiutil create jbod N would do the trick. BTW, the mfiutil is coredumping when provided with inexistant disks (just noticed) Regards, Hugo _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
