darianf

Did you try with macvlan driver? Also, can you share how did you configure your interface for the vlan? Did you allocate an IP to it? Did you also try to create the particular custom network from the GUI Page of the Docker Settings? As the ones defined from cli are not persisting...

I updated 2 towers from 6.6.7 to 6.7.0 without any issue. 1 optiplex 9010 and 1 asus x99-m ws (passthrough 1 ssd, 2 nvidia 10xx cards and 1 usb controller) no marvel controllers thou... Thank you for another great update!

the iommu setting did not solve the issue, but maybe the recreation of the usb. Your previous network was defined as static IP 192.168.1.66, but is your network 192.168.1.x or is it 192.168.0.x ? probably it should have been 192.168.0.66 some routers do not display properly the static clients (showing no ip), since they did not allocate IP by the dhcp server. regarding the //tower issue, it's because your w10 pc cannot resolve the "tower" to an ip address. you could try accessing the shares via the IP: \\192.168.0.66\share_name

do you have older vm's that are still working? or experiencing issues with all your current vm's? diagnostics are available in tools menu.

hi i see this that might cause the issue, not sure what's next Apr 11 03:32:06 Tower emhttpd: shcmd (24): /etc/rc.d/rc.nginx start Apr 11 03:32:06 Tower root: unable to load certificate Apr 11 03:32:06 Tower root: 23132667103040:error:0909006C:PEM routines:get_name:no start line:crypto/pem/pem_lib.c:745:Expecting: TRUSTED CERTIFICATE Apr 11 03:32:06 Tower root: Starting Nginx server daemon... Apr 11 03:32:06 Tower root: nginx: [emerg] PEM_read_bio_X509_AUX("/etc/ssl/certs/unraid_bundle.pem") failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: TRUSTED CERTIFICATE)

the /boot/macros file does not exist (i searched for macros file recursively in the flash). so no additional information to corroborate. indeed, in the go file, it should normally be only the emhttp daemon startup. but... as part of a manual configuration that i did for using rsync between a synology nas and this tower, i added extra commands to handle the ssh keys exchanged. Hence there are some extra commands for copying the keys and update some permissions (briefly mentioned in my previous post). this extra setup i had to take care when upgrading from 6.2 to 6.3 or something alike (i vaguely remember there was one UNRAID upgrade that was sensitive and the go file had to be "stock" during the upgrade). And it worked very well without issues so far. But for sure that entry in the go file for /boot/macros was not added by me. I found more info here - https://wiki.unraid.net/Console But still not sure how it came added... and why only the entry in the go file, without the actual /boot/macro file... In regards to keyboard issue, this is how i solved it indeed - I left a wireless dongle of a rii keyboard inserted in the tower I will try when i have time, to recreate the flash usb without the UEFI and see the behavior without keyboard. The bios option is to not report missing keyboard; and i specifically toggled this checkbox to make sure it's status is set. But to no effect. Any advantage on UNRAID between between uefi vs legacy flash? I guess no change... thanks a lot -d

ok, so running df didn't show something wrong on /boot I then created from scratch the usb, after backing up the config. Once usb was ready, i restored the config, overwriting the fresh/original one. Same behavior But, i noticed an error caused by something executing in my go file. Fixed that (the /root/.ssh dir was missing, required for copying some ssh keys, for rsync) And at the end of the go file, i found this 😮 # Add macros to the profile /boot/macros There's no such file macros, and i'm perplexed who added it - for sure not me/manually. I commented it out and things started to work. thanks @itimpi for suggesting recreating the flash, this enabled to get closer to the issue. Any idea what this macros entry could be? P.S: Another thing worth sharing. I discovered that my machine (dell optiplex 9010) does not boot unless a keyboard is attached to it (even if that option in bios is disabled - e.g. to error if no keyboard present). So after boot post, the unraid menu does not appear, if a keyboard's missing. Once a keyboard is plugged in, the blue unraid boot menu appears and OS loads fine. The new usb flash was created with uefi support. This was not the case with the previous flash, created about 1.5 or 2 years ago without the usb creator tool, for an older machine (non-uefi). With the old flash, it was booting without a keyboard (and monitor as a matter of fact) successfully. thanks -d

"As I recall, you have to drop the security level on G-mail to be able to send email from Unraid using it. " you can generate a password in gmail, for 3rd party applications like unraid, and use that.

