search

OpenMediaVault-Plugin-Developers / installScript

script that installs omv-extras and openmediavault if not installed already.
1.07k stars 206 forks source link

OMV Installation fails on Raspberry Pi 2 Model B #104

Closed moeinio closed 2 years ago

moeinio commented 2 years ago

OMV Installation fails on Raspberry Pi 2 Model B. The installation fails to process php7.4-fpm, collectd and openmediavault

here is part of the terminal output:

`update-alternatives: using /usr/bin/php-cgi.default to provide /usr/bin/php-cgi (php-cgi) in auto mode update-alternatives: using /usr/lib/cgi-bin/php.default to provide /usr/lib/cgi-bin/php (php-cgi-bin) in auto mode Setting up libpangocairo-1.0-0:armhf (1.46.2-3) ... Setting up librrd8:armhf (1.7.2-3+b2) ... Setting up samba-vfs-modules:armhf (2:4.13.13+dfsg-1~deb11u4) ... Setting up collectd (5.12.0-7.1) ... Job for collectd.service failed because a fatal signal was delivered to the control 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 preset: enabled) Active: activating (auto-restart) (Result: signal) since Fri 2022-08-19 11:36:47 CEST; 191ms ago Docs: man:collectd(1) man:collectd.conf(5) https://collectd.org Process: 18305 ExecStartPre=/usr/sbin/collectd -t (code=killed, signal=SEGV) CPU: 21ms dpkg: error processing package collectd (--configure): installed collectd package post-installation script subprocess returned error exit 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 Setting up rrdcached (1.7.2-3+b2) ... Setting up salt-minion (3003+ds-1) ... Created symlink /etc/systemd/system/multi-user.target.wants/salt-minion.service → /lib/systemd/system/salt-minion.service. Setting up samba-common-bin (2:4.13.13+dfsg-1~deb11u4) ... Checking smb.conf with testparm Load smb config files from /etc/samba/smb.conf Loaded services file OK. Weak crypto is allowed Server role: ROLE_STANDALONE

Done Setting up rrdtool (1.7.2-3+b2) ... Setting up samba (2:4.13.13+dfsg-1~deb11u4) ... Adding group `sambashare' (GID 118) ... Done. Samba is not being run as an AD Domain Controller: Masking samba-ad-dc.service Please ignore the following error about deb-systemd-helper not finding those services. (samba-ad-dc.service masked) Created symlink /etc/systemd/system/multi-user.target.wants/nmbd.service → /lib/systemd/system/nmbd.service. Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked. /usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory Created symlink /etc/systemd/system/multi-user.target.wants/smbd.service → /lib/systemd/system/smbd.service. samba-ad-dc.service is a disabled or a static unit, not starting it. Setting up wsdd (0.7+gitc87819b) ... Created symlink /etc/systemd/system/multi-user.target.wants/wsdd.service → /lib/systemd/system/wsdd.service. Setting up liblvm2cmd2.03:armhf (2.03.11-2.1) ... Setting up dmeventd (2:1.02.175-2.1) ... Created symlink /etc/systemd/system/sockets.target.wants/dm-event.socket → /lib/systemd/system/dm-event.socket. dm-event.service is a disabled or a static unit, not starting it. Setting up lvm2 (2.03.11-2.1) ... update-initramfs: deferring update (trigger activated) Created symlink /etc/systemd/system/sysinit.target.wants/blk-availability.service → /lib/systemd/system/blk-availability.service. Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-monitor.service → /lib/systemd/system/lvm2-monitor.service. Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-lvmpolld.socket → /lib/systemd/system/lvm2-lvmpolld.socket. Processing triggers for dbus (1.12.20-2) ... Processing triggers for initramfs-tools (0.140) ... Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u3) ... Processing triggers for rsyslog (8.2102.0-2+deb11u1) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for php7.4-cli (7.4.30-1+deb11u1) ... Processing triggers for php7.4-fpm (7.4.30-1+deb11u1) ... Job for php7.4-fpm.service failed because a fatal signal was delivered to the control process. See "systemctl status php7.4-fpm.service" and "journalctl -xe" for details. invoke-rc.d: initscript php7.4-fpm, action "restart" failed. ● php7.4-fpm.service - The PHP 7.4 FastCGI Process Manager Loaded: loaded (/lib/systemd/system/php7.4-fpm.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Fri 2022-08-19 11:42:13 CEST; 189ms ago Docs: man:php-fpm7.4(8) Process: 20708 ExecStart=/usr/sbin/php-fpm7.4 --nodaemonize --fpm-config /etc/php/7.4/fpm/php-fpm.conf (code=killed, signal=ILL) Process: 20709 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.4/fpm/pool.d/www.conf 74 (code=exited, status=0/SUCCESS) Main PID: 20708 (code=killed, signal=ILL) CPU: 250ms

