kingfetty

Members
  • Posts

    85
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

kingfetty's Achievements

Rookie

Rookie (2/14)

5

Reputation

  1. In the same boat here, I'm just awaiting someone to post a solution. Been fiddling with it for a couple weeks now with zero luck. -edit managed to capture a photo quick enough to see an error:
  2. Also have an IP assigned to a docker on a br0 port and it's causing crashes. I've been troubleshooting this for months and now found this and was able to stop the random crashes.
  3. It's gotta be software at this point. I've had this issue since 6.6.7 and was convinced it was hardware. Alas, I have replaced every single piece of hardware and still get kernel panic NF_NAT IPTables about once a week. I'm not sure where to go from here. I don't have a log file of the kernel panic as once it panics and you reboot, the logs are gone. I'm attaching a diagnostic file, and will await instruction on what to do next. tower-diagnostics-20190705-0148.zip
  4. Bug Description: When using quotes " in the value of a variable for a docker container the UI does not parse the line correctly when reading the xml file. How to reproduce: Create a docker and add a variable called test. Set the value of the variable to something that contains quotes. (ex: this"is"my value ). Then edit the container configuration. Upon editing the value will be depicted as truncate where the quotes began. (ex: this ) Expected results: Quotes should be parsed and represented html safe encoding " Actual results: Quotes are not parsed correctly. Other information: Examining the xml file shows that it is stored correctly the first time it is entered but not parsed correctly when editing.
  5. I too would like this to work. Currently I have a script that I run each time I reboot the box that creates my networks. I have to do this manually though.
  6. I've created some custom docker network entries. How does one persist them between unraid restarts?
  7. Help, Fresh install of the docker. Made sure the /config mapping is correct, made sure the UID and GID map to correct ID numbers from unraid. On startup the MongoDB server won't run, it crashes with a fatal assertion: LogFile::synchronousAppend failed with 8192 bytes unwritten out of 8192 bytes; b=0x3786000 errno:22 Invalid argument 2017-12-25T20:30:41.286-0600 [initandlisten] Fatal Assertion 13515 2017-12-25T20:30:41.291-0600 [initandlisten] 0xedb3e9 0xe6fb3f 0xe4a1c1 0xe7039b 0x8869fa 0x886f3a 0x88ea86 0x87d184 0x61f92f 0x620903 0x5e943c 0x2b47beb77830 0x61a2d9 bin/mongod(_ZN5mongo15printStackTraceERSo+0x39) [0xedb3e9] bin/mongod(_ZN5mongo10logContextEPKc+0x21f) [0xe6fb3f] bin/mongod(_ZN5mongo13fassertFailedEi+0x71) [0xe4a1c1] bin/mongod(_ZN5mongo7LogFile17synchronousAppendEPKvm+0x29b) [0xe7039b] bin/mongod(_ZN5mongo3dur20_preallocateIsFasterEv+0x22a) [0x8869fa] bin/mongod(_ZN5mongo3dur19preallocateIsFasterEv+0x2a) [0x886f3a] bin/mongod(_ZN5mongo3dur16preallocateFilesEv+0x966) [0x88ea86] bin/mongod(_ZN5mongo3dur7startupEv+0x74) [0x87d184] bin/mongod(_ZN5mongo14_initAndListenEi+0x76f) [0x61f92f] bin/mongod(_ZN5mongo13initAndListenEi+0x23) [0x620903] bin/mongod(main+0x23c) [0x5e943c] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x2b47beb77830] bin/mongod(_start+0x29) [0x61a2d9] 2017-12-25T20:30:41.291-0600 [initandlisten] ***aborting after fassert() failure ---- Edit ---- More info, to help tshoot. I have verified file permissions match up, plus it's obviously writing out the files to the /appdata/unifi folder as I'm able to get the logs. It's not a port issue as I have mapped it to it's own IP address on a seperate NIC and I'm able to ping the unique IP for the container. I have tried to wipe the /appdata/unifi folder and restart and just repeats with the same errors over and over. I cannot let it run for long as the log files get gigantic. I have tried wiping the image and redownloading with no luck. I saw before someone else had the same error and had to switch to another docker image, that docker image is what I'm trying to move away from as it has several bugs of it's own. --- Edit 2 ---- From what I can tell this is an error that the MongoDB can't write out correctly. Which is strange as it's creating all the files and the log files. Is there a specific filesystem format that has to exist for this to run? My cache drive (where appdata is) is formatted as XFS. ---Edit 3--- It just started working after stopping and starting enough times. Truly odd.
  8. It would be nice to have some way to use VLAN tagging or implement VSwitch support. With unRAID now having the ability to act as a hypervisor with KVM it becomes necessary to manipulate the networking components.
  9. My unraid is running super sluggish due to a process "kworker/u16:19" eating all the cpu. It's so bad I can't even stop the array gracefully.
  10. Documented in the defect reports thread with work around documented: https://lime-technology.com/forum/index.php?topic=41650.0
  11. If you have multiple USB devices with the same Vendor and Product then the passthrough does not work as the UI currently builds the XML file with USB based on the Vendor / Product and not the Address Bus= Device= syntax. Since this is the case if you attempt to passthrough any usb devices that have duplicate Vendor/Product you will not be able to start your VM. The workaround is to manually edit the xml to the Address syntax. Examples: Bus 011 Device 003: ID 08bb:2704 Texas Instruments Audio Codec Bus 011 Device 002: ID 08bb:2704 Texas Instruments Audio Codec Current Syntax: <hostdev mode='subsystem' type='usb' managed='yes'> <source > <vendor id='0x08bb'/> <product id='0x2704'/> </source> </hostdev> This will result in a non booting VM Fixed Syntax: <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='11' device='2'/> </source> </hostdev>
  12. Whenever I start my VM my syslog on unraid get's spammed with Feb 1 14:58:50 Tower kernel: usb 1-3.4: usbfs: usb_submit_urb returned -28 tons of these, like 10 a second. Here's my VM config: <domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Media</name> <uuid>d8070111-f188-78ce-cfdb-dcdd7f271bea</uuid> <metadata> <snapshot1422724253>All Installed, Base Kodi</snapshot1422724253> <snapshot1422717187>Drivers Installed</snapshot1422717187> <snapshots/> </metadata> <memory unit='KiB'>6291456</memory> <currentMemory unit='KiB'>6291456</currentMemory> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <loader>/usr/share/qemu/bios-256k.bin</loader> <boot dev='cdrom'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='yes'/> <timer name='hypervclock' present='yes'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <pm> <suspend-to-mem enabled='no'/> <suspend-to-disk enabled='no'/> </pm> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none' io='native'/> <source file='/mnt/cache/vm/Media/Media.qcow2'/> <backingStore/> <target dev='hda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </disk> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb0'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb0'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb0'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x2'/> </controller> <controller type='ide' index='0'> <alias name='ide0'/> </controller> <interface type='bridge'> <mac address='52:54:00:46:29:be'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x150a'/> <product id='0x1203'/> <address bus='1' device='6'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x0719'/> <address bus='1' device='7'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0403'/> <product id='0x6001'/> <address bus='1' device='5'/> </source> <alias name='hostdev2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='1' device='4'/> </source> <alias name='hostdev3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0424'/> <product id='0x2507'/> <address bus='1' device='3'/> </source> <alias name='hostdev4'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=02:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=02:00.1,bus=pcie.0'/> </qemu:commandline> </domain>
  13. Running a corsair 750 watt power supply with not splitters. Gonna go swap out my 8087 SAS cables and see if that does the trick
  14. Been running the same hardware for a long time now. Started getting errors on all drives. Shut down and did a fresh boot. Here's the complete syslog. Is my AOC-SAS2LP-MV8 failing?? syslog.zip