BetaQuasi

I no longer run an ESXi setup, I'm running bare metal and have moved my VM's to KVM.

I know it's very easy to update your VMDK's yourselves, but if anyone wants to host a v6 final VMDK, I can link it from the first post. Would be good for anyone 'new' to it all!

I've moved Plex servers around quite a few times now and always kept the base config and metadata (re-doing my library takes waaaaay too long!). The steps for doing so are here, obviously not all are relevant in your scenario, but specifically the red note about the Plug-ins folder will be. If you can, I'd go back to a state where I had the unRAID plugin version working, then back up the Plex Plugins folder, delete it, and try and get your docker going. https://support.plex.tv/hc/en-us/articles/201370363-Move-an-Install-to-Another-System

Great stuff!

PS/2 keyboards pretty much always require to be plugged in prior to starting up in order to initialise in my experience. I don't think you have any issue with your drives... by the looks of your terminal output, it simply failed to create the bootable portion of the USB drive successfully, and that's what you're seeing when it tries to boot up... that error message is fairly typical of not being able to successfully find anything to boot from. I'd have another crack at running the make_bootable script and copying over your config etc again, and booting up from there. Perhaps even try doing that step from a different PC.

Hi Phaze - just a quick note, I believe you said you were considering doing a nzbget plugin at some stage? I just wanted to point this thread out: http://lime-technology.com/forum/index.php?topic=12188.msg373578#msg373578 Looks like it may have gotten a hell of a lot easier? (PS this is not me asking for the plugin again, rather just hoped to share in case you were looking to work on it and weren't aware of what might be a huge shortcut )

Brilliant! Hopefully this will make it much easier for Phaze to put his plugin wrapper around it too, might drop a note in his thread as I believe he was looking at doing a plugin for nzbget eventually.

Yes it appears you can convert VirtualBox -> KVM. I'd keep a backup just in case (which you should always do regardless!) and take a look here: http://cheznick.net/main/content/converting-a-virtual-machine-from-virtualbox-to-kvm The only required line is the convert to raw image command using vboxmanage. You can then convert to qcow2 if you want to save space. You will then be able to set up a VM using that existing disk and off you go. Plenty more info on the forums here on how to achieve that. Ignore that final step completely (executing KVM), as you will do all that from the web interface. Also, note KVM and Docker are two different things.. KVM is the virtualisation platform, which is what you need to run actual VM's.

Yep.. run the latest v6b15 and use KVM.

So I've upgraded, and followed the first post (i.e. removed dmacias' old libvirt and vmmanager plugin.) However, the new VMs tab is not showing any of my existing VM's. The xml's were successfully copied across and I can see them in /etc/libvirt/qemu as per below: Any ideas? Have tried multiple reboots etc EDIT: Ignore, VM's were 'off' in Settings -> VM Manager. Not sure if that's supposed to be the default, but switching it on and rebooting fixed it.

Not sure sorry, I have a 2013 rMBP and use SMB regularly with unRAID. No such issues.

This will be the issue.

Out of interest, I did this same update on my server, and have the same RAM as you. I did not experience this issue. I know that doesn't help much... hopefully Supermicro can assist you!

What Squid said, just point it at your user share /mnt/user/tv or whatever

Looks like you're using a SNAP destination for your app data? (/mnt/disk/....) Is it possible this is because the plugin is starting before SNAP has mounted the drive? I'd use your normal cache drive (eg. /mnt/cache/appdata or similar, set to cache only) and see if it works fine there. If so, it's not the plugin, and therefore not an issue for PhAzE.

Regardless, my point is that you're targetting the flash disk as the source of the problem, when it's actually RAM... which is why your workaround resolves the issue. Agreed, I'm not using a remote destination, and I daresay most use cases, people don't use a remote destination.. which is why this wouldn't have come up before. If you look through the forums, most people use rsync for remote destinations.

/tmp is in RAM, perhaps you are running out of the allocated ram disk space, in which case I suspect adding more RAM would resolve this for you. I haven't experienced this particular issue myself, I regularly use mc to move a large amount of folders around on drives.

When I had this same issue, my 'appdata' share (the cache only share for app install data) had changed to yellow somehow (i.e. the colour of the ball that shows there is data pending move to the array). No idea how... had to find the files from appdata that it had moved to the array and remove them so that the ball returned to red (mover hadn't actually removed them from appdata), then stop/start array and restart plugins and everything worked after that. Also not 100% sure why this would impact 'free space'.. there was still 200+Gb on the cache disk... but there it is.

If Overbyrn has indeed stopped working on his, I'd love to see a NZBget plugin! I'd be happy to donate again to help proceedings

While what you've created should be fine, the recommended method is to create a cache-only share for holding your application data. You would then point those folders to that share. An example might be /mnt/user/appdata/plex/libraries and /mnt/user/appdata/plex/transcode if you created a cache-only share called "appdata"

They have on board video, just a very simple chip. Enough to run a screen off.

This is also my most wanted feature, and I would be willing to pay for it.

Thanks mate, I'll update the OP once you have it up there.

Are there routes between the two subnets? (If you don't know the answer to that, can you ping a device on 192.x from 10.x?). If so, then yes there should be no issue... run up dnsmasq and then change your DHCP servers on both subnets to hand out your unRAID server for DNS (and something else for secondary, eg. 8.8.8.8 for google, or maybe your ISP's DNS server.)

FYI to all, issue has gone away on latest beta with Chrome.