are the SMB Extra options set to the recommended settings in the refenced posting?
Beiträge von mi-hol
-
-
Apologize you are right, my statement was for OMV core and core plugins only
-
vague reference to OMV taking over all system config
that is incorrect, starting with OMV 5.6.13 all config files managed by OMV [update]core and core plugins are registered as "deviation" see https://github.com/openmediavault/openmediavault/issues/986
-
card "IO CREST Internal 5 Port Non-Raid SATA III 6GB/S Pci-E X4 Controller Card JMB585 Chipset SI-PEX40139"
Isn't the mentioned limitation below, too much of a restriction for flexible use?
"This card is only design for storage Use only, can not Boot any OS/ system drives" -
Sounds like a bug in SAMBA on ARM platform could be the root cause.
OMV is leveraging SAMBA as is without modification.
Did you consider to search in the SAMBA bug tracker and eventually raise an issue there?
-
the MOBO doesn't provide a NVMe interface, only:
SATA-600 -connectors: 2 x 7pin Serial ATA - 2 devices - RAID 0 / RAID 1 / RAID 10 / RAID 5
SATA-300 -connectors: 4 x 7pin Serial ATA - 4 devices - RAID 0 / RAID 1 / RAID 10 / RAID 5
-
So what performance are you currently getting?
Details on how to measure performance are in the post linked in my signature
-
To answer much more info about your hardware is needed.
Best in the signature
-
Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked.
invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed.
● lvm2-lvmpolld.service - LVM2 poll daemon
Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; vendor preset: enabled)
Active: inactive (dead)
Docs: man:lvmpolld(8)
Aug 04 14:38:03 raspberrypi systemd[1]: Started LVM2 poll daemon.
dpkg: error processing package lvm2 (--configure):
installed lvm2 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of openmediavault:
openmediavault depends on lvm2; however:
Package lvm2 is not configured yet.lvm2 seems to cause errors on RPI see [SOLVED ?!] Failed to update/upgrade OMV5 webgui/nginx fails/forbidden/refused to connect
-
from the log file provided
CodeThe system has been successfully converted. Processing triggers for man-db (2.8.5-2) ... run-parts: executing /root/openmediavault-upgrade-4.7/post.d/70-omv-salt /root/openmediavault-upgrade-4.7/post.d/70-omv-salt: 13: /root/openmediavault-upgrade-4.7/post.d/70-omv-salt: omv-salt: not found run-parts: /root/openmediavault-upgrade-4.7/post.d/70-omv-salt exited with return code 127
the last script running unsuccessfully is
did you find a more detailed log explaining the reason for the non-zero return code?
this script will need to finish successfully before the next script (sudo run.d/81-apt-dist-upgrade-omv) will work
-
the top 4 pinned posts in forum section for updates Updates/Upgrades
-
Trying to update my installation of OMV (ver 5.6.13-1)
OMV ver 5.6.13-1 is the latest stable version already!
what command did you run that gave above errors?
-
path where the script looks for omv-salt?
export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
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?
-
compulen, this is an old & lang resolved thread.
-
omv has wlan0 still in its configuration database.
The error should disappear when you enable wlan again following the RPI tutorial
https://www.raspberrypi.org/do…/wireless/wireless-cli.md -
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