dalben

Thanks for the explanation. Yes, it's a non-issue and has no impact on the functionality of anything. But it's an oddity so IMHO worth highlighting to limetech in case they had nothing else to do and felt like looking into it.

I don't use an adblocker these days. PiHole has eliminated the need for that I've stripped down my plugins to LastPass, nzbget-chrome and Transmission easy client. Still happens. Next time I have a multi-update I'll disable one at a time.

An ad blocker, lastpass, transmission monitor and nzbget minor. Need to check if there is anything else. But pretty sure this wasn't showing in earlier releases. Over the weekend I can load up a 6.7x and check.

Yes. I have a script running at array start via User Scripts that I needed to install when the flash drive got locked down. When I'm home I can try disabling that

Updated. So far all good. The status bar showing Array Stopped•Starting services... despite the array having started is still there though, but thats just cosmetic

Yes, though my scripting skills aren't great but the ability to shutdown dockers and plugins before a parity check would be handy. Though I'm assuming doing so would speed up the parity check.

Ah, ok, thanks. I'll have a look at the plugin as if it allows me to stop selected services and docker containers when doing the parity check it might be handy. Thanks

Case should always matters. Windows was the first OS I worked with where userid case wasn't an issue.

I'm running 6.8 rc4. Latest version of Nerdpack. It shows utempter-1.1.6-x86_64-2.txz has an update ready. When I update it I get utempter-1.1.6 package missing! Not sure what it's used for and everything seems to work fine but the OCD in my is getting worked up over the failure to update. Any suggestions?

I'm not sure of the editions but there is a working Minecraft server docker in the apps section. I think it uses MCPE, but my kids would know better.

OK, fixed now. In a moment of spring cleaning I stripped back a lot of old files and stuff from my flash drive. It dropped in the default syslinux.cfg file. That in turn had over written the change I made to make the nct6775 driver available: append initrd=/bzroot acpi_enforce_resources=lax

Thanks for that. I'll roll back to rc3 and see if that makes a difference. UPDATE: OK, something is amiss but I have no idea where to start looking: sensors-detect output: Driver `nct6775': * ISA bus, address 0x290 Chip `Nuvoton NCT5573D/NCT5577D/NCT6776F Super IO Sensors' (confidence: 9) Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) sensors output: root@tdm:~# sensors acpitz-acpi-0 Adapter: ACPI interface temp1: +27.8°C (crit = +99.0°C) MB Temp: +29.8°C (crit = +99.0°C) coretemp-isa-0000 Adapter: ISA adapter CPU Temp: +39.0°C (high = +80.0°C, crit = +98.0°C) Core 0: +37.0°C (high = +80.0°C, crit = +98.0°C) Core 1: +35.0°C (high = +80.0°C, crit = +98.0°C) Core 2: +39.0°C (high = +80.0°C, crit = +98.0°C) Core 3: +36.0°C (high = +80.0°C, crit = +98.0°C) modprobe coretemp nct6775 is my go file and I've run it a couple more times. with no change to the discrepancy between sensors-detect and sensors

The 6.8 series seems to have broken the System Temp plugin for my system. It was working fine with 6.7. Sensors-detect still finds the sensor chip and driver required, the nct6776. Found `Nuvoton NCT5573D/NCT5577D/NCT6776F Super IO Sensors' Success! (address 0x290, driver `nct6775') But it seems the sensors.conf file in the plugin directory isn't being read. as only the coretemp probes are available.

I have a couple of modeprobe commands in my go file. Can they still be run from there or should they be somewhere else? the system temp plugin isn't working with rc1 and rc 4 # start sensors modprobe coretemp modprobe nct6775

rc3 and adding server min protocol = NT1 to smb-extra.conf worked for me. Here are the 2 testparm -sv outputs. One is rc1 and the other rc3 before the smb-extra.conf change. Also note the coreelec install is linux, not android. testparm68rc3.txt testparm68rc1.txt

Never tried. I just use unraid user credentials when I access the shares. It's a local user created on the unraid server, not my Windows pc.

If there is anything I can do to test whether the patches solve the issue before the next release, let me know.

The report is over 2 threads so let me consolidate and add more here: There was no issue on rc1 and previous releases. I have supplied diags from rc1 and rc3 Corelelec was set to SMB min 2 max 3, I changed that to min1 max 3 but no change. I don't know how to change the setting on an Android phone WS-Discovery on Unraid was enabled, I disabled, no change Netboid was enabled on unraid, I disabled, no change AFP Legacy was enabledon unraid, i disabled, no change. I have, reverting back to rc1 solves the problem for me. If you're expecting me to work out what's changed between rc1 and rc3 that's created this issue then I'm out of my depth. Happy enough to try different things when asked to help identify the issue, but I've reached my technical limitations.

Not sure. All I can tell you is it's worked fine for years up to 6.8rc1. With rc3 I can't connect to server shares.

Unraid server. If they are bonded try just using a single NIC and see if that helps

Do you have booked NICs by any chance? I had a similar issue. Unbonded, or is that debonded, disabled one NIC and all worked great.

Same. I'm using the White theme