# file ./MegaCli64 ./MegaCli64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.0, stripped # ./MegaCli64 Fatal error - Command Tool invoked with wrong parameters Exit Code: 0x01

# ./MegaCli64 --help Invalid input at or near token - Exit Code: 0x01

# ./MegaCli64 -h | wc -l 277

MegaCli -AdpPR -Dsbl|EnblAuto|EnblMan|Start|Suspend|Resume|Stop|Info|SSDPatrolReadEnbl |SSDPatrolReadDsbl |{SetDelay Val}|{-SetStartTime yyyymmdd hh}|{maxConcurrentPD Val} -aN|-a0,1,2|-aALL

Last (psychotic) episode we looked at how to download and install LSI controller management tools.Today's special will look at using them, or trying to, or finding reasons to be totally drunk.Ho hum. Err. 0x01 you say? -ESTUPIDUSER I guess.Invalid? --help? Erf. Uhm. Now I could really use some, err, help?Will -h work? Yes it does ... but ...But at least: Exit Code: 0x00 - yey?The bad news is the syntax of this ancient demon summoning device. To quote:First there's no explanation at all what AdpPR means. And that it's actually case-independant.Second one notes Dsbl instead of disable, because characters are precious (and why not use Off then?)And that's the best part of it.There's also a few excellent features in these "RAID" "Controllers" that might make you a bit grumpy.For example it will only boot off the first disk, so in JBOD mode (with software raid on top of it maybe?) if the first disk fails you will have to manually change the config at boot time to, err, boot. But on the upside it will stop if *any* disk has failed, or any array is degraded, so you'll do that often enough.You might ask, why software raid? Well - the controller firmware does not support growing volumes that are on a shared disk, so if you have [sda1 sda2] etc. and make a raid1 out of sd{a,b,c,d}1 and a raid5 out of sd{a,b,c,d}2 then you cannot grow these partitions in the future, which means you have to move all data away, destroy array, recreate array, copy back.And that's supposed to be the Market Leader ?!