jonp

A feature we are considering REMOVING at some point in the future of unRAID 6 would be that of spin up groups. This feature was originally designed to combat an issue specific to the use of IDE hard drives that are no longer prevalent in today's computers. The poll question here is to ascertain who, if anyone, is using this feature today and if so, for what purpose. Please provide your feedback and if you do use spin up groups, please let us know how they help you! Thanks!

Shouldn't be. Can you review BIOS settings and let me know what options exist for on board graphics or anything graphics related?

In an effort to streamline the development of unRAID extensions (Plugins, Containers, and Virtual Machines), we are changing the way this board will work. Instead of allowing anyone to post in here, we will be promoting certain member accounts to the group of Community Developer. Only forum accounts belonging to this group will be able to post in this forum (both new topics and replies). Regular forum members will be allowed to view all the contents of this board and its threads, but will not be able to reply. If you are contributing work to the community in the form of containers, virtual machines, or plugins and are not in the Community Developer member group, please send me a PM. Thanks everyone and I will sticky this thread soon.

Still is, just not ready to address that just yet. Still bigger fish to fry.

Correct, lxc isn't something I think we'd ever consider. Seems like there would be a very niche fit for this and not worth the implementation effort.

Gotta be honest, if someone wants to submit a pull, by all means, we would consider implementing it. But if not, its probably not going to happen anytime soon.

It wouldn't decrease. Let's say the move failed half way through because the target disk filled up. You wouldn't want to lose the file, right? A move operation is really more like a copy then delete.

Advanced view when editing or adding a container. Put it in the extra parameters section.

Shutdown your system and then plug your flash device into a PC and run a check disk, repairing any errors found.

Small correction, you don't even need to actually remove the container, just update the extra parameters section of the existing one and save it.

Yes sir cause i cant get it to work, please post What can't you get to work?

Please attach diagnostics file. From under the tolls -> diagnostics page.

Assigning physical NICs to VMs is still not officially supported and won't be for unRAID 6.0. This guide is for advanced users that want to do it anyway, at their own risk. There are multiple reasons why which I have spoken on here before about. This pertains to SATA and USB controllers as well.

Click the name of the VM on the VMs page and a section will expand underneath the VM showing the size of the vdisk. Click that size and rename it to your new size, then press enter. Should do the resize command for you pretty easily.

I probably don't know enough to answer that properly but I believe we should have some basic rules regarding plugins. I'm sure you do already. Compliance really. If you create a plugin, just make sure it has all the libs/apps to make it work properly. If we don't start off that way then we will all be installing extras and not adhering to what unraid is trying to be for the basic user. Automated and easy. Hope that makes sense. Well that's not how plugins work explicitly, it ideally, we shouldn't be installing packages that won't work because they are missing another component. This just slipped by us as we are plugging through the RC phase, but we will fix this at some point soon. You guys are doing an excellent job! Who ever is piloting the ship I take my hat off to them. I understand things will always slip by, especially in beta/RC time lines. I already bought two PRO keys, so I'm dedicated. We all share the responsibility in manning the helm from time to time and we all take ownership of any issues caused along the journey. Team effort here all the way. Thanks for the support btw, means a lot.

I probably don't know enough to answer that properly but I believe we should have some basic rules regarding plugins. I'm sure you do already. Compliance really. If you create a plugin, just make sure it has all the libs/apps to make it work properly. If we don't start off that way then we will all be installing extras and not adhering to what unraid is trying to be for the basic user. Automated and easy. Hope that makes sense. Well that's not how plugins work explicitly, it ideally, we shouldn't be installing packages that won't work because they are missing another component. This just slipped by us as we are plugging through the RC phase, but we will fix this at some point soon.

A nice benefit of btrfs pooling on unraid. In a normal raid array, that'd be 128GB.

So a separate plugin for python than the nerd pack?

You're using my setup. What kind of SSDs you have? I have 2 x Sandisk 512GBs and 1 x Corsair 256GB. 3x 128GB Kingston SSDNow So usable capacity of 256GB?

@reluctantflux. Yes to your 240GB limit. You could add another ~250GB SSD and then get ~500GB of usable capacity in a 4 disk pool configuration.

We will have to add python to it at some point.

You're using my setup. What kind of SSDs you have? I have 2 x Sandisk 512GBs and 1 x Corsair 256GB.

Running vdisks off the array isn't actually too bad, but not during the installation of the OS. If done during installation, the install will take a LONG time, as it is being bottlenecked in write performance. Post install, VM performance is still not very good, but it really depends on what you're doing with the VM. For localized virtual desktops (where you pass through a graphics device and attach monitor, mouse, and keyboard to the VM) will highly benefit from their vdisks living in an SSD-backed cache pool.

Hey this is pretty slick! Nice work! Will need to give it a try.