installScript VS Collectd

I am using a Raspberry Pi 4 model B. The actual problem I have is, after executing the command wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash, the Pi shuts down as expected, but after trying to reboot it remains off (red light on and green light off). Trying to power it off and on again leads to the same result.

hpoddar@raspberrypi:~$ sudo wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash Redirecting output to ‘wget-log.3’. Current / permissions = 755 New / permissions = 755 Forcing IPv4 only for apt... Updating repos before installing... Ign:1 https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/4.4 InRelease Ign:2 https://repo.mongodb.org/apt/ubuntu jammy/mongodb-org/6.0 InRelease Fetched 229 kB in 11s (20.8 kB/s) Reading package lists... Done W: https://repo.mongodb.org/apt/ubuntu/dists/focal/mongodb-org/4.4/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. Installing lsb_release... Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded. Need to get 10.8 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 lsb-release all 11.1.0ubuntu4 [10.8 kB] Fetched 10.8 kB in 1s (12.9 kB/s) (Reading database ... 102650 files and directories currently installed.) Preparing to unpack .../lsb-release_11.1.0ubuntu4_all.deb ... Unpacking lsb-release (11.1.0ubuntu4) over (11.1.0ubuntu4) ... Setting up lsb-release (11.1.0ubuntu4) ... Processing triggers for man-db (2.10.2-1) ... NEEDRESTART-VER: 3.5 NEEDRESTART-KCUR: 5.15.0-1032-raspi NEEDRESTART-KEXP: 5.15.0-1032-raspi Supported architecture Unsupported version. Only Debian 10 (Buster) and 11 (Bullseye) are supported. Exiting...

Finally got it thanks to another reddit thread ! I've used this https://github.com/OpenMediaVault-Plugin-Developers/installScript

I get this error after using the following command: wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash

The script is the same as this one https://github.com/OpenMediaVault-Plugin-Developers/installScript/blob/master/install you can check it if you not trust the source

Not sure what you mean, you install Debian using the net install, just install ssh, then use the script to install OMV on top of Debian

In cases like this the suggestion is to use the Debian NetInstall if the network card works then deploy OMV using the script here

OMV-extras is easily installed via a script. It is designed to install OMV on top of Debian, but once it sees you already have OMV installed, it will just install OMV-extras (make sure sudo and wget are installed before running the script... apt install sudo wget)... https://github.com/OpenMediaVault-Plugin-Developers/installScript

Manual Debian install used to be kind of cumbersome, but OMV 6 has an install script that can be invoked with one line.

https://collectd.org/ does the gathering (and writing to RRDTool database, if you so desire) part very well. Many plugins, easy to add more (just return one line of text)

Still need RRD viewere but that's not a huge stack

And it scales all the way to hundreds of hosts, as on top of network send/receive of stats it supports few other write formats aside from just RRD files.

Then you will have same problems but now you can bother manufacturer about it!

Also unless there is something horribly wrong about how often data is written, that SSD should run for ages.

We ran (for a test) consumer SSDs in busy ES cluster and they still lasted like 2 years just fine

The whole setup was a bit of overcomplicated too. RAID10 with 5+1 or 7+1 (yes Linux can do 7 drive RAID10) with hotspare woud've been entirely fine, easier, and most likely faster. You need backups anyway so ZFS doesn't give you much here, just extra CPU usage

Either way, monitoring wait per drive (easy way is to just plug collectd [1] into your monitoring stack, it is light and can monitor A TON of different metrics)

* [1]https://collectd.org/

Collectd pulls metrics from the OS, applications, logfiles and external devices for use in monitoring systems, finding performance bottlenecks and capacity planning. hombre_sabio explains, "Collectd is a tiny daemon that gathers information from a system. It enables mechanisms to collect and observe the values in different techniques. It is an open-source monitoring tool to retrieve and manage SNMP master agents."

Setting up php7.4-fpm (7.4.25-1+deb11u1) ... Job for php7.4-fpm.service failed because a fatal signal was delivered to the co ntrol process. See "systemctl status php7.4-fpm.service" and "journalctl -xe" for details. invoke-rc.d: initscript php7.4-fpm, action "start" failed. ● php7.4-fpm.service - The PHP 7.4 FastCGI Process Manager Loaded: loaded (/lib/systemd/system/php7.4-fpm.service; enabled; vendor pre set: enabled) Active: failed (Result: signal) since Mon 2021-12-27 23:53:51 GMT; 215ms ag o Docs: man:php-fpm7.4(8) Process: 2755 ExecStart=/usr/sbin/php-fpm7.4 --nodaemonize --fpm-config /etc /php/7.4/fpm/php-fpm.conf (code=killed, signal=ILL) Process: 2756 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/ph p/php-fpm.sock /etc/php/7.4/fpm/pool.d/www.conf 74 (code=exited, status=0/SUCCES S) Main PID: 2755 (code=killed, signal=ILL) CPU: 281ms Dec 27 23:53:51 raspberrypi systemd[1]: Starting The PHP 7.4 FastCGI Process Man ager... Dec 27 23:53:51 raspberrypi systemd[1]: php7.4-fpm.service: Main process exited, code=killed, status=4/ILL Dec 27 23:53:51 raspberrypi systemd[1]: php7.4-fpm.service: Failed with result ' signal'. Dec 27 23:53:51 raspberrypi systemd[1]: Failed to start The PHP 7.4 FastCGI Proc ess Manager. dpkg: error processing package php7.4-fpm (--configure): installed php7.4-fpm package post-installation script subprocess returned error exit status 1 Setting up collectd (5.12.0-7.1) ... Job for collectd.service failed because a fatal signal was delivered to the cont rol process. See "systemctl status collectd.service" and "journalctl -xe" for details. invoke-rc.d: initscript collectd, action "restart" failed. ● collectd.service - Statistics collection and monitoring daemon Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor prese t: enabled) Active: activating (auto-restart) (Result: signal) since Mon 2021-12-27 23: 53:52 GMT; 200ms ago Docs: man:collectd(1) man:collectd.conf(5) https://collectd.org Process: 2768 ExecStartPre=/usr/sbin/collectd -t (code=killed, signal=SEGV) CPU: 24ms dpkg: error processing package collectd (--configure): installed collectd package post-installation script subprocess returned error e xit status 1 dpkg: dependency problems prevent configuration of openmediavault: openmediavault depends on collectd; however: Package collectd is not configured yet. dpkg: error processing package openmediavault (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: php7.4-fpm collectd openmediavault E: Sub-process /usr/bin/dpkg returned an error code (1)

For metrics storage I'm using a Graphite database and the graph UI itself is Grafana. To get these I'm using the Debian repos they supply with mostly off-the-shelf configs. For collecting metrics from the Pi to send to Graphite I use collectd. It has a lot of off-the-shelf plugins you can use to grab metrics like CPU usage & load average, network in/out, memory stats etc. The Minecraft-specific stuff you can get from configuring collectd plugins as well, like the tick lag graph I use the "tail" plugin to follow and parse the server log.

For monitoring, personally I use collectd and Collectd Graph Panel (sadly the latter is abandoned, but it still works fine)