search for: sas2ircu

Hi, John, John R Pierce wrote: > On 7/12/2016 10:19 AM, m.roth at 5-cent.us wrote: >> Got an older Dell R410, with an LSI 1068E PCI-Express Fusion-MPT SAS >> (rev 08). It*appears* that a) trying MegaRaid, and b) from what I'm >> googling, that what I need are mptfusion-related packages. >> Unfortunately, yum shows me nothing available in base, epel, or >>

...stems using their own brand name proprietary raid piles. there's a sas/scsi control command (it escapes me at the moment) which will turn on and off the backplane lights, but there's no standard glue for connecting this to the drive failure events. A quick batch of googling suggests sas2ircu (LSI proprietary?), and ledmon (https://sourceforge.net/projects/ledmon/) are worth investigating. I've printed labels with the partial WWN of the drives and stick them on each hot swap tray, and identified the failed drive via those. to verify, I'll do something like a dd if=/dev/mdX...

My setup: A SuperMicro 24-drive chassis with Intel dual-processor motherboard, three LSI SAS3081E controllers, and 24 SATA 2TB hard drives, divided into three pools with each pool a single eight-disk RAID-Z2. (Boot is an SSD connected to motherboard SATA.) This morning I got a cheerful email from my monitoring script: "Zchecker has discovered a problem on bigdawg." The full output is

>> #1. Map the physical drive slots to how they show up in FBSD so if a >> disk is removed and the machine is rebooted all the disks after that >> removed one do not have an 'off by one error'. i.e. if you have >> ada0-ada14 and remove ada8 then reboot - normally FBSD skips that >> missing ada8 drive and the next drive (that used to be ada9) is now