Aug 19 11:42:12 pi systemd[1]: Starting The PHP 7.4 FastCGI Process Manager... Aug 19 11:42:13 pi systemd[1]: php7.4-fpm.service: Main process exited, code=killed, status=4/ILL Aug 19 11:42:13 pi systemd[1]: php7.4-fpm.service: Failed with result 'signal'. Aug 19 11:42:13 pi systemd[1]: Failed to start The PHP 7.4 FastCGI Process Manager. dpkg: error processing package php7.4-fpm (--configure): installed php7.4-fpm package post-installation script subprocess returned error exit status 1 Processing triggers for php7.4-cgi (7.4.30-1+deb11u1) ... Errors were encountered while processing: collectd openmediavault php7.4-fpm E: Sub-process /usr/bin/dpkg returned an error code (1) failed to install openmediavault package. pi@pi:~ $ sudo apt install collectd Reading package lists... Done Building dependency tree... Done Reading state information... Done collectd is already the newest version (5.12.0-7.1). collectd set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up php7.4-fpm (7.4.30-1+deb11u1) ... Job for php7.4-fpm.service failed because a fatal signal was delivered to the control 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 preset: enabled) Active: failed (Result: signal) since Fri 2022-08-19 11:52:28 CEST; 190ms ago Docs: man:php-fpm7.4(8) Process: 21895 ExecStart=/usr/sbin/php-fpm7.4 --nodaemonize --fpm-config /etc/php/7.4/fpm/php-fpm.conf (code=killed, signal=ILL) Process: 21896 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.4/fpm/pool.d/www.conf 74 (code=exited, status=0/SUCCESS) Main PID: 21895 (code=killed, signal=ILL) CPU: 257ms

Aug 19 11:52:27 pi systemd[1]: Starting The PHP 7.4 FastCGI Process Manager... Aug 19 11:52:27 pi systemd[1]: php7.4-fpm.service: Main process exited, code=killed, status=4/ILL Aug 19 11:52:28 pi systemd[1]: php7.4-fpm.service: Failed with result 'signal'. Aug 19 11:52:28 pi systemd[1]: Failed to start The PHP 7.4 FastCGI Process 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 control 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 preset: enabled) Active: activating (auto-restart) (Result: signal) since Fri 2022-08-19 11:52:29 CEST; 170ms ago Docs: man:collectd(1) man:collectd.conf(5) https://collectd.org Process: 21908 ExecStartPre=/usr/sbin/collectd -t (code=killed, signal=SEGV) CPU: 20ms dpkg: error processing package collectd (--configure): installed collectd package post-installation script subprocess returned error exit 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)`

ryecoaaron commented 2 years ago

Did you follow the RPi install guide? https://forum.openmediavault.org/index.php?thread/28789-installing-omv6-or-omv5-on-raspberry-pi-s-armbian-sbc-s-i386-32-bit-platforms/

moeinio commented 2 years ago

yes i run this command after a fresh install and updating the packages: wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash

ryecoaaron commented 2 years ago

Since the php7.4-fpm package is failing to start, there isn't a lot the script can do. This package is a debian package not OMV or omv-extras. Is the SD card new?

moeinio commented 2 years ago

i have done nothing beside a fresh install and then sudo apt update and sudo apt upgrade. the SD card is not new but it works fine in my phone and nvidia shield tv the problem is that it breaks the package manager and whenever i try to install or update anything it retries to install these packages and fails.

ryecoaaron commented 2 years ago

And those problems can be caused by a bad SD card. Using it in your phone or shield doesn't touch anywhere as much sectors as an OMV install. I might have to get one of my RPi2s out to test.

What is the output of: cat /proc/cpuinfo

I would also be curious if installing the php7.4-fpm package before running the script would work.

moeinio commented 2 years ago

this is the output: 900032

ryecoaaron commented 2 years ago

That is not the output of the command I gave you. I want more than just the revision.

moeinio commented 2 years ago

this is the full output:

processor : 0 model name : ARMv6-compatible processor rev 7 (v6l) BogoMIPS : 697.95 Features : half thumb fastmult vfp edsp java tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xb76 CPU revision : 7

Hardware : BCM2835 Revision : 900032 Serial : 000000004448c273 Model : Raspberry Pi Model B Plus Rev 1.2

ryecoaaron commented 2 years ago

And that is why I didn't have the 900032 included originally. I need to revert that change. You have a Raspberry Pi Model B Plus Rev 1.2. It is NOT a Raspberry Pi 2. It will not work.

moeinio commented 2 years ago

Sorry for the confusion, i thought i have the raspberry Pi 2. so OMV cannot be installed on my raspberry pi?

ryecoaaron commented 2 years ago

It is possible with a lot of work involving rebuilding packages. But the RPi1 is VERY slow and almost unusable. I haven't taken my three RPi1s out of the box in years.