PeteyBoPetey
-
Posts
79 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by PeteyBoPetey
-
-
1 pool of 3 drives. I created a new pool and added the drives in logical order nvme0 , nvme1, nvme2. Seems to be working. created new VMs but no vga output yet. I think I need to VNC into them and update drivers?
BTW: Thankyou to you and Jorge for your help. Much apreciated
-
Hi Guys,
Doing a clean install. So far I have:
- Created the USB Unraid drive by downloading 6.10.2 installer
- Run "Make bootable" as administrator
- Copied super.dat & plus.key from backup to config folder of new install
The array drives appesr in correct order. The cache drives are listed in unassigned devices. How do I mount these in the correct order? I dont want to corrupt the cache, they have my vm vdisk image on them.
TIA
Peter
-
10 hours ago, JonathanM said:
*.key
Ok 90% of the way there. All the array drives are listed, copied Plus.key to new config folder. However, the cache drives are listed in unassigned devices, these have my VMs vdisks on them. I assume the need to be mounted in the correct order as well?. Can I just copy a file the same as super.dat with the array?
-
1 hour ago, JonathanM said:
did you copy your license file?
which one is the licence file?
-
1 hour ago, JorgeB said:
Yes.
No, you can re-assign the disks if you know the original positions or copy super.dat from the existing config folder on the flash drive.
Yes, but that would basically be the same as using current flash.
Clean install is being treated as a trial, didn't seem to recognise the USB ID. Will this be resolved with the super.dat overwrite, or do I need to buy a licence key?
So just to confirm,
Download Unraid 6.10.2
Make bootable as administrator
Overwite new super.dat with old super.dat
Install USB and boot machine
TIA
-
Hi Guys,
Installed a new Corsair Commander Pro and pcie USB 3.0 card. Unraid booted and worked ok, but VMs wouldn't start. I noticed that the USB controllers I had bound to the vfio to be passed through to the VMs had become unbound and had different identifiers. I get errors such as "unable to mount sda1" and "Can not bond:0" others I can't remember atm. Tried different usb ports etc.
Can I start with a clean slate?. Can I down load Unraid 6.10.2 and see if it boots with a fresh install?. Will this write to, or corrupt the array?. Can I just overwrite the Config folder in 6.10.2 with my old config folder from my back up?
TIAPeter
-
Hi Guys,
Passed through 2 x 2070Super's connected with a Quadro nvlink. They show up in device manager without errors. However, Nvidia control panel doesn't show the option to enable nvlink.
Is this a:Nvidia driver problem?
vbios problem?
Virt motherboard problem?
Peter
-
Trying to get Open RGB to control my rainbow puke. Get an error message stating I need to load i2c-dev and i2c-i801. How do I do this?. Do I add a command to syslynix and reboot?
-
I've got the same problem. The two gpu's show up in device manager, but I can't see an option to enable nvlink in nvida's control panel? How did you fix this?
-
ASUS X299-E II
Excellent IOMMU groups, everything except the sound is in a separate group. 3 x USB controllers passed through to 3 separate VM's without problem.
ASUS 2080ti Advanced Dual
ASUS 2070 Super Dual
Both passed through with multifunction='on' without problem
Sonnet Alegro USB 3
Renesass USB 3Gave up on these cards. Detected in Unraid, but code 10 when passed through to windows 10 VM
Edimax Bluetooth 5.0 Dongle
Got code 43. Resolved by unplugging all other usb devices and installed driver from manufacturers website. Works fine
Creative Sound Blaster X3Works passed through and natively
-
14 minutes ago, ghost82 said:
Strange, never heard of such issue.
But on which bus, and on which machine type?
for q35 you have bus 0, 1, 2, .....x and each bus have slot 0, 1, 2, ...Y.
i440fx is older than q35 chipset, q35 is optimized for pcie passthrough devices, maybe the issue is with your gpu coupled with i440fx.
Sorry, I read your post but didn't take it in. I'm currently running i440fx on all 3 VM's. Would it be better to change to q35 and put VM 1 GPU on bus 1 slot 5, VM 2 GPU bus 2 slot 5 and VM 3 bus 3 slot 5?
-
2 hours ago, ghost82 said:
3. in all vms, a multifunction gpu should have target address defined as multifunction, otherwise it may not work because of the drivers.
I've followed SpaceInvaders tutorial on making sure all 3 functions are in the same slot 0=video 1=sound 2=usb controller, 3=usb port and added multifunction='on'
I don't have any problems doing this until I put them into slots 10 or higher, then I get code 43 errors. Considering slots 1-4 and 7-8 are taken by default it only leaves 5,6 and 9 available for GPU's. Given that I get code 43 errors from GPU's in slots 10 or higher, is it possible that other devices in slots higher than 10 give code 43 errors?. If so, what would be the best bus/slot allocation?. -
Hi Guys, (Space Invader One impersonation)
I know nothing about VM's or XMLing, but I love Unraid. I'm the sought of person who likes to root around under the bonnet when the car won't start and manage to get it going even though I don't know what I'm doing. I'm doing the same with Unraid.
I've noticed that when I create VM's using bus='0x00' and slots higher than slot='0x10' Nvidia throws the dreaded code 43 even though I've placed functions 1 to 3 in the same slot. Just recently I've had a Edimax bluetooth dongle spit out a code 43 error on one VM, but work perfectly fine on another?. The VM with the problems has it GPU on slot 9, I don't know if the USB hub the dongle it plugged into is on a slot higher than 10 or not, but if it is, it could be causing my code 43 problem.
I've noticed that the VM template uses up bus=0x00 slots 1 to 4 & slot 7 for something (don't know what, but all the VM's have those slots) and the VM's use up the following slots:
VM 1 GPU: Slot 5
VM 2 GPU: Slot 6
Taken by all VM: Slot 7
Taken by all VM: Slot 8
VM 3 GPU: Slot 9
I've run out of slots below 10. Can I put VM 1 on bus=0x00 slots 1-6, VM 2 on bus=01 slots 1-6 and VM 3 on bus 0x02 slots 1-6 ?
TIAPeter
-
11 hours ago, ijuarez said:
What is the mobo you are using?
ASUS X299-E II
-
35 minutes ago, ijuarez said:
Do you have a raid card?
Nope
-
Intel Rapid Off. Still looking for USB devices on 11 to 21. Should only be sandisk, asatek rgb crap etc. I passed a USB3 controller through fpr my peripherals
-
Turn it off in the bios?
-
Diagnostic File attached.
Also worth noting, couldn't upgrade to 6.10. Dunno if this USB problem has anything to do wid it?.
-
Hi Guys,
Unraid keeps looking for devices on USB Bus 001 Device 11 to 21 but there aren't any. Why is Unraid doing this?
May 19 22:25:18 Tower kernel: usb usb12-port1: Cannot enable. Maybe the USB cable is bad?May 19 22:25:18 Tower kernel: usb usb12-port1: Cannot enable. Maybe the USB cable is bad?
May 19 22:25:18 Tower kernel: usb usb12-port1: Cannot enable. Maybe the USB cable is bad?
May 19 22:25:18 Tower kernel: usb usb12-port1: Cannot enable. Maybe the USB cable is bad?
May 19 22:25:18 Tower kernel: usb usb12-port1: Cannot enable. Maybe the USB cable is bad?
May 19 22:25:18 Tower kernel: usb usb12-port1: Cannot enable. Maybe the USB cable is bad?
May 19 22:25:18 Tower kernel: usb usb12-port1: Cannot enable. Maybe the USB cable is bad?
May 19 22:25:18 Tower kernel: usb usb12-port1: Cannot enable. Maybe the USB cable is bad?
May 19 22:25:18 Tower kernel: random: crng init done May 19 22:25:18 Tower kernel: random: 7 urandom warning(s) missed due to ratelimiting
May 19 22:25:18 Tower kernel: overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. May 19 22:25:18 Tower kernel: overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off.
May 19 22:25:18 Tower kernel: xhci_hcd 0000:04:00.0: remove, state 4
May 19 22:25:18 Tower kernel: usb usb4: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:04:00.0: USB bus 4 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:04:00.0: remove, state 4
May 19 22:25:18 Tower kernel: usb usb3: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:04:00.0: USB bus 3 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:05:00.0: remove, state 4
May 19 22:25:18 Tower kernel: usb usb6: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:05:00.0: USB bus 6 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:05:00.0: remove, state 4 May 19 22:25:18 Tower kernel: usb usb5: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:05:00.0: USB bus 5 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:06:00.0: remove, state 4 May 19 22:25:18 Tower kernel: usb usb8: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:06:00.0: USB bus 8 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:06:00.0: remove, state 4
May 19 22:25:18 Tower kernel: usb usb7: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:06:00.0: USB bus 7 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:07:00.0: remove, state 4
May 19 22:25:18 Tower kernel: usb usb10: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:07:00.0: USB bus 10 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:07:00.0: remove, state 4
May 19 22:25:18 Tower kernel: usb usb9: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:07:00.0: USB bus 9 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:08:00.0: remove, state 1
May 19 22:25:18 Tower kernel: usb usb12: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:08:00.0: USB bus 12 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:08:00.0: remove, state 1
May 19 22:25:18 Tower kernel: usb usb11: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: usb 11-1: USB disconnect, device number 2
May 19 22:25:18 Tower kernel: usb 11-1.1: USB disconnect, device number 3 May 19 22:25:18 Tower kernel: usb 11-1.2: USB disconnect, device number 4
May 19 22:25:18 Tower kernel: usb 11-1.3: USB disconnect, device number 5
May 19 22:25:18 Tower kernel: usb 11-1.4: USB disconnect, device number 6
May 19 22:25:18 Tower kernel: xhci_hcd 0000:08:00.0: USB bus 11 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:0a:00.0: remove, state 4
May 19 22:25:18 Tower kernel: usb usb14: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: usb 14-2: USB disconnect, device number 2
May 19 22:25:18 Tower kernel: usb 14-2.1: USB disconnect, device number 3
May 19 22:25:18 Tower kernel: xhci_hcd 0000:0a:00.0: USB bus 14 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:0a:00.0: remove, state 1
May 19 22:25:18 Tower kernel: usb usb13: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: usb 13-2: USB disconnect, device number 2
May 19 22:25:18 Tower kernel: usb 13-2.1: USB disconnect, device number 3 May 19 22:25:18 Tower kernel: usb 13-2.3: USB disconnect, device number 4
May 19 22:25:18 Tower kernel: usb 13-2.4: USB disconnect, device number 5
May 19 22:25:18 Tower kernel: xhci_hcd 0000:0a:00.0: USB bus 13 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:0c:00.0: remove, state 4
May 19 22:25:18 Tower kernel: usb usb16: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:0c:00.0: USB bus 16 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:0c:00.0: remove, state 1
May 19 22:25:18 Tower kernel: usb usb15: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: usb 15-1: USB disconnect, device number 2
May 19 22:25:18 Tower kernel: usb 15-1.1: USB disconnect, device number 3
May 19 22:25:18 Tower kernel: usb 15-1.4: USB disconnect, device number 4
May 19 22:25:18 Tower kernel: xhci_hcd 0000:0c:00.0: USB bus 15 deregistered
May 19 22:25:18 Tower kernel: vfio-pci 0000:17:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
May 19 22:25:18 Tower kernel: xhci_hcd 0000:17:00.2: remove, state 4
May 19 22:25:18 Tower kernel: usb usb18: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:17:00.2: USB bus 18 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:17:00.2: remove, state 4
May 19 22:25:18 Tower kernel: usb usb17: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:17:00.2: USB bus 17 deregistered
May 19 22:25:18 Tower kernel: vfio-pci 0000:65:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
May 19 22:25:18 Tower kernel: xhci_hcd 0000:65:00.2: remove, state 4
May 19 22:25:18 Tower kernel: usb usb20: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:65:00.2: USB bus 20 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:65:00.2: remove, state 4
May 19 22:25:18 Tower kernel: usb usb19: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:65:00.2: USB bus 19 deregistered
May 19 22:25:18 Tower kernel: vfio-pci 0000:b5:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
May 19 22:25:18 Tower kernel: xhci_hcd 0000:b5:00.2: remove, state 4
May 19 22:25:18 Tower kernel: usb usb22: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:b5:00.2: USB bus 22 deregistered
May 19 22:25:18 Tower kernel: xhci_hcd 0000:b5:00.2: remove, state 4
May 19 22:25:18 Tower kernel: usb usb21: USB disconnect, device number 1
May 19 22:25:18 Tower kernel: xhci_hcd 0000:b5:00.2: USB bus 21 deregistered
-
You're a champ. Cache mounted and VM running. I'll be able to sleep tonight. THANK YOU VERY MUCH! high fives ;D. If you're ever in Australia look me up, I'll meet up and buy you dinner and a few beers
-
1
-
-
Ok, should I just upgrade to 6.9?
-
Just noticed the cache drives aren't mounted. Do I simply press 'mount' and will I get my VM's and vdisks back?. Or do I need to copy another file from my unraid back up to the unraid flash?
-
Oh my gawd I love you. It's working!
On 6.8.3, I can always update. To stressed to do anymore tonight. I'm going to bed. I'll look at debugging tomorrow. Atleast I can look at log files etc now to see what the problems are?
Pete
-
1
-
-
So, unzip the old unraid to the flash, then copy the current config file to the flash?
No VGA Output (Nvidia)
in VM Engine (KVM)
Posted
Hi Guys,
I am completely stumped. Had 3 VMs running flawlessly on Unraid 6.9. Did a clean install to 6.10.2 with the exception of copying super.dat and plus.key to my config folder. Created a VM like I have a million times before ....and................nuttin, nudda, ziploa. I have:
Used the previous vdisks with a Windoze 10 installed
vbios with the nvidia header removed
Added multifunction='on' after the vbios line in the xml
Changed all functions 0,1,2,& 3 to the same PCI slot
The VMs work when I set them up VNC. Also I note that one core is constantly pegged at 100%
What have I forgotten?
TIA
Peter