[unRaid (6.9.2) crashes periodically]

I tried disabling C-State in my BIOS, but it still crashed last week.

 

Can someone provide any suggestions on where to look at? I'm at a total loss here.

 

If I'm missing anything, let me know and I'll try to provide more information.

[unRaid (6.9.2) crashes periodically]

Would anyone be able to help with this?

[unRaid (6.9.2) crashes periodically]

My unraid has been crashing every once in a while for quite some time now. And when it does, it takes my entire home network down with it.

 

Back story: I always thought it was my ethernet switch that's failing, since each time unraid crashes, nothing connected to the switch is accessible, but everything else on my network is. I've been going back and forth with the manufacturer, where they were kind enough to send me 2 new units to try out, but after a while, it is still happening. Thinking the switch was a piece of trash, I switched to another manufacturer's switch, but odd enough, same thing is still happening.

 

So I decided to dig around my unraid a bit more by syncing the syslog to my USB. It crashed again last night, but this time it didn't take out my whole network, because I only have 1 ethernet connected to it at this time (probably crashing because of link aggregation).

 

Below is what I caught in the syslog, and also attached diagnostics of my server.

 

Any help would be greatly appreciated, thanks!

 

Jan  2 22:06:18 <redacted> kernel: BUG: kernel NULL pointer dereference, address: 0000000000000030
Jan  2 22:06:18 <redacted> kernel: #PF: supervisor write access in kernel mode
Jan  2 22:06:18 <redacted> kernel: #PF: error_code(0x0002) - not-present page
Jan  2 22:06:18 <redacted> kernel: PGD 0 P4D 0 
Jan  2 22:06:18 <redacted> kernel: Oops: 0002 [#1] SMP NOPTI
Jan  2 22:06:18 <redacted> kernel: CPU: 8 PID: 9758 Comm: nginx Tainted: G        W         5.10.28-Unraid #1
Jan  2 22:06:18 <redacted> kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570D4I-2T, BIOS P2.10 12/28/2020
Jan  2 22:06:18 <redacted> kernel: RIP: 0010:down_write+0x15/0x36
Jan  2 22:06:18 <redacted> kernel: Code: f0 ff ff 19 c0 f7 d0 83 e0 fc eb 07 e8 78 b5 9c ff 31 c0 5d c3 51 48 89 3c 24 e8 21 ea ff ff 31 c0 48 8b 3c 24 ba 01 00 00 00 <f0> 48 0f b1 17 74 0b 5a be 02 00 00 00 e9 24 b9 9c ff 65 48 8b 04
Jan  2 22:06:18 <redacted> kernel: RSP: 0018:ffffc90002627d80 EFLAGS: 00010246
Jan  2 22:06:18 <redacted> kernel: RAX: 0000000000000000 RBX: ffff8881517faa80 RCX: ffff888149d0d259
Jan  2 22:06:18 <redacted> kernel: RDX: 0000000000000001 RSI: 00001500e0749000 RDI: 0000000000000030
Jan  2 22:06:18 <redacted> kernel: RBP: ffff8881517faa80 R08: 00001500e5d1c000 R09: 0000000000000000
Jan  2 22:06:18 <redacted> kernel: R10: ffff88816e435f18 R11: ffff88816e435f18 R12: ffff88815168e568
Jan  2 22:06:18 <redacted> kernel: R13: 0000000000000030 R14: 0000000000000000 R15: ffff8881517fb380
Jan  2 22:06:18 <redacted> kernel: FS:  0000000000000000(0000) GS:ffff88880ea00000(0000) knlGS:0000000000000000
Jan  2 22:06:18 <redacted> kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan  2 22:06:18 <redacted> kernel: CR2: 0000000000000030 CR3: 00000001da92a000 CR4: 0000000000350ee0
Jan  2 22:06:18 <redacted> kernel: Call Trace:
Jan  2 22:06:18 <redacted> kernel: unlink_file_vma+0x2a/0x4f
Jan  2 22:06:18 <redacted> kernel: free_pgtables+0x89/0xbb
Jan  2 22:06:18 <redacted> kernel: exit_mmap+0xc4/0x155
Jan  2 22:06:18 <redacted> kernel: __mmput+0x3b/0xcf
Jan  2 22:06:18 <redacted> kernel: do_exit+0x3b4/0x8eb
Jan  2 22:06:18 <redacted> kernel: do_group_exit+0x8e/0x8e
Jan  2 22:06:18 <redacted> kernel: __x64_sys_exit_group+0xf/0xf
Jan  2 22:06:18 <redacted> kernel: do_syscall_64+0x5d/0x6a
Jan  2 22:06:18 <redacted> kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan  2 22:06:18 <redacted> kernel: RIP: 0033:0x1500e5e139d6
Jan  2 22:06:18 <redacted> kernel: Code: Unable to access opcode bytes at RIP 0x1500e5e139ac.
Jan  2 22:06:18 <redacted> kernel: RSP: 002b:00007ffd577488f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
Jan  2 22:06:18 <redacted> kernel: RAX: ffffffffffffffda RBX: 00001500e5f04760 RCX: 00001500e5e139d6
Jan  2 22:06:18 <redacted> kernel: RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
Jan  2 22:06:18 <redacted> kernel: RBP: 0000000000000000 R08: 00000000000000e7 R09: ffffffffffffff60
Jan  2 22:06:18 <redacted> kernel: R10: 00007ffd5774876a R11: 0000000000000246 R12: 00001500e5f04760
Jan  2 22:06:18 <redacted> kernel: R13: 0000000000000002 R14: 00001500e5f0d428 R15: 0000000000000000
Jan  2 22:06:18 <redacted> kernel: Modules linked in: xt_mark xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net vhost vhost_iotlb tap nft_compat nft_counter nf_tables tun macvlan veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfs md_mod iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables ixgbe mdio ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm wmi_bmof crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd ccp wmi ahci i2c_piix4 acpi_ipmi input_leds i2c_core libahci led_class glue_helper k10temp rapl button ipmi_si acpi_cpufreq [last unloaded: mdio]
Jan  2 22:06:18 <redacted> kernel: CR2: 0000000000000030
Jan  2 22:06:18 <redacted> kernel: ---[ end trace 9343108eacf12b41 ]---
Jan  2 22:06:18 <redacted> kernel: RIP: 0010:down_write+0x15/0x36
Jan  2 22:06:18 <redacted> kernel: Code: f0 ff ff 19 c0 f7 d0 83 e0 fc eb 07 e8 78 b5 9c ff 31 c0 5d c3 51 48 89 3c 24 e8 21 ea ff ff 31 c0 48 8b 3c 24 ba 01 00 00 00 <f0> 48 0f b1 17 74 0b 5a be 02 00 00 00 e9 24 b9 9c ff 65 48 8b 04
Jan  2 22:06:18 <redacted> kernel: RSP: 0018:ffffc90002627d80 EFLAGS: 00010246
Jan  2 22:06:18 <redacted> kernel: RAX: 0000000000000000 RBX: ffff8881517faa80 RCX: ffff888149d0d259
Jan  2 22:06:18 <redacted> kernel: RDX: 0000000000000001 RSI: 00001500e0749000 RDI: 0000000000000030
Jan  2 22:06:18 <redacted> kernel: RBP: ffff8881517faa80 R08: 00001500e5d1c000 R09: 0000000000000000
Jan  2 22:06:18 <redacted> kernel: R10: ffff88816e435f18 R11: ffff88816e435f18 R12: ffff88815168e568
Jan  2 22:06:18 <redacted> kernel: R13: 0000000000000030 R14: 0000000000000000 R15: ffff8881517fb380
Jan  2 22:06:18 <redacted> kernel: FS:  0000000000000000(0000) GS:ffff88880ea00000(0000) knlGS:0000000000000000
Jan  2 22:06:18 <redacted> kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan  2 22:06:18 <redacted> kernel: CR2: 0000000000000030 CR3: 00000001da92a000 CR4: 0000000000350ee0
Jan  2 22:06:18 <redacted> kernel: Fixing recursive fault but reboot is needed!

 

diagnostics-20220103-1148.zip

[Docker slow after upgrading to 6.9]

sorry for the late reply. attached is my diagnostics. let me know if you're able to find anything that's causing the slowness.

 

<attachment removed>

 

EDIT: I decided to recreate my docker img (in Settings > Docker > Enable Docker > No, Apply, then flip it back to Yes again with defaults), and after recreating it, docker is quick again!

 

Just wanted to mention that here in case someone runs into the same issue.

 

 

[Docker slow after upgrading to 6.9]

how do I get diagnostics from docker?

[Docker slow after upgrading to 6.9]

I recently upgraded my unraid server, and the first thing I noticed was that all my docker commands are responding VERY slowly. It takes nearly 30 seconds now to start up a new container that I already have the image of, and a docker pull can take almost 5 minutes depending on how many steps it has.

 

Did anyone notice this after the upgrade? If so, is there any way to fix this? Or steps to figure out why its so slow?

 

Edit: Once the container is started though, the container itself is fine. Its only when creating a new container, pulling a new image, building a new image, or stopping a container that's slow.

[[Support] SpaceinvaderOne - Macinabox]

Does the new version of macinabox support USB passthrough of an iphone? Not the full USB controller, but just the iphone.

[[Support] SpaceinvaderOne - Macinabox]

15 hours ago, mSedek said:

why would you pass an iphone?? pass the whole usb controller and then you can hotswap ANY device as like you have a bare metal system

All my usb ports are under one iommu group. I don't know what will happen if I pass the whole thing to the VM, since that would also include the unraid usb drive.

[[Support] SpaceinvaderOne - Macinabox]

Has anyone successfully passed through an iPhone to the macinabox vm?

 

I was able to pass through a USB thumb drive after lots of research (had to delete the <address> tag), but I could not get the vm to see my iphone using the same method.

 

Here is my xml:

 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>MacinaboxCatalina</name>
  <uuid>88c6efc0-f46e-49d2-a978-4f216945c255</uuid>
  <description>MacOS Catalina</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="MacOS" icon="/mnt/user/domains/MacinaboxCatalina/icon/catalina.png" os="Catalina"/>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='4'/>
    <vcpupin vcpu='1' cpuset='12'/>
    <vcpupin vcpu='2' cpuset='5'/>
    <vcpupin vcpu='3' cpuset='13'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-3.1'>hvm</type>
    <loader readonly='yes' type='pflash'>/mnt/user/domains/MacinaboxCatalina/ovmf/OVMF_CODE.fd</loader>
    <nvram>/mnt/user/domains/MacinaboxCatalina/ovmf/OVMF_VARS.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='2' threads='2'/>
  </cpu>
  <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/user/domains/MacinaboxCatalina/Clover.qcow2'/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/Catalina-install.img'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/macos_disk.img'/>
      <target dev='hde' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='4'/>
    </disk>
    <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>
    <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='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:3c:2b:8d'/>
      <source bridge='br0'/>
      <model type='vmxnet3'/>
      <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'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x05ac'/>
        <product id='0x12a8'/>
      </source>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </memballoon>
  </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=???????????????????????????(c)AppleComputerInc'/>
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/>
  </qemu:commandline>
</domain>
 

[SSD Cache available at basic?]

So to clarify, does that mean on a Basic license, the cache drive is considered one of the 6 drives? If I have this set up:

 

1x Parity

5x HDD

1x SSD Cache

 

I would need at least a Plus license?