Leaderboard

Oh yes, these are definitely my kind of people!

I only came across DietPi a day or so ago which seems a interesting rpi project that is easy to install using Kvm after a few procedures. First go to https://dietpi.com and download their Vmware vdmk image to your Unraid machine. Then we need to convert the image to a qcow2 image using qemu. To convert the image use the following command and adjust paths and file names accordingly. qemu-img convert /mnt/user/isos/DietPi_VMware-x86_64-Stretch.vmdk -O qcow2 dietpi.qcow2 Once the file is converted which should take not to long we need to make a linux vm template using seabios and for the first drive set to manual and point to the qcow2 we just created and set that drive to sata. Set ram and cpus as you require, save and boot. here is a working vm template with instructions from above. Dietpi seems to offer a lot of packages/software from the installer, i was surprised at what was available and also just being able to run a rpi image without any hassle seemed cool.

The automatic video converter and hooks run under a non-privileged user, so killing process id 1 won't work. However, since exiting HandBrake also terminate the container, this should work: killall -sigterm ghb

Most of your disks are also old and you are running them at very high temperature - above 50 and even 55 degC (and even higher in previous power cycles). Keep this in mind.

Unfortunately, viewing signatures is disabled by default on this forum. At the upper right on this (or any forum) page, click on the dropdown beside your name and go to Account Settings to turn on signatures and also set your own sig if you want.

Updating the BIOS should be your first resort. In fact every few weeks you should go to your board manufacturer site and check for new updates and pry to the computer gods that they keep releasing new updates.... Just RTFM first and then follow the procedures strictly - and make sure that if there is a jumper or switch to enable / disable the flashing you use it and then you disable it back, as the UEFI chip can be a desirable home for very nasty computer viruses/rootkits.

It's not based on a timeout, and it doesn't restart the container, it checks to see if the rtorrent process is listening and also that the process is present, so you can't really change either of these. Sent from my EML-L29 using Tapatalk

Nginx is not listening on port 80 by default because mapping port 80 is optional for this image (unless you're doing http validation) The readme states that listening on 80 for http and redirecting to https can be enabled in the default site config

Not sure if this will help anyone, but a discord group I'm part of, Tronyx reported this helps when having this specific issue.

Not sure if this is just a random artifact or if it's supposed to be there. Seeing it in Safari and Firefox.

Don't put your server direct on the internet! I don't get it why people thinking it's an good idea to have Unraid facing directly to the internet.

Norco 4224 case 9x 6TB 6x 4TB 2x 500GB SSD 1x 1TB SSD Intel® Core™ i7-5820K Asus X99-DELUXE 32 GB DDR4 Nvidia P2000 3x LSI 9211-8i This has been updated a little since these pictures were taken. I'll update here when I take new pictures.

It's running pretty good. However, some things I changed in the meantime: The fans in the JBOD expansion boxes run nearly at full speed all the time (this powerboard has no temperature sensor) and cry like hell. But the JBODs don't need so much cooling. So I removed the two fans in the back. In addition I replaced the three fans in the fan wall with Supermicro FAN-0074L4 fans (green ones, direct replacement possible). However, I would not do that in a warm environment. The "copy large files from bare metal to VM via SMB problem" is still there. I changed copy direction and do fetch files on bare metal from VM now, always, always, always. I do not mount all these drives in Unassigned Devices. I created individual User Scripts for all mount and unmount commands. This way they don't show up on the Main page. I experienced a lot of problems if the Main page refeshed before all mount points were collected and shown. Starting the whole stuff is a manual activity: 1. Physically start the JBODs. 2. Physically start the bare metal server. 3. Do not start VMs automatically on bare metal server (starting two Unraid VMs at once did result in some problems with USB license sticks). 4. Automatically start only those Dockers (bare metal and JBODs) that don't need access to the other servers. 5. On bare metal server manually start the VMs one after another and wait til completion (JBOD web GUIs are reachable and their arrays are started). 6. Mounts in VMs to bare metal server automatically start with JBOD arrays (mount/unmout commands in User Scripts attached to Array Start/Array Stop). 7. Mounts in bare metal server to JBODs are started manually after the VMs are up and running. 8. Now start all those Dockers on bare metal server manually that need access to JBOD mounts.

I've made a correction to rebuild USB controllers. Please retest when new release is available.

Well, this was easier than I thought. This is a pretty basic script that runs the 'tree' command against each of your array disks, creating a txt of their contents. My primary purpose for this is to serve as an archive of my array contents in case I have a catastrophic failure, then I can easily discern what I'm missing and start rebuilding from backups/etc. Default save directory goes to your flash drive in a subfolder called indexTree, with subfolders named for each disk containing a date stamped txt file. #!/bin/sh # Tree Index Array #description=Creates an inventory tree of all mounted disks (not cache) #arrayStarted=true SAVEPATH=/boot/config/indexTree for f in /mnt/disk* do echo "Scanning tree for $f" mkdir -p $SAVEPATH/$(basename $f) tree -o $SAVEPATH/$(basename $f)/$(date +%Y%m%d).txt "$f" done echo "indexTree complete!" exit 0 tree_index_array_drives.zip