Arbadacarba
Members
-
Joined
-
Last visited
Everything posted by Arbadacarba
-
I'm seeing the same thing here.jupiter-diagnostics-20220406-1523.zip
-
Sure... I appreciate the help. jupiter-diagnostics-20220315-0016.zip This is after trying several troubleshooting steps that I performed to write the post in the prerelease bug forum.
-
I think I did, and I think he already replied there Thanks
-
I'm running a pfsense VM with a 2port NIC and an Atheros Wifi card passed through. (I have a slightly unreliable POINT to POINT LTE connection, and occasional mission critical internet requirements - So the Wifi card is set to automatically connect to my cell phone hotspot) I had trouble getting this Wifi card to work with an error message referencing hostdev1 or something not fitting in BARs. I searched, I posted, I got a great answer from Ghost82 who translated the info I had found into the xml: <qemu:commandline> <qemu:arg value='-set'/> <qemu:arg value='device.hostdev1.x-msix-relocation=bar2'/> </qemu:commandline> </domain> This, with minimal fiddling (hostdev0 not hostdev1) worked perfectly. 20220220_2240_pfSense - Cerberus.xml Right up until I updated to RC3. First the VFIO passthrough changed in System Devices, and then after I re-enabled that it still would not boot the VM. But now it doesn't refer to any hostdev id... it refers to it as bellow If I remove the Wifi card the 2 NIC ports get alias' lines, but if I add the Wifi card back in nothing does. Working - No WIFI.txt If I edit the xml to give the Wifi card an alias and put the comandline part back in. WIFI Added with Command.txt I get an error claiming there is no hostdev0 and when I look back in the XML the alias' are all gone. Alias missing.txt Ghost82 suggests editing the XML in the cli but I haven't tried that yet. Would it make a difference? Should it? Has there been some change t the way alias' are handled? I don't understand why they disappear. Thanks for any help Arbadacarba jupiter-diagnostics-20220315-0016.zip
-
Failed sarcasm... Was supposed to show that I fully understood just how unique this question was and that I was in no way surprised that it wasn't foreseen and therefore fixed ahead of time... WOW, I know I don't do sarcasm well... I shouldn't even have tried. Really... that was intended as entirely self deprecating and to express my appreciation for the efforts to make this bizarre use case possible at all. Thanks Again Ghost82 I did try editing it in the gui and did try inserting the alias there... but when I run the VM with the Atheros card connected (?) even the alias' for the other NIC vanish from the XML Arbadacarba
-
So this worked GREAT right up until I installed RC3... What do you mean you didn't see this scenario? There must be 1 of us doing this... So after upgrading I rebooted and my VM would not start. I look and discover that my Atheros card is no longer included in the VFIO I added it back in and rebooted. Then on reboot I get a slightly different version of the message I got before... Only now when I look I don't see an appropriate alias assign to the wifi card. And further if I add an alias, it's gone when I look again after I attempt to start the VM.
-
Thank You for the explanation.
-
So to confirm, there is NO WAY to use Intel Rapid Storage Tech with Unraid? I would love to stripe my NVME drives which I then pass on to a Gaming VM
-
How about just adding a persistent text area to the GUI so that you can insert things? I've had to insert an ARG for my pfsense box, and am not looking forward to it breaking when I next edit the VM and forget the changes.
-
I'm curious if there was a resource you can point me to for the conversion from Proxmox Scripting to Unraid's XML? Or are you a witch? Seriously appreciate your help on this... It worked perfectly.
-
I looked at that and could not figure out how to add that arg to the file... I swapped the Wifi cards and gave it a try. Other than having to realize that the hostdev changed to 0 it worked like a charm Thank You VERY much. Arbadacarba
-
OK, Much like the Poster of that thread I was sent, my problem seems to have lain with the switch... I had reset the switch, so it wasn't a change I had made... But rather a default configuration of the TP-link switch... (TL-SG1016PE) I turned OFF IGMP Snooping and it seems to have stopped the error. Does this make sense? MAybe it has something to do with the multiple Dockers using the same connection? (No, It happened with NO dockers installed) I will take a CLOSE look at my switching tonight and make sure that I do not have a loop, but honestly, I don't think I do (It's behind my server so I can't see it easily.
-
I've looked and looked and only found references to this type of error with regards to passing through NVME drives. I am trying to set up my pfsense VM to connect to a hotspot int the certain event that my point to point LTE connection fails. To do this I want to pass through a Wifi card. I cannot use my built in AX card because FreeBSD does not support current cards. I bought a Ralink corp. RT3090 Wireless 802.11n card and the VM works but my whole server locks up every few days (Working on troubleshooting that currently) So I bought a Atheros card and bound that to VFIO using the System Devices Tool. I see it properly in my VM editor, and can select it and apply, but when I try to boot the VM I get: I've looked and looked and found a couple of references: PCIe Passthrough of Atheros AR9280 (OK, Looks like One reference) I've tried 2 different versions of the same card, both giving the same error.. I've tried tow different slots in my mainboard... I just don't know where else to look. Thanks Arbadacarba
-
OK, Tried something new: I reformatted the USB drive Using the Unraid USB Creator Booted Fresh to a new copy of the OS with GUI and checked the logs (Attached) jupiter-syslog-20220218-2039.zip I also reset my Switch to factory new so there is no Port controlled VLAN And Pulled the 2 port Intel Nic right out of the machine. All still resulted in the error message spamming my Logs... I did take a picture of the Unraid USB Creator configured for my USB drive:
-
During boot I see the following: There are differences between boot sector and its backup. This is mostly harmless. Differences: (offset:original/backup) 65:01/00, 282:e0/b2, 283:43/42, 284:00/05, 303:1a/6e, 304:81/45, 305:37/2a, 306:6d/6c <--Not my numbers... There are a LOT of them Not automatically fixing this (Graphical glitch is caused by the video scrolling faster than my capture) I first noticed this AFTER upgrading my system (Mainboard, CPU, USB key I have: Pulled the thumb drive out and scanned it with Windows (no errors found) Formatted and Restored the Backup Zip File Using the Unraid USB Creator Formatted with a fresh install of RC2 Using the Unraid USB Creator I recorded the boot, but none of this stuff shows up in the log. I was worried that something was wrong with my USB disk, or my install, but now that I'm seeing it on a fresh install... I'm curious if there is something wrong with the Unraid USB Creator? And if there is a way to fix the problem? jupiter-syslog-20220218-2039.zip
-
Yes, I had read that... I assumed that since the NIC was passed through to the VM (and the VM service is off) that it should not be interfering... I disconnected the two network cables that work with the pfsense box from the server (from ~420pm to 7pm) and still got that error... Along with a bunch of complaining about not having an internet connection (I assume) jupiter-syslog-20220216-0022.zip
-
I think I found the solution to my specific problem and thought I would post it here in case any one else is fighting it... Scenario: I'm booting a vm from an ISO in order to manipulate (Acronis, Paragon Disk Manager, etc.) physical hard drives plugged into my system in a dock. Problem: I have to edit the XML file every time I add a drive because the drive order changes to the 1st HDD preceding the "CD" drive. Solution: I renamed the .iso to .img and mounted it as the primary dard drive in the VM. Further: Is there a way to mount a share as a drive? Hope someone else finds this useful. Arbadacarba
-
Feb 14 21:52:45 Jupiter kernel: br0: received packet on eth0 with own address as source address (addr:a8:a1:59:89:af:49, vlan:0) I get thousands of these messages a day… I’ve looked through several pages of questions on the forum, and nothing has rung true as a solution. Notes: Running 6.10.0-rc2 Not Bonding any NICs I am running pfsense in a VM, so there are mutlitple cables going from the server to the switch, but they have different IP addresses… No special configuration on my switch that I can find Attempted so far: I tried shutting down the Docker and VM services… but still got them. I disabled bridging, and they seemed to stop, but as soon as I re-enabled bridging they were back… I’m fairly close to throwing in the towel and reinstalling everything from scratch. Thanks for any help jupiter-syslog-20220215-0300.zip
-
Hahaha.. I've spent the last 6 months double nat'd and just noticed that my external IP matches what it's supposed to be... I quickly try to check with MyServers and... Oh well... I'll check back later... Arbadacarba
-
Forgot to include the answer to the where I'm seeing that question: Pops up when I try to start a VM that uses any virtual NIC. OK, found some more info... When I rebooted things worked until I tried to run Transmission-VPN... Where the logs show a problem creating tun... Starting container with revision: e7bda4030dfcc1ba5bb86fa53373e4f796f5c45b Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists if I delete tun then Transmission starts to work but I lose the ability to start VMs. Yes... I did this yesterday... probably should have mentioned that.
-
So I'm attaching a diagnostic, but in fact the problem went away with a reboot. Thanks Squid. I didn't realize just how huge and bloated my logs are... Log.txt
-
I'm running into this all of a sudden... Was there ever a solution? I've found two specific references in the forums but no replies...
-
Even just the ability to clone the configuration and give it a new name... I do this routinely when I'm resurrecting a clients dead drive. I plug it into my USB or Drive Bay (Hot Swap) and boot the machine up with a standard configuration and attach the physical drive to the VM
-
I currently have a Samsung 980 Pro that I pass directly through to my Gaming VM I picked up a second 980 Pro (I haven't opened it yet) and wanted to add it to my system and use Intel Enhanced RST to run the two drives in a stripped raid passed through to the VM. I tried it first using my 980 Pro and an Intel 600P. I don't expect good results from this mismatched pair, but I wasn't expecting what I got. I created the Array in BIOS and it made a slightly larger drive than the 1TB drive, but when I boot into Unraid I don't see the drive at all... Has anyone tried this? got it to work at all? Thanks
-
I run pfsense in a VM and there are definitely times that I would find it usefull to take down the array without having to lose my router. Currently it's located on the cache but I would move it to the NVMe drive in an instant if this would work. I don't do it often, but there are times I seem to have to do it many times over a few days.
