So I got this error on my Unraid server for a drive, “Unmountable: Volume not encrypted” for a drive I had used on another server. There was nothing on the drive I wanted so I just wanted to overwrite or format it.
Finally found a link to just overwrite the filesystem.
So I bought some RAM recently in one of those bins on clearance because it was opened, etc. I installed it with another two sticks I already had. All four sticks are DDR4, of course, but the old ones were 2x8GB 26666, and the new ones are 2×16 GB 3200. Unraid would only show 16GB usable rather than the 48GB. Unraid did notice them, but they were unable to be used.
After some googling which didn’t get me anywhere, I decided to remove all the sticks and just use the new ones in A2 and B2. Well, now Unraid shows 32GB of RAM usable. So next, I put in the other two sticks in A1 and B1. Boom!!! Now it can use all 48GB. I assume it has to do with a mismatch in either speed or capacity.
There does appear to be one quirk you need to know. Only one set of the SAS controllers reads SATA drives. I think it’s the bottom one so hook up your mini SAS cables there.
Also, I had some 14TB drives that I just installed and they kept giving me an “unsupported partition layout”. To fix this I just had to reboot the Unraid box. I’m not sure why but it worked after that.
You’ll also need a SAS card as well. I have the LSI 9200-8e. Something like the pic below. You can buy them on eBay too. I like this seller https://www.ebay.com/str/theartofserver .
There was some useful information below however it related to TrueNAS.
This docker container should work out of the box with Nginx Proxy Manager to parse proxy logs. The goaccess.conf has been configured to only access proxy logs and archived proxy logs. No fuss, no muss.
The docker image scans and includes files matching the following criteria: proxy-host-*_access.log.gz proxy-host-*_access.log
Create a share on the VM machine itself in Unraid.
Let’s assume your mount tag is “test”.
Make sure you create your mount folder within the VM. In our case its “/whatever”. Modify your /etc/fstab file like this to mount the share. Then reboot.
test /whatever 9p trans=virtio,version=9p2000.L,_netdev,rw 0 0
Is your display setting too small when viewing a virtual machine via NoVNC? If you are using Windows 10 install the Redhat Display Driver, virtio-win-xxx\qxldod\w10\amd64\ . That’ll fix the problem.
This is more docker related but should be similar to just a plain jane install. You can add your static entries to the /etc/hosts file or you can add it the the dnsmasq.d configuration file.
Create a file under /etc/dnsmasq.d, something like myhosts.conf and add the following. Keep adding entries until your done.
host-record=hostname.com,192.168.1.1
Find your pi-hole dns configuration under /etc/dnsmasq.d. Open the file and add the following line to end of your the configuration file.
conf-file= /etc/dnsmasq.d/ myhosts .conf
Go back to the pi-hole GUI and restart the DNS under settings/system “restart DNS resolver”.