can you associate the frequent freezes (e.g. daily) with high network activity? do you see many errors in the dashboard for the network? i had an issue with an on-board NIC (marvell chipset) when transferring high amount of data to the unraid tower. Freezing even in 1-2 hours, after starting a transfer of files (few hundred GB). Only hard reset was possible. This was a somehow an unnoticeable problem during the previous year, when i did not transfer so many files at once. I ended up buying a separate pcie NIC card from intel and problem solved.

not sure, but i would start sharing the diagnostics and a bit of background. for example, only this distro having issue? first time creating a VM and encountering this issue? passingthrough anything to that VM? have you tried with both seabios and ovmf? can you try selecting different options for the VNC?

thanks @itimpi, i will try this and update on the df results tonight. i will also try backing up config and recreating the usb stick.

hi, I am experiencing several issues after a restart of tower. Server is starting, i can login with root via console, but nothing else is accessible/starting (web interface, vm's or dockers). As I logged in to terminal via console, i could see this email notification: root : unable to stat /etc/sudoers : Permission denied ; TTY=unknown ; PWD=/ ; USER=root ; I tried chkdsk in windows on flash drive, no issues found. After plugging back the flash drive and started server again, issue with the sudoers disappeared. However any command i run (e.g. shutdown) i get error like /sbin/init cannot execute ls -ld /sbin/init tells me that the file is missing execute permissions (compared to my other tower, should have 755) -rw------- root root [...] /sbin/init The other files in /sbin/ seem to have proper executable permissions. If i change init to 755, i can execute the shutdown, but on restart, the init is again missing execute permissions. Tried restarting in gui mode, but the web admin console is not accessible and the firefox browser asking me to restart the browser (restart required). Tried that, but same issue... I also tried to start the unraid in gui without plugins, same behavior. The initial restart of the tower was due to ram upgrade (extra sticks), but i checked the ram with memtest and ram is ok. Also reverted now to the initial ram sticks, just to rule out the ram as the culprit, and same issue occurs. Not sure what should i try next... Running out of options. attaching also the diagnostics: towerq77-diagnostics-20190409-0024.zip kindly please suggest thanks a lot! -d

hello Anyone facing VM initialization issues after upgrade from 6.5.3 to 6.6.0 / 6.6.1 ? My vm's are not starting up. in the boot log of vm's i get errors like this one: Begin: Running /scripts/local-block ... mdadm: CREATE group disk not found Also i saw in another vm, an error like: Guest has not initialized the display (yet) (screenshots attached) This is caused by 6.6.0/6.6.1 since i can revert to 6.5.3 and the issue gets solved. No GPU passthrough. I could not find any similar error in the forum. Thanks, -d

hi, try the recommendations from the cpu pinning sticky thread... also try the tweaks plugin and reduce the cache values from the default ones (you could make them half if you have more than 16GB RAM on the host) -d

hi, i bought a pcie riser x1 and moved the usb pcie card from the x16 slot (the one receiving lanes from CPU) to a x1 pcie slot (the small slot under my primary 2-slot wide gpu, closest to the CPU). Now after this change, the following happens: 1) no more such errors as reported in this post on the guest VM's that have the pcie usb card passed though. 2) i can passthrough this usb pcie card to my Windows 10 VM (in the past it was not possible, the windows vm was not initiating, but it was working only in Linux VM's) 3) my windows 10 VM can start with more than 4 cpu's allocated (in the past allocating more than 4 would fail to load the windows 10 VM) - i tried now with 3:2 and 4:2 and it's working fine my understanding is that some pcie slots are using the PCIe lanes from CPU while other slots (x4, x1) from the motherboard chipset. due to my case and motherboards space constraints, i initially placed this usb pcie card in the x16 slot that usually is for dual sli. And although it was having different iommu group from the primary GPU, somehow it was causing these issues. Now i placed my 2 GPU's in the apropriate x16 slots and took away this usb pcie card with the help of the x1 riser. Passthrough of the 2 GPUs is fine and no issues encountered so far. -d

Hi, i encountered this issue when passing through a usb pcie controller to the VM's https://www.amazon.co.uk/gp/product/B00JEVLEFQ the VM's start showing this message, for various ID's (10, 20, 30, 21, 31), 5 minutes after VM started. Removed the passthrough of this card from the vm definition, and message disappeared. i will update if removing the usb devices from the pcie usb controller card is helping... -d

thanks gridrunner, will for sure try at least the WOL option.

