Alexander

This is similar to my situation. I use a memory card reader that has unique serial numbers (a KingstonFCR-HS4). The Sandisk 32 GB SD card broke and my unraid did not start anymore. So i replaced the memory card with a new one with a fresh v6.10.3 on it. I started it as a trial. Did Tools/registration and put my license link in there (that i got on my mail and was used with that memory card reader before). I assigned my parity and data drive (luckily I had labeled the drives in my machine) and my WD red drives has a label with their number on them on the front side. On the Main tab iIt shows in red "Parity All existing data on this device will be OVERWRITTEN when array is Started" exactly as in the picture above. I tick the box Parity is already valid BEFORE starting the array. And now I start it. Hopefully it will work as I want it to. Message " Proceed to start Parity valid requires ALL disks to have their original content" shows. I click PROCEED because I have not touched the machine since I ran Unraid last time. I do not use cache drives so array setup was easy, but I will in the future. Then i got my VMs back because I have them on my array! My Windows passthrough VM started because I have it on autostart since before. Hurray. My passthrough Windows 10 VM started but stalled. I stop that Windows VM (no need to force stop stop works perfectly) and started it again (I have had some stalls in it starting lately). Of course this is because Windows 10 (at least as VM installed a while ago) is maybe not "up to date" there are a lot of updates recently it has nothing to do with Unraid. It starts! It is working. Totally amazing. My only computer that has Unraid and Windows 10 on it is working. I have to set it to autostart the array also. Is OFF with new unraid from scratch. Settings/Disk Settings/Enable auto start: Yes also i set Shutdown time-out: 900 90 sec is sometimes too little on my machine without SSD cache drives and Windows 10 VM sometimes need a lot of time to stop properly when it needs to update itself. So I set it to the max which is 900. It automatically shuts down immediately if the stopping processes has finished. This is exactly how I want it to work. I just want to say thank you very much to all developers and contributors. It really works as I want and expected.

I can't get UPnP working. UPnP Set to on in router. Set to Yes in "Management Access" and "VPN Manager". In VPN Manager on Local Endpoint line i get "UPnP: tunnel is inactive" I even tried installing Merlin on My ASUS RT AC 68U router but still same result. Any solution to this?

OK I just reproduced the problem on my unraid and it is not the same problem you have. You get an IP address so your unraid port works. Since you get a 169.254.x.x address your routers DHCP doesn't seem to work or be set right. Source: https://superuser.com/questions/238625/why-is-windows-default-ip-address-169-xx-xx-xx https://www.lifewire.com/automatic-private-internet-protocol-addressing-816437 "When the DHCP process fails, Windows automatically assigns an IP address from the private range, which is 169.254.0.1 to 169.254.254.255." Do not read "Windows" litterally above it applies to all kind of OSes. Try to fix your router DHCP settings. -------------------------------------------------------- Now I describe my case. I disabled my bridge of eth0: and eth1: When the cable was connected to eth1: or eth2: result was "IPv4 address not set" at unraid boot/start. Then it was impossible to connect to it remotely or do anything meaningful except login and write "command like things". I have 3 LAN ports on my motherboard (shows up as eth0: eth1: eth2:). Link to my motherboard if someone needs it: https://asrock.com/MB/Intel/Fatal1ty Z370 Professional Gaming i7/index.asp The copper (ethernet) cable had to be connected to the original eth0: port to get an IPv4 address on my machine. The unnraid ipv4 address is the one I set the router to appoint to the port (static) or one random from the DHCP range I set the router to use on the LAN when I disabled the "static" rule. If you have several ports on your computer try to connect them one at a time (cycle connection through them) to your router and start your unraid machine each time. Hopefully with one of the connections unraid will get an IPv4 address. Then you can use it. If you like me, then still want to use a "non working" port connected alone to your router instead, a solution I found was to bridge the used port together with the working port in Network Settings. After that your options is to not connect anything to the "working" port, or connect an extra connection to it as well if you like. In my case there is little use to connect it (my eth0:) since it would only add 1 Gb to my eth1: 10 Gb port and I prefer to have less cables around. As I pointed out you can only edit Network Settings with the Docker and VMs turned off, so you should not see DOCKER and VM in the unraid menu when you change your Network Settings. In Network Settings in my case I set "Enable bridging: Yes" and "Bridge members of br0: eth0,eth1".

