nars

Yes, that's why I told you to use my mirror links on my post(s) signature I just posted the wiki link so you could confirm the file md5.

@Fuggin: You can get it at my mirrors on my signature and you can confirm md5 with the one at: http://lime-technology.com/wiki/index.php/Release_Notes

Indeed But you can just disable that passing biosdevname=0 as boot option on install.

@HAVOC: Guess you installed some plugin(s) incompatible with unRaid 6.0 that probably installed 32bit slackware packages on your 6.0 (rsync and smartctl at least) ... ? Remove the plugins or any old packages on extra folder and it should fix it.

It refers to this issue: http://lime-technology.com/forum/index.php?topic=27783.0

I did noticed same yesterday when compiling vbox, I had to force re-installing glibc with 'installpkg' instead of 'upgradepkg --install-new' to get full package installed... is this a correct thing to do?

VirtualBox 4.3.6 package for unRaid 6.0 beta (64-bit): http://nars.aloj.net/temp/unraid/vbox-4.3.6-unRAID-3.10.24p-x86_64.tgz Note: to use it with the VirtualBox plugin you may need to remove the '-x86_64' suffix on the package filename or the plugin may not like it... @theone: is the suffix a problem? can it be sorted? also if you are going to do changes on the plugin could you please also make it support .txz packages? as it does an huge difference in package size... Also I did updated my 'buildev.sh' script to support unRaid 6.x, detecting it and getting the right slackware 14.1 packages.

@limetech: next beta please create '/var/log/setup/tmp' dir like for 5.x, if you remember, when installing some slackware packages seems they need it.

Found this on a quick search: http://serverfault.com/questions/555641/settings-kvm-on-atom-processor

@hoek: If you are referring to the steps/scripts I did posted some pages back, vboxpkgc.sh script maybe doesn't need any changes but buildev.sh will surely need some changes, at least to get proper Slackware 14.1 x64 packages for unRaid 6.0 instead of Slackware 13.1. I will soon test unRaid 6.0 on a VM and may check what changes needed on these scripts, but as you said KVM will be surely a better option on unRaid 6.0, when all ready for it.

As promised, and seeing that lainie isn't still updating his packages, here is my own compiled package for VirtualBox 4.3.6, with modules compiled on unRaid 5.0.5: http://nars.aloj.net/temp/unraid/vbox-4.3.6-unRAID-3.9.11p.tgz

Ok, thanks

I do have same problem, would like to benefit the discounted key but not sure about a pen/card reader for it yet... no way we can purchase it with no guid assigned for now and email later (like for 2nd key, when purchasing 2 keys) ?

Thanks Edit: Upgraded my server to this version, did some basic testing and all seems ok so far.

You mean one usable for 5.x and one for 6.x, right? +1, but to make it simple I would just keep 'extra' as-is for 32bit and use maybe just a simple 'extra64' for 64bit... Also keeping them separate would allow easy setup multiboot 5.x/6.x on same flash, useful for testing at least Couldn't it be easier to maintain one single .plg file (with proper simple script checks added for unraid version, to install the right packages for it, etc) and just add some xml tag on the plg file specifying compatible unraid versions (if no tag present take it as 5.x compatible only), and when trying to install an incompatible plugin just ignore it...? that would still prevent installing incompatible plg's and make it possible a single .plg file to be maintained, compatible with multiple unraid versions (even thinking on future... yet newer unraid will hopefully eventually come again, based on an yet newer slackware or other distro, etc that would require yet different packages again even if also x64...) I mean something like firefox plugins minver/maxver compatibility check or similar... Anyway I do also surely agree with some way of .plg separation, even if just file extension based.

@grumpybutfun: suggestion for your next guide (that could complement this one): how to setup an iscsi server on unraid (stock slack based one ) and be able to boot a full windows install from pxe and running from a remote iscsi drive (stored on unraid server as an hdd image file). I have some pages bookmarked about doing it but had no time to fully go though them yet

I did already had similar questions to myself about this before... even writing a big file on an fully empty file system I do also get some "reasonable" (in the thousands for something like 10GB) number of extents. Wasn't it supposed that a non fragmented / contiguous file have just 1 extent?

Your last step should be: cp vbox-4.3.6-unRAID-3.9.11p.tgz /boot/config/plugins/virtualbox

Wait... there is something wrong then... as my script do not create package with that file name, I guess that is the virtualbox file you downloaded from virtualbox site? not the created package - that one should be created as vbox-4.3.6-unRAID-3.9.11p.tgz as theone pointed. Then I guess your mistake was the last 'cp', you did actually copy to the flash the file you downloaded from virtualbox site and not the created package.

Yes, but I'm guessing his problem may be the plugin doesn't know it needs to load the new package version - with different file name - that he did manually copy to the flash... I don't use the plugin myself then not sure how this is done to make the plugin use a different vbox package file, but you can surely help him on that.

Guess you need to somehow "let the plugin know" what package file it should load at startup?

Did you got some error or something while creating 4.3.6 package?

Yes, it should work. Only if there are some big changes on vbox or unraid they should require changes. No. Unraid runs on a ramfs, loaded from bzroot file at every boot, any changes to this filesystem (in this case installing development tools, etc) will "disappear" after reboot.

So it wasn't my fault I couldn't get the server running? Phew! Sent from my Nexus 7 using Tapatalk 4 No. It's all stated 1 or 2 pages back on this topic

As said before on this same topic lainie's 4.3.4 package for 3.9.11p is broken, it will not work, and lainie seems too busy to fix it at this moment. I did "compiled" vbox 4.3.4 myself on unRaid 5.0.3, I think it should also be ok for 5.0.4 since same kernel and minor config changes on it apparently... if you want to try it: http://nars.aloj.net/temp/unraid/vbox-4.3.4-unRAID-3.9.11p.tgz Else you can use these simplified steps/scripts to "compile" it yourself: http://lime-technology.com/forum/index.php?topic=25099.msg274366#msg274366 I didn't bothered to upgrade unRaid to 5.0.4 yet, since nothing really new on it that affects me, I'm waiting 5.0.5 that should be out soon apparently, and will then "compile" new vbox 4.3.6 on it and upload new package if lainie still busy to care about this.