Well understood
Posts by carriba
-
-
Thank you for the obvious pointer
I am using the user "admin" now, authenticated with the default password, and am getting the following window.
Let me go through the setup panel....
-
Attached a sequence of six screen dumps taken form the web browser:
- Login window, populated with the user name "pi".
- First window after successful login displaying the "Dashboard" and underneath the message "Information: The dashboard has not yet been configured. To personalize it, please go to the settings page" (Note: the "settings page" is a hypertext label).
- After clicking the "settings page" hypertext label, the next 3rd window opens with overlapping check marks without description field. The "Save" button remains greyed out.
- After clicking the overlapping check marks, the "Save" button turns to a blue colour.
- After clicking the "Save" button, it reopens the same window after login as above the navigation reiterates ad infinitum.
- Last window shows the "Settings/Your profile" panel of the user "pi".
Not sure yet, if I can find anything on the OMV web browser logs for more details (digging through the log files).
-
Cookies are enabled on all web browsers, and full refresh of the OMV web page reveals the same observations as described before.
-
After a fresh installation of OMV 6, which went just fine on a headless Raspberry Pi device running the latest and updated version of Raspberry Pi Bullseye Lite-OS , I am encountering the following issue:
When I successfully log in with any modern browser on my PC (Edge and Firefox), I am landing on a message under the "Home/Dashboard" panel:
Information: The dashboard has not yet been configured. To personalise, please go to the settings page.
I click on the "settings page" hypertext link, which brings me to the "Home/Dashboard/Settings" panel that displays underneath some overlapped check marks on the same line and then further below the title "Enabled widgets".
I click all the check boxes that are all overlapped without particular message on the same line, and then click the "Save" button that changes its colour from grey to blue. I then click on the blue coloured Save button, which brings me back to above described "Home/Dashboard" panel with the same "Information" message.
Please, what is going on here?
-
Thank you for the feedback on this and do appreciate having forwarded the "What's all this with USB?" article.
It is not my intend to use any RAID setup with disks hanging on a single USB cable or hub. Though, for educational purposes it does merit a mention on how RAID can be setup with any kind of disks setup.
I stop here for now on this topic
-
The fact that this function does not exist is not because it cannot be implemented, it is designed that way precisely to avoid problems. Are you sure you need Raid? Do you know that Raid is not a backup? Do you have a separate backup of your data? If you continue with this you will need it.
The RAID function does exist on the OS level. Yes, I know that RAID is not a backup and am not using it for this purpose.
-
So, RAID configuration for external USB storage... Do the following at your own risk. As others have said, it's not a great idea, but if you are determined to do it, here's how you can fool OMV into letting you proceed.
a) install the LVM plugin available from omv-extras
b) Add each of your USB drives to LVM under Physical Volumes. disk1, disk2, disk3, etc.
c) Create a Volume Group for each physical volume. group1, group2, group3, etc.
c) Create a logical volume for each volume group. volume1, volume2, volume3, etc.
d) Head on over to RAID configuration, and all of your logical volumes should be available.
Is this a workaround for the above said? There is no "undocumented" feature available for OMV to still configure a RAID for a bunch of USB disks?
-
-
If you are using an unsupported release, you will have to be creative. Most disaster recovery won't involve a fresh install. It will be restoring a backup image.
Thank you for your feedback. A disaster recovery plan also considers a fresh installation and applying the necessary configuration settings to bring a platform back to its original state of operation.
Debian Stretch is still in an EOL LTS release as reviewed back some time ago, and, as such, OMV 4.x ought to be supported as well.
A re-installation ought to resolve my particular situation. This said, I will indeed spend some time and validate OMV 5.x in a test platform soon.
-
I went ahead with a bare metal install with OMV 4.x under Raspbian Stretch as my previous platform was running with this version and it goes faster for me
Thus, on the terminal prompt fired the command:
Code
Display Moresudo sh -c 'cat >> /etc/apt/sources.list.d/openmediavault.list' << EOF > deb http://packages.openmediavault.org/public arrakis main > # deb http://downloads.sourceforge.net/project/openmediavault/packages arrakis main > ## Uncomment the following line to add software from the proposed repository. > # deb http://packages.openmediavault.org/public arrakis-proposed main > # deb http://downloads.sourceforge.net/project/openmediavault/packages arrakis-proposed main > ## This software is not part of OpenMediaVault, but is offered by third-party > ## developers as a service to OpenMediaVault users. > # deb http://packages.openmediavault.org/public arrakis partner > # deb http://downloads.sourceforge.net/project/openmediavault/packages arrakis partner > EOF
Then I fired the command:
Codesudo sh -c 'apt update ; apt --allow-unauthenticated install openmediavault-keyring ; apt update'
And I got the following output:
Code
Display MoreHit:1 http://archive.raspberrypi.org/debian stretch InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease Get:3 http://packages.openmediavault.org/public arrakis InRelease [12.8 kB] Err:3 http://packages.openmediavault.org/public arrakis InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7E7A6C592EF35D13 NO_PUBKEY 24863F0C716B980B Reading package lists... Done W: GPG error: http://packages.openmediavault.org/public arrakis InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7E7A6C592EF35D13 NO_PUBKEY 24863F0C716B980B E: The repository 'http://packages.openmediavault.org/public arrakis InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package openmediavault-keyring Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease Hit:2 http://archive.raspberrypi.org/debian stretch InRelease Get:3 http://packages.openmediavault.org/public arrakis InRelease [12.8 kB] Err:3 http://packages.openmediavault.org/public arrakis InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7E7A6C592EF35D13 NO_PUBKEY 24863F0C716B980B Reading package lists... Done W: GPG error: http://packages.openmediavault.org/public arrakis InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7E7A6C592EF35D13 NO_PUBKEY 24863F0C716B980B E: The repository 'http://packages.openmediavault.org/public arrakis InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.
To me it looks like it is a matter to get access to the public GPG key. Is it possible to obtain access or enable the installation through other means?
Otherwise, how can you do a disaster recovery when you have been using OMV 4.x all the time?
-
It is a headless device, and if I can no longer access the device with a terminal application using SSH, then indeed I need to skip the network configuration part as mentioned above.
Need to flash again the SD card with the Raspberry Pi OS Buster "lite" image and start over again
, unless it goes faster with installing OMV 4.x under Raspbian Stretch
.
-
Due to installation challenges of OMV 5.x under Raspberry Pi OS Buster, I thought I give another try and reinstall OMV 4.x under Raspbian Stretch.
Are there any installation guides on how OMV 4.x can be installed under Raspbian Stretch? (The original OMV 4.x images are no longer available.)
I have found a pointer with the article titled Installing OMV 4.x under Raspbian Stretch on how the installation can be prepared and another note titled Installing OMV Extras for OMV4 under Raspbian Stretch on how the Extras can be installed.
Is there anything else that I may need to observe?
-
I have rebooted the device with a "sudo shutdown -r now ; exit", logged in again and relaunched the installation again as above, and this time the installation of the "nginx-full" package worked fine
.
Here an extract of the output of the transcript on my terminal:
Code
Display More[...] Setting up nginx-full (1.14.2-2+deb10u4) ... [ ok ] Upgrading binary: nginx. Setting up lsb-release (10.2019051400+rpi1) ... Setting up nginx (1.14.2-2+deb10u4) ... Setting up openmediavault (5.6.19-1) ... Creating users/groups ... Updating local package archive ... Updating service units ... Created symlink /etc/systemd/system/dbus-org.freedesktop.network1.service ? /lib/systemd/system/systemd-networkd.service. Created symlink /etc/systemd/system/multi-user.target.wants/systemd-networkd.service ? /lib/systemd/system/systemd-networkd.service. Created symlink /etc/systemd/system/sockets.target.wants/systemd-networkd.socket ? /lib/systemd/system/systemd-networkd.socket. Created symlink /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service ? /lib/systemd/system/systemd-networkd-wait-online.service. Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service ? /lib/systemd/system/systemd-resolved.service. Created symlink /etc/systemd/system/multi-user.target.wants/systemd-resolved.service ? /lib/systemd/system/systemd-resolved.service. systemd-journald.service is a disabled or a static unit, not starting it. [...]
The installation script moved forward, however I lost connection to the terminal during the installation step where the script was configuring network interfaces.
When I tried to log in again, and even again after a power recycle, I could no longer login to the device, always getting an "Acess denied" message despite supplying the known login name and the correct password
.
I powered the device off and on again (by unplugging the power cord and plugging it in again), still no luck: I can no longer login to the device
.
-
-
I started with a a fresh new image of the latest version of the Raspberry PI OS Buster, and have followed the online guide "Installing OMV", next to firing the OS packages repository updates also the commands:
Codesudo rm -f /etc/systemd/network/99-default.link wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash
However, the installation fails with an error message when processing the package "nginx-full"
.
Here the installation transcript with the relevant parts as displayed on my terminal:
Code
Display More[...] Setting up nginx-full (1.14.2-2+deb10u4) ... Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details. invoke-rc.d: initscript nginx, action "start" failed. ? nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2021-11-07 12:19:21 CET; 53ms ago Docs: man:nginx(8) Process: 14763 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE) Nov 07 12:19:21 raspberrypi systemd[1]: Starting A high performance web server and a reverse proxy server... Nov 07 12:19:21 raspberrypi nginx[14763]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) Nov 07 12:19:21 raspberrypi nginx[14763]: nginx: configuration file /etc/nginx/nginx.conf test failed Nov 07 12:19:21 raspberrypi systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE Nov 07 12:19:21 raspberrypi systemd[1]: nginx.service: Failed with result 'exit-code'. Nov 07 12:19:21 raspberrypi systemd[1]: Failed to start A high performance web server and a reverse proxy server. dpkg: error processing package nginx-full (--configure): installed nginx-full package post-installation script subprocess returned error exit status 1 Setting up netplan.io (0.95-2) ... Setting up salt-common (3003+ds-1) ... Setting up bsd-mailx (8.1.2-0.20180807cvs-1) ... update-alternatives: using /usr/bin/bsd-mailx to provide /usr/bin/mailx (mailx) in auto mode Setting up cpufrequtils (008-1.1) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Setting up proftpd-basic (1.3.6-4+deb10u6) ... Adding system user `proftpd' (UID 117) ... Adding new user `proftpd' (UID 117) with group `nogroup' ... Not creating home directory `/run/proftpd'. Adding system user `ftp' (UID 118) ... Adding new user `ftp' (UID 118) with group `nogroup' ... Creating home directory `/srv/ftp' ... '/usr/share/proftpd/templates/welcome.msg' -> '/srv/ftp/welcome.msg.proftpd-new' Setting up samba-common-bin (2:4.9.5+dfsg-5+deb10u1+rpi1) ... Checking smb.conf with testparm Load smb config files from /etc/samba/smb.conf Loaded services file OK. Server role: ROLE_STANDALONE Done Setting up php7.3-cli (7.3.31-1~deb10u1) ... update-alternatives: using /usr/bin/php7.3 to provide /usr/bin/php (php) in auto mode update-alternatives: using /usr/bin/phar7.3 to provide /usr/bin/phar (phar) in auto mode update-alternatives: using /usr/bin/phar.phar7.3 to provide /usr/bin/phar.phar (phar.phar) in auto mode Creating config file /etc/php/7.3/cli/php.ini with new version Setting up jq (1.5+dfsg-2+b1) ... Setting up rrdtool (1.7.1-2) ... Setting up samba (2:4.9.5+dfsg-5+deb10u1+rpi1) ... Adding group `sambashare' (GID 127) ... 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. Setting up php7.3-cgi (7.3.31-1~deb10u1) ... update-alternatives: using /usr/bin/php-cgi7.3 to provide /usr/bin/php-cgi (php-cgi) in auto mode update-alternatives: using /usr/lib/cgi-bin/php7.3 to provide /usr/lib/cgi-bin/php (php-cgi-bin) in auto mode Creating config file /etc/php/7.3/cgi/php.ini with new version Setting up php7.3-fpm (7.3.31-1~deb10u1) ... Creating config file /etc/php/7.3/fpm/php.ini with new version Created symlink /etc/systemd/system/multi-user.target.wants/php7.3-fpm.service ? /lib/systemd/system/php7.3-fpm.service. Setting up php-pam (1.0.3-1+deb10u1) ... Setting up proftpd-mod-vroot (0.9.4-2) ... dpkg: dependency problems prevent configuration of nginx: nginx depends on nginx-full (<< 1.14.2-2+deb10u4.1~) | nginx-light (<< 1.14.2-2+deb10u4.1~) | nginx-extras (<< 1.14.2-2+deb10u4.1~); however: Package nginx-full is not configured yet. Package nginx-light is not installed. Package nginx-extras is not installed. nginx depends on nginx-full (>= 1.14.2-2+deb10u4) | nginx-light (>= 1.14.2-2+deb10u4) | nginx-extras (>= 1.14.2-2+deb10u4); however: Package nginx-full is not configured yet. Package nginx-light is not installed. Package nginx-extras is not installed. dpkg: error processing package nginx (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of openmediavault: openmediavault depends on nginx; however: Package nginx is not configured yet. Package nginx-full which provides nginx is not configured yet. dpkg: error processing package openmediavault (--configure): dependency problems - leaving unconfigured Setting up php-yaml (2.0.2+1.3.1-4+b1) ... 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 wsdd (0.6.4+git6d5922e2-1) ... Created symlink /etc/systemd/system/multi-user.target.wants/wsdd.service ? /lib/systemd/system/wsdd.service. Setting up php-fpm (2:7.3+69) ... Setting up php-cgi (2:7.3+69) ... Setting up liblvm2cmd2.03:armhf (2.03.02-3) ... Setting up dmeventd (2:1.02.155-3) ... 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.02-3) ... 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 initramfs-tools (0.133+deb10u1) ... Processing triggers for libc-bin (2.28-10+rpt2+rpi1) ... Processing triggers for rsyslog (8.1901.0-1) ... Processing triggers for systemd (241-7~deb10u8+rpi1) ... Processing triggers for man-db (2.8.5-2) ... Errors were encountered while processing: nginx-full nginx openmediavault E: Sub-process /usr/bin/dpkg returned an error code (1) failed to install openmediavault package. [...]
Double-checking with the "journalctl -xe" command for further error messages, I am getting the following output:
Code
Display MoreNov 07 12:22:54 raspberrypi systemd[1]: Starting A high performance web server and a reverse proxy server... -- Subject: A start job for unit nginx.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit nginx.service has begun execution. -- -- The job identifier is 7906. Nov 07 12:22:54 raspberrypi nginx[20715]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) Nov 07 12:22:54 raspberrypi nginx[20715]: nginx: configuration file /etc/nginx/nginx.conf test failed Nov 07 12:22:54 raspberrypi systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStartPre= process belonging to unit nginx.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Nov 07 12:22:54 raspberrypi systemd[1]: nginx.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit nginx.service has entered the 'failed' state with result 'exit-code'. Nov 07 12:22:54 raspberrypi systemd[1]: Failed to start A high performance web server and a reverse proxy server. -- Subject: A start job for unit nginx.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit nginx.service has finished with a failure. -- -- The job identifier is 7906 and the job result is failed.
Thus, not sure if or whether any latest potential OS updates may break the installation. Do welcome any pointer(s) that may allow me troubleshoot further on above observed issues
.
-
[...] And once Debian stretch updates stop, you should not be using an unsupported distro let alone and unsupported version of OMV.
It did not mention anything about Debian Stretch. Sure, once the underlying OS is no longer supported, then most likely the original OMV version introduced for this Linux OS version is maybe no longer supported either. That's clear.
-
[...]
Just because it works fine doesn't mean you should stop moving to newer, supported versions.
I hate giving out these instructions because people will just stop upgrading...
For OMV 4.x only
cd /etc/apt/sources.list.d
sudo mv omv-extras-org.list omv-extras-org.bak
echo "deb https://openmediavault-plugin-developers.github.io/packages/debian arrakis main" | sudo tee omv-extras-org.list
cd /etc/apt/trusted.gpg.d/
sudo wget https://openmediavault-plugin-developers.github.io/packages/debian/omvextras2026.asc
sudo apt-key add omvextras2026.asc
sudo apt-get update
Please keep this repository up and running for OMV 4.1.36-1 (Arrakis). It is not about not willing to upgrade or use the latest version, it is simply that a running system like OMV 4.1.36-1 (Arrakis) should stay running using its best hardware today.
Thank you
-
I'm using OMV 4.1.7-1 (Arrakis) and when checking today for the latest available RPM updates for my NAS box, it seems now I have the choice of 2 different versions as outlined with:
user@nasbox:~ $ sudo apt list --upgradable -a
Listing... Done
openmediavault/arrakis,arrakis 4.1.28-1 all [upgradable from: 4.1.27-1]
openmediavault/now 4.1.27-1 all [installed,upgradable to: 4.1.28-1]Which one shall I choose to update my current platform?
-
Have a look at my posting "Windows 10 Creators failure to locate CIFS/SMB shares" to workaround the issue you're facing by simply launching the "Local Security Policy" tool, and under the branch "Security Options" and then under the option "Network Security: LAN Manager authentication level" , just change the settings from "Send LM & NTLM - use NTLMv2 session security if negotiated" to "Send NTLMv2 responses only".
This did work for my PCs running Windows 10 Home and Professional back some time ago.
To me it is clearly a Windows 10 issue as I can access the OMV's SMB shares with Windows 7, macOS High Sierra, Ubuntu MATE without any additional setup.
This said, I do not need to make these kind of changes on my Windows 10 PCs when accessing a SMB shared drive residing on a commercial NAS. Thus, it could be also an OMV setup issue.
Otherwise, setup an NFS server under OMV, and use NFS client that comes with Windows 10; see the "Setup NFS Client under Windows 10" guide on how to accomplish this. This is the approach I had to take for a PC running Windows 10 Enterprise as it is locked in a domain, and I could not perform above changes despite having admin rights.
Hope this helps!