Jump to content

TheSkaz

Members
  • Content Count

    44
  • Joined

  • Last visited

Community Reputation

6 Neutral

About TheSkaz

  • Rank
    Advanced Member
  • Birthday 01/05/1984

Recent Profile Visitors

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

  1. @steini84 getting a weird error: Sep 27 13:14:40 Tower kernel: VERIFY3(zfs_btree_find(tree, value, &where) != NULL) failed (0000000000000000 != 0000000000000000) Sep 27 13:14:40 Tower kernel: PANIC at btree.c:1780:zfs_btree_remove() Sep 27 13:14:40 Tower kernel: Showing stack for process 8689 Sep 27 13:14:40 Tower kernel: CPU: 54 PID: 8689 Comm: txg_sync Tainted: P O 4.19.107-Unraid #1 Sep 27 13:14:40 Tower kernel: Hardware name: System manufacturer System Product Name/ROG ZENITH II EXTREME ALPHA, BIOS 1101 06/05/2020 Sep 27 13:14:40 Tower kernel: Call Trace: Sep 27 13:14:40 Tower kernel: dump_stack+0x67/0x83 Sep 27 13:14:40 Tower kernel: spl_panic+0xcf/0xf7 [spl] Sep 27 13:14:40 Tower kernel: ? zfs_btree_find_in_buf+0x4a/0x99 [zfs] Sep 27 13:14:40 Tower kernel: ? zfs_btree_find_in_buf+0x4a/0x99 [zfs] Sep 27 13:14:40 Tower kernel: ? zfs_btree_find+0x148/0x182 [zfs] Sep 27 13:14:40 Tower kernel: zfs_btree_remove+0x57/0x7d [zfs] Sep 27 13:14:40 Tower kernel: range_tree_add_impl+0x4f3/0xa97 [zfs] Sep 27 13:14:40 Tower kernel: ? _cond_resched+0x1b/0x1e Sep 27 13:14:40 Tower kernel: ? __kmalloc_node+0x11e/0x12f Sep 27 13:14:40 Tower kernel: ? range_tree_remove_impl+0xad5/0xad5 [zfs] Sep 27 13:14:40 Tower kernel: range_tree_vacate+0x16a/0x1b3 [zfs] Sep 27 13:14:40 Tower kernel: metaslab_sync_done+0x327/0x4c2 [zfs] Sep 27 13:14:40 Tower kernel: ? _cond_resched+0x1b/0x1e Sep 27 13:14:40 Tower kernel: vdev_sync_done+0x42/0x66 [zfs] Sep 27 13:14:40 Tower kernel: spa_sync+0xbd1/0xd6a [zfs] Sep 27 13:14:40 Tower kernel: txg_sync_thread+0x246/0x3f2 [zfs] Sep 27 13:14:40 Tower kernel: ? txg_thread_exit.isra.0+0x50/0x50 [zfs] Sep 27 13:14:40 Tower kernel: thread_generic_wrapper+0x67/0x6f [spl] Sep 27 13:14:40 Tower kernel: ? __thread_exit+0xe/0xe [spl] Sep 27 13:14:40 Tower kernel: kthread+0x10c/0x114 Sep 27 13:14:40 Tower kernel: ? kthread_park+0x89/0x89 Sep 27 13:14:40 Tower kernel: ret_from_fork+0x22/0x40 froze up my vms that are stored on the zfs pools. does this make any sense? is there any way to recover without rebooting?
  2. working beautifully. you sir, are a scholar among men (or women )
  3. 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?
  4. 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?
  5. If everything is exactly the same backwards and forward, meaning there isnt a redundant path or something, it could be the difference in read/write speed on one of the devices. to put it in a simpler way, One device might be able to read at 112MBps but only write at 77MBps. here is mine: from client to server: and server to client: ~30MB difference
  6. ok, It did it again while creating a Ubuntu VM. here are the syslog and diagnostics tower-syslog-20200922-2124.zip tower-diagnostics-20200922-1426.zip
  7. I am running version 6.9.0-beta25. I changed my configuration of KVM to this: /VMstorage is a ZFS Pool (RAID10): ever since the change KVM will hang and fill up the log files in a second. its kind of erratic. usually happens when editing or creating a new VM tower-diagnostics-20200922-1131.zip
  8. 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
  9. 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.
  10. do you know how long I looked for one of those???? all I could find was expanders (and they still took up another pcie slot)
  11. I understand that, although I didnt know you could get a cable to go from one to the other. that is pretty cool. Full Disclosure: the whole system has 3 GPUs in 3 of the slots. in the 4th slot there is an 8 port HBA. so 8 of my drives are there. I am using 4 of the onboard sata ports. the other 4 are disabled due to an nvme drive in the back slot. I also have 4 other nvme drives. this is a new mobo and was trying to hook up all my drives. I have 2 more that I figured could go USB, but that doesnt work. If I could just get those last drives connected......
  12. that would be awesome. I dont have an eSATA port. and dont have a pcie slot available. All 4 are taken. The only thing that I have open is USB 3, 3.1, and 3.2
  13. 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
  14. here is what I am trying now: (causes a kernel panic when trying to start vm)