New installation: Best way to preserve raid and shares?

berritorre · 12. Februar 2018

I have upgraded from 2.x to 3.x. This worked fine, except for the GUI, which is not working anymore. So I got the recommendation to make a clean install. This is what I wanted to avoid, because I would have to setup all the shares, users, etc again.

What will also happen with my Raid1? Will the new installation recognize this or will I have to set up a new raid? What will happen to the content of these 2 disks? Will it be still acessible?

How would you do this new install step-by-step to keep (transfer) as much as possible from my settings?

gderf · 12. Februar 2018

There is no way to transfer anything between an existing installation to a new installation, other than by using documentation. Every setting must be configured from scratch by hand. How well this turns out depends on the quality and completeness of your notes about the existing install, any screenshots of it you have taken, etc.

You can make a copy of the existing install's config.xml for reference purposes, but it can not be imported into another installation with the expectation that it this will work.

Since your upgrade from 2.x to 3.x worked fine except for a broken GUI, you should try your hardest to repair that before giving up.

berritorre · 12. Februar 2018

well, that is what I thought, but the recommendations here in the forum that I got and that I have seen where all: do a fresh install.

Is there any tutorial for getting the GUI to work?

I followed this blog post, but could not get it fixed: https://www.penguinpunk.net/bl…ting-from-2-2-x-to-3-0-x/

Where do I start to find out what stops the gui from working? Currently I am getting 502 error.

berritorre · 12. Februar 2018

by the way: is 4.x stable already? Because while I am going through the hassle I might just go the next step as well to have some time without any upgrade.

gderf · 12. Februar 2018

Zitat von berritorre

by the way: is 4.x stable already? Because while I am going through the hassle I might just go the next step as well to have some time without any upgrade.

I am running 4.x and have had no problems with it so far.

Before committing to a 4.x install, you should review your use of plugins and confirm which ones are available on OMV 4.x and which are not.

For those that are unavailable on 4.x, you will have to decide how important they are to you and what you are willing to do to get those programs running on 4.x. Your choices are essentially: run dockers, manually install the programs if they and any required dependencies are compatible with OMV, or use an alternative program that does have a 4.x plugin.

Yes, a fresh install seems to be the most often recommendation.

I started with OMV 2.x, upgraded it to 3.x, and then upgraded again to 4.x. If I could not have upgraded and was forced to do a fresh install each time, I would have stuck with 2.x. The upgrade from 2.x to 3.x was highly challenging and it took several tries to get it completed. The upgrade from 3.x to 4.x was uneventful.

Good luck.

berritorre · 12. Februar 2018

So I am currently investigating this.

I found this approach and went for it: https://www.unixmen.com/how-i-…nx-502-bad-gateway-error/

When trying to restart nginx I got an error message and then went for "systemctl status nginx.service". And this came out: Unfortunately I don't really understand what it means, so I will have to do some investigation on that too.

Code

root@XXX:~# systemctl status nginx.service
● nginx.service - A high performance web server and a reverse proxy server
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled)
   Active: failed (Result: exit-code) since Mon 2018-02-12 14:18:41 -02; 16s ago
  Process: 1206 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /run/nginx.pid (code=exited, status=1/FAILURE)
  Process: 4131 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)
  Process: 4129 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
 Main PID: 998 (code=exited, status=0/SUCCESS)


Feb 12 14:18:38 pdb-matrix nginx[4131]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Feb 12 14:18:39 pdb-matrix nginx[4131]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Feb 12 14:18:39 pdb-matrix nginx[4131]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Feb 12 14:18:40 pdb-matrix nginx[4131]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Feb 12 14:18:40 pdb-matrix nginx[4131]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Feb 12 14:18:41 pdb-matrix nginx[4131]: nginx: [emerg] still could not bind()
Feb 12 14:18:41 pdb-matrix systemd[1]: nginx.service: control process exited, code=exited status=1
Feb 12 14:18:41 pdb-matrix systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Feb 12 14:18:41 pdb-matrix systemd[1]: Unit nginx.service entered failed state.

