jonp
-
Posts
6,442 -
Joined
-
Last visited
-
Days Won
24
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by jonp
-
-
The 1 year limit is only in reference to how frequently you can swap the USB flash drive for a new drive. Just keep using the drive you have and all should be fine.
-
13 minutes ago, xaositek said:
Hmm well I tried this and didn't really care for the need to expose port forwarding... Now I'm stuck with the cryptic Unraid.net DNS hostname even when I've signed out and remove the plugin.
How can I go back to local hostname and that's sufficient?
Edit: Figured it I could go into Management Access and set Use SSL / TLS to No and it set local DNS names back into effect.
Keep in mind you only need to do port forwarding for remote access. Local network access secured by ssl does not require port forwarding.
-
Hello Unraid Community!
Today we're excited to give you a sneak peak at something we've been working on for quite some time. A new feature we like to call My Servers.
"My Servers" is designed to extend the value of your investment in Unraid by enabling you to more easily connect, share, monitor, and access your systems. For the initial beta launch, we are focusing on the following key features:
Secure Remote Access
Whether you need to add a share, container, or virtual machine, do it all from the webGui from anywhere and at any time using using HTTPS. Best of all, all SSL certificates are verified by Let's Encrypt, so no browser security warnings.
Online Flash Backup
When your Unraid configuration changes, the new settings on the flash drive will automatically be backed up to Unraid.net, enabling easy recovery in the event of a device failure. Never self-manage/host your flash backups again!
Real-time Monitoring
Get quick real-time info on the status of your servers such as storage, container, and VM usage. And not just for one server, but all the servers in your Unraid fleet!
License Management
Download any registration key linked to your account. Upgrade keys to higher editions. In addition, Trial keys are now downloaded automatically. Simply sign-in!
Installing
For the full details on how to install and configure, check out the wiki.
-
15
-
2
-
-
In addition to the public availability of the My Servers plugin, we also wanted to let everyone know about our new Unraid Community Discord Server! As great as the forums are for providing support and long-hand conversations, sometimes you just want to chat with someone in real-time. Discord gives us that ability and is just another great way to communicate.
If you're not familiar with Discord, you can create an account and download their apps at discord.gg. Once done, you can join our discord server using this link:
Please note that we do require you to link your Unraid.net forum account in order to join our discord server. Your username will be automatically set to match your display name here. This is done in order to prevent impersonation of other community members. No exceptions will be made to this policy.
We intend to do more and more with Discord over time, as it is a powerful platform with lots of intriguing possibilities for our community. Join today and be a part of the conversation!!
Also we want to give a special thanks to the guys who are running the Unofficial Discord Server @Roxedusand @GilbN (and if I'm missing anyone else, please forgive me). They were fantastic in helping us and the community and will be moderators in our server as well.
-
11
-
1
-
-
-
Thomas is providing a workaround to the issue you're reporting. The real issue here is that we don't support manual VNC ports in the current version of Unraid. You can obviously override things using the XML editor, but any changes made there could be lost when further edits are made using the form-based editor. I realize the value of being able to set a VNC port and will make a request to the dev team for us to add official support for manually setting VNC ports using the form-based editor.
All the best,
Jon
-
Hi @Fizzyade, this is going to be a tough one to solve. I personally haven't seen any issues with virtual display adapters throughout testing the 6.9 series, and without more details, I really can't say why this is happening. Do you see any messages in the server or QEMU's event logs? What about Windows? Are you using QXL drivers or no? Latest VirtIO drivers in use? If this is an issue with QEMU, then the best we can do is let the QEMU developers know about the bug. We don't actually build the virtualization technology ourselves here at Lime Tech. We leverage open source KVM / QEMU, which means issues relating to those components will have to be fixed by those developers. Lastly, please report back after updating to 6.9.1 and let us know if these issues persist.
-
4 hours ago, Fizzyade said:
And still no reply. Seriously? I called you out on poor support, you tell me to email, which I did on the 24th of Feb and I still get no response.
This is my fault, not Spencer's. He did inform me that he wanted us to take a closer look at your most recent support threads. Between the devs working towards the 6.9-stable release and myself being busy with a few other internal projects, this just slipped through the cracks and for that, I do apologize. I am looking at your issues regarding VNC port mapping not sticking as well as the virtual display adapter. It would be helpful if you updated those posts with results after testing with 6.9.1 that was just released, as sometimes kernel/package updates fix these types of problems.
-
3
-
-
Hi there,
Can you try replicating this issue on a stock setup? You have a number of plugins installed. Please boot either in safe mode or remove all plugins first. This will help us narrow down the cause.
-
Just an FYI guys, we are aware of this issue and plan to have a fix in for 6.9.1.
-
3
-
1
-
-
Hi there,
Can you please attach your system diagnostics to this thread (preferably taken right after you attempt to install a plugin).
-
Sounds like you might be a good candidate to be a guest on the show!
-
1
-
1
-
-
Hi there,
Unfortunately I really have no ideas on how to guide you purchasing hardware from that far back. I wish I could give you a bulletproof answer so you can buy with confidence, but short of us purchasing all that gear and testing it ourselves, I can't guarantee anything. You'll just have to do some research and decide for yourself which is the best option at this point.
-
Hi there,
Sorry to see that no one has replied in here. One thing that I would ask you to try first is to boot in safe mode, which will disable all plugins. See if you can recreate the issue there. If so, stop all VMs and containers and see if you can reproduce the crash. Then slowly turn services on one at a time until you find the culprit. Its got to be either a plugin or a container or its very likely a hardware issue.
-
Thanks for letting us know! I've got the link updated in the wiki now.
-
1
-
1
-
-
Great feedback! Keep it coming!
-
1
-
-
What system on your network has IP address ending in 222? I see nginx is rate limiting that client from connecting for some reason. Curious if you have a rogue machine on the network just hammering your server.
-
Can you try creating the VM using OVMF instead of SeaBIOS and see if the issue persists?
-
1
-
-
Hi there,
We do not have explicit UI support for specifying which interface should be "primary". However, setting up the bond involves loading the bonding kernel module. If running latest 6.9 release, you can specify which interface to set as primary using this method:
Create a file on the flash: config/modprobe.d/bonding.conf which contains the single line:
options bonding primary=eth0
(You might need to create the 'modprobe.d' directory.)
Then reboot. Of course, instead of eth0, specify eth1 or eth2, etc. depending on which interface you want to be primary. After reboot you can check if it worked by typing this command:
cat /proc/net/bonding/bond0
You should see the selected interface show up as "Primary Slave".Let us know if you try this and have any issues (or successes)!
-
2
-
3
-
-
Hi there,
Sorry to hear you have to wait so long to get the replacement board. Hoping everything works out for you! As far as where to install the SATA controller, I would NOT use the first PCIe slot. I would use a secondary slot as you will not saturate PCIe 16x speed for storage anyway. A GPU is better suited in that primary slot. As far as recommendations on HBAs, you should check out the hardware forum: https://forums.unraid.net/forum/9-hardware/
-
As of right now, using unassigned devices or pre-clear aren't things that we at Unraid developed ourselves, so you'd have to look to those plugin authors for any support on issues related to their usage. We do have plans with 6.9's upcoming release to support multiple pools natively, which means you wouldn't need to use the Unassigned Devices plugin anymore for those download disks. In fact, you could just put both into a btrfs raid 0 if you wanted and then create a vdisk on them that utilizes the combined capacity of the two devices.
If you could replicate this behavior where the OS is configured using standard tools, we could have something to investigate. All of that being said, this is likely something unique to your hardware / configuration as I know there are plenty of users out there leveraging preclear and Unassigned Devices without issue. Another thing that would help is if you attached your system diagnostics to this forum thread so we all could see the OS configuration you have.
-
Hi again,
Wanted to check in on you with regards to this issue. For the NAS3200 box, I would suggest running the New Permissions script under the Tools page. This will fix any permissions that are out of whack. I would probably do the same on coraid just in case there are permissions issues within the individual folders of the shares. That's a good way to make sure that permissions are set correctly. This will take a while to run as it has to touch every file in your system.
As for the server that won't shut down gracefully, are you saying that since you accidentally yanked the stick out, that server has NEVER been shut down? Not even just a manual poweroff? If so, you are going to need to hard power off that system and plug the flash back in and try to boot. If that doesn't work correctly, you'll need to try repairing the flash drive on a Windows or mac computer in case there are damaged files inside.
Did your data replication job complete ok at this point? Let me know where things stand so we can continue.
-
Hi Brent,
I'm honestly at a loss here. I don't see anything glaringly wrong in your system logs, but I'm also unfamiliar with the kind of network setup you have. Can you give us a brief overview of how your network is configured? Seems like something must be amiss in the network configuration otherwise I'd expect to see this behavior with a much larger quantity of users.
-
As jonathanm stated, trying all the various inputs is another way to go.
Another thing you can try is to get the VM fully set up with VNC graphics. Then install some type of remote desktop client in the VM. Then switch the VM from VNC graphics to your NVIDIA card and start the VM. Even if the monitor is still black, you should be able to connect in to the VM using a remote desktop client (either teamviewer, realvnc, or any other platform you're comfortable with). From there, you can see if there is an issue with the driver loading or not. If the card shows present in device manager and driver loaded, but the screen is still black, again, try what jonathanm suggested by utilizing the different inputs.
If none of that works, I really don't know what to tell you from here. Clearly we have an insane amount of users that are utilizing GPU pass through in VMs. There are countless youtube videos of folks having great success with this. I really don't know what's unique or wrong with your setup to prevent you from making further progress. I feel like you're problem missing something somewhere. Did you try enabling the VFIO allow unsafe interrupts option on the VM Manager page (turn on Advanced View in the top right to discover that)? I doubt that's the issue, but if it is, you'll need to turn that on, reboot, and try again.
UEFI booting the base OS has been known to cause issues with VMs and GPU pass through, but now that you are in legacy boot mode (which btw, you need to configure in your BIOS as well), everything should be working.
As a last resort, if you want to schedule a services session with us, you can do so here: https://unraid.net/services but I warn you, there are no guarantees that we can get it to work, but if you want me to remote into your environment and give it a whirl, that is the method we offer folks to schedule a session and it's not cheap ;-(.
Am I misremembering or didn't you say you had a friend that is using the same exact hardware/setup and not having any problems? Maybe give them a buzz and have them come over to review your setup?
Help!!! (I cannot get windows vm to run)
in VM Engine (KVM)
Posted
Hi again,
Seems like you're just destined for problems with this setup! Whenever you make a hardware change like this and need support though, you always need to attach a new copy of your system diagnostics. The issue you are experiencing now is different than what you originally experienced, so you need to get us new diagnostics so we can analyze. There are a few things that could be going on here, but without that zip file, we cannot analyze.