I had this experience too. Only way for me was to use another computer. Login in on my router from the other computer to see what IP address my unraid server got. Then let unraid run quite long after start. And finally I somehow managed to type unraid IP in browser of my other computer and log in (I had extra direct cable between computer and unraid server). Router managed to show unraid IP to me but I could not connect through it since unraid IP was outside of set router DHCP range. When inside unraid, fix common problems showed me this kind of problem https://forums.unraid.net/topic/89462-unraid-os-version-683-available/?do=findComment&comment=849149 I changed those "DNS" settings in my router. Also I had these problems https://forums.unraid.net/topic/89462-unraid-os-version-683-available/?do=findComment&comment=841960 Had to fix that too. I chose to Disable Dockers and VM Manager in settings, don't forget "Enable: No" and then <apply> on both then reboot, so you can edit network settings. Then in Settings/Network settings i changed eth0: to bridge with my eth1:. I have unraid connected (copper cable ethernet) with my eth1: 10 Gb port and unraid is slow booting up with it so bond fails and result is unraid geting strange IP that is out of my router set range. After bridging it with my 1 Gb eth0: port (I bridged my 1 Gb eth0 with eth1: actually) then boot/start went fast again and unraid got IP as I had set up in router (inside router DHCP range, and static as I had set it to). After that it works again. Even reordering so my 10 Gb port becomes eth0: still results in slow start/bootup. "Starting haveged entropy daemon:" shows during 1 minute or something before continuing and it says something about bond0 "not working". Above bridge solution bundled my eth1 with the "hardware first port" (shows up on top with default new unraid) and that is since 6.8.2 (I think) my eth0: 1 Gb, and then it got fast booting up again, no "bond0" issue. I do not use any cable to eth0: 1 Gb port to clarify. Prior to 6.8.2 (until 6.8.1) or something the kernels put my 10 Gb port on top as eth0: so then I did not experience these issues. I guess I could as well use a cable only on eth0: (now since 6.8.2 my 1 Gb) and it will probably work too, but I don't want to. 3rd thing I did was to untick my USB port passthrough in my VFIO-PCI CFG plugin. But even when I plugged in my keyboard in a USB port that was not passed through the keyboard was dead (no lights) and didn't work in unraid GUI boot mode after haveged daemon part. But after above fixes from another computer it works.

From link above. Changes in this release: - Added support for 5.6 kernel version (probably = next stable unraid 6.9.x) ixgbe is linux driver for for intel 10 Gb network controllers 82598 and 82599. Source: https://www.intel.com/content/www/us/en/support/articles/000005688/network-and-i-o/ethernet-products.html

Yes that file is not available as download (executable file) anymore unfortunately. If you have to use a GUI interface the only ones available also have hard link options and makes the interface harder to use. If you opt to use one of those I suggest HardLinkShellExt_X64.exe

On a terminal (not using VM and passthrough). Don't use splashtop. Use NoMachine and the sound will work, no need to use <sound model> part then I think. https://www.nomachine.com/ NoMachine is free and fast. NoMachine was probably not available when the video was made and now splashtop is not free any more. On a VM passthrough. Easiest solution is to get a USB Audio device. For example one of these. https://focusrite.com/en/scarlett With the above you need to passthrough your USB port(s) otherwise a click/abrupt change happens like every 2 seconds. I guess this is because it shares the port access with unraid when not passthrough. This is hard to hear but I noticed it after long testing. To avoid the almost unnoticeable "click" You will need to have at least 1 port non-passthrough for your unraid flash and that has to be in another IOMMU group than the passed through VM ones. So you might have to buy an extra USB PCIE card if your motherboard doesn't have USB in at least 2 different IOMMU groups (means usually uses at least 2 USB controllers chips on motherboard). Obviously such motherboards are not among the most common ones and are not the cheapest. If you have a graphics card you could try to passthrough to its sound part. I only have my Intel CPU graphics that do not have sound, so I use external USB sound as above. It is very nice to passthrough the motherboard main USB controller, that is usually almost all computer ports if you have 2 USB IOMMU group setup. You can then unplug and plug things in after the VM has started as and when you like (keyboard, mouse, USB sound, printer, etc), and they will all have trouble-free fast access. Avoid the use of a USB hub.

I don't use a cache pool. When the parity check starts my Windows VM (on my array) practically freezes. I guess this is normal? Fix is to pause the parity check until I am finished with my VM. I guess another solution is to use cache or to put your VM "unprotected" on an unassigned device?

I don't know but if you have uprgaded your unraid version to 6.8.x lately ethx: ports got reordered. see my answer here: https://forums.unraid.net/topic/91852-problem-with-10gbe-unstable-web-connection/?do=findComment&comment=852828 Don't know if this helps. Just trying to help you.

