Beiträge von Flaschie

Calculating upgrade...
The following packages were automatically installed and are no longer required:
  dkms libelf-dev libnvpair1linux libuutil1linux libzfs2linux libzpool2linux
  linux-headers-amd64 spl-dkms zfs-dkms
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  openmediavault-zfs sysv-rc zfs-zed zfsutils-linux
The following NEW packages will be installed:
  libeinfo1 librc1 openrc
The following packages will be upgraded:
  zfs-dkms
1 upgraded, 3 newly installed, 4 to remove and 0 not upgraded.

>>> *************** Error ***************
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --allow-downgrades --allow-change-held-packages --fix-broken --fix-missing --auto-remove --allow-unauthenticated --show-upgraded --option DPkg::Options::="--force-confold" install libeinfo1 librc1 openmediavault-zfs openrc sysv-rc zfs-dkms zfs-zed zfsutils-linux 2>&1' with exit code '100': Leser pakkelister...


Skaper oversikt over avhengighetsforhold...


Leser tilstandsinformasjon...


sysv-rc er allerede den nyeste version (2.88dsf-59.9).
openmediavault-zfs er allerede den nyeste version (4.0.4).
Noen pakker ble ikke installeres. Dette kan bety at du har bedt om
en umulig tilstand eller, hvis du bruker den ustabile utgaven av Debian,
at visse kjernepakker ennå ikke er laget eller flyttet ut av «Incoming» for
distribusjonen.
Følgende informasjon kan være til hjelp med å løse problemet:


Følgende pakker har uinnfridde avhengighetsforhold:
 openrc : Avhenger av: insserv men skal ikke installeres
          Er i konflikt med: sysv-rc men 2.88dsf-59.9 skal installeres
 sysv-rc : Avhenger av: insserv (> 1.12.0-10) men skal ikke installeres
E: Klarer ikke å rette problemene, noen ødelagte pakker er holdt tilbake.
<<< *************************************

#! /bin/sh
#
# Calomel.org
#     https://calomel.org/zfs_health_check_script.html
#     FreeBSD ZFS Health Check script
#     zfs_health.sh @ Version 0.17


#Updates by Arve: ##


##Removed `hostname` from start of emailSubject as OMV does this automatically
##Changed email from <root@<OMV_NAME>.localdomain> to <root@<OMV_NAME>.LAN> to fit OMV3 (a bug maybe? missing environmental vars? also working: root, name.nameson@domain.end)


# Check health of ZFS volumes and drives. On any faults send email.




# 99 problems but ZFS aint one
problems=0




# Health - Check if all zfs volumes are in good condition. We are looking for
# any keyword signifying a degraded or broken array.


condition=$(/sbin/zpool status | egrep -i '(DEGRADED|FAULTED|OFFLINE|UNAVAIL|REMOVED|FAIL|DESTROYED|corrupt|cannot|unrecover)')
if [ "${condition}" ]; then
        emailSubject="ZFS pool - HEALTH fault"
        problems=1
fi




##Moved capacity check to bottom (don't need capacity warnings if pool errors exists...)




# Errors - Check the columns for READ, WRITE and CKSUM (checksum) drive errors
# on all volumes and all drives using "zpool status". If any non-zero errors
# are reported an email will be sent out. You should then look to replace the
# faulty drive and run "zpool scrub" on the affected volume after resilvering.


if [ ${problems} -eq 0 ]; then
   errors=$(/sbin/zpool status | grep ONLINE | grep -v state | awk '{print $3 $4 $5}' | grep -v 000)
   if [ "${errors}" ]; then
        emailSubject="ZFS pool - Drive Errors"
        problems=1
   fi
fi




# Scrub Expired - Check if all volumes have been scrubbed in at least the last
# 8 days. The general guide is to scrub volumes on desktop quality drives once
# a week and volumes on enterprise class drives once a month. You can always
# use cron to schedual "zpool scrub" in off hours. We scrub our volumes every
# Sunday morning for example.
#
# Scrubbing traverses all the data in the pool once and verifies all blocks can
# be read. Scrubbing proceeds as fast as the devices allows, though the
# priority of any I/O remains below that of normal calls. This operation might
# negatively impact performance, but the file system will remain usable and
# responsive while scrubbing occurs. To initiate an explicit scrub, use the
# "zpool scrub" command.
#
# The scrubExpire variable is in seconds. So for 8 days we calculate 8 days
# times 24 hours times 3600 seconds to equal 691200 seconds.


