Beiträge von jackren

    ctrl-shift-R?


    I did search the omv and debian 11 forums and read throw very many topic related to nfs-server not starting but did't find a fix for my situation , so thats why I started a new thread here.


    root@jacksbox3:~# cat /proc/fs/nfsd/versions +2 +3 +4 +4.1 +4.2 root@jacksbox3:~# awk '{ for (i=1; i<=NF; i++) if ($i > 0) printf "%s,", $i }' /proc/fs/nfsd/versions | sed -e 's/+//g' -e 's/,$//' 2,3,4,4.1,4.2root@jacksbox3:~#

    [tt][

    root@jacksbox3:~# cat /proc/fs/nfsd/versions

    +2 +3 +4 +4.1 +4.2

    root@jacksbox3:~# cat /etc/default/nfs-kernel-server

    # This file is auto-generated by openmediavault (https://www.openmediavault.org)

    # WARNING: Do not edit this file, your changes will get lost.


    # Number of servers to start up

    RPCNFSDCOUNT="8"


    # Runtime priority of server (see nice(1))

    RPCNFSDPRIORITY="0"


    # Options for rpc.nfsd.

    RPCNFSDOPTS="--no-nfs-version 2 --nfs-version --nfs-version 3 --nfs-version 4 --nfs-version 4.1 --nfs-version 4.2 "


    # Options for rpc.mountd.

    RPCMOUNTDOPTS="--no-nfs-version 2 --nfs-version 0 --nfs-version 3 --nfs-version 4 --manage-gids"


    # Do you want to start the svcgssd daemon? It is only required for Kerberos

    # exports.

    NEED_SVCGSSD=


    # Options for rpc.svcgssd.

    RPCSVCGSSDOPTS=""

    root@jacksbox3:~# cat /etc/default/nfs-common

    # This file is auto-generated by openmediavault (https://www.openmediavault.org)

    # WARNING: Do not edit this file, your changes will get lost.


    # Do you want to start the statd daemon? It is not needed for NFSv4.

    NEED_STATD="yes"


    # Options for rpc.statd.

    # Should rpc.statd listen on a specific port? This is especially useful

    # when you have a port-based firewall. To use a fixed port, set this

    # this variable to a statd argument like: "--port 4000 --outgoing-port 4001".

    # For more information, see rpc.statd(8) or http://wiki.debian.org/SecuringNFS

    STATDOPTS=""


    # Do you want to start the idmapd daemon? It is only needed for NFSv4.

    NEED_IDMAPD="yes"


    # Do you want to start the gssd daemon? It is required for Kerberos mounts.

    NEED_GSSD=

    root@jacksbox3:~# omv-confdbadm read --prettify conf.service.nfs

    {

    "enable": true,

    "shares": {

    "share": []

    },

    "versions": ",3,4,4.1,4.2"

    }



    /tt]

    Hello All,


    I recently noticed that NFS wasn't working anymore on my omv server, I think it happend after upgrade to OMV 6, didn't notice any errors after update but when I tried to add a nfs-share on webinterface, I couldn't apply changes , keeps giving big error messages.

    when I try to start nfs-server from cl, I get depency error;


    root@jacksbox3:~# systemctl start nfs-server.service

    A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.

    root@jacksbox3:~# journalctl -xe

    Jul 20 13:53:05 jacksbox3 systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.

    ░░ Subject: A start job for unit rpc-svcgssd.service has finished successfully

    ░░ Defined-By: systemd

    ░░ Support: https://www.debian.org/support

    ░░

    ░░ A start job for unit rpc-svcgssd.service has finished successfully.

    ░░

    ░░ The job identifier is 6025.

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]: /usr/sbin/rpc.mountd: bad version number: 0

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]: Usage: /usr/sbin/rpc.mountd [-F|--foreground] [-h|--help] [-v|--version] [-d kind|--debug kind]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-o num|--descriptors num]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-p|--port port] [-V version|--nfs-version version]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-N version|--no-nfs-version version] [-n|--no-tcp]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-H prog |--ha-callout prog] [-r |--reverse-lookup]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-s|--state-directory-path path] [-g|--manage-gids]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-t num|--num-threads=num] [-u|--no-udp]

    Jul 20 13:53:05 jacksbox3 systemd[1]: nfs-mountd.service: Control process exited, code=exited, status=1/FAILURE

    ░░ Subject: Unit process exited

    ░░ Defined-By: systemd

    ░░ Support: https://www.debian.org/support

    ░░

    ░░ An ExecStart= process belonging to unit nfs-mountd.service has exited.

    ░░

    ░░ The process' exit code is 'exited' and its exit status is 1.

    Jul 20 13:53:05 jacksbox3 systemd[1]: nfs-mountd.service: Failed with result 'exit-code'.

    ░░ Subject: Unit failed

    ░░ Defined-By: systemd

    ░░ Support: https://www.debian.org/support

    ░░

    ░░ The unit nfs-mountd.service has entered the 'failed' state with result 'exit-code'.

    Jul 20 13:53:05 jacksbox3 systemd[1]: Failed to start NFS Mount Daemon.

    ░░ Subject: A start job for unit nfs-mountd.service has failed

    ░░ Defined-By: systemd

    ░░ Support: https://www.debian.org/support

    ░░

    ░░ A start job for unit nfs-mountd.service has finished with a failure.

    ░░

    ░░ The job identifier is 6009 and the job result is failed.

    Jul 20 13:53:05 jacksbox3 systemd[1]: Dependency failed for NFS server and services.

    ░░ Subject: A start job for unit nfs-server.service has failed

    ░░ Defined-By: systemd

    ░░ Support: https://www.debian.org/support

    ░░

    ░░ A start job for unit nfs-server.service has finished with a failure.

    ░░

    ░░ The job identifier is 6005 and the job result is dependency.

    Jul 20 13:53:05 jacksbox3 systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.

    root@jacksbox3:~# systemctl list-dependencies nfs-server

    nfs-server.service

    ● ├─auth-rpcgss-module.service

    ● ├─nfs-config.service

    ● ├─nfs-idmapd.service

    ● ├─nfs-mountd.service

    ● ├─proc-fs-nfsd.mount

    ● ├─rpc-statd.service

    ● ├─rpc-svcgssd.service

    ● ├─rpcbind.socket

    ● ├─system.slice

    ● └─network.target

    root@jacksbox3:~# systemctl status nfs-mountd.service

    ● nfs-mountd.service - NFS Mount Daemon

         Loaded: loaded (/lib/systemd/system/nfs-mountd.service; static)

    Active: failed (Result: exit-code) since Thu 2023-07-20 13:53:05 CEST; 1min 56s ago

    Process: 26593 ExecStart=/usr/sbin/rpc.mountd $RPCMOUNTDARGS (code=exited, status=1/FAILURE)

            CPU: 3ms

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]: Usage: /usr/sbin/rpc.mountd [-F|--foreground] [-h|--help] [-v|--version] [-d kind|--debug kind]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-o num|--descriptors num]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-p|--port port] [-V version|--nfs-version version]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-N version|--no-nfs-version version] [-n|--no-tcp]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-H prog |--ha-callout prog] [-r |--reverse-lookup]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-s|--state-directory-path path] [-g|--manage-gids]

    Jul 20 13:53:05 jacksbox3 rpc.mountd[26593]:         [-t num|--num-threads=num] [-u|--no-udp]

    Jul 20 13:53:05 jacksbox3 systemd[1]: nfs-mountd.service: Control process exited, code=exited, status=1/FAILURE

    Jul 20 13:53:05 jacksbox3 systemd[1]: nfs-mountd.service: Failed with result 'exit-code'.

    Jul 20 13:53:05 jacksbox3 systemd[1]: Failed to start NFS Mount Daemon.

    root@jacksbox3:~# 

    seems nfs-mountd is the problem, search all the forums but couldn't find a fix,

    has anybody here an idea?

    thanks.

    This does not mount:


    Code
    /srv/dev-disk-by-uuid-174a1c5d-9c81-47c6-98cd-ef4770b8e308: can't read superblock on /dev/mapper/jacksbox3-TVopnames. 

    referenced in the config.

    so the problem is that the partition doesn't mount cause of a bad superblock on the "TVopnames "partition?


    is there a simple fix , or just replace whole drive?

    If there are still old disks mounted, go to the UI (do not apply) and umount the old disks. You may have to remove the usages first.

    Then apply all in one go.


    And please next time, do one step at a time first fix broken disks, then upgrade.

    There are no old disks mounted, I did unmount old disks and removed them before I installed new disks.

    update,

    after a , apt-get upgrade and apt-get -f install, the login problem seems fixed.( tried it cuple months earlier but didn't work then)


    But now in the webinterface . the yellow popup windows keeps coming up with message: configuration changed . U have to apply changes for them to take effect.


    But when I press; apply , I get following error;


    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': unassigned-hostname.unassigned-domain: ---------- ID: create_filesystem_mountpoint_353e652a-9141-4cc2-806e-6d333a07cffa Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_353e652a-9141-4cc2-806e-6d333a07cffa for file /etc/fstab was charged by text Started: 13:43:34.562792 Duration: 1.369 ms Changes: ---------- ID: mount_filesystem_mountpoint_353e652a-9141-4cc2-806e-6d333a07cffa Function: mount.mounted Name: /srv/dev-disk-by-uuid-fde263dc-53e1-47fd-95be-85378a648856 Result: True Comment: Target was already mounted Started: 13:43:34.565622 Duration: 337.687 ms Changes: ---------- umount: Forced remount because options (user_xattr) changed ---------- ID: create_filesystem_mountpoint_a4990782-41bb-4e01-a3d0-474248ccd731 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_a4990782-41bb-4e01-a3d0-474248ccd731 for file /etc/fstab was charged by text Started: 13:43:34.903616 Duration: 1.586 ms Changes: ---------- ID: mount_filesystem_mountpoint_a4990782-41bb-4e01-a3d0-474248ccd731 Function: mount.mounted Name: /srv/dev-disk-by-uuid-d45cdb90-3012-45f8-bbed-ab6e3ca0a71d Result: True Comment: Target was already mounted Started: 13:43:34.905393 Duration: 77.613 ms Changes: ---------- umount: Forced remount because options (user_xattr) changed ---------- ID: create_filesystem_mountpoint_440c5dfc-82ad-45c4-b756-dcbf48427d6d Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_440c5dfc-82ad-45c4-b756-dcbf48427d6d for file /etc/fstab was charged by text Started: 13:43:34.983291 Duration: 1.45 ms Changes: ---------- ID: mount_filesystem_mountpoint_440c5dfc-82ad-45c4-b756-dcbf48427d6d Function: mount.mounted Name: /srv/dev-disk-by-uuid-0885a914-17e2-44cd-a97a-498b4c1d3dc8 Result: True Comment: Target was already mounted Started: 13:43:34.984904 Duration: 16.589 ms Changes: ---------- ID: create_filesystem_mountpoint_bc230c26-27bc-4266-83d5-fe5a216600ae Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_bc230c26-27bc-4266-83d5-fe5a216600ae for file /etc/fstab was charged by text Started: 13:43:35.001768 Duration: 1.379 ms Changes: ---------- ID: mount_filesystem_mountpoint_bc230c26-27bc-4266-83d5-fe5a216600ae Function: mount.mounted Name: /srv/dev-disk-by-uuid-f2d49f70-263d-43b7-a4de-9107fb4bd4fc Result: True Comment: Target was already mounted Started: 13:43:35.003294 Duration: 14.889 ms Changes: ---------- ID: create_filesystem_mountpoint_55805b0f-7467-47e7-b410-7c1c1417fe7c Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_55805b0f-7467-47e7-b410-7c1c1417fe7c for file /etc/fstab was charged by text Started: 13:43:35.018458 Duration: 1.359 ms Changes: ---------- ID: mount_filesystem_mountpoint_55805b0f-7467-47e7-b410-7c1c1417fe7c Function: mount.mounted Name: /srv/dev-disk-by-uuid-2bbcb325-05b8-4931-939e-19b67c2c7cdf Result: True Comment: Target was already mounted Started: 13:43:35.019966 Duration: 14.965 ms Changes: ---------- ID: create_filesystem_mountpoint_03a8040e-cef7-4c3a-8b55-28c24e5e925c Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_03a8040e-cef7-4c3a-8b55-28c24e5e925c for file /etc/fstab was charged by text Started: 13:43:35.035203 Duration: 1.359 ms Changes: ---------- ID: mount_filesystem_mountpoint_03a8040e-cef7-4c3a-8b55-28c24e5e925c Function: mount.mounted Name: /srv/dev-disk-by-uuid-174a1c5d-9c81-47c6-98cd-ef4770b8e308 Result: False Comment: mount: /srv/dev-disk-by-uuid-174a1c5d-9c81-47c6-98cd-ef4770b8e308: can't read superblock on /dev/mapper/jacksbox3-TVopnames. Started: 13:43:35.036707 Duration: 37.235 ms Changes: ---------- ID: create_bind_mountpoint_0ff1f312-7b22-4493-ac3d-75c331bc8baa Function: file.accumulated Result: True Comment: Accumulator create_bind_mountpoint_0ff1f312-7b22-4493-ac3d-75c331bc8baa for file /etc/fstab was charged by text Started: 13:43:35.074284 Duration: 1.392 ms Changes: ---------- ID: mount_bind_mountpoint_0ff1f312-7b22-4493-ac3d-75c331bc8baa Function: mount.mounted Name: /export/Backup Result: True Comment: Target was already mounted Started: 13:43:35.075825 Duration: 15.093 ms Changes: ---------- ID: create_bind_mountpoint_e841220e-0881-4961-b845-04da17f8a272 Function: file.accumulated Result: True Comment: Accumulator create_bind_mountpoint_e841220e-0881-4961-b845-04da17f8a272 for file /etc/fstab was charged by text Started: 13:43:35.091185 Duration: 1.381 ms Changes: ---------- ID: mount_bind_mountpoint_e841220e-0881-4961-b845-04da17f8a272 Function: mount.mounted Name: /export/Films Result: True Comment: Target was already mounted Started: 13:43:35.092717 Duration: 14.919 ms Changes: ---------- ID: create_bind_mountpoint_a8b9e56b-2ae1-45c0-a048-dcd34d18bfb6 Function: file.accumulated Result: True Comment: Accumulator create_bind_mountpoint_a8b9e56b-2ae1-45c0-a048-dcd34d18bfb6 for file /etc/fstab was charged by text Started: 13:43:35.107907 Duration: 1.426 ms Changes: ---------- ID: mount_bind_mountpoint_a8b9e56b-2ae1-45c0-a048-dcd34d18bfb6 Function: mount.mounted Name: /export/Fotos Result: True Comment: Target was already mounted Started: 13:43:35.109483 Duration: 14.875 ms Changes: ---------- ID: create_bind_mountpoint_afc024f4-62bc-486c-ad2d-5fe6a8829bd3 Function: file.accumulated Result: True Comment: Accumulator create_bind_mountpoint_afc024f4-62bc-486c-ad2d-5fe6a8829bd3 for file /etc/fstab was charged by text Started: 13:43:35.124624 Duration: 1.437 ms Changes: ---------- ID: mount_bind_mountpoint_afc024f4-62bc-486c-ad2d-5fe6a8829bd3 Function: mount.mounted Name: /export/Muziek Result: True Comment: Target was already mounted Started: 13:43:35.126213 Duration: 14.882 ms Changes: ---------- ID: create_bind_mountpoint_6ca68f63-88e2-47bc-be46-6f33111f2a8d Function: file.accumulated Result: True Comment: Accumulator create_bind_mountpoint_6ca68f63-88e2-47bc-be46-6f33111f2a8d for file /etc/fstab was charged by text Started: 13:43:35.141399 Duration: 1.381 ms Changes: ---------- ID: mount_bind_mountpoint_6ca68f63-88e2-47bc-be46-6f33111f2a8d Function: mount.mounted Name: /export/TVopnames Result: True Comment: Target was already mounted Started: 13:43:35.142925 Duration: 15.165 ms Changes: ---------- ID: append_fstab_entries Function: file.blockreplace Name: /etc/fstab Result: True Comment: No changes needed to be made Started: 13:43:35.163028 Duration: 5.441 ms Changes: Summary for unassigned-hostname.unassigned-domain ------------- Succeeded: 22 (changed=2) Failed: 1 ------------- Total states run: 23 Total run time: 594.872 ms

    I think therea still disk UUID's from old hdd's present somewhere.

    I've been running a OMV server for almost 10 years whitout much trouble, but recently I had to replace a broken hdd and also did an upgrade to omv usul and since that,

    I can only login to OMV (web gui or ssh on cl) for a for certain period of time. After a reboot I can only login for about half an hour or an hour or something.

    After that time I get error with ssh;

    kex_exchange_identification: read: Connection reset by peer


    I think it's something of a wrong config setting , but I did,t change anything that I know off.

    when I noticed I couldn't access omv web-interface , I tried ssh login, but also failure.

    Then I connected a monitor to my omv server and rebooted,

    the boot procces stopped halfway, and asked for root passwd for maintenance or ctrl-d to continue, but non worked, stayed in loop.


    When testing hhd's I noticed 1 drice was broken.

    I have my omv system on a ssd and 2 more hhd's for extra storage.

    de ssd is ok.

    The system id setup with LVM paritians.

    How can I make my system bootup completely so I can access the webinterface and reconfigure my storage with 1 or 2 new hdd's and copy back my backup folder from amazon S3 bucket?

    Thanks,fstab.txt

    fstab.txt

    OMV 2.x has long gone EOL and is no longer supported.


    Are you running JDownloader by any chance?


    Have you looked into what the source/destination IP addresses and ports are for this network traffic?

    Had some trouble upgrading last time (long time ago ) and all seemed to run ok, so didn't upgrade anymore. ( is it still safe to upgrade from 2.2.7 whitout much problems?)


    not running Jdownloader , but maybe SABnzbd or sickbeard are using java an cause the trouble?


    What can I best use to see the source/destination IP addresses and ports ?


    ps I'm not a IT-pro , just a linux hobbyist

    I have had a problem with a huge drop in internetspeed on all the devices on my lan ( pc's tablets phones on wifi ) for a couple of weeks, and after much searching and trying, i figgered out that the problem seems to come from my openmediavault-server.
    When i disconnect the ethernetcable from the openmediavaulr server, all other devices on my lan see a huge increase in downloadspeed ( responsiveniss )


    When I login to the weginterface of the openmdiavault server, I see no errors , but when i look at the runnning processes, I see at top ;


    java command with cpu% between 110 and 160%


    which program needs the java command?


    Also I can see in the graphs that the averge cpu% went up from 60 to almost 100% since a cuple of weeks.


    same for load average.


    When I look in syslog , I see a lot of the following;


    openmediavault-jack monit[2927]: 'localhost' loadavg(5min) of 3.9 matches resource limit [loadavg(5min)>2.0]



    Can anybody help me diagnose this problem?


    ps I didn't make any changes to my openmediavault setup last year. 2.2.7


    regards,



    Is there an easy way I could backup current setup and config files before reinstall ( LVM, NFS, minidlna, plex etc..)

    Zitat von "ryecoaaron"

    Assuming you have omv-extras installed and use omv-release-upgrade, you don't need to. The upgrade script does it for you.


    Thanks , upgrade to OMV 0.6 succeeded :D


    Got insync-headless installed and backupfolder is now syncing to google drive.


    Update, not dirs under backup folder were synced to google drive, I thought it was a file permission issue , so I thought I chown folder to root.


    I did a ; chown -R root:root /* in the backup folder.


    I think this was wrong and now whole sytem has been set to root:root :?


    Can I undo this??