Alles anzeigen

ryecoaaron · 12. Februar 2018

As mentioned on your other thread, there is probably a conflict with apache.

berritorre · 12. Februar 2018

Thanks @ Ryecoaaron, I'll be looking into this apache issue.

I am now wondering if it wouldn't be more sensible to go straight to 4.x and see what problems appear there. I don't know if I should fix this problem first in 3.x or rather go to 4.x and see what problems will appear there?

I was also checking on the plugins, as @gderf suggested and I noticed that the USB-Backup plugin doesn't exit for both, 3.x and 4.x. Has this moved into core? this is the main plugin I am using to make my offsite backups every week.
http://omv-extras.org/joomla/i…hp/omv-plugins-3/3-stable

ryecoaaron · 12. Februar 2018

Zitat von berritorre

I am now wondering if it wouldn't be more sensible to go straight to 4.x

I would use 4.x.

Zitat von berritorre

I noticed that the USB-Backup plugin doesn't exit for both, 3.x and 4.x.

openmediavault-usbbackup is a core plugin and always has been. openmediavault-backup is an omv-extras plugin but wouldn't make offsite backups. Looking at my OMV 4.x installs, the usbbackup plugin is in the list.

berritorre · 12. Februar 2018

Great to know! I'll give the upgrade to 4.x a try and see what happens then. More than having to do a fresh install can't really happen, which currently is the most recommended solution anyway.

berritorre · 12. Februar 2018

OK, so I ran the upgrade to 4.x. Seemed to run all fine, can connect to the shares, etc. But I am still running into the same problem as before with the GUI (502 Bad Gateway).

At the end of the process, I got the following error messages:

So there seems to be a problem with openmediavault and php7.0-fpm, correct?

Any suggestions?

Bash

Configuration file '/etc/default/openmediavault'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
 ==> Keeping old config file as default.
Created symlink /etc/systemd/system/multi-user.target.wants/openmediavault-issue.service -> /lib/systemd/system/openmediavaul                                                                     t-issue.service.
Updating configuration database ...
chown: invalid group: ':openmediavault-config'
ERROR: Failed to create the default configuration: Command '['/usr/share/openmediavault/confdb/create.d/conf.sh']' returned n                                                                     on-zero exit status 1
dpkg: error processing package openmediavault (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Processing triggers for php7.0-fpm (7.0.27-0+deb9u1) ...
Job for php7.0-fpm.service failed because the control process exited with error code.
See "systemctl status php7.0-fpm.service" and "journalctl -xe" for details.
invoke-rc.d: initscript php7.0-fpm, action "restart" failed.
* php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
   Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2018-02-12 17:00:31 -02; 25ms ago
     Docs: man:php-fpm7.0(8)
  Process: 25259 ExecStart=/usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf (code=exited, status                                                                     =78)
 Main PID: 25259 (code=exited, status=78)


Feb 12 17:00:30 pdb-matrix systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
Feb 12 17:00:31 pdb-matrix php-fpm7.0[25259]: [12-Feb-2018 17:00:31] ERROR: [pool openmediavault-webgui] cannot get u…webgui'
Feb 12 17:00:31 pdb-matrix php-fpm7.0[25259]: [12-Feb-2018 17:00:31] ERROR: FPM initialization failed
Feb 12 17:00:31 pdb-matrix systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/n/a
Feb 12 17:00:31 pdb-matrix systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
Feb 12 17:00:31 pdb-matrix systemd[1]: php7.0-fpm.service: Unit entered failed state.
Feb 12 17:00:31 pdb-matrix systemd[1]: php7.0-fpm.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package php7.0-fpm (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for resolvconf (1.79) ...
Processing triggers for ca-certificates (20161130+nmu1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for dbus (1.10.24-0+deb9u1) ...
Processing triggers for systemd (232-25+deb9u1) ...
Errors were encountered while processing:
 openmediavault
 php7.0-fpm
E: Sub-process /usr/bin/dpkg returned an error code (1)

Alles anzeigen

Jetzt mitmachen!