dlandon

I've released a Python 2 package plugin to CA. It may take a few hours to show up in CA.

You have the wrong mapping of the drive. You're referring to the drive in the docker mounted at /mnt/disks/TEAM4TB, but the drive is actually mounted at: Aug 22 21:57:10 KRAKEN unassigned.devices: Successfully mounted 'nvme0n1p1' on '/mnt/disks/112110050430099' Do the following: Stop the plex docker container. Unmount the UD drive. Click on the UD mount point and change it to 'TEAM4TB'. Mount the UD drive. Start the plex docker container.

Do they show up in the UD page with the preclear icon?

I don't think this is the solution to your problem, but your log is being spammed with this: Aug 20 20:53:54 KRAKEN nmbd[74745]: [2022/08/20 20:53:54.152573, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce) Aug 20 20:53:54 KRAKEN nmbd[74745]: process_local_master_announce: Server GIGABYTE at IP 10.0.0.120 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election. Aug 20 20:53:54 KRAKEN nmbd[74745]: [2022/08/20 20:53:54.152691, 0] ../../source3/nmbd/nmbd_become_lmb.c:151(unbecome_local_master_success) Aug 20 20:53:54 KRAKEN nmbd[74745]: ***** Aug 20 20:53:54 KRAKEN nmbd[74745]: Aug 20 20:53:54 KRAKEN nmbd[74745]: Samba name server KRAKEN has stopped being a local master browser for workgroup WORKGROUP on subnet 10.0.0.17 Aug 20 20:53:54 KRAKEN nmbd[74745]: Aug 20 20:53:54 KRAKEN nmbd[74745]: ***** Aug 20 20:54:12 KRAKEN nmbd[74745]: [2022/08/20 20:54:12.727010, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Aug 20 20:54:12 KRAKEN nmbd[74745]: ***** Aug 20 20:54:12 KRAKEN nmbd[74745]: Aug 20 20:54:12 KRAKEN nmbd[74745]: Samba name server KRAKEN is now a local master browser for workgroup WORKGROUP on subnet 10.0.0.17 Aug 20 20:54:12 KRAKEN nmbd[74745]: Aug 20 20:54:12 KRAKEN nmbd[74745]: ***** The local master browser election is bouncing back and forth causing a lot of log messages. It makes it hard to analyze your log when it's filling with those messages. Not sure what your LAN configuration is, but maybe install the local master plugin to make Unraid always win the election for master browser. Once you've solved that, unmount and remount the UD drive you use for plex and post new diagnostics. Also post a screen shot of the mapping of the drive to the plex docker container.

If you leave that folder you can move any packages you need to /flash/extra/ and Unraid will install them.

You can do a key change yourself after 1 year from the last key change. You can always request support to do a manual key change anytime.

Email support and request a key change.

Remove the NerdPack plugin and reboot.

It's not a SMB issue with the characters it's the use of php by UD. php reserved characters cause a problem. How do you know it's a credentials problem? Did you see the same login failure in the syslog? Try setting the "Specify SMB Version when Mounting Remote Shares?" to "Yes" in the UD settings. UD defaults to not specifying the SMB version to let the server set the protocol it prefers. This doesn't always work, and the remote server may want the SMB version specified. On your next post, please attach the diagnostics file. Just telling me it "Doesn't work", is not very helpful unless I can see in the diagnostics why it "Doesn't work".

When you tried to mount a share with SMB, there was a credentials issue: Aug 21 13:36:54 Alent unassigned.devices: Mounting Remote Share '//NAS/video'... Aug 21 13:36:54 Alent unassigned.devices: Mount SMB share '//NAS/video' using SMB default protocol. Aug 21 13:36:54 Alent unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_video' '//NAS/video' '/mnt/remotes/NAS_video' Aug 21 13:36:54 Alent kernel: CIFS: Attempting to mount \\NAS\video Aug 21 13:36:54 Alent kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE Aug 21 13:36:54 Alent kernel: CIFS: VFS: \\NAS Send error in SessSetup = -13 Aug 21 13:36:54 Alent kernel: CIFS: VFS: cifs_mount failed w/return code = -13 Avoid special characters in names and passwords. Letters and numbers only are the best. When you tried to mount a share with NFS, the remote server mount was denied: Aug 21 13:41:55 Alent unassigned.devices: Mounting Remote Share '10.10.10.10:/volume1/video'... Aug 21 13:41:55 Alent unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs' -o rw,noacl '10.10.10.10:/volume1/video' '/mnt/remotes/10.10.10.10_video' Aug 21 13:41:55 Alent rpc.mountd[24794]: refused mount request from 10.10.10.10 for /volume1/video (/): not exported Aug 21 13:41:55 Alent unassigned.devices: NFS mount failed: 'mount.nfs: access denied by server while mounting 10.10.10.10:/volume1/video '. You need to look into the NFS requitements of the remote server. You were mounting it with NFSv3 on Unraid. The remote server may want NFSv4. You can set UD to mount NFSv4 in the UD Settings. Check that /volume1/video/ is a valid share folder. You also ran into an issue trying to rename a mount point to "NFS-Share": Aug 21 13:31:36 Alent unassigned.devices: Error: Device '10.10.10.10:/volume1/video' mount point 'NFS-Share' - name is reserved, used in the array or by an unassigned device. You can't have two share/mountpoint names the same.

Post your diagnostics.

If Nerd Pack doesn't have screen, use tmux. Nerd Pack doesn't include "everything".

What isn't working? You can't get the screen or tmux packages to install?

