jamesy829

Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by jamesy829

  1. Hi everyone, all of sudden my WebGUI doesn't start up (it was working for a long long time). And checking the logs, i'm seeing a weird error, with the line `...Floating point exception...` 2021-04-15 08:48:58,049 DEBG 'nzbget' stdout output: [info] NZBGet configuration file exists [info] Patching NZBGet config file for WebDir and ConfigTemplate locations... 2021-04-15 08:48:58,494 DEBG 'nzbget' stderr output: /home/nobody/start.sh: line 26: 295 Floating point exception/usr/local/bin/nzbget/nzbget -c /config/nzbget.conf -s 1>&- 2021-04-15 08:48:58,494 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22718133147120 for <Subprocess at 22718116771888 with name nzbget in state STARTING> (stdout)> 2021-04-15 08:48:58,494 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22718116788128 for <Subprocess at 22718116771888 with name nzbget in state STARTING> (stderr)> 2021-04-15 08:48:58,494 INFO exited: nzbget (exit status 136; not expected) 2021-04-15 08:48:58,494 DEBG received SIGCLD indicating a child quit 2021-04-15 08:48:58,494 INFO gave up: nzbget entered FATAL state, too many start retries too quickly Has anyone run into this issue and have a resolution for this?
  2. Is it possible to have an image for the Corsair 900D and Rosewill RSV-R4100 made as well? For the 900D, can you also add the IcyDock HDD cage?
  3. I am also seeing the same issue with the x299 platform, did you end up fixing the issue for your MacOS vm?
  4. Just bumping this to ask if this has been resolved? I am also running into this issue, passing through AMD RX580 to a OSX VM and it locks up unraid server
  5. Hi all, I have just encountered a repeatable issue where my VM would freeze up and my VM tab would not be accessible, then my server would shut down. This has happened for a few times now and I'm not exactly sure what is going on. Can I please get support for this issue? I pasted below the logs before it shut down my server as well as diagnostic reports after the server booted up. System spec Motherboard - EVGA Corp. X299 FTW K bio v1.24 CPU - 10980xe RAM - 128GB (4x32GB) G.Skill Ripjaws V 3600 Mhz CL18 Dec 29 13:06:47 Zoo kernel: sdi: sdi1 sdi2 Dec 29 13:06:47 Zoo rc.diskinfo[12677]: SIGHUP received, forcing refresh of disks info. Dec 29 13:06:47 Zoo unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_500GB_S2RANX0J423685P', mountpoint 'Samsung_SSD_850_EVO_500GB_S2RANX0J423685P-part2' is not set to auto mount. Dec 29 13:06:47 Zoo unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_500GB_S2RANX0J423685P', mountpoint 'EFI' is not set to auto mount. Dec 29 13:06:47 Zoo unassigned.devices: Don't spin down device '/dev/sdi'. Dec 29 13:06:47 Zoo unassigned.devices: Don't spin down device '/dev/sdi'. Dec 29 13:08:46 Zoo nginx: 2020/12/29 13:08:46 [error] 15144#15144: *1169005 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.208, server: , request: "POST /plugins/dynamix.vm.manager/include/VMajax.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.138", referrer: "http://192.168.1.138/Dashboard" Dec 29 13:09:52 Zoo kernel: vfio-pci 0000:17:00.0: enabling device (0100 -> 0103) Dec 29 13:09:52 Zoo kernel: vfio_ecap_init: 0000:17:00.0 hiding ecap 0x19@0x270 Dec 29 13:09:52 Zoo kernel: vfio_ecap_init: 0000:17:00.0 hiding ecap 0x1b@0x2d0 Dec 29 13:09:52 Zoo kernel: vfio_ecap_init: 0000:17:00.0 hiding ecap 0x1e@0x370 Dec 29 13:09:52 Zoo kernel: vfio-pci 0000:17:00.1: enabling device (0100 -> 0102) Dec 29 13:10:44 Zoo kernel: DMAR: DRHD: handling fault status reg 40 Dec 29 13:11:33 Zoo kernel: DMAR: DRHD: handling fault status reg 40 Dec 29 13:11:43 Zoo kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Dec 29 13:11:43 Zoo kernel: rcu: 14-...0: (11 GPs behind) idle=842/1/0x4000000000000000 softirq=82647151/82647151 fqs=14345 Dec 29 13:11:43 Zoo kernel: rcu: (detected by 29, t=60002 jiffies, g=120045541, q=2514330) Dec 29 13:11:43 Zoo kernel: Sending NMI from CPU 29 to CPUs 14: Dec 29 13:11:43 Zoo kernel: NMI backtrace for cpu 14 Dec 29 13:11:43 Zoo kernel: CPU: 14 PID: 8335 Comm: qemu-system-x86 Tainted: P O 4.19.107-Unraid #1 Dec 29 13:11:43 Zoo kernel: Hardware name: EVGA Corp. X299 FTW K/X299 FTW K, BIOS 1.24 10/20/2020 Dec 29 13:11:43 Zoo kernel: RIP: 0010:qi_submit_sync+0x154/0x2db Dec 29 13:11:43 Zoo kernel: Code: 30 02 0f 84 40 01 00 00 4d 8b 96 b0 00 00 00 49 8b 42 10 83 3c 30 03 75 0b 41 bc f5 ff ff ff e9 27 01 00 00 49 8b 06 8b 48 34 <f6> c1 10 74 68 49 8b 06 8b 80 80 00 00 00 c1 f8 04 41 39 c3 75 57 Dec 29 13:11:43 Zoo kernel: RSP: 0018:ffffc9002926fba0 EFLAGS: 00000093 Dec 29 13:11:43 Zoo kernel: RAX: ffffc9000003e000 RBX: 0000000000000100 RCX: 0000000000000000 Dec 29 13:11:43 Zoo kernel: RDX: 0000000000000001 RSI: 0000000000000244 RDI: ffff88a01f035080 Dec 29 13:11:43 Zoo kernel: RBP: ffffc9002926fc00 R08: 000000000000008f R09: 0000000000000009 Dec 29 13:11:43 Zoo kernel: R10: ffff88a01f035080 R11: 0000000000000090 R12: 0000000000000910 Dec 29 13:11:43 Zoo kernel: R13: ffff88a01f035080 R14: ffff88a01f023200 R15: 0000000000000046 Dec 29 13:11:43 Zoo kernel: FS: 0000147373db6e00(0000) GS:ffff88a01f980000(0000) knlGS:0000000000000000 Dec 29 13:11:43 Zoo kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 29 13:11:43 Zoo kernel: CR2: 00000001213bb000 CR3: 000000010cb08004 CR4: 00000000003626e0 Dec 29 13:11:43 Zoo kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Dec 29 13:11:43 Zoo kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Dec 29 13:11:43 Zoo kernel: Call Trace: Dec 29 13:11:43 Zoo kernel: qi_flush_dev_iotlb+0x98/0xb4 Dec 29 13:11:43 Zoo kernel: iommu_flush_dev_iotlb.part.0+0x5f/0x7b Dec 29 13:11:43 Zoo kernel: intel_iommu_unmap+0xde/0x129 Dec 29 13:11:43 Zoo kernel: __iommu_unmap+0xa5/0x10f Dec 29 13:11:43 Zoo kernel: vfio_unmap_unpin+0x136/0x2a6 Dec 29 13:11:43 Zoo kernel: vfio_remove_dma+0x12/0x3b Dec 29 13:11:43 Zoo kernel: vfio_iommu_type1_ioctl+0x647/0x758 Dec 29 13:11:43 Zoo kernel: ? kvm_vm_ioctl+0x303/0x7b2 [kvm] Dec 29 13:11:43 Zoo kernel: vfs_ioctl+0x19/0x26 Dec 29 13:11:43 Zoo kernel: do_vfs_ioctl+0x533/0x55d Dec 29 13:11:43 Zoo kernel: ksys_ioctl+0x37/0x56 Dec 29 13:11:43 Zoo kernel: __x64_sys_ioctl+0x11/0x14 Dec 29 13:11:43 Zoo kernel: do_syscall_64+0x57/0xf2 Dec 29 13:11:43 Zoo kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Dec 29 13:11:43 Zoo kernel: RIP: 0033:0x1473755a44b7 Dec 29 13:11:43 Zoo kernel: Code: 00 00 90 48 8b 05 d9 29 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a9 29 0d 00 f7 d8 64 89 01 48 Dec 29 13:11:43 Zoo kernel: RSP: 002b:00007ffd5439daa8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Dec 29 13:11:43 Zoo kernel: RAX: ffffffffffffffda RBX: 00007ffd5439dbd0 RCX: 00001473755a44b7 Dec 29 13:11:43 Zoo kernel: RDX: 00007ffd5439dac0 RSI: 0000000000003b72 RDI: 000000000000002c Dec 29 13:11:43 Zoo kernel: RBP: 00001473733a9a00 R08: 0000000000000000 R09: 0000000090000000 Dec 29 13:11:43 Zoo kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd5439dac0 Dec 29 13:11:43 Zoo kernel: R13: 00007ffd5439dab0 R14: 00001473733a9a00 R15: 0000000000000000 Dec 29 13:12:05 Zoo kernel: DMAR: DRHD: handling fault status reg 40 zoo-diagnostics-20201229-1321.zip
  6. Thanks @cat2devnull! I figured that was the issue so I looked up after I posted, but I forgot to update the post. Now I need to know the magical number to create the img so I can dd into a ssd.
  7. @SpaceInvaderOne I notice a bug, where I specified the size of physical disk is 500G, but when everything is up and running, the total storage size is actually 536.87GB? I wanted to be 500G as I want to convert the img to a physical disk so it would be running off my SSD instead of using the cache drive. Should this be consider a bug and is there a simple way to resize the img?
  8. hey @mSedek how did you show your CPU properly? I'm giving my hackintosh 14 cores but it would only display as `3 GHz Unknown`, I've configured to use iMac Pro 1,1 as well in the PlatformInfo.
  9. I just want to give a big shoutout to @SpaceInvaderOne for his hard work for both version of macinabox! It has simplify the process of running mac in a vm much simpler! He deserves to be appraised and his YouTube channel are very informative for anything unraid and even outside of unraid! Beers coming up @SpaceInvaderOne, thanks again for your amazing work and future works to come! *wink* *wink*
  10. Thanks @Vr2Io for your help! Unfortunately I didn't discover whether any hardware failure (hopefully there isn't ha...) I'll look into the nvidia build when I get my windows and hackintosh VM up and running again thanks again!
  11. So.... I suspect its one of my parity (I got 2) that went bad, either when it did parity swap or prior to parity swap. I verified yesterday with a trial unraid usb and connecting them, seems fine when I left it running for 2 hours with no plug-in, dockers or any config, so I couldn't rule out any hardware issues, which is very frustrating. Then I did a reset config parity and disk (shifted order of disks as I like to sort them haha) on my unraid usb and parity sync finished after 1 and half day. Now its running fine (cross fingers) but I get a lot of multiple bar for nvidia, likely due to unraid nvidia no longer available to I need to rebuild the kernel and upgrade to rc1.
  12. Hey @Vr2Io just providing some updates, after doing the no parity, start array and using for a few hours, there were no issues so I decided to reboot and do the process again. Unfortunately it still got stuck, this time at 66%, so I decided to reset both parity and disk array, letting the parity rebuild instead. Knock on wood, its going well at 66% as we speak and parity will be done in another 13 hours... Will update as things progress, thanks!
  13. Ah ok, will trial and error. What does it mean by simple and basic, and maybe I should upgrade to rc1 as I'm still on 6.8.3
  14. Oh didn't notice you modified the msg, yea, the board is sick and I'm running the 10980xe, but maybe I should update the BIOS (which I need to figure out how). I just did a new config with no parity and it start up fine. But I'm seeing weird kernel errors (could be I am using old unraid nvidia kernel that caused system to errror?) And 1 or the error i saw was the backup plug-in thats in the screenshot.
  15. Yea, I tried to access the logs but no dice as the WebGUI just keep loading so I decided to reboot. It did generate a diagnostic report thou which I'll try to pull out (not sure where it saved at)
  16. Good idea, i won't assign the parity disk (1x10TB and 1x12TB) for fresh setup. This is the kernel logs when I clicked pause and trying to reboot the server.
  17. Thanks @Vr2Io I will reset the config for parity and array. I have a feeling its also the plugins that caused some irreversible changes to my disk as I had quite a bit of plugin which I'm not sure if they did anything, 1 of them was the file integrity plugin and the other one I can't remember as I saw 2 plugins that were red in the logs from the last data rebuild.
  18. Wow thanks for this instruction, I'll list what I have done. Tried to identify hardware and software issue * I switch to a new motherboard/cpu combo 2 months ago and it was running fine for a month and then 1 of the drive died), left it emulated for a few weeks as I was waiting for my new drives to arrive * did a full memory test prior to moving to the new system and everything is passed for 48 hours I did not know about the Unraid backup feature, I will need to look into it but wouldn't the plug-in for backup automatically do this? By start fresh, do you mean reset the config for parity and array to reassign the drives? No USB disk is attached other then the Unraid disk itself.
  19. Yea... it is very frustrating me ha... its been 1 week downtime, as I got 2 12TB to replace parity and use parity as replacement drives for emulated and small drive... fortunately I was able to backup everything on that emulated drive. Can you suggest the steps to "start fresh" where I just replace that emulated drive without data rebuild and copy the stuff back when my system is back up?
  20. Hey @Vr2Io! I tried to pause the rebuild, it doesn't actually pause... before my last rebuild, I reconnected all my sata connectors.
  21. Hi @JorgeB, bad news... so it ran in safe mode data rebuild for a day and was going at 80-100MB/s, and all of sudden it dropped to 750KB/s... attached is the diagnostic logs if you can help, thanks! zoo-diagnostics-20201212-1132.zip
  22. Hi @JorgeB, thank you for helping me out! Was busy at work so didn't get a chance to respond. I started in safe mode and maintenance mode, currently running the data rebuild (20%) so will report back when it either passes or stuck (I hope not...)!
  23. Hi everyone, I recently did a parity upgrade and using the old parity drive to replace a dead drive that has been emulating for a few weeks. I ran the parity check before the parity sync happen and it passed. So I move forward with replacing the dead drive with the old parity drive and the data re-build was going well (around 80MB/sec) and when it hit 40% it dropped to 500KB/sec and I let it ran for a few hours and it was still moving at that rate. So I did a reboot of server and it restarted the data rebuild, and this time it hit 50% and it dropped to 500KB/sec again. I have uploaded a diagnostic as I would like to know what is going on and fix this issue so I can have my server back up and running... The order of which I did 1. upgrading 1 of the parity disk from 10TB to 12TB 2. replace an emulated 8TB drive with the old 10TB parity drive 3. started parity sync (no docker or vm is running) and successfully completed 4. started data rebuild (1st time) and it was hitting 80MB/sec until 40% and drop to 500KB/sec 5. rebooted the server, started data rebuild again (2nd time) and it was hitting 80MB/sec until 50% and drop to 500KB/sec Currently still running the data rebuild as I'm posting this, please provide help! UPDATE: * Currently its on 50.3% and rebuilding at 100KB/sec, still hoping it will speed up or I'm force to copy off the data from the emulated drive and start new configuration UPDATE 2: * With the help of @Vr2Io, I manage to get my unraid server up and running, by reseting the configuration for parity and disk to for a parity sync from scratch and everything worked. Its likely my parity had some corruption either during parity copy (from 10TB to 12TB) or prior to the parity copy (unlikely as I ran parity check right before I took server offline and performing upgrade of drives. zoo-diagnostics-20201210-1552.zip
  24. I am running into an issue since after the new years where running binhex/arch-plexpass will always buffer when watching anything. My system is ryzen 7, 3800x with 32gb of ram with no gpu, updated docker to latest. I tried playing the videos directly and it works fine so it's definitely not the video file. Then I observe when watching through plex, there would be very little cpu usage but when I pin the cpu (4 in this case) I will see it not buffer and all 4 cores spiking in usage.