bondoo0

Here is the output:

Yes, it is the correct user and domain, and there are no different user/same machine issues. It definitely appears related to NTLMv1, since I just switched to "Send NTLMv2 response only" on one machine and that solved the issue, but creates the issue I can't connect to anything needing NTLMv1 (like my Windows Home Server).

I just updated to 6.1.1.0 RC5, and lost access to my private windows shares (public works fine). I tried downgrading back to RC4, and that didn't seem to fix it either with a quick test. When I attempt to access a share with my credentials I get "invalid user/password" message I assume it is perhaps related to either: samba: version 4.16.5 or more likely "SMB: remove NTLMv1 support since removed from Linux kernel" mentioned in the change list, but I have not been able to fix it. I did find a setting "LAN Manager Authentication Level" on the Windows machines, which was set to Send LM & NTLM – use NTLMv2 session security if negotiated, but I'm hesitant to change that to NTLMv2 only since I still have a Windows Home Server (based on Windows Server 2003) that doesn't natively support NTLMv2.

Okay, that makes sense, thanks for looking into this for me, and thanks for all your work on this plugin (and also explains why when I manually restarted nginx I still had to wait 5 minutes or so for the GUI to come up).

Here are my diagnostics and a screen shots. I wasn't sure if you wanted the UD config page (I believe I left everything at the default) or the page showing the UD tab from main. I have one drive that is used for offline backups, so it isn't typically connected, but is still shown/remembered. unraid-server1-diagnostics-20201116-1320.zip

Sorry, I should have been clear. I get a timeout page going to the unraid home page (or other unraid pages such as Dashboard, UD, Main, etc). However, I have dockers, such as Plex that publish their own web page outside of unraid, and those pages are available. The only way to get the unraid pages to come back up is to login via SSH, and start nginx, which shows as not running on system boot when I have UD installed, and I believe is what provides the unraid web front end.

Yes, multiple browsers, multiple PC's

I'm not clear what the screen shot you are asking for would be. In my case when I have unassigned devices plugin installed, after a reboot, there is no unraid web page to display, and when I telnet in nginx isn't running, I can manually start nginx, and after a couple minutes unraid's web page comes up, and all appears normal, until the next reboot.

