path where the script looks for omv-salt?
is used in all upgrade scripts.
If omv-salt is not found in one of these directories, openmediavault package could be corrupted on the download mirror server used. no idea how to fix that though.
Did you follow the guidelines in first post (copied below)?
Before you attempt any upgrade I recommend the following steps:
Make a full backup of your operating system and make sure you know how to play it back in case something awful happens.
Uninstall all unused plugins. Those make the upgrade harder. But if you don't use/need them then don't install them.
Disable all services running on the OMV machine except for SSH. This will prevent any users from trying to access these services during the upgrade process and it will also allow to remount the data partitions/devices with the shared folders, samba shares, etc. as read-only before attempting the upgrade (mandatory at the moment)
If the upgrade attempt is done remotely via SSH I highly recommend to install screen and run the script in a screen session (see below). Otherwise if the SSH connection breaks the console session will close too and the running script will be terminated even if it has not finished and leaves the system broken.
If you are running encryption (especially on the boot device), if you have unusual boot configurations (scripts), if you are running graphical desktop environments, if you have a lot of third party packages installed, or if you want to stay with sysvinit instead of systemd please make sure you read the Debian release notes. In these cases you are probably better off with a manual upgrade or you have to prepare your system before you can run the scripts.
a powered USB hub will work too
there was a package error in log:
dpkg: error: cannot access archive '/var/cache/apt/archives/libtommath1_1.0-4_armhf.deb': No such file or directory
E: Sub-process /usr/bin/dpkg returned an error code (2)
Mybe that is related. can you check or reinstall libtommath1?
well, printing 3A on a label versus actually delivering 3A consistently is the real difference for a power supply.
From forum and blog post at https://www.raspberrypi.org/blog/ it seems even the RPI foundation had issues to find a reliable supplier
or the power supply is not delivering enough power at full load. That is a common issue, especially if a non-genuine Raspberry Pi power supply is used.
Der Title "Log file" ist wohl zu unattraktiv
Unfortunately I just bought this 4 bay enclosure
please mention the brand & model, so at least others that read blog posts before they buy will benefit from your bad experience.
Usually dealers accept a return of sold good due to technical issues. Have you engaged their support?
the HDD enclosure /Sata to USB adapter is to blame for the low performance.
This is indicated by
a good enclosure / adapter would be supported by Driver=uas
I'm recommending enclosure / adapter with ASMedia chipsets.
Reasons can be found in https://github.com/openmediava…diavault/debian/changelog
you are not revealing hardware details of HDD and how you connect the HDD.
The quoted post mentions the commands to get these details
Maybe we could help but only if you'd reveal all necessary hardware details
omv-salt deploy run --no-color avahi 2>&1' with exit code '1': Destiny.flat.intranet: Data failed to compile:
---------- Rendering SLS 'base:omv.deploy.avahi.services.nfs' failed: Jinja error: shares: The value ' ' is not an object.
seems an issue caused by avahi.
THE PART "The value ' ' is not an object" could indicate avahi was not correctly configured before you tried to upgrade.
have a mix of php versions installed
yes, would have come to the same conclusion.
I don't know where they come from
usually other applications have been installed directly without placing them in a docker container, screwing OMV up.
Can I fix this somehow?
2. uninstall all other applications but watch out for "dependent packages" uninstall to not include openmediavault
i dont want to mess with configs omv will then rewrite on the next update.
next 5.x release will have a feature to flag the config files maintained by OMV clearly.
I'd doubt the requested feature will be implemented by OMV because it seems to be a unique setup and not in line with OMV approach to simplify a NAS setup.
Just my 2 cent
openmediavault (5.6.13-1) stable; urgency=low * Issue #986: Divert files modified by openmediavault to prevent problems when package updates want to override them.
The output is also nothing
Actually this is exactly what I expected, because grub is only used on X86/amd64 PC platform but not on ARM platform.
In other words nothing to worry about