To allow me to use my UNRAID server to upload data into databases I built a OpenJDK Java Docker. The Docker runs a script which executes a Java program. I am not sure if this how you are supposed to use Docker, but it works nicely for me.
Quick video on what I use my UNRAID server for. I introduce using the UNRAID to serve the Neo4J database that runs some network visualisation for the website Algorithmic Indexing. Neo4J network visualisations form an important part of my academic research.
I have more or less stopped fiddling with my UNRAID system. Upgraded to 128GB of RAM and another nvme m.2 drive in the cache. I need the GPU and then loads of the HDDs and I will have a great UNRAID system for my needs.
UNRAID build log! Building my new UNRAID server with Chinese X99 dual CPU motherboard from eBay, its the ZX-DU99D4 V1.11. Two Xeon E5-2650LV3 and 64GB of Ram (both used of eBay). This will be a great base system for playing with VMs and dockers etc in UNRAID, as well as running backups.
I settled on using two CoolerMaster 92mm Hyper H412R Compact Intel/AMD CPU Coolers. Which fit fine if you off set the fans a little.
I am building a direct attached storage (DAS) case that I will attach to my workstation using an external SAS card. External RAID DAS cases for SAS drives are not cheap so homemade it is! So far I have been assembling the parts, I have the drives, case, and lots of wires. I will do a more in depth video of the whole process later. You could use this as part of a NAS if you wanted.
I decided to replace a bunch of external hard drives with an UNRAID server. Setup to work with rsync and backintime backup software for Linux. Managed to sort out an error with rsync and the samba shares not liking files that start with “._”. This is a great use of my UNRAID system.
I have the base components of my new UNRAID server. I got a Chinese X99 dual CPU motherboard off eBay, it’s the ZX-DU99D4 V1.11. Which I will be running two Xeon E5-2650LV3 with 64GB of Ram (both used of eBay). This will be a great base system for playing with VMs and dockers etc in UNRAID using the ZX-DU99D4, as well as running backups.
Quick post on how to get Lightworks running on Opensuse Leap 15.2 as I ran into a few problems. I discovered that Opensuse Leap 15.2 is not officially supported by lightworks however it was relatively simple to get it working. The error I was getting was because the glibc version installed by Opensuse is too old. I think it is something like version 2.26 and lightworks needs version 2.29 or above. Why the version in opensuse is so old I do not know, we are on version 2.33 I think.
So what I did was download the rpm of version 2.33 from here, and extract it as an archive. I then found the required library that lightworks needed, “libm.so.6” which is a simlink to “libm-2.33.so”.
All that was then required was to copy both of those files into “/usr/lib/lightworks/” as that is one of the first places that lightworks looks for libraries. This seems to have solved the problem. I did not install all of glibc 2.33 as I think this would have caused problems elsewhere, and it seems that this is the only missing library that lightworks needed.
I have recently setup a secondary server using Unraid to run backups (including with BackInTime). (I will do a full post about it at some point.) I will use this server as a BackInTime server for my Linux workstation, and the Time Machine server for my Mac laptops. Getting it working with the Macs was a bit of a pain, but I got there in the end. But today I shall talk about getting it to work with BackInTime, which I think I have now done.
I ran into a problem thar the standard rsync configuration used by BackInTime was not able to copy files that started with an ‘_’ from the workstation over to the smb share on the Unraid server. This was because when rsync made the temporary ‘._*’ file it would fail as smb doesn’t allow that file name. This was a problem because some of the software libraries that I was using for projects have files that start with ‘_’. So the result was that the snapshots were missing those files and completing with errors. Not ideal. The actual number of files that this affects is fairly low and I could probably live with it, but really it would be better if a solution could be found.
It turned out that the solution was fairly straight forward in the end. I had to disable the vfs objects fruit and streams_xattr for the share. Then it worked perfectly. The problem is that unraid sets those automatically for each share. So I have to manually delete them, and then restart samba each time I reboot the server. Fortunately that will not be very often.
Still, it would be better to find a more permanent solution. I am currently looking for that, and have posted to a couple of forums to see if anyone knows if it is possible to have custom settings for a share that are not overwritten each time the array is started.