Thanks for the advice.
If you say that reinstall would be better that is what I will do when I overcome my laziness.
Thanks for the advice.
If you say that reinstall would be better that is what I will do when I overcome my laziness.
The full output of the upgrade would be better. It is really hard to tell where it is going wrong. Maybe a fresh install would be better.
I did provide full log as well. Here it is again.
I succeeded in restoring from backup and precoded with the release upgrade again
Some hand picked errors during installation here.
Should I be worried? Should I do something? Should I restore from backup and only think about migrating by full reinstall?
Full terminal log
Inside the browser UI I am greeted by message saying there are pending changes for :
When I tired to apply them an errors occur - log copied from UI
Thanks for helping me.
Going go and try refreshing my memory how the restore works Haven't used it since I set it up and tested that it works a while back.
What is you definition of "well"?
I replaced couple of files that had 'conflicts' during install with the package owner version and not mine. More importantly it ended with errors:
Installing new version of config file /etc/udev/rules.d/99-openmediavault-nonrot.rules ...
Failed to stop ntp.service: Unit ntp.service not loaded.
Unit ntp.service does not exist, proceeding anyway.
Created symlink /etc/systemd/system/ntp.service → /dev/null.
Failed to stop systemd-timesyncd.service: Unit systemd-timesyncd.service not loaded.
Unit systemd-timesyncd.service does not exist, proceeding anyway.
Created symlink /etc/systemd/system/systemd-timesyncd.service → /dev/null.
Creating configuration database ...
Migrating configuration database ...
Running migration conf_6.0.0
Running migration conf_6.0.7
Running migration conf_6.0.31
Running migration conf_6.3.2
Running migration conf_6.3.3
Running migration conf_6.3.11
Running migration conf_6.4.0
Setting up Salt environment ...
[ERROR ] Unable to connect pusher: Stream is closed
[ERROR ] Unable to connect pusher: Stream is closed
[ERROR ] Unable to connect pusher: Stream is closed
[ERROR ] Unable to connect pusher: Stream is closed
[ERROR ] Unable to connect pusher: Stream is closed
[ERROR ] Unable to connect pusher: Stream is closed
[ERROR ] Unable to connect pusher: Stream is closed
[ERROR ] Unable to connect pusher: Stream is closed
[ERROR ] Unable to connect pusher: Stream is closed
[ERROR ] Unable to connect pusher: Stream is closed
[ERROR ] Unable to connect pusher: Stream is closed
[ERROR ] Unable to connect pusher: Stream is closed
Processing system modifications ...
[ERROR ] Parent directory not present
[ERROR ] Command 'php-fpm7.4' failed with return code: 127
[ERROR ] stderr: /bin/bash: line 1: php-fpm7.4: command not found
[ERROR ] retcode: 127
[ERROR ] {'pid': 27392, 'retcode': 127, 'stdout': '', 'stderr': '/bin/bash: line 1: php-fpm7.4: command not found'}
/var/lib/dpkg/info/openmediavault.postinst: 948: /var/lib/dpkg/info/openmediavault.postinst: php7.4: not found
dpkg: error processing package openmediavault (--configure):
installed openmediavault package post-installation script subprocess returned error exit status 127
dpkg: dependency problems prevent configuration of openmediavault-omvextrasorg:
openmediavault-omvextrasorg depends on openmediavault (>= 6.4); however:
Package openmediavault is not configured yet.
dpkg: error processing package openmediavault-omvextrasorg (--configure):
dependency problems - leaving unconfigured
Processing triggers for dbus (1.12.24-0+deb10u1) ...
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...
Processing triggers for libc-bin (2.31-13+rpi1+deb11u6) ...
Processing triggers for rsyslog (8.1901.0-1+deb10u2) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for initramfs-tools (0.140) ...
Errors were encountered while processing:
openmediavault
openmediavault-omvextrasorg
E: Sub-process /usr/bin/dpkg returned an error code (1)
Display More
Should I continue with the fix5to6upgrade script?
I am in dire need of help.
So.. I did hit ctrl-c mid sudo omv-release-upgrade:
I wanted to copy a warning that poped up just in case I need it later :
dpkg: warning: unable to delete old directory '/var/www/openmediavault/js/omv/util': Directory not empty
dpkg: warning: unable to delete old directory '/usr/lib/systemd/system-sleep': Directory not empty
Stopping the update logs the following with a list of the affected packages after it:
W: --force-yes is deprecated, use one of the options starting with --allow instead.
W: Operation was interrupted before it could finish
W: APT had planned for dpkg to do more than it reported back (628 vs 2759).
How bad is it can I 'resume' it some how by rerunning the command or something?
Even if I can resume in some way would the update be guaranteed as if everything went ok the first try? Is it overall better to restoring my backup and then do a clean release upgrade?
Thank you for the response. Did it and things are churning along as normal.
I have the same error apt clean did not help. If i do apt update from CLI I have extra option to accept the change
QuoteE: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N]
Should I accept the change?
Yup making a live system clone with borgupdates is too advanced for me. For some reason it doesn't work their documentation says this should be the command
Where $DISK is I suppose my physical device lets say /dev/sda . I did try /dev/sda1 which where / is mounted with similar result. I exclude at least /dev because documentation says we might get into infinite loop if we try to back up /dev/zero with --read-special.
I will just stick to fsarchive for auto live back up. And from time to time I will make manual off-line back up using USBimager.
PS.
Borg/the plugin backs up the root file system, which you can specify if not detected automatically
FYI I did check out the source code and omv-backup plugin with option borg has the root hard coded in it. It will always back up only / directory. It will not care even if someone manually sets root dir form the plugin web interface.
Fsarchiver is great in this case because it is actually made to backup a file system to a compressed archive.
Borg is designed for normal file backup
For SD-cards, it's easier to simply clone them
Well I will looking into that. I will test making a full disk image with borg. If it works it could be added as a back up option.
BTW I did test fsarchiever and it works perfectly. I will use it if borg doesn't pin out. Thank you ryecoaaron for making it so easy to back up and restore.
I am using omv on a rpie. The system is installed on a SD
I decided to try out borg. Simulating a scenario where my SD card dies.
My boot is a separate partition and it seems that borg doesn't back up those files. I was wondering if it is the same for you?
When I tried to list the files in the boot dir it shows no files. Don't I need them to restore my /boot?
Seeing that you are running a VM I saw some info in borg documentation check it. Dunno how relevant that is.
I will try fsarchiever and maybe use that.