Xeniummm

Members
  • Posts

    7
  • Joined

  • Last visited

Xeniummm's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hello All For me is now working the VM Manager I have manually removed the VIB file as suggested and restarted the Server. After Restart I was able to start the VM with no problem and I have tried to create a VM. after I filled up the VM profile with the latest settings I tried to create the VM and got a new surprise The GUI was unresponsive. I considered that I made a mistake in configuration and I may have assigned the same IP address to the new VM. After rebooting the server and rebuilding the Parity I tried again to create a VM and all went smoothly and with no problems. Thank you for your Support
  2. Hello SimonF Here is how my system devices looks like for the Raid controler I will go for the second atempt where I will try to delete the vifo from cli I will post the result.
  3. I tried to delete the vifo but I can't find any documentation on how to do this. Can you please provide me with the command to delete the Vifo file ?
  4. Hello I have also a similar error on my Unraid server when I try to start the VM Manager After I run the command cat /boot/config/vfio-pci.cfg i get the error BIND=0000:03:00.0|1106:3432 when i run lspci I see that 03:00.0 RAID bus controller: Adaptec Series 8 12G SAS/PCIe 3 (rev 01) the main Idea is that I have upgraded my Unraid server an I now get this error. If I started the VM then one of the HDD's from the Parity will become unavailable and I had to rebuild the parity. As a next step I have deleted all the VM's from my unraid server and I still get this error ... Can anyone help on this matter ? ErrorsUnraid.txt
  5. Hello all and thank you for looking in to this problem. I have checked on my unraid server and here is the current configuration what I have 1 array of 3 disks 1 chache of 2 ssd's 1 cache of 1 ssd 1 cache of 1 disk I don't think that my server errors are triggered by m.2 After my server rebooted I noticed 1 error what I haven't had before. the error is refering to an vifo-pci. I have atached the print screen for a better view.
  6. Hello I have the same problem on my Unraid server initialy was bouncing to 100% verry offten. I have stopped the Array first and the usage change to 80-100% constant. I have disabled the Docker and still the same 80-100% constant. I am trying to gather the diagnostics but page is crashing constantly. is there any known bug what I can follow to fix my unraid server ?