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.
I recently updated my Unraid to use an EMC KTNSTL3 storage array. I use a lot of small drives which are really cheap.
So far it’s working great. Bought it on eBay.
I’m using SATA drives so you need to buy the Interposers. They turn your SATA into SAS drives so they fit in the caddy.
You’ll need 15 of them otherwise you can use straight SAS drives.
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.
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