Micconos

My server locked up, and I had to do an "unclean" reboot. On boot the parity check went fine, and the offended disk isn't disabled in the array. However, Fix Common Problems keeps that "disk2 has read errors". I did a SMART extended self-test (see the attached log for details) which "completed without error". I looked through the log but I couldn't spot anything serious, but then again I more a software guy, than a hardware guy Can anyone else spot some errors? And should I replace the disk or not? WDC_WD60EFRX-68MYMN1_WD-WX81DA4HN2VK-20190301-1247.txt

Hi, I have (had) a build based on an ASRock C2750 Avoton board. However, the board died on me yesterday, so I'm looking to upgrade to a newer and hopefully better build. While my old setup comfortably ran 2 Plex transcodings, several dockers, and a VM, I'm locking for bit more "umpf" hence the Xeon CPU. Also I like "future proofing" in the new setup, i.e. being able to add a SATA adapter and more RAM if needed. Any suggestions or comments are welcome. PCPartPicker part list: https://se.pcpartpicker.com/list/3BzsXP CPU: Intel - Xeon E5-2603 V4 1.7GHz 6-Core Processor CPU Cooler: Cooler Master - Hyper 212X 82.9 CFM CPU Cooler Motherboard: ASRock - X99 Extreme4 ATX LGA2011-3 Motherboard Memory: Kingston - ValueRAM 8GB (1 x 8GB) DDR4-2400 Memory Memory: Kingston - ValueRAM 8GB (1 x 8GB) DDR4-2400 Memory Storage: Seagate - Archive 8TB 3.5" 5900RPM Internal Hard Drive Storage: Seagate - Archive 8TB 3.5" 5900RPM Internal Hard Drive Storage: Seagate - Archive 8TB 3.5" 5900RPM Internal Hard Drive Storage: Seagate - Archive 8TB 3.5" 5900RPM Internal Hard Drive Storage: Seagate - Archive 8TB 3.5" 5900RPM Internal Hard Drive Storage: Seagate - Archive 8TB 3.5" 5900RPM Internal Hard Drive Storage: Seagate - Archive 8TB 3.5" 5900RPM Internal Hard Drive Storage: Seagate - Archive 8TB 3.5" 5900RPM Internal Hard Drive Video Card: MSI - GeForce GT 710 1GB Video Card Case: Nanoxia - Deep Silence 5 ATX Full Tower Case Power Supply: Cooler Master - MasterWatt Lite 230V 400W 80+ Certified ATX Power Supply

Thanks for the advice, I'll try it out... I have previously been concerned about memory usage. I used to have a Windows VM also, but I have replaced that with an Ubuntu one to lower memory consumption. Since I did that the "Memory usage", shown in the dashboard, have been bellow 50% whenever I checked it, so I'm not quite sure that the issue lies here. However, it's worth a test I have also set the "Fix Common Problems" plugin to "Troubleshooting" mode, so if it happens again, then maybe I'll have some more info logged

Well... the poweroff command seemed to make the server reboot after about 10 mins. But still, have anyone else been experiencing "random" VM/docker container "shutdowns"?

So recently I have been noticing that some of my dockers and VMs have been shutting down "by them selves". All the dockers and VMs would be "up" the day before, and the next day some of them is down (red) when I check the dashboard. Same thing happened this morning, and a VM was down so I started it again. But I when used the VNC browser window to access the VM, the response from the VM was extremely slow, i.e. when I typed something it would take almost 10 secs before something appeared on the VM screen. So I decided a complete server reboot was maybe the best thing to do, so I tried to reboot from the Web UI. But now the Web UI has simply become unresponsive, the server doesn't reboot, and I can still access some of the dockers (so they're still still running). What is the most graceful way to regain control over the server? (I would prefer not to simply "pulling the plug" on my server) unraided-diagnostics-20170319-0632.zip

Hi, I'm a on migrating an application I have been developing to Docker. So I have been trying to familiarize myself with Docker a bit by creating some new Docker templates for unRAID. I tried to create a vanilla postgres docker: https://github.com/Micconos/unraid_docker Everything seems to work fine, expect I get a "Version not available" in the Docker tab next to the container (see attached image). Does anybody know why I get that message? /Micconos