klippertyk

I have this motherboard and although it's stable I'm constantly having issues with USB drives and devices with it. I can reboot unraid 3-5 times, all will be fine, on the next reboot, the unraid boot menu comes up then a message like "looking for sda" appears, the drive times out, and i'm forced to restart, at this point, the USB drive is not detected until I pull the power cable and fully restart the server. NONE of the USB2 ports seem to work, I've tried my Unraid USB and a Samsung T5 SSD and some tiny sandisk thing. other than that I quite like the board

Thank you - just folllowed this and it worked beautifully. You're awesome for spending the time writing that up for us. Thank you very much indeed - personally I'd have been completely stuck. Again, THANK YOU!

woo woo woo!! It's back. Thank you again @JorgeB!!

Thank you very much @JorgeB i’ll try it and report back. Could you let me know how you discovered that? I’m keen to learn - I have an IT background just not in Linux much.

ok so something strange happened just now. I've had no vms for a while, but just turned the service back on, I created a new vm and selected the windows 11 iso to start the install. Turned on the vm and an old Windows 11 vm immediately popped up in the vnc window - that wasn't even listed. I checked the domains folder and found only the windows 11 folder, I'm wondering if something has happened to the opnsense image not being deleted properly in Unraid or something, but saying that, it wouldn't cause Eth1 doesn't exist on Unraid boot up would it? I'm really confused, I feel like doing a factory reset would probably solve this, but setting all this up took more time than I currently have.

Hi All, I have an issue with the 2nd 2.5GB NIC on my server. The story goes... I've been using Unraid for about 2 years. When I first set it up I flirted with the idea of running opnsense in a vm as my router and abandoned the idea shortly after reading up on the forbidden router. I did however assign a physical NIC to the vm when I was playing about with it. Fast forward 18 months and a couple of Unraid updates later, I deleted the VM. I then had issues upgrading from 6.12.13 to 6.12.14 when upgrading the server I was getting eth0 interface is down showing -1Mbps, half duplex, mtg 1500 - likely unrelated to this issue. I downgraded back to 6.12.13 and everything went back to normal. I recently upgraded to 7.0.1 (love it btw) but I can't seem to get the 2nd NIC to show up anywhere. When I watch the OS loading log I briefly see an entry "Eth1 doesn't exist" Really don't know how to attack this one, I've attached diagnostics. Would appreciate someone more knowledgeable giving me a hand, I would like to get this working again for a future project. I suspect it might have been caused by assigning the nic to the VM and deleting the vm before unassigning it? A wild guess.. thank you.

I just collected diagnostic logs and reverted back to 6.12.13 and eth0 is back up and running. Phew. happy to share my diagnostic log if it'll help or are people already aware of this issue?

HI All, Server working fine until I decided to update to 6.12.14 today - now my eth0 interface is down showing -1Mbps, half duplex, mtg 1500. I have an Asus W680 IPMI motherboard with 2x 2.5g intel nics, and fortunately I got eth1 up and running (can anyone tell me how to quickly change my docker network config to use eth1 while I troubleshoot this please?) but can't get eth0 to come back at all. Everything was 100% ok prior to the update (I'm not using macvlan) Help! anyway to reset the Nic?

for others... https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications I am new to this, so any advice apprciated - pre-req checks or gotchas would be useful.

I'm having the same issue - my docker.img is 42.9gb. I've had this error for a while actually and only got around to invesitgating the problem recently. Can I please ask - are there updated links for your articles above? They appear to be out of date. My primary concern is losing my config, my containers took hours to setup - i'm curious as to what is writing to the docker.img though - any tips to investigate that?

I don't think this is an Unraid issue, but as I'm using it on this board, I thought it worth posting. I updated the BIOS to 2802 today from 2305 as part of some prep to update from 6.11.5. When I do a shutdown via unraid, on the next power on, all the drives are no longer detected in POST. I have to powerdown again via IPMI then everything behaves itself. Warm restarts are ok. I'm posting just incase anyone uses this board and has the same issue and if anyone has any ideas why this might be happening (ACPI settings?) as the update blew away my BIOS config so I may have forgotten to set something correctly. This is repeatable. Normal.... Not normal...

just signed up to mullvad but the link in 1st post (and their site) I get a 404. Sooo.... I'm a bit stuck? okaaay had to embarass myself in public to work it out. you have to click account on the top right...

still beavering away at this and my previous comment jumped the gun a bit and didn't solve all my issues. I'm having real trouble getting containers to communicate with each other depending if they are setup to use gluetun or not. I thought I found the answer here which sounds ideal, but I'm on a lengthy NordVPN subscription. At this point I'm prepared to sign up with another provider just to get the VPN tunnel setup but not sure who to go with (I'm based in the UK)

in an effort to fix the prowlarr issue myself, I watched this vid and thought it was excellent. i realised I needed to specify the bridge ip and volia! sorted. Im really interested in try macvlan now though, he's right, the networking in dockers is so cool

Hello! TL:DR - 1. Prowlarr on Gluetun won't connect to other containers not using gluetun's container connection. 2. how to get vpn working for containers generally. I've been scratching my head a little. I've setup the gluetunvpn container to securely provide vpn tunnels to containers. I reviewed spaceinvaders guide to sharing that connection with other containers, and all appeared to be working quite well, I linked jackett via gluetun to sonarr (bridge) and things were going well and the idea was proven. Until I decided to switch from jackett to prowlarr, I need to run prowlarr using gluetun's connection as I did with jackett but when I do, I cannot get it to communicate to sonarr or anything else, switching sonarr over to use gluntun's connection works fine, until I change it back to the container bridge again. Basically I cannot connect to any other containers with prowlarr when it's on gluetun and they are not. browsing several forums, I get the impression this is an "issue" with prowlarr, but I don't understand enough to fix it. Anyone been able to get prowlarr to connect with sonarr or qbittorrent without them also being on a gluetun connection? Which leads me into point 2. My router isn't powerful enough to have an openvpn connection setup on it, else I would do that for all connections and not use gluetun at all, so my question here is, how are you guys securing your containers over vpn (if different to the above) I plan to look at nginxproxymanager next to see what that offers.