Click the red X next to the ID and it will remove the partition. Then format will be an option.

Ud settings at the bottom of the page.

Go to ud settings and change that drive uuid. The duplicate is because it was previously in the array.

You'll need to install it mnually.

Post your diagnostics zip file. Also provide screen shots of the device settings. Click on the "Cache" and "Dev 1" texts and post those screen shots.

CIFS (Common Internet FIle System) is the method used to mount a remote SMB share.

Insert the flash drive, right click Properties, Tools, Check to check the drive. The timeout warning is from a 'cat' command that shows the contents of a file. That file is in the ramfs and should be extremely fast. Something slowed it down.

The UD error is happening because your system is too busy, or hanging up somewhere. There are some file missing errors in the log: Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739665 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /us HTTP/1.1", host: "localhost" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739666 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /us HTTP/1.1", host: "127.0.0.1" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739667 open() "/usr/local/emhttp/status/format/json" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status/format/json HTTP/1.1", host: "127.0.0.1" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739668 open() "/usr/local/emhttp/basic_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /basic_status HTTP/1.1", host: "127.0.0.1" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739669 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /stub_status HTTP/1.1", host: "localhost" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739670 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /stub_status HTTP/1.1", host: "127.0.0.1" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739671 open() "/usr/local/emhttp/nginx_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /nginx_status HTTP/1.1", host: "127.0.0.1" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739672 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status HTTP/1.1", host: "127.0.0.1" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739673 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status?full&json HTTP/1.1", host: "localhost" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739674 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status?full&json HTTP/1.1", host: "127.0.0.1" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739675 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: ::1, server: , request: "GET /status?full&json HTTP/1.1", host: "[::1]" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739676 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "localhost" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739677 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "127.0.0.1" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739679 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "localhost" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739680 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "127.0.0.1" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739681 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?format=plain HTTP/1.1", host: "localhost" Aug 15 17:16:25 iceberg nginx: 2022/08/15 17:16:25 [error] 9676#9676: *3739682 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?format=plain HTTP/1.1", host: "127.0.0.1" Aug 15 17:16:26 iceberg kernel: wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information. Aug 15 17:16:26 iceberg kernel: wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <[email protected]>. All Rights Reserved. Aug 15 17:16:33 iceberg nginx: 2022/08/15 17:16:33 [error] 9676#9676: *3739814 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status HTTP/1.1", host: "localhost" Aug 15 17:16:33 iceberg nginx: 2022/08/15 17:16:33 [error] 9676#9676: *3739815 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status HTTP/1.1", host: "127.0.0.1" Aug 15 17:16:33 iceberg nginx: 2022/08/15 17:16:33 [error] 9676#9676: *3739816 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: ::1, server: , request: "GET /status HTTP/1.1", host: "[::1]" I'm not sure where these are coming from. There may be a plugin causing this. Your diagnostics zip is missing a lot of folders in the /flash/config/ folder. For example, plugins/ is missing. It looks like there may be an issue on your flash. I woud do the following: Shut down your system and check the flash drive on a PC. Remove NerdPack. There may be a package causing some issues. See if the UD timeout messages continue. Start your system in safe mode and run it that way to see if the random shut downs continue.

Go to UD Settings and set for NFS export:

Yes. There are some characters used in the password that cause an issue with php. The '+' character is one of them.

It looks like a disk controller issue: Aug 11 13:38:19 THOR kernel: mpt3sas 0000:05:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM Aug 11 13:38:19 THOR kernel: r8169 0000:08:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM Aug 11 13:38:21 THOR unassigned.devices: Mounting 'Auto Mount' Remote Shares... Aug 11 13:38:30 THOR kernel: mdcmd (37): nocheck cancel Aug 11 13:38:30 THOR kernel: md: recovery thread: exit status: -4 Aug 11 13:43:14 THOR kernel: smartctl[1871]: segfault at 146a1f38 ip 0000152cab3776ea sp 00007fffd8de7940 error 6 in libc-2.33.so[152cab2b0000+15e000] Aug 11 13:43:14 THOR kernel: Code: 00 00 00 83 f8 0f 0f 84 11 18 00 00 48 8b 4b 70 8d 50 01 48 8b 7c 24 08 48 c1 e0 06 89 93 80 00 00 00 66 0f ef c0 48 8d 14 01 <0f> 11 44 01 08 48 8d 74 01 08 48 c7 42 18 00 00 00 00 f3 0f 6f 3f Aug 11 13:45:46 THOR kernel: smartctl[12254]: segfault at 38 ip 00001475db5e6a1c sp 00007ffdaa770790 error 4 in libc-2.33.so[1475db51c000+15e000] Aug 11 13:45:46 THOR kernel: Code: 83 c7 01 41 83 ff 40 75 d5 83 c3 40 49 83 c4 08 81 fb 00 01 00 00 75 c1 4c 8b 65 00 e9 8d f6 ff ff 0f 1f 44 00 00 49 8b 56 20 <8b> 72 38 48 8b 55 18 89 34 82 4d 8b 6e 08 4d 85 ed 74 14 4d 89 ee smartctl is segfaulting. We will need a disk guru like @JorgeB to take a look. You also have a realtek NIC and that may be causing some issues. Realtek drivers on Linux are troublesome because they are not updated for each release of Linux.

I have a potential fix for your situation. I'll do some more testing before I consider it ready for prime time. I have to say, I am amazed this hasn't come up until now. Normally I come across these kinds of issues when I'm testing UD. This is kind of a corner case, but pretty messy when it happens.