Posts by tsch

Thanks votdev.

So I have to check if there where any changes in KODI.

This is my etc/exports:

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.


# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
/export/OMV7-02 192.168.178.0/24(fsid=9608d0ca-2b34-4268-9fd0-50c21a573b13,rw,subtree_check,insecure)
/export 192.168.178.0/24(ro,fsid=0,root_squash,subtree_check,insecure)

After upgrading to the newest version of OMV 7.x I can't access the nfs share on my OMV 7 NAS.

Any changes and hints how to make the share available from my android-tv via KODI?

I've 4 OMV systems. 3x ASUS Mainboard and 1x MSI Barebone.

All are running the newest OMV 7.x and all have in common that Autoshutdown, if I don't reboot the NAS after having used ist for copying file to/from, freezes

I suppose a setting is wrong on all my OMV-NAS.

For what keyword do I have to search in which syslog file to find the problem?

I'll take a look at my BIOS Settings following your posted Link.

What exactly is the magic behind sudo omv-salt stage run deploy ?

I first thought this command just display settings but seems it solved my problem with the Web-GUI and I'm just curious why.

But the CLI still looks the same.

Indeed it's working now and I can access the web console again.

I'll take a look at the local CLI.

Thanks a lot for helping macom.

Radnabe

That wasn't intentional and I didn't realize this was exclusively your thread.

Do I need a Debian Linux or can I restore on a Ubuntu or eventualy Windows client?

Thanks a lot macon.

I'll give it a try using the plugin.

Attached the requested output.

I'm very interested in a working backup too.

What Backup-option would you suggest to backup an USB-Stick with the OMV-system?

And because backup is fine but successfull restore is finer: What exactly is the workflow for restoring the backup to an USB-Stick on another system?

Thanks a lot and maybe this would help other OMV-Users as well.

If anybody could help please.

And if any information is missing please give me a "call".

After my holiday I started one of my OMV-systems and couldn't access the webinterface.

Rebooting several times was successfull allowing me to access the webinterface to install updates but after rebooting no access again.

Acessing the OMV-Shares is possible, no problems there.

Hopefully someone with better LINUX-knowledge is able to isolate the error taking a look at the following Error-message on my console:

Thanks a lot for helping.

My three OMV-NAS are not running 24x7 becausse I use it for Backup/Archiving purposes only.

Unfortunately AutoShutdown is only working if I wake up my NAS using WOL and let it shutdown, when not used.

If I copy files from or to the OMV-NAS and afterwards shutdown should shuts down the OMV-NAS this doesn't work. I can't reach the OMV via webconsole nor use the shared folders on it.

Only a hard reset helps in this case.

Here my settings for AutoShutdown:

I managed to use the OMV-Backup to write the backup files to a shared folder.

My OMV boots from a USB-Stick and I'd like to make things easier and write the OMV backup directly to another attached USB-Stick using the integrated backup.

Is this possible?

Quote from ryecoaaron

Working lots of hours now. Don't have time to help with this. I would put omv-engined in debug mode and see if the output tells something when navigating to the remotemount plugin

login as root

monit stop omv-engined

omv-engined -df

Thank you ryecoaaron for "takover".

Maybe we're getting close to the problem:

omv-engined[168396]: Executing RPC (service=System, method=getInformation, params=[], context={"username":"admin","role":1}) ...
omv-engined[168396]:
PHP Fatal error:  Class OMV\System\Filesystem\Remote contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (OMV\System\Filesystem\FilesystemInterface::getDetails) in /usr/share/php/openmediavault/system/filesystem/remote.inc on line 28

Quote from Krisbee

Well, the latest set of logs and other posts since your last re-boot appear to show no errors during booting in journalctl , all expected remote systemd mounts have mounted correctly. Yet I assume you still have this persistent WEBUI error. Right now I'm out of ideas so perhaps the puling author ryecoaaron can assist.

Thank you very much for your help so far!

Here the requested output:

root@OMV7-02:~# systemctl -t mount | grep remote
srv-remotemount-SYN.mount                                                               loaded active mounted RemoteMount mount for SYN:7ce2fd8c-c74a-4485-905b-69f1ae3257b4
srv-remotemount-SYN_DS218j.mount                                                        loaded active mounted RemoteMount mount for SYN_DS218j:0d61c6b9-9dd0-4846-8351-34ca54d5235e
srv-remotemount-syn_fam.mount                                                           loaded active mounted RemoteMount mount for syn_fam:7a566c49-3bdc-4516-b74e-0a0af23a8f47

Here is the output:

root@OMV7-02:~# findmnt --real
TARGET                        SOURCE                        FSTYPE OPTIONS
/                             /dev/sda2                     ext4   rw,relatime,e
├─/srv/dev-disk-by-uuid-2aae7a96-a8ea-4856-9696-8ab90d2fee17
│                             /dev/nvme0n1p1                ext4   rw,relatime,j
├─/export/OMV7-02             /dev/nvme0n1p1[/OMV7-02]      ext4   rw,relatime,j
├─/boot/efi                   /dev/sda1                     vfat   rw,relatime,f
├─/srv/remotemount/SYN_DS218j //192.168.178.19/MEDIA        cifs   rw,relatime,v
├─/srv/remotemount/syn_fam    //192.168.178.19/familie      cifs   rw,relatime,v
└─/srv/remotemount/SYN        192.168.178.19:/volume1/MEDIA nfs4   rw,relatime,v

All /srv/... mounts are working from the CLI doing a ls.

Only my OMV-GUI does not show these remote mounts.