TheSkaz

working beautifully. you sir, are a scholar among men (or women )

you have built one for me before, that would be awesome, I REALLY dont want to lose that data. maybe it could help someone else too?

just downgraded from unraid beta25 to 6.8.3 and had build 2 pools on the previous version. when trying to import them, I get this: root@Tower:~# zpool import pool: datastore id: 7743322362316987465 state: UNAVAIL status: The pool can only be accessed in read-only mode on this system. It cannot be accessed in read-write mode because it uses the following feature(s) not supported on this system: com.delphix:log_spacemap (Log metaslab changes on a single spacemap and flush them periodically.) action: The pool cannot be imported in read-write mode. Import the pool with "-o readonly=on", access the pool on a system that supports the required feature(s), or recreate the pool from backup. config: datastore UNAVAIL unsupported feature(s) mirror-0 ONLINE sdk ONLINE sdn ONLINE mirror-1 ONLINE sdl ONLINE sdm ONLINE pool: vmstorage id: 4552063121711083272 state: UNAVAIL status: The pool can only be accessed in read-only mode on this system. It cannot be accessed in read-write mode because it uses the following feature(s) not supported on this system: com.delphix:log_spacemap (Log metaslab changes on a single spacemap and flush them periodically.) action: The pool cannot be imported in read-write mode. Import the pool with "-o readonly=on", access the pool on a system that supports the required feature(s), or recreate the pool from backup. config: vmstorage UNAVAIL unsupported feature(s) mirror-0 ONLINE nvme2n1 ONLINE nvme3n1 ONLINE mirror-1 ONLINE nvme0n1 ONLINE nvme1n1 ONLINE is there a way to recover?

googled the error and found that running: echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind works. NVLink seems to work too

I have the VM up and able to boot with both gpus showing. in the VM logs for the machine, I am getting hundreds of these: 2020-09-22T06:21:28.221139Z qemu-system-x86_64: vfio_region_write(0000:01:00.0:region1+0x801b8, 0x0,8) failed: Device or resource busy that is my primary video card for the system and 1 of the 2 gpus for the VM. anything that attempts to use the gpus freezes.

