UBUNTU RAID MONITOR INSTALL
UBUNTU RAID MONITOR DRIVER

The steps as follows is what I did to get it working for Ubuntu 16.04. Physicaldrive 2I:1:8 (port 2I:box 1:bay 8, Solid State SATA, 240.0 GB, OK) You can stop all active arrays by typing: sudo mdadm -stop -scan. Step outside of the mounted directory and unmount it by typing: cd.

UBUNTU RAID MONITOR INSTALL

It comes pre-installed some Linux distributions such as Ubuntu by default, otherwise install it as shown. To stop an array, the first step is to unmount it. Physicaldrive 2I:1:7 (port 2I:box 1:bay 7, Solid State SATA, 240.0 GB, OK) Sensors is a simple command-line utility that displays the current readings of all sensor chips including the CPU. Physicaldrive 1I:1:4 (port 1I:box 1:bay 4, Solid State SATA, 240.0 GB, OK) Physicaldrive 1I:1:3 (port 1I:box 1:bay 3, Solid State SATA, 240.0 GB, OK) Physicaldrive 2I:1:5 (port 2I:box 1:bay 5, SAS, 300 GB, OK)Īrray B (Solid State SATA, Unused Space: 0 MB) Physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 300 GB, OK) An easy example: ~]# hpacucli ctrl all show config You may need to also apt-get install lib32gcc1 lib32stdc++6 libc6-i386 to meet 32-bit prerequisites.įrom there, you can use some common hpacucli commands to obtain RAID status. In order to just get the RAID configuration and management software, pull the hpacucli utility down from HP's repository. That' more of a comprehensive approach that can generate SNMP traps and nifty email alerts. However, there is a Debian ProLiant Support Pack that includes agents and tools for Ubuntu/dpkg systems. Ubuntu and Debian have always had less official support from HP than the Red Hat/SuSE.

At the very least, you'll want the hpacucli command line utility. Regardless, your key to monitoring Smart Array RAID controllers is to install the HP Management Agents. With the newer driver, you won't see the CCISS block driver.

UBUNTU RAID MONITOR DRIVER

With the move from G5 to G6 servers, the HP RAID controller driver changed from the legacy CCISS driver to the new HPSA driver. Your drive device will vary depending on your Smart Array controller. Zenity -info -window-icon=/usr/share/icons/Humanity/devices/64/drive-harddisk.svg -text='A Test Message hast benn generated on device' $deviceĬan someone please help me, I did not find anything useful.What type of HP ProLiant server is this? (model and generation, please) Notify-send -urgency=critical -i '/usr/share/icons/Humanity/devices/64/drive-harddisk.svg' 'Raid test message' Zenity -info -window-icon=/usr/share/icons/Humanity/devices/64/drive-harddisk.svg -text='The Array '$device' is degraded because of disk '$3 Notify-send -urgency=critical -i '/usr/share/icons/Humanity/devices/64/drive-harddisk.svg' 'Disk '$3' in the Array '$device' is degraded' Zenity -info -window-icon=/usr/share/icons/Humanity/devices/64/drive-harddisk.svg -text='A failure has been detected on spare disk '$3' in the Array '$device Notify-send -urgency=critical -i '/usr/share/icons/Humanity/devices/64/drive-harddisk.svg' 'Spare Disk '$3' in the Array '$device' has a failure' It will daemonize and run in the background, sending an email to the specified address if it detects any problems related to a disk failure. Zenity -info -window-icon=/usr/share/icons/Humanity/devices/64/drive-harddisk.svg -text='A failure has been detected on disk '$3' in the Array '$device This will fire up mdadm to keep an eye on your arrays. by default (built-in), scan all partitions (/proc/partitions) and all containers for. nf Please refer to nf (5) for information about this file. When i kill the process afterwards and run mdadm -monitor -scan again, everything is ok and the script runs on failures. Notify-send -urgency=critical -i '/usr/share/icons/Humanity/devices/64/drive-harddisk.svg' 'Disk '$3' in the Array '$device' has a failure' the mdadm monitoring program is not working after boot.

# instruct the monitoring daemon where to send mail alertsĪRRAY /dev/md/0 metadata=1.2 UUID=bdb46a13:5602ce29:d84bf5cd:28e91923 name=ubuntu:0ĪRRAY /dev/md/1 metadata=1.2 UUID=e94eb878:bf152bd0:bdb66444:fce7ac6f name=ubuntu:1Īnd the /usr/local/bin/raid-evnt script #!/bin/bash # automatically tag new arrays as belonging to the local system # auto-create devices with Debian standard permissionsĬREATE owner=root group=disk mode=0660 auto=yes alternatively, specify devices to scan, using # by default (built-in), scan all partitions (/proc/partitions) and all # Please refer to nf(5) for information about this file. The mdadm monitoring program is not working after boot.

Ubuntu raid monitor