Jump to content

DavidNguyen

Members
  • Posts

    35
  • Joined

  • Last visited

Posts posted by DavidNguyen

  1. 9 hours ago, JorgeB said:

    post the output of:

     

    ls -la /boot/config/shares

     

     

    total 128
    drwx------  2 root root 8192 Dec 13 18:46 ./
    drwx------ 11 root root 8192 Dec 13 18:47 ../
    -rw-------  1 root root  463 Dec  4 18:52 appdata.cfg
    -rw-------  1 root root  443 Nov 30 10:41 backup.cfg
    -rw-------  1 root root  450 Dec  4 18:52 books.cfg
    -rw-------  1 root root  443 Nov 30 10:41 courses.cfg
    -rw-------  1 root root  463 Nov 30 10:50 domains.cfg

     

    and ...etc didn't post all of my shares, but there is no #012.cfg

    the ghost folder in Krusader has the subfolder '.fontconfig' filled with random cache-7 files.

  2. I'm getting a constant looping of a service trying to start and failing.

    It's a strange thing that came out of the blue.

    I've attached the output of the syslogs, which repeats itself constantly.

    Dec 12 11:05:10 Unraid emhttpd: error: put_config_idx, 610: Invalid argument (22): fopen: /boot/config/shares/#012.cfg
    Dec 12 11:05:10 Unraid emhttpd: Starting services...
    Dec 12 11:05:10 Unraid emhttpd: shcmd (133422): /etc/rc.d/rc.samba restart
    Dec 12 11:05:10 Unraid wsdd2[20361]: 'Terminated' signal received.
    Dec 12 11:05:10 Unraid winbindd[20367]: [2023/12/12 11:05:10.776774,  0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler)
    Dec 12 11:05:10 Unraid winbindd[20364]: [2023/12/12 11:05:10.776786,  0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler)
    Dec 12 11:05:10 Unraid winbindd[20367]:   Got sig[15] terminate (is_parent=0)
    Dec 12 11:05:10 Unraid winbindd[20364]:   Got sig[15] terminate (is_parent=1)
    Dec 12 11:05:10 Unraid wsdd2[20361]: terminating.
    Dec 12 11:05:11 Unraid avahi-daemon[20406]: Service "Unraid" (/services/ssh.service) successfully established.
    Dec 12 11:05:11 Unraid avahi-daemon[20406]: Service "Unraid" (/services/smb.service) successfully established.
    Dec 12 11:05:11 Unraid avahi-daemon[20406]: Service "Unraid" (/services/sftp-ssh.service) successfully established.
    Dec 12 11:05:12 Unraid root: Starting Samba:  /usr/sbin/smbd -D
    Dec 12 11:05:12 Unraid smbd[20564]: [2023/12/12 11:05:12.992838,  0] ../../source3/smbd/server.c:1741(main)
    Dec 12 11:05:12 Unraid smbd[20564]:   smbd version 4.17.12 started.
    Dec 12 11:05:12 Unraid smbd[20564]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
    Dec 12 11:05:12 Unraid root:                  /usr/sbin/wsdd2 -d -4
    Dec 12 11:05:13 Unraid root:                  /usr/sbin/winbindd -D
    Dec 12 11:05:13 Unraid wsdd2[20578]: starting.
    Dec 12 11:05:13 Unraid winbindd[20579]: [2023/12/12 11:05:13.108034,  0] ../../source3/winbindd/winbindd.c:1440(main)
    Dec 12 11:05:13 Unraid winbindd[20579]:   winbindd version 4.17.12 started.
    Dec 12 11:05:13 Unraid winbindd[20579]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
    Dec 12 11:05:13 Unraid winbindd[20581]: [2023/12/12 11:05:13.115473,  0] ../../source3/winbindd/winbindd_cache.c:3117(initialize_winbindd_cache)
    Dec 12 11:05:13 Unraid winbindd[20581]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
    Dec 12 11:05:13 Unraid emhttpd: shcmd (133427): /etc/rc.d/rc.avahidaemon restart
    Dec 12 11:05:13 Unraid root: Stopping Avahi mDNS/DNS-SD Daemon: stopped
    Dec 12 11:05:13 Unraid avahi-daemon[20406]: Got SIGTERM, quitting.
    Dec 12 11:05:13 Unraid avahi-dnsconfd[20415]: read(): EOF
    Dec 12 11:05:13 Unraid avahi-daemon[20406]: Leaving mDNS multicast group on interface br0.IPv4 with address 10.15.86.130.
    Dec 12 11:05:13 Unraid avahi-daemon[20406]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.130.
    Dec 12 11:05:13 Unraid avahi-daemon[20406]: avahi-daemon 0.8 exiting.
    Dec 12 11:05:13 Unraid root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214).
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: Successfully dropped root privileges.
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: avahi-daemon 0.8 starting up.
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: Successfully called chroot().
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: Successfully dropped remaining capabilities.
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: Loading service file /services/sftp-ssh.service.
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: Loading service file /services/smb.service.
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: Loading service file /services/ssh.service.
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: Joining mDNS multicast group on interface br0.IPv4 with address 10.10.10.130.
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: New relevant interface br0.IPv4 for mDNS.
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.1.130.
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: New relevant interface eth1.IPv4 for mDNS.
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: Network interface enumeration completed.
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: Registering new address record for 10.10.10.130 on br0.IPv4.
    Dec 12 11:05:13 Unraid avahi-daemon[20629]: Registering new address record for 192.168.1.130 on eth1.IPv4.
    Dec 12 11:05:13 Unraid emhttpd: shcmd (133428): /etc/rc.d/rc.avahidnsconfd restart
    Dec 12 11:05:13 Unraid root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped
    Dec 12 11:05:13 Unraid root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon:  /usr/sbin/avahi-dnsconfd -D
    Dec 12 11:05:13 Unraid avahi-dnsconfd[20638]: Successfully connected to Avahi daemon.
    Dec 12 11:05:14 Unraid avahi-daemon[20629]: Server startup complete. Host name is Unraid.local. Local service cookie is 1081371307.
    Dec 12 11:05:14 Unraid emhttpd: error: put_config_idx, 610: Invalid argument (22): fopen: /boot/config/shares/#012.cfg

     

    I've also attached my diagnostics.

    unraid-diagnostics-20231213-0602.zip

  3. I think there should be a jeOS integrated backup solution to make incremental backups simple, secure and reliable

    Kinda like how VPN is implemented via the GUI

    So, automatic encryption, compression and connectivity over the network, basically a zero config setup

     

    It should be offered for free for Pro users who are serious about their data. The backup version of unraid will just be a thin client without containers, VMs etc but will allow a quick restore.

  4. <= 6.11.5 one could simply minimise each object rather than delete it

    When minimised it just gave a single line of information which was enough.

    Not necessary to delete the entire panel.

     

    Can it be added back or with a plugin?

    • Like 1
    • Upvote 5
  5. 5 hours ago, ich777 said:

    I‘m not too sure anymore. I know that nvidia-persistenced can cause issues on some systems because persistenced can sometimes introduce latencys that are higher than usual and cause such errors on the container runtime.

    It's started working again. I'm completely confused because I literally just went to sleep woke up and it worked.

    Anyway, I included the diagnostics file again in case you see something compared to my old file when it wasn't working.

    tower-diagnostics-20220927-1912.zip

  6. On 9/25/2022 at 6:05 PM, ich777 said:

    Even of you disable the iGPU with modprobe.d (so that the driver will not load) it will output the console just fine so that you can use PiKVM just fine.

    So, I tried disabling iGPU and it wouldn't work.

    Came back after a while and tried manually nvidia-persistenced and suddenly both Plex & JF containers started successfully.

    Then I tried rebooting, running persistenced again, and it wouldn't start.

    So, that's another symptom, sometimes it starts, sometimes not, and when it does, it doesn't survive a reboot.

    Could be a hardware problem, maybe should do a teardown to see if there's a busted cap, or flash vbios.

  7. 1 hour ago, ich777 said:

    From what I see in your Diagnostics everything seems fine too me, nvidia-smi reports your card correctly.

    I can also see that your first card is recognized as a amdgpu and your second card is your Nvidia.

    Have you yet tried to remove nvidia-persistenced from your go file and/or disabling your iGPU if that helps?

    Do you use your iGPU for something on your system?

    Tried removing persistenced setting without luck.

    I thought of the iGPU, I had tried disabling it before.

    It just happened that was my previous daily driver and was being used to run PiKVM

  8. 3 hours ago, ich777 said:

    @DavidNguyen everything seems fine, please try to upgrade to Unraid 6.11.0 that was released just now and if it doesn't work please send over new Diagnostics.

    Still not running after the update. Redownloaded the NVIDIA driver, same problem as before.

    I think either the card is faulty or there is a hardware incompatibility at this point unless there's anything else I can try.

    tower-diagnostics-20220924-0800.zip

  9. 9 hours ago, ich777 said:

    Please post the output from:

    cat /etc/docker/daemon.json

     

    {
        "runtimes": {
            "nvidia": {
                "path": "/usr/bin/nvidia-container-runtime",
                "runtimeArgs": []
            }
        }
    }

     

    9 hours ago, ich777 said:

    and also from:

    ls -la /dev/dri

     

     

    total 0
    drwxrwxrwx  3 root root       100 Sep 23 01:36 ./
    drwxr-xr-x 17 root root      4080 Sep 23 01:40 ../
    drwxrwxrwx  2 root root        80 Sep 23 01:36 by-path/
    crwxrwxrwx  1 root video 226,   0 Sep 23 01:37 card0
    crwxrwxrwx  1 root video 226, 128 Sep 23 01:37 renderD128

     

  10. 8 hours ago, ich777 said:

    Have you yet tried if it's the same with Jellyfin?

    Yes, same error. Neither container will load with extra parameters box filled.

    I might take out the gpu and test it on another system to see if it's a faulty card or just hardware compatibility.

    however, I happen to get a DP output via PiKVM

  11. 47 minutes ago, ich777 said:

    Try to uninstall the Nvidia Driver Plugin, reboot, pull a fresh copy from the CA App and reboot again.

     

    42 minutes ago, ich777 said:

    From what I see you are booting with UEFI mode, please try to boot with Legacy (CSM) mode and also disable all the C-State options in your BIOS.

     

    I tried both of these, still no joy.

  12. 2 hours ago, ich777 said:

    can you give me the output from your docker run command with --runtime=nvidia

    root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='Plex-Media-Server' --net='host' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="Plex-Media-Server" -e 'PLEX_CLAIM'='claim-C71axTEgtyALFeQPPAFu' -e 'PLEX_UID'='99' -e 'PLEX_GID'='100' -e 'VERSION'='latest' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-06da0ef1-768c-8997-2635-5dddcc599084' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web' -l net.unraid.docker.icon='https://raw.githubusercontent.com/plexinc/pms-docker/master/img/plex-server.png' -v '/tmp':'/transcode':'rw' -v '/mnt/user/':'/data':'rw' -v '/mnt/user/appdata/Plex-Media-Server':'/config':'rw' --runtime=nvidia 'plexinc/pms-docker'
    2474d3059f7df110dde81210862c5d861afedf8092b5b0fd0858ab44624b5591
    docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
    nvidia-container-cli: initialization error: open failed: /proc/sys/kernel/overflowuid: permission denied: unknown.
    
    The command failed.

     

  13. 5 hours ago, ich777 said:

    Please post them, without them I really can‘t say much…

     

    What do you mean with that?

    I mean that the Unraid gui freezes when trying to download the diagnostics.

    Having said that, I went to another machine and applied the GPU settings.. and it worked?

    I have no idea how or why and am quite confused. But it works now.

    • Like 1
  14. I'm having trouble with my P600, it fails when starting the container on both Plex and Jellyfin

    I'm using the R5 2400G, is it possible that the iGPU is messing with the NV somehow?

    I also have a diagnostics zip, but since I'm checking if creating it from the CLI anonymises data (gui seems borked somehow)

    1387984514_unraidnvidia-smi.png.ef4743e854c22c086694222b6e3c390a.png1335703163_unraidnvidiafailed.thumb.png.467f12f3d37f536b4d47c8cdc73dd3a4.png

  15. I'm using Unraid's built-in Wireguard to VPN into the server remotely from Android

    However, when I do this, I'm unable to access qB's webui; radarr and sonarr work fine.

    I imagine it's because I have a separate wireguard enabled in qB, and they don't work used together, but I don't know where to correct this.

     

  16. On 6/22/2022 at 5:47 PM, doron said:

    Very good. Now let's hope @bonienl considers adding the code fix into the plugin.

    Hey doron, it might be that the plug-in won't get updated as it's been about 2 years since.

     

    I might do a script to automate the process. I've already used the User Scripts plug-in to do the cp/chmod part. Is there a way to toggle the fans disabled/enabled in cli or will this need to be done manually via gui?

     

    Cheers

  17. 8 hours ago, ich777 said:

    I would recommend to switch over to the official one because I've deprecating the container in the near future because the official one has everything that my container has also built in.

     

    To switch over simply change the repository in the docker template from ich777/jellyfin to jellyfin/jellyfin

    Thanks, I just did that, and it's working great. I just worry in the future users won't be aware of it because Jellyfin's documentation is quite vague. Anyway, for me it's working smoothly.

     

    8 hours ago, ich777 said:

    I think that the official one already supports AMD HW transcoding or am I wrong?

    It would seem not, as I've been trying for the past week (unless I've missed something or configured it wrong).

    I've gone into extra paramters and entered

    --device=/dev/dri

    which to my understanding is the syntax for iGPU.

    What I liked about your JF container was how clear the instructions were written up; if it's possible to activate in official or mauimauer's I'd appreciate the help.

×
×
  • Create New...