1812

Members
  • Posts

    2625
  • Joined

  • Last visited

  • Days Won

    16

Everything posted by 1812

  1. Worst thing: system instability, dataloss if you're writing to the array when it occurs but with that said, I've run most of my servers that way for several years and it hasn't caused an issue (knock on wood)
  2. it's probably not the card since mine is in slot 4 of 6(counting pci gen 1 slot at the bottom) in the z420. my money says HP issue considering you have still have the memory map issue in your logs. look in the bios and make sure all network boot is disabled and that if you have pcie options, they are set to specifics and not auto (I don't remember what the bios options are for that gen, but I have a z400 collecting dust that if needed I can pull and take a look at since they should be similar enough.) there's a plugin to disable mitigations and keep that performance.
  3. Jan 18 21:50:43 Procyon kernel: Call Trace: Jan 18 21:50:43 Procyon kernel: ? efx_pci_probe+0x6ae/0x81d [sfc] Jan 18 21:50:43 Procyon kernel: ? pci_bus_read_config_word+0x44/0x66 Jan 18 21:50:43 Procyon kernel: efx_pci_probe+0x6ae/0x81d [sfc] Jan 18 21:50:43 Procyon kernel: local_pci_probe+0x39/0x7a Jan 18 21:50:43 Procyon kernel: pci_device_probe+0x13f/0x199 Jan 18 21:50:43 Procyon kernel: really_probe+0x13d/0x288 Jan 18 21:50:43 Procyon kernel: driver_probe_device+0x9c/0xd1 Jan 18 21:50:43 Procyon kernel: __driver_attach+0x89/0xb9 Jan 18 21:50:43 Procyon kernel: ? driver_probe_device+0xd1/0xd1 Jan 18 21:50:43 Procyon kernel: bus_for_each_dev+0x70/0xa6 Jan 18 21:50:43 Procyon kernel: bus_add_driver+0xe1/0x1c6 Jan 18 21:50:43 Procyon kernel: driver_register+0x99/0xcf Jan 18 21:50:43 Procyon kernel: ? 0xffffffffa014d000 Jan 18 21:50:43 Procyon kernel: efx_init_module+0x7a/0x1000 [sfc] Jan 18 21:50:43 Procyon kernel: do_one_initcall+0x71/0x147 Jan 18 21:50:43 Procyon kernel: ? _cond_resched+0x1b/0x1e Jan 18 21:50:43 Procyon kernel: ? kmem_cache_alloc+0x30/0xeb Jan 18 21:50:43 Procyon kernel: do_init_module+0x51/0x1c7 Jan 18 21:50:43 Procyon kernel: load_module+0x1890/0x1ec2 Jan 18 21:50:43 Procyon kernel: ? __insert_vmap_area+0x6c/0xb0 Jan 18 21:50:43 Procyon kernel: ? __se_sys_init_module+0xcf/0x10a Jan 18 21:50:43 Procyon kernel: __se_sys_init_module+0xcf/0x10a Jan 18 21:50:43 Procyon kernel: do_syscall_64+0x57/0xf2 Jan 18 21:50:43 Procyon kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jan 18 21:50:43 Procyon kernel: RIP: 0033:0x14fdb343213a Jan 18 21:50:43 Procyon kernel: Code: 48 8b 0d 59 7d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 26 7d 0c 00 f7 d8 64 89 01 48 Jan 18 21:50:43 Procyon kernel: RSP: 002b:00007ffe0a48c8d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af Jan 18 21:50:43 Procyon kernel: RAX: ffffffffffffffda RBX: 000000000065de00 RCX: 000014fdb343213a Jan 18 21:50:43 Procyon kernel: RDX: 000014fdb351184d RSI: 0000000000072d50 RDI: 0000000000e95000 Jan 18 21:50:43 Procyon kernel: RBP: 000014fdb351184d R08: 000000000064701a R09: 0000000000000006 Jan 18 21:50:43 Procyon kernel: R10: 0000000000647010 R11: 0000000000000246 R12: 0000000000e95000 Jan 18 21:50:43 Procyon kernel: R13: 000000000067b6b0 R14: 0000000000020000 R15: 000000000065de00 Jan 18 21:50:43 Procyon kernel: ---[ end trace 87b5401780146dfe ]--- Jan 18 21:50:43 Procyon kernel: sfc 0000:0f:00.0 (unnamed net_device) (uninitialized): could not map memory BAR at 0+ff0800 Jan 18 21:50:43 Procyon kernel: sfc: probe of 0000:0f:00.0 failed with error -12 Jan 18 21:50:43 Procyon kernel: kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround Jan 18 21:50:43 Procyon kernel: sfc 0000:0f:00.1 (unnamed net_device) (uninitialized): Solarflare NIC detected Jan 18 21:50:43 Procyon kernel: sfc 0000:0f:00.1 (unnamed net_device) (uninitialized): Part Number : SFN5122F Jan 18 21:50:43 Procyon kernel: sfc 0000:0f:00.1 (unnamed net_device) (uninitialized): could not map memory BAR at 0+ff0800 Jan 18 21:50:43 Procyon kernel: sfc: probe of 0000:0f:00.1 failed with error -12 the card isn't getting assigned memory. Jan 18 21:50:43 Procyon kernel: DMI: Hewlett-Packard HP Z600 Workstation/0AE8h, BIOS 786G4 v01.17 08/19/2009 I'd start by updating your bios first, as HP may have fixed this issue.
  4. make a copy of the config/network.cfg file from the flash drive to your desktop (as a backup), then delete the one on the flash drive and reboot the server. this will force new settings and maybe it will pickup the solar flare card. if not, I'll dig through your diags a bit more looking at your logs, this prob won't help.
  5. I run a SFN5122F in a z420 and actually split the ports: 1 for Unraid and 1 for a VM. so it works. post a screenshot of the following section in the network settings:
  6. I'll also try the 2 hp workstations I have and see what happens just for "fun." I never use GUI mode because I don't have a use case for it, but now I'm very interested!
  7. (I'm reading through this pre-coffee), all very interesting because I run 2 ml30 g9's without issue but have never booted them into GUI mode. I will try it this weekend when one of them is not in use and try to confirm the behavior though I'm sure it will occur. I vaguely recall getting intermittent errors related to video output on one or two previous HP servers I've used Unraid on, but. I don't remember which ones specifically. I don't recall it causing shutdown issues either, but that doesn't mean its not a problem. iLo seems to rear an issue every now and then on Unraid but usually nothing this drastic.
  8. I bought an isobox studio 20u used on eBay about a year ago and love it for all my stuff. Recently replaced all the fans with Noctua NF-F12 iPPC 3000 and a different fan controller. I keep 1 server plus a workstation computer, jbod enclosure, and a monster 220v backup in it and run about 8-10f more than ambient. The low hum of the fans is glorious vs the whine of the electronics. https://www.soundconstructionsupply.com/isobox-studio/
  9. I've used h220 cards for years and they have no issues. Running 2 right now.
  10. its below. there is some extra lines in it for trim to work <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MacinaboxCatalina</name> <uuid>8049a941-a0bd-4a55f-a179-35056162d3a21</uuid> <description>MacOS Catalina</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="catalina.png" os="Catalina"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <iothreads>1</iothreads> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='10'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='11'/> <emulatorpin cpuset='1'/> <iothreadpin iothread='1' cpuset='1'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/disks/Samsung_SSD_840_EVO_250GB_S1DBNSCFA55e357V/MacinaboxCatalina/ovmf/OVMF_CODE.fd</loader> <nvram>/mnt/disks/Samsung_SSD_840_EVO_250GB_S1DBNSCFA4f5157V/MacinaboxCatalina/ovmf/OVMF_VARS.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'/> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/disks/Samsung_SSD_840_EVO_250GB_S1DBNSCFA576357V//MacinaboxCatalina/Clover.qcow2'/> <target dev='hda' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none' io='native' discard='unmap'/> <source file='/mnt/disks/Samsung_SSD_840_EVO_250GB_S1DBNSCFA889157V/MacinaboxCatalina/macos_disk.img'/> <target dev='hdb' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:45:01:4b:ac:f8'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <rom file='/mnt/cache/domains/gigabyte590.dump'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=cashruleseverythingaroundmeCREAM'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='IvyBridge,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check,fma,avx,avx2,bmi1,bmi2'/> <qemu:arg value='-set'/> <qemu:arg value='device.sata0-0-1.rotation_rate=1'/> </qemu:commandline> </domain>
  11. each one of them are like cherished children. so special.... until the next comes along....
  12. I just put in an rx 590 8gb gigabyte card in a Catalina vm about 2 weeks ago. Was on sale! Doesn't have the reset bug as it is switched between Catalina and win 10 every few days without rebooting the server.
  13. It’s a toss up between what I like most: 1: LimeTech is responsive to the community 2: the community is a fantastic support apparatus the thing I’d like to see added actually demonstrates the first point because it is going to be added: multiple cache polls! (Maybe I should say all ssd array instead?)
  14. I had this issue and resolved it by uninstalling the Nvidia driver, shutting down the vm, and then only passing through the video only, no audio, from the card. You may have to use acs functions to split your card into separate iommu groups. Upon restart, it works as expected minus GPU sound, but I'm using something else for that anyways so it wasn't a big deal. there may be a better way to resolve this though.
  15. your loader and nvram files are wrong. they changed when you changed ram amounts. they should point to the files in the macinabox folder.
  16. I think that use to be correct, but plex has gotten better at reading a RAM disk size. I use to use one exclusively until I started using the dvr, which needs a scratch disk the size of the recording (which is big for football games.) sometimes when setting up a RAM disk for the first time, plex may crash the stream filling it up, but then never exceeded it again. Sometimes it reads the size right the first time and there are no problems.
  17. something in your setup isn't configured correctly is my guess. I use utm 9 and had to watch a couple videos to get all my traffic setup properly and have to constantly remember that the https port is 4444.... did you setup your traffic routing to allow wan access to anywhere, including internet traffic? there are so many variables which is why sophos, while a great product, is also a pita.
  18. Did you setup sophos correctly? By default it doesn’t respond to pings and doesn’t allow any traffic at all. also set your gateway as the sophos device
  19. you are probably using vmxnet3. change to e1000-82545em
  20. htop shows: edit: figured it out..... I have 3 time machine backups running to this server.....
  21. changed the computer out from a z400 to a z440 and problem persists even after upgrading to 6.8.0 stable. Problem does not occur on the other 2 servers in my house, including a z420.
  22. check if its changing your loader and nvram location to something not within the macinabox folder. I've noticed this behavior a few times causing what you describe. also make sure that you remove topology when you change core count (covered in the video)
  23. No worries, I’m still twiddling my thumbs considering an AMD card for Catalina, and all the other fun that ensues by updating!