peppingc

For those following I seem to have solved my issue using the guide here :- https://kodi.wiki/view/SMB Note I used the steps outlined for Device Name method rather than IP address (skip step 4 and go straight to step 5). It's not as simple as when SMB v1 was enabled and I could just browse to the relevant file path but is apparently a more secure way of sharing files.

Thanks so much, just waiting for a parity check to finish and will do that. I tried Googling a solution but got lost in the confusing posts it returned. I'm assuming I can also turn off SMB 1.0/CIFS Client on the Winows 10 side when I apply this change. Edit2: I followed your suggested steps and turned off SMB 1.0/CIFS Client in Windows 10 but now when I browse for my media directories over on the UnRAID server I can not see the existing file paths, just a single entry for BORG.modem (Borg being the name of my UnRAID server. Is there anything else I need to do on the UnRAID server? Edit3: I can see the file paths if I open up the BORG.modem entry and can access the files that way however I can not see my other Windows based file sources on other PCs any more (other PCs are all still running Windows 7 though, not 10.

I have recently built a HTPC running Kodi via Windows 10. In order to get the HTPC to see my SMB shares I have had to renable SMB 1.0/CIFS Client as per this article :- https://www.windowscentral.com/how-access-files-network-devices-using-smbv1-windows-10 I understand SMBv1 is no longer supported in Windows 10 by default due to security concerns but how do I make UnRAID support SMBv2?

Won't be an issue for me as the drive bays on my Gen8 Microserver are non-hot swap. Can't recall exactly which model it is but it only has 4 bays and is running a Pentium G2020T CPU.

ACPI Error Message Issues I was getting the same ACPI error messages detailed towards the start of this thread on my Gen8 Microserver which was already running the latest J06 BIOS dated 04/04/2019. I followed the advice given there namely ;- "This is essentially a misreading and does not affect anything but spamming your system log. To remove, disable "acpi_power_meter" module from the kernel by adding this line to the /boot/config/go file: rmmod acpi_power_meter" After a reboot I am now seeing this message in the system logs :- Nov 25 12:21:25 Borg kernel: ACPI: Early table checksum verification disabled Nov 25 12:21:25 Borg kernel: ACPI: RSDP 0x00000000000F4F00 000024 (v02 HP ) Nov 25 12:21:25 Borg kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aControlBlock: 16/32 (20180810/tbfadt-564) Nov 25 12:21:25 Borg kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm2ControlBlock: 8/32 (20180810/tbfadt-564) Nov 25 12:21:25 Borg kernel: ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20180810/tbfadt-669) Nov 25 12:21:25 Borg kernel: ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 32, using default 8 (20180810/tbfadt-669) I have attached a copy of the post-reboot system log for your reference. Is there anything to worry about here or are we all good to go now? borg-syslog-20201125-0124.zip