June 1, 20215 yr Hey all: Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages. A reboot of your server will at least temporarily solve this problem, but ideally you should seek assistance in the forums and post your So I'm a bit lost as to what the issue is...I have not rebooted and have downloaded logs...but which log do I need to post for hopefully some support from those who know a tonne more than me?! The syslog file is empty, and the syslog1 file has a lot in it but without cutting and pasting the whole thing...what sort of thing should I be looking for for clues? [EDIT: Now posted what I would assume are the issues, please take a look!]: May 27 11:41:27 Tower kernel: eth0: renamed from veth7a23812 May 27 11:41:27 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth09226e7: link becomes ready May 27 11:41:27 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 9583 TIMES] ### May 27 11:41:27 Tower rc.docker: Plex_CF: started succesfully! May 27 11:41:27 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 9366 TIMES] ### May 27 11:41:27 Tower kernel: docker0: port 13(vethbf9300d) entered blocking state May 27 11:41:27 Tower kernel: docker0: port 13(vethbf9300d) entered disabled state May 27 11:41:27 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 2 TIMES] ### May 27 11:41:27 Tower kernel: device vethbf9300d entered promiscuous mode May 27 11:41:27 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 3 TIMES] ### May 27 11:41:27 Tower kernel: docker0: port 13(vethbf9300d) entered blocking state May 27 11:41:27 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] May 27 11:41:27 Tower kernel: docker0: port 13(vethbf9300d) entered forwarding state May 27 11:41:27 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 28065 TIMES] ### May 27 11:41:28 Tower kernel: docker0: port 13(vethbf9300d) entered disabled state May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 3882 TIMES] ### May 27 11:41:28 Tower kernel: eth0: renamed from vethefaa31e May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 839 TIMES] ### May 27 11:41:28 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbf9300d: link becomes ready May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 3 TIMES] ### May 27 11:41:28 Tower kernel: docker0: port 13(vethbf9300d) entered blocking state May 27 11:41:28 Tower kernel: docker0: port 13(vethbf9300d) entered forwarding state May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 7769 TIMES] ### May 27 11:41:28 Tower avahi-daemon[6198]: Joining mDNS multicast group on interface vethcbbffd9.IPv6 with address fe80::60c2:ff:fec6:39e4. May 27 11:41:28 Tower avahi-daemon[6198]: New relevant interface vethcbbffd9.IPv6 for mDNS. May 27 11:41:28 Tower avahi-daemon[6198]: Registering new address record for fe80::60c2:ff:fec6:39e4 on vethcbbffd9.*. May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 7157 TIMES] ### May 27 11:41:28 Tower rc.docker: Sabnzbd_CF: started succesfully! May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 9594 TIMES] ### May 27 11:41:28 Tower kernel: docker0: port 14(veth04c9b4e) entered blocking state May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] May 27 11:41:28 Tower kernel: docker0: port 14(veth04c9b4e) entered disabled state May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 3 TIMES] ### May 27 11:41:28 Tower kernel: device veth04c9b4e entered promiscuous mode May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 5 TIMES] ### May 27 11:41:28 Tower kernel: docker0: port 14(veth04c9b4e) entered blocking state May 27 11:41:28 Tower kernel: docker0: port 14(veth04c9b4e) entered forwarding state May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 33028 TIMES] ### May 27 11:41:28 Tower kernel: eth0: renamed from veth391184a May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 783 TIMES] ### May 27 11:41:28 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth04c9b4e: link becomes ready May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 7223 TIMES] ### May 27 11:41:29 Tower rc.docker: xteve: started succesfully! May 27 11:41:29 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 10747 TIMES] ### May 27 11:41:29 Tower kernel: veth391184a: renamed from eth0 May 27 11:41:29 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 1899 TIMES] ### May 27 11:41:29 Tower kernel: docker0: port 14(veth04c9b4e) entered disabled state May 27 11:41:29 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 10984 TIMES] ### May 27 11:41:29 Tower kernel: docker0: port 14(veth04c9b4e) entered disabled state May 27 11:41:29 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 228 TIMES] ### May 27 11:41:29 Tower kernel: device veth04c9b4e left promiscuous mode May 27 11:41:29 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] May 27 11:41:29 Tower kernel: docker0: port 14(veth04c9b4e) entered disabled state May 27 11:41:29 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 26777 TIMES] ### May 27 11:41:29 Tower avahi-daemon[6198]: Joining mDNS multicast group on interface veth09226e7.IPv6 with address fe80::3426:7cff:fe3b:dd56. May 27 11:41:29 Tower avahi-daemon[6198]: New relevant interface veth09226e7.IPv6 for mDNS. May 27 11:41:29 Tower avahi-daemon[6198]: Registering new address record for fe80::3426:7cff:fe3b:dd56 on veth09226e7.*. May 27 11:41:29 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 12666 TIMES] ### May 27 11:41:29 Tower rc.docker: ZeroTier: started succesfully! May 27 11:41:29 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 3382 TIMES] ### May 27 11:41:29 Tower avahi-daemon[6198]: Joining mDNS multicast group on interface ztbtoxmevv.IPv4 with address 172.25.119.245. May 27 11:41:29 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 151 TIMES] ### May 27 11:41:29 Tower avahi-daemon[6198]: New relevant interface ztbtoxmevv.IPv4 for mDNS. May 27 11:41:29 Tower avahi-daemon[6198]: Registering new address record for 172.25.119.245 on ztbtoxmevv.IPv4. May 27 11:41:29 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 58978 TIMES] ### May 27 11:41:30 Tower avahi-daemon[6198]: Joining mDNS multicast group on interface vethbf9300d.IPv6 with address fe80::9c56:76ff:fecc:3ee7. May 27 11:41:30 Tower avahi-daemon[6198]: New relevant interface vethbf9300d.IPv6 for mDNS. May 27 11:41:30 Tower avahi-daemon[6198]: Registering new address record for fe80::9c56:76ff:fecc:3ee7 on vethbf9300d.*. May 27 11:41:30 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 114184 TIMES] ### May 27 11:41:31 Tower avahi-daemon[6198]: Joining mDNS multicast group on interface ztbtoxmevv.IPv6 with address fe80::188f:e2ff:fe4a:265. May 27 11:41:31 Tower avahi-daemon[6198]: New relevant interface ztbtoxmevv.IPv6 for mDNS. May 27 11:41:31 Tower avahi-daemon[6198]: Registering new address record for fe80::188f:e2ff:fe4a:265 on ztbtoxmevv.*. May 27 11:41:31 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 130499 TIMES] ### May 27 11:41:34 Tower nmbd[6610]: [2021/05/27 11:41:34.119621, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) May 27 11:41:34 Tower nmbd[6610]: ***** May 27 11:41:34 Tower nmbd[6610]: May 27 11:41:34 Tower nmbd[6610]: Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.108 May 27 11:41:34 Tower nmbd[6610]: May 27 11:41:34 Tower nmbd[6610]: ***** May 27 11:41:36 Tower kernel: usb 1-3: reset full-speed USB device number 2 using xhci_hcd May 27 11:41:37 Tower kernel: usb 1-8: reset full-speed USB device number 5 using xhci_hcd May 27 11:41:37 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 630710 TIMES] ### May 27 11:41:50 Tower kernel: vfio-pci 0000:01: Thanks/sorry! Edited June 1, 20215 yr by Lunch
June 1, 20215 yr 1 minute ago, Lunch said: which log do I need to post Tools -> Diagnostics and attach the resulting zip file.
June 1, 20215 yr Author 6 minutes ago, John_M said: Tools -> Diagnostics and attach the resulting zip file. tower-diagnostics-20210601-0953.zip
June 1, 20215 yr Your syslog is being spammed with this message May 27 11:41:28 Tower kernel: vfio-pci 0000:01:00.0: BAR 1: can't reserve [mem 0x90000000-0x9fffffff 64bit pref] ### [PREVIOUS LINE REPEATED 7223 TIMES] ### which is related to your Nvidia graphics card and the fact that you've bound it to the vfio stub driver for passthrough. I don't know the cause but you could try a web search.
June 1, 20215 yr Author 11 minutes ago, John_M said: Do the messages stop when you shut down your Windows 10 VM? To be honest I'm not sure....when I restart the server itself I need to run a script from spaceinvader one that binds it....doesnt always work. But in answer to your question...If I stop the windows VM and then recheck wont the syslog still be full? Can I/do I have to try and delete the log first before doing?
June 1, 20215 yr The easiest thing to try is to reboot the server and start the array but not the VM. Let it run for a while then start the VM, noting the time. Let it run for a short time then shut it down. Then grab diagnostics. I'm just trying to establish whether the error messages are produced continuously, or just when the VM is running. I'm not sure why you have to run a script - does the vfio binding mechanism that's built into Unraid not work or are you trying to do something specific?
June 2, 20215 yr Community Expert Why have you given 90G to docker.img? 20G should be more than enough but you are using nearly twice that. You almost certainly have some docker application misconfigured. The usual reason for writing into docker.img is an application writing to a path that isn't mapped. Linux is case-sensitive, so any path specified in an application must match a container path including upper/lower case.
Archived
This topic is now archived and is closed to further replies.