superjudge_13

it was working on that old server now no workie

# Version 6.12.4 2023-08-31 ## Upgrade notes ### Known issues Please see the [6.12.0 release notes](https://docs.unraid.net/unraid-os/release-notes/6.12.0/#known-issues) for general known issues. ### Rolling back Before rolling back to an earlier version, it is important to ensure Bridging is enabled: * ***Settings > Network Settings > eth0 > Enable Bridging*** = Yes Then Start the array (along with the Docker and VM services) to update your Docker containers, VMs, and WireGuard tunnels back to their previous settings which should work in older releases. Once in the older version, confirm these settings are correct for your setup: * ***Settings > Docker > Host access to custom networks*** * ***Settings > Docker > Docker custom network type*** If rolling back earlier than 6.12.0, also see the [6.12.0 release notes](https://docs.unraid.net/unraid-os/release-notes/6.12.0/#rolling-back). ## Fix for macvlan call traces The big news in this release is that we have resolved issues related to macvlan call traces and crashes! The root of the problem is that macvlan used for custom Docker networks is unreliable when the parent interface is a bridge (like br0), it works best on a physical interface (like eth0). We believe this to be a longstanding kernel issue and have posted a [bug report](https://bugzilla.kernel.org/show_bug.cgi?id=217777). If you are getting call traces related to macvlan, as a first step we recommend navigating to ***Settings > Docker***, switch to advanced view, and change the "Docker custom network type" from macvlan to ipvlan. This is the default configuration that Unraid has shipped with since version 6.11.5 and should work for most systems. However, some users have reported issues with port forwarding from certain routers (Fritzbox) and reduced functionality with advanced network management tools (Ubiquity) when in ipvlan mode. For those users, we have a new method that reworks networking to avoid this. Tweak a few settings and your Docker containers, VMs, and WireGuard tunnels should automatically adjust to use them: * ***Settings > Network Settings > eth0 > Enable Bridging*** = No * ***Settings > Docker > Host access to custom networks*** = Enabled Note: if you previously used the [2-nic docker segmentation method](https://forums.unraid.net/topic/137048-guide-how-to-solve-macvlan-and-ipvlan-issues-with-containers-on-a-custom-network/), you will also want to revert that: * ***Settings > Docker > custom network on interface eth0*** (i.e. make sure eth0 is configured for the custom network, not eth1) When you Start the array, the host, VMs, and Docker containers will all be able to communicate, and there should be no more call traces! ### Troubleshooting * If your Docker containers with custom IPs are not starting, edit them and change the "Network type" to "Custom: eth0". We attempted to do this automatically, but depending on how things were customized you may need to do it manually. * If your VMs are having network issues, edit them and set the Network Source to "vhost0". Also, ensure there is a MAC address assigned. * If your WireGuard tunnels will not start, make a dummy change to each tunnel and save. * If you are having issues port forwarding to Docker containers (particularly with a Fritzbox router) delete and recreate the port forward in your router. ### To get a little more technical... After upgrading to this release, if bridging remains enabled on eth0 then everything works as it used to. You can attempt to work around the call traces by disabling the custom Docker network, or using ipvlan instead of macvlan, or using the 2-nic Docker segmentation method with containers on eth1. Starting with this release, when you disable bridging on eth0 we create a new macvtap network for Docker containers and VMs to use. It has a parent of eth0 instead of br0, which is how we avoid the call traces. A side benefit is that macvtap networks are reported to be faster than bridged networks, so you may see speed improvements when communicating with Docker containers and VMs. FYI: With bridging disabled for the main interface (eth0), then the Docker custom network type will be set to macvlan and hidden unless there are other interfaces on your system that have bridging enabled, in which case the legacy ipvlan option is available. To use the new fix being discussed here you will want to keep that set to macvlan. ## System Drivers page Navigate to ***Tools > System Drivers*** for visibility into the drivers available/in use on your system. 3rd party drivers installed by plugins (such as NVIDIA and Realtek) have an icon that links to the support page for that driver. You can also now add/modify/delete the modeprobe.d config file for any driver without having to find that file on your flash drive. ## Other bug fixes and improvements * This release resolves corner cases in networking, Libvirt, Docker, WireGuard, NTP, NGINX, NFS and RPC. And includes an improvement to the VM Manager so it retains the VNC password during an update. * The shutdown process was modified to allow the NUT plugin to properly shut the system down. * The notification display time before auto-closing is now configugurable (see ***Settings > Notification Settings***). * A small change is that packages in /boot/extra are now treated more like packages installed by plugins, and the installation is logged to syslog rather than to the console. * The Update OS process will automatically update the Plugin-Update-Helper script if necessary. ## Changes vs. [6.12.3](https://docs.unraid.net/unraid-os/release-notes/6.12.3/) ### Base distro * create_network_ini: * fixed dhcp hook * improved IP address collection * diagnostics: * Add previous Unraid version to diagnostics version txt file. * Add ntp.conf, sshd.config, and servers.conf (with anonymized URLs) * anonymize IP addresses * docker: * add routing when shim or macvtap network is used * fix routing when "host access" is enabled * remove IPv6 from shim/vhost interface (some routers are incompatible) * libvirt, nginx, nfs, rpc: changed running process detection * nfsclient: start negotiation with v4, turn off atime modification * rc.6: leave /usr and /lib mounted during shutdown * rc.docker: * create same IPv6 network for containers and services * add more logging when stopping dockerd * rc.inet1: * do not use promiscuous mode for bridging * add persistent option to dhcpcd * rc.library: interfaces always listed in the same order, fix show ipv6 * rc.libvirt: remove 'itco' watchdog from XML if present * rc.local: annotate auto-generated /etc/modprobe.d/zfs.conf file * rc.services: * add logging * exclude WireGuard "VPN tunneled access for docker" tunnels from services * exclude WireGuard tunnels for ntp (code optimization) #### Package updates * btrfs-progs: 6.3.3 * curl: version 8.2.0 (CVE-2023-32001) * firefox: version 117.0.r20230824132758 (AppImage) * kernel-firmware: version 20230724_59fbffa * krb5: version 1.19.2 (CVE-2023-36054) * openssh: version 9.3p2 (CVE-2023-38408) * openssl: version 1.1.1v (CVE-2023-3817 CVE-2023-3446) * samba: version 4.17.10 (CVE-2023-3496 CVE-2022-2127 CVE-2023-34968 CVE-2023-3496 CVE-2023-3347) ### Linux kernel * version 6.1.49 (CVE-2023-20593) * CONFIG_SCSI_MPI3MR: Broadcom MPI3 Storage Controller Device Driver ### webGUI * Dashboard: hide ZFS bar when no ZFS is used * Docker settings: fix subnet sizes * Feedback: refactor feedback script * Network settings: fix DNS settings sometimes disappear * Notifications: new notification option: auto-closure time, default is 5 seconds * Pools: minimum free space: only enabled when array is stopped * Shares and Pools: show "Minimum free space" as absolute number instead of percentage * System Drivers: new page * Translations: trim key and value in language files * VM Manager: Retain VNC password during update. * VM Manager: Remove downloaded '.vv' files. * CSS: set overflow-x to 'auto' * update monitor_nchan