When i changed to more recent Unraid version it reordered my ethx: ports. The 10 Gb was eth0: and now it became eth1: after unraid update. eth0 is connected to br0 and possibly vibr0 used in dockers and VMs or something. So old settings when dockers and VMs were created don't match (1 and 10 Gb ports are not at same brx, vibrx). My solution was to reorder NICs (eth0, eth1) back in Network settings. If this is your problem (i do not know, just speculating) then my fix is as follows. To change Network Settings you must go to Settings and Disable in VM Engine and Docker first. Then you can edit Netw. Sett. Once you changed MAC numbers in "Interface Rules" so 10 Gb is back on eth0: or whatever you had there you have to apply setting and REBOOT. Only after reboot will they change to what they were set to. I'm not sure this is the cause behind your problems. Just trying to help. If you like me have several NICS (ethernet ports) and your 10 Gb has been reordered in the ehtx: numbering this might fix it. A wild guess is that the new NIC order is an effect of a new linux kernel used in more recent unraid versions. Maybe some linux user problems were fixed for multiple NIC boards by this change, but it messed up old unraid configs when updating unraid version.

I prefer to set the address as "static" in the router, and leave on automatic in unraid. How to set a "static" address on a ASUS router is described here. https://www.asus.com/support/FAQ/114068 Note that the router will still use the HDCP dynamic addresses in the range you decided to use, so all other devices connected to it will always connect and get a dynamic address (prevents address conflicts). You can reserve addresses in the used range. That is what a "static" address as in the link above is. The "reserved" address is linked to the MAC address (=unique) of your physical communication port and thus work as a "local" LAN "static" address. If you only set your static addresses on the router it will not allow you to give the same address to several devices or to be outside the used range. As an example If you want to suddenly use the 192.168.X.X range instead of 10.X.X.X which you can choose to do on your router. Then your unraid static ip has to be changed at the same time to fit in that range before you can access it. The router will immediately notice you that your static IP is not valid, unraid will not, because it doesn't know that you are changing the router "IP range". I prefer to keep track of all this management in my router. For example if you connect several unraid servers to your router you manage all addresses on the router instead of on the router (IP range) and all your unraid servers (static addresses). If you connect to several different routers (network backup scenario or something) or if someone else manages the router and you can't configure them then I can see a point in setting the static address in unraid. If you happen to mess with the settings, at least unraid will try to connect at some non conflicting address if you have it set to automatic. Just log into your router and see where it is or use the id name like "Tower" when searching from a terminal device. Do note that a static address on WAN (the internet) is something else and usually what people mean when they talk about a static address. In the context of unraid of course we talk about our local (LAN) "static" IP.

Yes VM Edit bug is still there. Change Primary vDisk Location: Auto to Manual. => your vdisk greyed out path gets Black. Then change/edit all your VM options. Then update. Next time you edit it, it will unfortunately be set to AUTO again, so you will have to change it to Manual again. Otherwise it doesn't update any changes (when Primary vDisk Location: is set to Auto). This applies to everything, name change, icon change, memory amount change, machine type change etc. This solution is mentioned in post above and here: https://forums.unraid.net/topic/75460-vm-settings-wont-update/?do=findComment&comment=701903

Interesting. Does the XG-U2008 router show that it has Full 10 Gb speeds on both links (blue lights for 10 Gb ports)? https://www.asus.com/Networking/XG-U2008/ See Signal Quality Indicator in the above link. Here is somebody else with the same "issue" on a specific motherboard.

I read that it did not work for somebody in this Unraid forum, but maybe it was this post. But that is for an older Aquantia 5 Gb controller the AQC111U. So it might work with the AQC108 5 Gb controller? Here a link to some Aquantia chips. There seems to be more than I knew of. https://www.marvell.com/products/ethernet-adapters-and-controllers/aqtion-ethernet-controllers.html For the linux driver to work OOTB (out of the box) it must be included in the linux kernel or "added" by Limetech, the later only possible if the driver code is "compatible" with the linux kernel used. Might work now or in the future. If it does report back. Since you have the card please try it. You can use the 30-Day Free Trial to test it, if you do not already have a license. You can not use the same USB key for a new trial after the expiry unless you buy it or maybe by contacting limetech for a trial extension (if possible). Go into settings / Network Settings. Scroll down to Interface Rules. If Interface eth0: eth1: eth2 etc ends with something like "PCI device 0x1234:0x1234 (atlantic) it will probably work. (atlantic) is the Aquantia driver used for my 10 Gb connection. Intel 1 Gb often has (igb) or (e1000e) drivers on recent boards.