coming back to the solus budgie issue. so i installed budgie by allocating cpu0 only. did the installation of the OS, upgraded all the available packages then installed nvidia drivers. shut down the machine, allocated 4 cpus (HT pairs 2:2) and restarted. i could login without issue.

i specified the updated iso in the virtio definition of my windows 10 vm. then booted the VM, and executed the iso drivers (4 in total) as recommended for the installation of windows wm. updated also the agent... not sure what's the difference

i figured out some things by now: 1) i gave up on solus-budgie (removed vm from disk) only to find out later that this issue could be caused by multiple cpu allocation. somebody faced similar issue, see the video and last post in this thread here: https://solus-project.com/forums/viewtopic.php?f=4&t=2784&p=13737&hilit=login+fails#p13737 i cannot validate if this solves the issue since i dont have the VM anymore; will try to reinstall later when i have the time. 2) although i reported in my previous post that solus-mate is also problematic, i found out today that it's working, when i tried again... maybe a restart of entire unraid solved it, not sure... hope this helps somebody with similar issues... -d

@hblockx - some motherboards allow selection of primary GPU, from a bios option. Some add this option only in newer versions of the bios. Mine does not (asus x99-m ws) yet and as a result, the slot 1 card is used to output the boot vga, and this is the card where unraid console is displayed. Once i start a VM using this primary card, the console output is taken for displaying the video output of that VM. And it's never returned back to unraid, even if VM stopped, until the unraid gets restarted.

@gridrunner - thank you for the awesome tutorials @rahool - i assume your friend has unraid already (or similar meanings to dump), so yes... The rom is specific to the GPU model/vendor, so it's independent of your/your friend's PC. No harm, it will either not work to pass through the GPU, or will not display the video output [properly], or worst case will freeze the unraid box and you'll probably need to powercycle/reset it (e.g. power your PC down, then power it up). My suggestion is to try first what i dumped, before attempting to do it yourself... Just so that you know, my card is the mini version (exact item model number ZT-P10610A-10L) and based on your SFF intention i assume this is the one you want. https://www.newegg.com/Product/Product.aspx?Item=N82E16814500405&cm_re=zotac_1060_mini_3g-_-14-500-405-_-Product Saying this, because there are other 3gb versions available, like AMP (at least i see this model in europe market), but who knows, probably they have same rom... -d

rahool, nobody confirmed so far that the dump for zotac 1060 3g mini works for them. lack of evidence does not means it's not working, it's just that probably nobody tried it yet, or bothered to reply it's fine. gridrunner, here's is the rom for zotac 1050ti oc 4g (https://www.newegg.com/Product/Product.aspx?Item=N82E16814500410&cm_re=zotac_1050ti_4g_oc-_-14-500-410-_-Product) http://www.filedropper.com/zotac1050tioc4g -d

another issue that I found, but not sure if it's related to this version, maybe somebody can replicate this issue, it;s simple... you cannot edit the vdisk size if by chance you forget to define it (it will default to 512B) create VM from template. Forget to define the vdisk size. try to install the OS and fail of course due to disk space (this step may not be required) then attempt to increase the disk space: edit the textbox (e.g. 20GB), save. The page will refresh with old value, so you cannot enlarge the allocated disk space. this is with Chrome latest version (not sure if browser matters). sorry if this is old issue and i just discovered it. just ignore / remove this post...

hi guys, since upgrade to 6.3.1 and 6.3.2, i had issues with my win10 VM not bootting up consistently. Sometimes it would work, but on many occasions, it would appears as freezing the unraid while booting that VM... i thought it's because of h/w changes, i added extra usb pcie card and changed 2nd gpu slot locations. Because the GPU i'm passing through remained constant in slot 1 (providing the rom file) i doubted that this is the reason for my issues. I have found that assigning 3:2 (HT pairs) cpu's to the windows 10 Vm is crashing it, exactly when it should switch from the windows blue logo (windows loading) to the windows login screen. as a matter of fact, the loading screen get's a bit dim, but then everything is freezing. I cannot stop the VM from the dynamix webgui, the windows 10 VM is not loading in the page (since it appears hanged probably). Going through the ssh > virsh destroy vm will stop the hanged win10 VM. I assigned 2:2 cpu's and solved this issue. went back to 3:2 and same issues are back. So had to make it 2:2 (i know, these are the recommendations not to assign more that 2:2 but... it worked with the past unraid versions - 6.2.4 for example). Will also try to see if i can assign 4:2, maybe the odd core number (e.g. 3) is an issue...