skumkaninen

My ever so stable unraid server has started doing kernel panics - only change resently is a Nvidia P400 and the drivers installed and used to config plex for transkoding. The crashes dont happen when under load, but can happen in the middle of the night with noone using the server. I know I have a disk 4 with some read errors, I will change it as soon as the server is stable enough for me to do the procedure 🙂 I have attached the complete diag file - I am not skilled enough to read it correctly yet. farmen03-diagnostics-20211126-0823.zip

Hi - my unraid server has stopped assigning ip adresses for new docker install's - the old application I have running can still start using both host and bridge. But new cannot, even if i set custom static ip adress, the port mapping still does not show up. This is from the boot of scrutiny docker app. Listening and serving HTTP on 0.0.0.0:8080 - I have tried what I could think of but really have no clue, I see no errors in any logs that should affect this, so any tips are welcome 🙂 And here - plex works (old app) and the newer Scrutiny does not. Im running a server with one 1GB card in. See below for Any ideas? Thanx

Has anybody got any tips to stop Pihole from having massive impact on my SSD/Cache - I can see from other treads on Reddit that others have the same problem, if I stop the docker with Pihole the problem goes away. But in a month it has written more than 100TB - yes that number is correct. (you can see the number under main - cache - and attributes.) I would understand alot of reads, but more than 300k reads per 24 hours, thats insane. 🙂 Im on the newest build of both unraid and the pihole docker container.

Hi - im new to unraid so pardon me if my question is dumb 🙂 I have a dual nic in my unraid system, one 10Gbit and one 1G - setup with the 10Gbit as eth0 and 1gb as eth1. Is this a bad idea, should I just remove the 1gb link completely? Eth1 says "interface down" even though it is cabled and works. I see these errors in my syslog - and I am worried it will give me problems. Currenly everything seems to be working, docker/vm file hosting working just fine, but I do not like these errors, and I dont quite undertand them. May 4 09:59:19 Farmen03 kernel: br0: port 2(vnet0) entered blocking state May 4 09:59:19 Farmen03 kernel: br0: port 2(vnet0) entered disabled state May 4 09:59:19 Farmen03 kernel: device vnet0 entered promiscuous mode May 4 09:59:19 Farmen03 kernel: br0: port 2(vnet0) entered blocking state May 4 09:59:19 Farmen03 kernel: br0: port 2(vnet0) entered forwarding state Anybody 🙂

Just talked to another user, same problem on his macinabox machine, out of the box without any changes, speed down is ok, speed up is below 1Mb/sek

Hi thanx - I did that allready, I just maybe did not explain that right, but I started with the e1000 - and changed it due to the strange performance, but no change. I have other Windows VM's running and they have no problems.

Great tool - worked like a charm, I have changed the cpu count and menory allocation, and it boots as it should. I have one problem, the netcard is giving me full download speed (500MB/sek) but the upload is all broken at like 0.5 - I have tried what I could think of. My network looks like below. I have tried with both names vmxnet and the other in the guide. Same result. <interface type='bridge'> <mac address='xx:xx:00:d2:xx:25'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='vmxnet3'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface>