• Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About Jarsky

  • Rank

Recent Profile Visitors

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

  1. I believe its more to do with Secure Boot in UEFI in my instance. You perhaps could try booting a Linux Live distro to make sure your card is actually working as it should normally, that would rule out UnRAID incase potentially your card has gone faulty or have a power issue to the card.
  2. I finally figured out my issue. You might want to check if you're booting UnRAID in UEFI or BIOS...you can check this in UnRAID GUI going to Main > Boot Device (Flash) > scroll down bottom to Server Boot Mode. If it say's UEFI, try booting to your BIOS and change the Boot Priority to USB: <Device Name> instead of UEFI: <Device Name> After Reboot, check the Server Boot Mode now says "Legacy". See if the GPU works now. Turned out when I updated my server, I set my boot priority to UEFI by mistake.
  3. I know but just pointing out there may be a larger Linux kernel issue thats affecting Scroopy, given that mine recently stopped working with the same issue. Mines been working in that setup for a year, and it just stopped working for no reason in the last week...only thing i'd changed up to that point was regular UnRAID and Ubuntu upgrades. The only thing that I can find that appears relevant is entries that say 'tainted kernel' e.g
  4. I'd just like to add that i'm having the same issue as @Scroopy Noopers, but my card is running in a VM...so seems to be a wider issue. I have a EVGA GTX1070 FTW being passed from UnRAID 6.9.0 to Ubuntu 20.04 So far things i've tried: - Upgrading drivers from NVIDIA 450.66 to 455.38 - Upgrading the Ubuntu VM - Upgrading UnRaid 6.9.0-beta29 to 6.9.0-beta30 - Checked Nouveau driver blacklisting - Binding to VFIO-PCI - Upgrading Machine version from Q35-4.2 to Q35-5.1
  5. Turns out my agentless backups complete fine...or when the VM is powered off. The problem is when trying to do one with qemu-guest-agent so I can do a snapshot backup of a running VM. It then kills libvirtd. So the workaround for me since this is just a home setup, is to allow the VM's to be shutdown to complete the backup. Not a fan of that, but better than killing my whole server. 2020-09-08 14:07:15 information: Elements can be found on the system. attempting backup. 2020-09-08 14:07:15 information: creating local Elements.xml to work with during backup.
  6. Just checking in to see if anyone has got this working OK on 6.9.0 without it crashing libvirtd?
  7. This should probably be a new thread, as this isn't related to the smbd panic I reported. SMBD Panic actually has a negative effect in that it terminates communication (i.e your network shares become unreachable) and times out. This seems to be related to an incorrect boolean value (i.e something isnt correctly defined as true/false or yes/no). This shouldn't cause a daemon crash, at most one of your shares isn't working.
  8. Is there someone that will be carrying this plugin forward? As of the new UnRAID 6.9.0 this plugin is having major issues for me. When I run a backup, it breaks the libvirtd service, so it can not discover the VM's. They are still running, however I then have to shutdown all the running VM's from within the guest and use lsof to close any further open files and reboot the entire server so I can get the libvirtd service back up and manage my VM's again. I have snapshots enabled and qemu-guest-agent installed on all the VM's. Sometimes it gets through 1 or 2 VM's, someti
  9. It seems this affects older SMB clients. Both my Ubuntu VM's were 18.04 with the default Linux 4.15 Kernel, which had samba version 4.7.2. I upgraded HWE (hardware enablement stack) which upgraded my Linux kernel to 5.2. That subsequently upgraded my samba version to 4.11.x, and now no longer getting panics on UnRAID. I'm not to familiar with OSX, but UnRAID should have a new 4.12.x samba in its next build I assume (6.9.0 RC1?), so it should be fixed then if it's related to the samba bug I linked above.
  10. It looks like it might be. It works fine to Windows, only seems to affect straight SMB. Check your /var/log/samba/log.smbd and you should see something like this, complaining about "can not close with outstanding aio requests" [2020/07/02 05:25:48.276594, 0] ../../source3/smbd/close.c:648(assert_no_pending_aio) assert_no_pending_aio: fsp->num_aio_requests=1 [2020/07/02 05:25:48.276625, 0] ../../source3/lib/util.c:829(smb_panic_s3) PANIC (pid 8790): can not close with outstanding aio requests [2020/07/02 05:25:48.276730, 0] ../../lib/util/fault.c:222(log_s
  11. P.S I did find this which is possibly related to this https://bugzilla.samba.org/show_bug.cgi?id=14301 ? Seems related with the error "outstanding aio requests" Due for fix in the next 4.12.xx build (UnRaid 6.9.0-beta22 is on Version 4.12.3)
  12. I wonder if anyone else is having this issue? I have several Ubuntu VM's mounting my primary share from the UnRAID pool via SMB. One of them in particular which runs qBitTorrent has high writes (up to approx 100MB/s). Since upgrading to the 6.9.0 build (from 6.8.3) the speed is constantly dropping as smbd appears to panic which loses connection. From my Ubuntu VM I can see smbd loses connection and blocks the app for 2 minutes [18358.622226] cifs_vfs_err: 23 callbacks suppressed [18358.622229] CIFS VFS: Server tower has not responded in 180 seconds. Reconnect
  13. While everyone is mentioning to update the VM network drive to virtio-net, I thought I would also mention an issue I was having. I was having major problems with apps becoming unresponsive in Linux VM's when trying to save to SMB shares mounted from my UnRAID host. When I checked dmesg, I was seeing errors such as this: CIFS VFS: Close unmatched open With the upgraded Linux kernel, don't forget to change your /etc/fstab mounts on any Linux VM's to cifs vers=3.0. Errors stopped after making the change and remounting the shares. Also for security, removin
  14. This is how i've been running as well. Using the ZFS Plugin with unassigned drives as a mirrored nvme ZFS pool just for Docker/VM/ISO. All the shares and backups are on the main UnRAID array. Best of both worlds really where you dont require high synchronous reads for general data.
  15. Yes that's all done fine, I can see the GPU in BOINC. The problem is, it says it doesnt support OpenCL Mon 25 May 2020 11:17:54 PM UTC | | CUDA: NVIDIA GPU 0: GeForce GTX 1070 (driver version 440.59, CUDA version 10.2, compute capability 6.1, 4096MB, 3972MB available, 6900 GFLOPS peak)