##scrubExpire=691200
##
##if [ ${problems} -eq 0 ]; then
##   currentDate=$(date +%s)
##   zfsVolumes=$(/sbin/zpool list -H -o name)
##
##  for volume in ${zfsVolumes}
##   do
##    if [ $(/sbin/zpool status $volume | egrep -c "none requested") -ge 1 ]; then
##        printf "ERROR: You need to run \"zpool scrub $volume\" before this script can monitor the scrub expiration time."
##        break
##    fi
##    if [ $(/sbin/zpool status $volume | egrep -c "scrub in progress|resilver") -ge 1 ]; then
##        break
##    fi
##
##    ### Ubuntu with GNU supported date format
##    #scrubRawDate=$(/sbin/zpool status $volume | grep scrub | awk '{print $11" "$12" " $13" " $14" "$15}')
##    #scrubDate=$(date -d "$scrubRawDate" +%s)
##
##    ### FreeBSD with *nix supported date format
##     scrubRawDate=$(/sbin/zpool status $volume | grep scrub | awk '{print $15 $12 $13}')
##     scrubDate=$(date -j -f '%Y%b%e-%H%M%S' $scrubRawDate'-000000' +%s)
##
##     if [ $(($currentDate - $scrubDate)) -ge $scrubExpire ]; then
##        emailSubject="ZFS pool - Scrub Time Expired. Scrub Needed on Volume(s)"
##        problems=1
##     fi
##   done
##fi




# Capacity - Make sure the pool capacity is below 80% for best performance. The
# percentage really depends on how large your volume is. If you have a 128GB
# SSD then 80% is reasonable. If you have a 60TB raid-z2 array then you can
# probably set the warning closer to 95%.
#
# ZFS uses a copy-on-write scheme. The file system writes new data to
# sequential free blocks first and when the uberblock has been updated the new
# inode pointers become valid. This method is true only when the pool has
# enough free sequential blocks. If the pool is at capacity and space limited,
# ZFS will be have to randomly write blocks. This means ZFS can not create an
# optimal set of sequential writes and write performance is severely impacted.


maxCapacity=85


if [ ${problems} -eq 0 ]; then
   capacity=$(/sbin/zpool list -H -o capacity | cut -d'%' -f1)
   for line in ${capacity}
     do
       if [ $line -ge $maxCapacity ]; then
         emailSubject="ZFS pool - Capacity Exceeded"
         zpool list | mail -s "$emailSubject" root@<OMV_NAME>.LAN ##Added email here for capacity issues (use "zpool list" in this email)
       fi
     done
fi




# Email - On any problems send email with drive status information and
# capacities including a helpful subject line. Also use logger to write the
# email subject to the local logs. This is also the place you may want to put
# any other notifications like playing a sound file, beeping the internal 
# speaker, paging someone or updating Nagios or even BigBrother.


if [ "$problems" -ne 0 ]; then
  ##OMV mail
  zpool status -v | mail -s "$emailSubject" root@<OMV_NAME>.LAN
  ##printf '%s\n' "$emailSubject" "" "`/sbin/zpool list`" "" "`/sbin/zpool status`" | /usr/bin/mail -s "$emailSubject" root@localhost
  ##logger $emailSubject
fi


##log
logger "ZFS Health check completed"


### EOF ###

autoshutdown[26927]: INFO: ' new supervision cycle started - check active hosts or processes'
autoshutdown[26927]: INFO: ' Checking the time: stay up or shutdown ...'
autoshutdown[26927]: INFO: ' System is in Stayup-Range. No need to do anything. Sleeping ...'
autoshutdown[26927]: INFO: ' Sleeping until 1:55 -> 0 seconds'
autoshutdown[26927]: INFO: ' sleep for 180s.'
autoshutdown[26927]: INFO: '------------------------------------------------------'
autoshutdown[26927]: INFO: ' new supervision cycle started - check active hosts or processes'
autoshutdown[26927]: INFO: ' Checking the time: stay up or shutdown ...'
autoshutdown[26927]: INFO: ' System is in Stayup-Range. No need to do anything. Sleeping ...'
autoshutdown[26927]: INFO: ' Sleeping until 1:55 -> 0 seconds'
autoshutdown[26927]: INFO: ' sleep for 180s.'
autoshutdown[26927]: INFO: '------------------------------------------------------'
autoshutdown[26927]: INFO: ' new supervision cycle started - check active hosts or processes'
autoshutdown[26927]: INFO: ' Checking the time: stay up or shutdown ...'
autoshutdown[26927]: INFO: ' System is in Stayup-Range. No need to do anything. Sleeping ...'
autoshutdown[26927]: INFO: ' Sleeping until 1:55 -> 0 seconds'
autoshutdown[26927]: INFO: ' sleep for 180s.'
autoshutdown[26927]: INFO: '------------------------------------------------------'
autoshutdown[26927]: INFO: ' new supervision cycle started - check active hosts or processes'
autoshutdown[26927]: INFO: ' Checking the time: stay up or shutdown ...'
autoshutdown[26927]: INFO: ' System is in Stayup-Range. No need to do anything. Sleeping ...'
autoshutdown[26927]: INFO: ' Sleeping until 1:55 -> 0 seconds'
autoshutdown[26927]: INFO: ' sleep for 180s.'