i have the orgingal USB from the old server if thats any help?

for sure it was in an old server we had lying round I updated Unraid recently as we were having AD syncing issues, but in the end decided to scrap it and stick the drive in my own unit

IOMMU group 0:[8086:1912] 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) IOMMU group 1:[8086:190f] 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07) IOMMU group 2:[8086:1901] 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07) [11ab:6485] 01:00.0 RAID bus controller: Marvell Technology Group Ltd. MV64460/64461/64462 System Controller, Revision B (rev 01) [1:0:0:0] disk ATA ST18000VE002-3BS EV01 /dev/sdi 18.0TB [1:0:1:0] disk ATA Samsung SSD 850 1B6Q /dev/sdj 250GB IOMMU group 3:[8086:a12f] 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) Bus 001 Device 001 Port 1-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002 Port 1-3 ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 003 Port 1-4 ID 413c:1003 Dell Computer Corp. Keyboard Hub Bus 001 Device 004 Port 1-6 ID 05dc:a761 Lexar Media, Inc. JD FireFly Bus 001 Device 005 Port 1-4.1 ID 413c:2010 Dell Computer Corp. Keyboard Bus 002 Device 001 Port 2-0 ID 1d6b:0003 Linux Foundation 3.0 root hub [8086:a131] 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) IOMMU group 4:[8086:a13a] 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) IOMMU group 5:[8086:a102] 00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31) [3:0:0:0] disk ATA Samsung SSD 850 2B6Q /dev/sdb 500GB [4:0:0:0] disk ATA ST18000VE002-3BS EV01 /dev/sdc 18.0TB [5:0:0:0] disk ATA ST18000VE002-3BS EV01 /dev/sdd 18.0TB [6:0:0:0] disk ATA ST18000VE002-3BS EV01 /dev/sde 18.0TB [7:0:0:0] disk ATA ST18000VE002-3BS EV01 /dev/sdf 18.0TB IOMMU group 6:[8086:a167] 00:1b.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 (rev f1) IOMMU group 7:[8086:a169] 00:1b.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #19 (rev f1) IOMMU group 8:[8086:a110] 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) IOMMU group 9:[8086:a112] 00:1c.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1) IOMMU group 10:[8086:a113] 00:1c.3 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #4 (rev f1) IOMMU group 11:[8086:a114] 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) IOMMU group 12:[8086:a118] 00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1) IOMMU group 13:[8086:a145] 00:1f.0 ISA bridge: Intel Corporation Z170 Chipset LPC/eSPI Controller (rev 31) [8086:a121] 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) [8086:a170] 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) [8086:a123] 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) IOMMU group 14:[1b21:0612] 03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) [8:0:0:0] disk ATA ST18000VE002-3BS EV01 /dev/sdg 18.0TB [9:0:0:0] disk ATA ST18000VE002-3BS EV01 /dev/sdh 18.0TB IOMMU group 15:[1b21:1242] 05:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller Bus 003 Device 001 Port 3-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001 Port 4-0 ID 1d6b:0003 Linux Foundation 3.0 root hub IOMMU group 16:[1969:e0a1] 06:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10) IOMMU group 17:[1103:3740] 07:00.0 RAID bus controller: HighPoint Technologies, Inc. Device 3740 (rev a1)

Hi Bud no the marvel card was pre-exisiting and has a couple of drives on it and the rest are on the main board all the new drives (not showing) are on the highpoint card (the one right at the bottom of the post below)

tower-diagnostics-20231128-1929.zip

Hi guys I recently removed a highpoint RocketRAID 3740A from a unraid server (6.12.3) that was working fine with 6 SSD's, i put both the card and all drives in my existing server and allthough the during boot the machine sees the card and attached drives, this paritular Unraid install (also 6.12.3) does not see any drives? any ideas

Cheers for the reply, Ive Just checked and that setting is already set, would this method require i set the new 500Gb SSD drive as a cache disk or add it to a cache pool? as these have not been setup as of yet

Hi Guys I just setup my first windows virtual machine, i assume the image resides in the defualt "domains" folder, now as far as i can see this exists on my Disk 5 my question is i wanted to put a 500GB SSD in after the fact and have that dedicated for the VM, is it just a case of stopping the VM and copying over the "domains" folder using Disk shares? that seems too easy