I have my eyes on this asrock mb with ipmi for amd newegg.com/amp/asrock-rack-x47…cessors/p/N82E16813140023 price has gone down a little bit since last time I checked.
Quote from jethro67: “My issue is, how do I ensure omv only uses network X for internet access and not network Y? ” Both nics with static ip, one with gateway defined, the other one without.
Have you attempted to mount it in a standard Debian server? I can’t imagine there are issues on xfs and nfs4. Check the nfs server sys log should spit errors from clients mount attempts. the 16tb limit is on very old Fs created longer than 3 years ago, now omv adds the 64 bit flag on every ext4 format. Was your filesystem older than that ?
No. omv offers no cloud outgoing service. You will have to look for a third party solution (paid probably) or implement your own. A vpn tunnel link with certificate is your best option imo.
Quote from votdev: “Does anyone else realize that proftpd is not stopped when using systemctl stop proftpd. IMO the systemd integration is very bad. Hopefully the Debian package maintainers will fix that soonish. ” I think upstream they want the service to start via socket activation, the same approach can be used at the moment with ssh. Maybe you should adopt the package distribution via omv repos
There is always performance penalty but as long as the cpu has aes extensions should be fine, shouldnt decrease that dramatically, a standard Hdd is around 150-190MB/s it won’t cap enough to notice the degrade over gbit Ethernet.
I am pretty sure fstab dependencies are resolved by systemd only when Fs are natives, mergerfs escapes from this. I use overlay for a very specific case and the mount occurs after the Fs under is ready in all of the cases. that’s also why many sf binds fail when using mergerfs and zfs. There is always the option to go back to legacy fstab ordering using kernel boot parameter fstab=yes
Why don’t you try just /usr/bin/systemctl restart proftpd I don’t have this issue in my system, I saw it a couple of times in a testing vm but not anymore in my current file server.
Quote from djres79: “root@serv-fefe:~# uname -r 5.3.10-1-pve root@serv-fefe:~# modinfo aqc11 modinfo: ERROR: Module aqc11 not found. ” is aqc111, just run dmesg -w, unplug and replug the adapter, should load the driver and you should see in the log registering the iface
Is rejecting says is not matching. All i can think is omv not actually saving the keys This folder should have all the public keys by username /var/lib/openmediavault/ssh/authorized_keys You can check there and see if they match. Another option if your username has home folder is to use ssh-copy-id, but you need to have password auth enabled to be able to transfer the key
Leave putty a side for a moment,install a WSL, choose a distro and start creating the keys from there see how it goes. Once you set it try to login verbosely ssh -vvv -i ~/.ssh/privatekey user@ip
From what I can see the driver should be included in your kernel. I can’t check certainly because non of my servers has atm kernel higher than 4.19. if you run modinfo aqc111 does it return something? If so can you paste it here
Per share you can enable audit which should track the file operations. Don’t know where the log is stored for that but should be one of the files at /var/log/samba