I'm not sure if anyone else has upgraded to 6.9.0 RC 35 with this installed, but it seems to create an issue for the web console (nginx). When I upgraded to RC 35, the console wouldn't come up, and after some trial and error I determine that it was due to something in unassigned devices plugin (I don't have the plus installed if that helps narrow it down). I could get the Web UI to start by restarting nginx, and waiting about 5 minutes. I verified this by re-adding the unassigned devices plugin, and once again the problem showed up, remove the plugin and the problem goes away. Any suggestions would be appreciated. Here is the link (hopefully this comes through) to the thread I started with my diagnostics.zip attached:

So the plugin causing this for me appears to be unassigned devices, once I removed that the Web UI is back to normal function on boot.

I'll give that a try, I guess I should be clear (after looking at the boot menu for the first time in ???). When I say GUI, I am actually referring to the Web UI, not the GUI option from the boot menu. I tried the Safe mode with no plugins, and the GUI loads, so it looks like I have an issue with a plugin . Now to determine which one...

I have not tried safe mode (keyboard issue on the server doesn't allow me to select options, so may need a new keyboard, although it works after bootup?, just not on the selection screen). I have discovered that on bootup the nginx service reports that it isn't running if I telnet in. If I restart nginx using the rc.d script it reports running, and gives me a 500 server error but if run nginx a couple of times (which comes up with port already in use errors) the GUI does seem to come up on either RC 30 or RC 35.

I just tried to upgrade from RC 30 to RC 35. When I did, I have no GUI, but it appears everything else is up and running (can view my dockers, telnet, and access shares). I reverted to RC 30, and I still had no GUI, but I was able to restart NGINX from the command line in /etc/rc.d. So I reinstalled RC 35, and same issue, no GUI. I tried starting the GUI from the command line, and could only get a 500 error. I didn't see anything in the syslog that stood out to me, so I'm hoping someone else will have a suggestion. I have attached the diagnostics from the first failed install of RC 35. unraid-server1-diagnostics-20201116-1320.zip

Are you on the latest version of Unraid? I haven't noticed the issue for the last couple of releases (probably 6.5 onward, but for sure in the 6.6 releases) it hasn't been an issue, although I've only had to reboot for OS upgrades so not very often.

Understood, basically as long as the parity check isn't killing usability (aka getting asked why the rest of the family can't watch a movie), I'm fine with that speed, especially since I think my HBA cards would become a bottleneck shortly after the CPU issue was fixed .

Good to know, and that would make sense now, since it was running about 16-17% which would be one of the six cores at 100 percent. I played with it a bit yesterday and found some things. The md_stripes and md_window don't seem to impact this issue, but the md_sync_thresh is the value that makes a huge difference. If I bump it up to say the 2000 value suggested above, the machine basically locks up, and has to be brought down from the command line. I had to reduce it all the way to 96 to get it so that the call traces don't show up, and I'm able to use the machine normally. The other thing of note is changing this didn't appear to slow the parity check. I'm still getting about 60 MB/s even with the reduced value. Thanks everyone for the help with this.

So I upgraded to 6.6.3, and changed the tunables. When I manually kicked off a parity check, I'm still gettin the slower (600 MB/s) throughput, and I would say the accessibility of the server is worse than before. For example, now not only can I not stream through Plex, SMB shares won't come up, and the log viewer won't come up either. I can also say I don't think it's CPU constrained since the CPU usage never goes above 20% I did discover that with the higher tunable values the server itself became unresponsive (I couldn't view the log, couldn't cancel the parity check, and finally had to reboot from the command line). When I reduce the values it goes back to the server being responsive, just can't stream etc. I did notice this happening in the logs, which I assume points to CPU issues (but why am I only seeing it on parity check)? Nov 1 07:37:07 unraid-server1 kernel: INFO: rcu_sched self-detected stall on CPU Nov 1 07:37:07 unraid-server1 kernel: 8-....: (420008 ticks this GP) idle=85a/1/4611686018427387906 softirq=9839/9839 fqs=103727 Nov 1 07:37:07 unraid-server1 kernel: (t=420008 jiffies g=7518 c=7517 q=888072) Nov 1 07:37:07 unraid-server1 kernel: NMI backtrace for cpu 8 Nov 1 07:37:07 unraid-server1 kernel: CPU: 8 PID: 10774 Comm: unraidd Not tainted 4.18.15-unRAID #1 Nov 1 07:37:07 unraid-server1 kernel: Hardware name: Supermicro H8DM8-2/H8DM8-2, BIOS 080014 10/22/2009 Nov 1 07:37:07 unraid-server1 kernel: Call Trace: Nov 1 07:37:07 unraid-server1 kernel: <IRQ> Nov 1 07:37:07 unraid-server1 kernel: dump_stack+0x5d/0x79 Nov 1 07:37:07 unraid-server1 kernel: nmi_cpu_backtrace+0x71/0x83 Nov 1 07:37:07 unraid-server1 kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Nov 1 07:37:07 unraid-server1 kernel: nmi_trigger_cpumask_backtrace+0x57/0xd7 Nov 1 07:37:07 unraid-server1 kernel: rcu_dump_cpu_stacks+0x91/0xbb Nov 1 07:37:07 unraid-server1 kernel: rcu_check_callbacks+0x23f/0x5ca Nov 1 07:37:07 unraid-server1 kernel: ? tick_sched_handle.isra.5+0x2f/0x2f Nov 1 07:37:07 unraid-server1 kernel: update_process_times+0x23/0x45 Nov 1 07:37:07 unraid-server1 kernel: tick_sched_timer+0x36/0x64 Nov 1 07:37:07 unraid-server1 kernel: __hrtimer_run_queues+0xb1/0x105 Nov 1 07:37:07 unraid-server1 kernel: hrtimer_interrupt+0xf4/0x20d Nov 1 07:37:07 unraid-server1 kernel: smp_apic_timer_interrupt+0x79/0x89 Nov 1 07:37:07 unraid-server1 kernel: apic_timer_interrupt+0xf/0x20 Nov 1 07:37:07 unraid-server1 kernel: </IRQ> Nov 1 07:37:07 unraid-server1 kernel: RIP: 0010:raid6_sse24_gen_syndrome+0xed/0x1b3 Nov 1 07:37:07 unraid-server1 kernel: Code: db e8 66 0f db f8 66 44 0f db e8 66 44 0f db f8 66 0f ef e5 66 0f ef f7 66 45 0f ef e5 66 45 0f ef f7 48 8b 0a 66 0f 6f 2c 01 <66> 42 0f 6f 3c 11 66 46 0f 6f 2c 01 66 46 0f 6f 3c 19 66 0f ef d5 Nov 1 07:37:07 unraid-server1 kernel: RSP: 0018:ffffc9000414fc80 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13 Nov 1 07:37:07 unraid-server1 kernel: RAX: 0000000000000440 RBX: 0000000000000008 RCX: ffff8802ee9a7000 Nov 1 07:37:07 unraid-server1 kernel: RDX: ffff8802ee9893f0 RSI: 0000000000000440 RDI: 0000000000000004 Nov 1 07:37:07 unraid-server1 kernel: RBP: ffff8806110da000 R08: 0000000000000460 R09: ffff8802ee989410 Nov 1 07:37:07 unraid-server1 kernel: R10: 0000000000000450 R11: 0000000000000470 R12: ffff8806110db000 Nov 1 07:37:07 unraid-server1 kernel: R13: 0000000000001000 R14: ffff8802ee9893d0 R15: 0000000000000008 Nov 1 07:37:07 unraid-server1 kernel: check_parity+0x202/0x349 [md_mod] Nov 1 07:37:07 unraid-server1 kernel: ? autoremove_wake_function+0x9/0x2a Nov 1 07:37:07 unraid-server1 kernel: ? __wake_up_common+0xa5/0x121 Nov 1 07:37:07 unraid-server1 kernel: handle_stripe+0xe8a/0x1226 [md_mod] Nov 1 07:37:07 unraid-server1 kernel: unraidd+0xbc/0x123 [md_mod] Nov 1 07:37:07 unraid-server1 kernel: ? md_open+0x2c/0x2c [md_mod] Nov 1 07:37:07 unraid-server1 kernel: md_thread+0xcc/0xf1 [md_mod] Nov 1 07:37:07 unraid-server1 kernel: ? wait_woken+0x68/0x68 Nov 1 07:37:07 unraid-server1 kernel: kthread+0x10b/0x113 Nov 1 07:37:07 unraid-server1 kernel: ? kthread_flush_work_fn+0x9/0x9 Nov 1 07:37:07 unraid-server1 kernel: ret_from_fork+0x22/0x40

I'm having an issue over the last several parity checks. I've gone from around 75-80 MB/s to 55-60 MB/s and of course the duration has gone up as well, from 11 hours to 14.5. The speed duration isn't a big deal, but I have also noticed that the server itself isn't as responsive while the parity check is running. Previously I was able to use Plex as normal while the parity check was running, but now it buffers or stops during playback if the parity check is running. I had previously changed the tunable attributes, so I changed those back to normal for the last 2 parity checks, but the issue still remains. I haven't changed any hardware or added anything during that time. When I looked at system stats before the issue I would see about 900 MB/s total throughput at the start of the check, now I'm seeing about 600 MB/s. Any suggestions to improve this? Hardware is 2 and 3 TB drives, on a supermicro H8DM8-2 motherboard with 2 Six-Core AMD Opteron 2431 2.4 Ghz chips, and 24 GB of RAM.. I use 5 ports on the MB, the other drives are connected to 3 Supermicro SAT2-MV8 HBA cards with a total of 12 disks connected. I'm running 6.6.0 RC 4, with dual parity drives, and Plex is in a docker. container I have attached my diagnostics zip, so let me know if there is something else that is needed to help diagnose this. Thanks for any help. unraid-server1-diagnostics-20181031-1529.zip

I've been having an issue for awhile now that shows up when I do a reboot. Basically it hangs, originally I thought on the command "Starting rsyslogd daemon: /usr/sbin/rsyslogd -i /var/run/rsyslogd.pid", but today after letting it sit for about 5 minutes I did see one more line show up. And that is "dhcpcd already running on pid 1755 (/run/dhcpcd-br0-4.pid)". If I do a power off it boots fine, it's just on a reboot where the issue comes up. I can't attach diagnostics, because, although it says it's going multiuser just before this, I can't telnet in, or use any shares since they aren't started. It's almost like some process is surviving a warm boot, but goes away on a cold boot? I'm attaching a screenshot of the "frozen" screen. Any suggestions would be appreciated.

Doh, I feel stupid, I had tried the plexinc one before and didn't like it, but the template on unraid still existed. Once I picked the correct template, all is good again. Thanks for helping me find the issue. Sent from my SM-G955U using Tapatalk

Here is the docker command, I have tried with both latest and plexpass for version Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='PlexMediaServer' --net='br0' --ip='192.168.1.193' --privileged=true -e TZ="America/Denver" -e HOST_OS="unRAID" -e 'PLEX_CLAIM'='claim-bDUEs3yvUDapqqBy8Cnz' -e 'PLEX_UID'='99' -e 'PLEX_GID'='100' -e 'VERSION'='latest' -v '/tmp/':'/transcode':'rw' -v '/mnt/user/':'/data':'rw' -v '/mnt/user/Apps/PlexMediaServer':'/config':'rw' 'plexinc/pms-docker' 0f5bdb8dc802e820c3c8f960f5aedad35923076f84b471563674f4086f041ca7 The command finished successfully Sent from my SM-G955U using Tapatalk

Same issue here, info in the post right above yours Sent from my SM-G955U using Tapatalk

I'm running into a plex update issue after having to remove/recreate the docker image. I ended up switching the fixed IP address (from .48 to .193). After recreating the docker, everything seems to work (I can play media, plex shows it is configured for remote access, and plex can determine there is a plex update available), but it doesn't update plex when I restart the docker container, and the log is much shorter than it was previously. I'm including the whole log file here to see if that triggers anything, my first thought was the container doesn't have outside access, but I would think that would mean no notification of update, and no remote access, so I'm kind of lost here. [s6-init] making user provided files available at /var/run/s6/etc...exited 0.[s6-init] ensuring user provided files have correct perms...exited 0.[fix-attrs.d] applying ownership & permissions fixes...[fix-attrs.d] done.[cont-init.d] executing container initialization scripts...[cont-init.d] 40-plex-first-run: executing...Plex Media Server first run setup complete[cont-init.d] 40-plex-first-run: exited 0.[cont-init.d] 50-plex-update: executing...[cont-init.d] 50-plex-update: exited 0.[cont-init.d] done.[services.d] starting services[services.d] done.Starting Plex Media Server.[cont-finish.d] executing container finish scripts...[cont-finish.d] done.[s6-finish] syncing disks.[s6-finish] sending all processes the TERM signal.[s6-finish] sending all processes the KILL signal and exiting.[s6-init] making user provided files available at /var/run/s6/etc...exited 0.[s6-init] ensuring user provided files have correct perms...exited 0.[fix-attrs.d] applying ownership & permissions fixes...[fix-attrs.d] done.[cont-init.d] executing container initialization scripts...[cont-init.d] 40-plex-first-run: executing...[cont-init.d] 40-plex-first-run: exited 0.[cont-init.d] 50-plex-update: executing...[cont-init.d] 50-plex-update: exited 0.[cont-init.d] done.[services.d] starting services[services.d] done.Starting Plex Media Server.

Found it, it's the advanced view (not advanced settings) accessed by the slider in the top left of the screen, then just update the URL there

Edit the container settings, open advanced view and you'll see the field for web ui. Plug the ip in there I don't see that under advanced view, with the latest version of the docker, The only thing there is container path.