The_PC_Guy

to clarify on this. 2.* You don't exactly need linux mint most debian distros should work. basically if you can install .deb package then it works. 4.* (to install if gui doesn't work then command for installing is `sudo dpkg -i hpssacli-2.10-14.0_amd64.deb` 6.* Make sure you're the root user or else you won't be able to able to execute commands. instead of `./hpssacli` run `sudo ./hpssacli` if you're not the root user (as default user is not the root user for most debian distros now). 7.1 * Make sure you don't have any logical drives or else you won't be able to set it to hba mode. you can check that by running `ctrl slot=0 ld 2 show` it should say `Error: the specified device does not have any logical drive`. If it shows any logical drives the easiest solution is to just unplug those drives before booting into os before enabling hbamode

@Waseh with the new plugin we have to manually create mount script with user scripts?

has anyone tried this ubuntu VM works fine with Windows but after on Ubuntu after a restart i just get blank screen and have to force stop the VM 2020-05-27T09:43:44.670228Z qemu-system-x86_64: vfio: Cannot reset device 0000:33:00.1, no available reset mechanism. 2020-05-27T09:43:44.674223Z qemu-system-x86_64: vfio: Cannot reset device 0000:33:00.1, no available reset mechanism. 2020-05-27T09:44:17.353232Z qemu-system-x86_64: vfio: Cannot reset device 0000:33:00.1, no available reset mechanism. 2020-05-27T09:44:17.357244Z qemu-system-x86_64: vfio: Cannot reset device 0000:33:00.1, no available reset mechanism. 2020-05-27T09:45:08.197995Z qemu-system-x86_64: terminating on signal 15 from pid 9026 (/usr/sbin/libvirtd) libusb: error [do_close] Device handle closed while transfer was still being processed, but the device is still connected as far as we know libusb: error [do_close] A cancellation hasn't even been scheduled on the transfer for which the device is closing libusb: error [do_close] Device handle closed while transfer was still being processed, but the device is still connected as far as we know libusb: error [do_close] A cancellation hasn't even been scheduled on the transfer for which the device is closing libusb: error [do_close] Device handle closed while transfer was still being processed, but the device is still connected as far as we know libusb: error [do_close] A cancellation hasn't even been scheduled on the transfer for which the device is closing 2020-05-27 09:45:10.399+0000: shutting down, reason=destroyed and after that i can neither get a output from windows or ubuntu VM i need to restart unraid server to get it working again

looks like the dev has been offline for a long time like the user mentioned above the webui takes a long time to startup with the exact same log