Does this mean anything useful in regards to my issue? Sep 17 08:44:57 Tower kernel: vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Sep 17 08:44:57 Tower kernel: Linux agpgart interface v0.103 Sep 17 08:44:57 Tower kernel: xhci_hcd 0000:01:00.2: remove, state 4 Sep 17 08:44:57 Tower kernel: usb usb2: USB disconnect, device number 1 Sep 17 08:44:57 Tower kernel: xhci_hcd 0000:01:00.2: USB bus 2 deregistered Sep 17 08:44:57 Tower kernel: xhci_hcd 0000:01:00.2: remove, state 4 Sep 17 08:44:57 Tower kernel: usb usb1: USB disconnect, device number 1 Sep 17 08:44:57 Tower kernel: xhci_hcd 0000:01:00.2: USB bus 1 deregistered Sep 17 08:44:57 Tower kernel: vfio-pci 0000:50:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Sep 17 08:44:57 Tower kernel: xhci_hcd 0000:50:00.2: remove, state 4 Sep 17 08:44:57 Tower kernel: usb usb16: USB disconnect, device number 1 Sep 17 08:44:57 Tower kernel: xhci_hcd 0000:50:00.2: USB bus 16 deregistered Sep 17 08:44:57 Tower kernel: xhci_hcd 0000:50:00.2: remove, state 4 Sep 17 08:44:57 Tower kernel: usb usb15: USB disconnect, device number 1 Sep 17 08:44:57 Tower kernel: xhci_hcd 0000:50:00.2: USB bus 15 deregistered Sep 17 08:44:57 Tower kernel: nvidia: loading out-of-tree module taints kernel. Sep 17 08:44:57 Tower kernel: nvidia: loading out-of-tree module taints kernel. Sep 17 08:44:57 Tower kernel: nvidia: module license 'NVIDIA' taints kernel. Sep 17 08:44:57 Tower kernel: nvidia: module license 'NVIDIA' taints kernel. Sep 17 08:44:57 Tower kernel: Disabling lock debugging due to kernel taint Sep 17 08:44:57 Tower kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 247 Sep 17 08:44:57 Tower kernel: vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Sep 17 08:44:57 Tower kernel: vfio-pci 0000:50:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Sep 17 08:44:57 Tower kernel: nvidia 0000:4e:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none Sep 17 08:44:57 Tower kernel: NVRM: The NVIDIA probe routine was not called for 2 device(s). Sep 17 08:44:57 Tower kernel: NVRM: This can occur when a driver such as: Sep 17 08:44:57 Tower kernel: NVRM: nouveau, rivafb, nvidiafb or rivatv Sep 17 08:44:57 Tower kernel: NVRM: was loaded and obtained ownership of the NVIDIA device(s). Sep 17 08:44:57 Tower kernel: NVRM: Try unloading the conflicting kernel module (and/or Sep 17 08:44:57 Tower kernel: NVRM: reconfigure your kernel without the conflicting Sep 17 08:44:57 Tower kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module Sep 17 08:44:57 Tower kernel: NVRM: again. Sep 17 08:44:57 Tower kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020

here is what I am trying now: (causes a kernel panic when trying to start vm)

I cant seem to find anything regarding NVLink and passthrough to a VM. Is it possible, or is there such a tutorial?

root@Tower:~# dmesg | grep ZFS [ 61.092654] ZFS: Loaded module v0.8.0-1, ZFS pool version 5000, ZFS filesystem version 5 Thank you so much for your help and quick turnarounds.

thank you so much! sorry for the headache

What I did was upload the files using WinSCP: and then rebooted, once it comes back up, it shows this: it seems to be reverting. I assume I don't need to rename the files right?

Thank you so much!!!!!!! [ 88.290629] ZFS: Loaded module v0.8.3-1, ZFS pool version 5000, ZFS filesystem version 5 I have it installed, and currently stress testing. Let's hope this works!

I previously posted about a kernel panic under heavy load, and it seems this was addressed 6 days ago: https://github.com/openzfs/zfs/pull/10148 Is there a way that we can get this implemented, or know of a workaround?

Anyone getting ZFS Kernel Panics? seems to only happen when nzbget is running full tilt. here is my error Apr 2 01:11:48 Tower kernel: PANIC: zfs: accessing past end of object e26/543cf (size=6656 access=6308+1033) Apr 2 01:11:48 Tower kernel: Showing stack for process 25214 Apr 2 01:11:48 Tower kernel: CPU: 2 PID: 25214 Comm: nzbget Tainted: P O 4.19.107-Unraid #1 Apr 2 01:11:48 Tower kernel: Hardware name: ASUSTeK COMPUTER INC. Z9PE-D16 Series/Z9PE-D16 Series, BIOS 5601 06/11/2015 Apr 2 01:11:48 Tower kernel: Call Trace: Apr 2 01:11:48 Tower kernel: dump_stack+0x67/0x83 Apr 2 01:11:48 Tower kernel: vcmn_err+0x8b/0xd4 [spl] Apr 2 01:11:48 Tower kernel: ? spl_kmem_alloc+0xc9/0xfa [spl] Apr 2 01:11:48 Tower kernel: ? _cond_resched+0x1b/0x1e Apr 2 01:11:48 Tower kernel: ? mutex_lock+0xa/0x25 Apr 2 01:11:48 Tower kernel: ? dbuf_find+0x130/0x14c [zfs] Apr 2 01:11:48 Tower kernel: ? _cond_resched+0x1b/0x1e Apr 2 01:11:48 Tower kernel: ? mutex_lock+0xa/0x25 Apr 2 01:11:48 Tower kernel: ? arc_buf_access+0x69/0x1f4 [zfs] Apr 2 01:11:48 Tower kernel: ? _cond_resched+0x1b/0x1e Apr 2 01:11:48 Tower kernel: zfs_panic_recover+0x67/0x7e [zfs] Apr 2 01:11:48 Tower kernel: ? spl_kmem_zalloc+0xd4/0x107 [spl] Apr 2 01:11:48 Tower kernel: dmu_buf_hold_array_by_dnode+0x92/0x3b6 [zfs] Apr 2 01:11:48 Tower kernel: dmu_write_uio_dnode+0x46/0x11d [zfs] Apr 2 01:11:48 Tower kernel: ? txg_rele_to_quiesce+0x24/0x32 [zfs] Apr 2 01:11:48 Tower kernel: dmu_write_uio_dbuf+0x48/0x5e [zfs] Apr 2 01:11:48 Tower kernel: zfs_write+0x6a3/0xbe8 [zfs] Apr 2 01:11:48 Tower kernel: zpl_write_common_iovec+0xae/0xef [zfs] Apr 2 01:11:48 Tower kernel: zpl_iter_write+0xdc/0x10d [zfs] Apr 2 01:11:48 Tower kernel: do_iter_readv_writev+0x110/0x146 Apr 2 01:11:48 Tower kernel: do_iter_write+0x86/0x15c Apr 2 01:11:48 Tower kernel: vfs_writev+0x90/0xe2 Apr 2 01:11:48 Tower kernel: ? list_lru_add+0x63/0x13a Apr 2 01:11:48 Tower kernel: ? vfs_ioctl+0x19/0x26 Apr 2 01:11:48 Tower kernel: ? do_vfs_ioctl+0x533/0x55d Apr 2 01:11:48 Tower kernel: ? syscall_trace_enter+0x163/0x1aa Apr 2 01:11:48 Tower kernel: do_writev+0x6b/0xe2 Apr 2 01:11:48 Tower kernel: do_syscall_64+0x57/0xf2 Apr 2 01:11:48 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 2 01:11:48 Tower kernel: RIP: 0033:0x14c478acbf90 Apr 2 01:11:48 Tower kernel: Code: 89 74 24 10 48 89 e5 48 89 04 24 49 29 c6 48 89 54 24 18 4c 89 74 24 08 49 01 d6 48 63 7b 78 49 63 d7 4c 89 e8 48 89 ee 0f 05 <48> 89 c7 e8 1b 85 fd ff 49 39 c6 75 19 48 8b 43 58 48 8b 53 60 48 Apr 2 01:11:48 Tower kernel: RSP: 002b:000014c478347640 EFLAGS: 00000216 ORIG_RAX: 0000000000000014 Apr 2 01:11:48 Tower kernel: RAX: ffffffffffffffda RBX: 0000558040d4e920 RCX: 000014c478acbf90 Apr 2 01:11:48 Tower kernel: RDX: 0000000000000002 RSI: 000014c478347640 RDI: 0000000000000005 Apr 2 01:11:48 Tower kernel: RBP: 000014c478347640 R08: 0000000000000001 R09: 000014c478b15873 Apr 2 01:11:48 Tower kernel: R10: 0000000000000006 R11: 0000000000000216 R12: 000000000000000b Apr 2 01:11:48 Tower kernel: R13: 0000000000000014 R14: 0000000000000409 R15: 0000000000000002