jimbobulator

Can you clarify what you mean by this? I assume we need to explicitly delete the container and recreate it from the image and template? Should we delete the image and re-download that as well?

garycase, any experience with any other software besides SyncBack for comparison? I've been trying various free options trying to settle on something to do basically exactly what you're doing. But I still haven't found what I'm looking for (cue the delay heavy guitar riff). Deltacopy is next on my list, and I haven't tried SyncBack.

I would like to see this included as well and was planning to make this request. I can test if a kernel with this driver is compiled. I suspect this board will become more popular as it's the only reasonably priced general purpose (non-server) mITX board with 6 SATA ports.

Check relative performance on the cpubenchmark website: What you have now: 667 - Intel Atom D510 @ 1.66GHz 7397 - Intel Xeon E3-1226 v3 @ 3.30GHz 6843 - Intel Xeon E3-1220 v3 @ 3.10GHz 3929 - Intel Atom C2750 @ 2.40GHz 2329 - Intel Atom C2550 @ 2.40GHz Some comparison points - You'll get a lot more performance out of the Xeon. - Idle power consumption probably won't be too different. Lower for the Atom, but we're talking single digits probably. - Max power consumption of the Xeon is going to be much higher, but you have that extra performance. - Atoms are fanless. - Search forums for examples of people using the Atom boards, I think there are some. Personally I'd go with the Xeon unless fanless/noise were a primary concern and you really don't need extra performance. That said, the Xeon with an aftermarket cooling solution can be VERY quiet. I find you can always use more performance though. If you plan to do any transcoding or anything, I'd just get the Xeon (in my opinion), although all the processors will handle some light transcoding activity. Never know what you might throw at it in the future. Edit: based on your use case description, any of the solutions you proposed will likely work fine, but it will depend on what you do with that windows VM. I ran a windows VM on unraid (early v6) on a processor with 1100 passmark score for testing and it handled it okay for basic use. Depends on what you want the VM to do really. Edit2: Another option, if you know you won't need the extra CPU performance, go for the Atom and take the savings and invest in an SSD for your VM and any other dockers/apps. You will feel this difference in the VM and any other applications.

Check https://support.plex.tv/hc/en-us/articles/206225077. I'm using needo's Plex docker and SSL is working as described. You're browser will complain about the certificate when you browse to your server locally unless you connect via the plex.tv site -> it validates the certificate with Plex, then loads the web app from their website, which then connects to your local server after which everything happens locally (or so they describe). You can also build a unique URL form info in your logs for external access that'll enable SSL, I read that somewhere last night.

Finally got some quiet time to troubleshoot... Turns out I had mapped the completed download folder into the container rather than the root download folder that is mapped to Deluge. Seems to be working now.

Hey, open question regarding sonarr/deluge configuration, if anyone can help me. I created a test library with a few episodes and sonarr found the files and added them, so it's seeing the path to my media. Was able to get sonarr to search for another episode and successfully pass it deluge. The file downloaded, and was moved to my complete folder, but sonarr won't import them for some reason. Do I need to point sonarr at the completed download folder somehow? I don't see an obvious way to do this. I'm sure I'm missing something simple. Thanks! As a side note, the deluge-vpn container is excellent! Quite happy, thanks binhex!

FYI, I've been using that motherboard with unRAID since last August with good results. Seems to be the most likely successor to the Asus H87 plus board that everyone liked. Only issue is that I had a problem with one of the Ethernet interfaces, which unRAID didn't seem to recognize. The second one worked and I haven't investigated this much. Spacing for USB, front panel and SATA connections is a little tight next to the RAM. I suspect this is an issue with most mini-ITX boards though.

Actually I've managed to get the gpu passed through without it now. So much simpler than the xen days.

Great. Thanks for the quick reply!

Corner case perhaps... Trying to get gpu passthrough working. I'm really new to KVM so bear with me. I'm getting a windows boot screen, but it freezes pretty quick. To reproduce: - Start VM (and it freezes) - Click on the VM icon in VM manager and clicked 'View XML' - Clicked back to the VM manager - VM showed as paused (yellow pause icon) - Clicked on the VM icon to stop it and the only options are resume and view xml - Clicked on resume and see an error saying VM has to be restarted, but the option to restart is not available from the pull down menu. See attachment. Thanks.

Hey jonp, any advice on how to pick the right ROM for our GPU? There are 4 different options for my card and I have no idea which is right. Thanks!

No issues after 2 days. Calling this one solved. Thanks guys!

To follow up here, I discovered that my RAM was bad, and this is likely the cause of most of my issues (to be confirmed). I regenerated my docker.img file and will keep an eye on checksum or any other issues.

I design electronics hardware for a living, and I spend a lot of time giving the software developers a hard time about how all our problems are software issues. Well, this time I'm eating my words because it appears I have a bad memory stick. Tons of errors in memtest86+ immediately. Currently running it with a borrowed stick from my desktop with no errors. Seems pretty conclusive. I'll continue on the borrowed ram for time being and report back if it solves my issues. Thanks again for helping out. I should've done this a long time ago, but since it ran for so long on beta6 I assumed everything must've been okay on the hardware.

Good point, I'll check. I updated it when I built the computer last summer, but it was a new product at the time and sometimes they spit out new versions pretty quick for new products.

Thanks for the input. To be honest, I've been hesitant to try safe mode largely because of my (family's) reliance on Plex. But I think it's time to bite the bullet and try it out. At the start shortly after moving from b6-b15 (clean install), I only had Plex running in a docker and NOTHING else (plugins or otherwise), and was still having issues. todo list * long memtest * safe mode for a few days at least * if all is good, slowly add things back in prioritized order and see if/when it starts breaking Might take a few days to get started as free time is limited.

Not sure about your case, but for me the checksum errors are within the btrfs docker image file. My drive is formatted ext4. Here's another case I found on the support forum with no responses [b15]: http://lime-technology.com/forum/index.php?topic=39372.0 edit: Nevermind - I see you specifically mentioned loop0. Sorry. So probably the same issue.

I have a photo of the screen after the kernel panic - will upload later tonight. Scratch that. Photo didn't turn out. Need a phone with a more reliable camera...

Upgraded to RC3, hoping docker 1.6 would fix my problems. Nope. Still seeing issues - webgui crashes - segmentation faults - monitor script errors in syslog - php errors in syslog - btrfs checksum issues crop up after a while, seen in the syslog when I attempt a scrub of hte docker.img file. I've tried deleted and regenerating the docker.img file a few times and the problems inevitably comes back. I attached a few syslogs for review. syslog-20150521-191617.zip I think this one was a webgui failure, so I did a initiated a powerdown over SSH. Plexwatch looked to be a culprit (similar findings on b15), so I disabled that docker going forward, but still had issues. syslog-20150526.zip From today. See back a couple days for btrfs checksum errors which popped into the syslog after doing a btrfs scrub on docker.img. This was after redoing my docker.img a couple days ago. More recently there was a general protection fault (I got a segfault email through notifications), but no other failures yet - still running. My SSD is mounted outside the array from my go file (ext4). It was previously a old spinner drive (had the same problems). Thanks in advance. syslog-20150521-191617.zip syslog-20150526.zip

I upgraded from b15 to RC3 shortly after it was released. I'm (still) having various issues that have persisted since the update. I was running b6 smoothly since it was released (months of uptime with no issues). I've been busy so I haven't had time to post, but I'll collect what I can in my other post. Some symptoms I'm seeing: - webgui crashes - btrfs checksum errors in docker.img - segmentation faults - at least 2 hard crashes, one of which was a kernel panic I updated my post linked below for further analysis. http://lime-technology.com/forum/index.php?topic=39569.0

I'm still having similar and new issues after updating to RC3 as described above. Incoming post with details and syslogs.

Glad your server made it okay even without a bit more preparation ==> Sorry to hear that (apparently) your guitars weren't quite as lucky This was an unintentional implication. The guitars arrived safely, I suspect in part due to my attention in ensuring they were packed carefully. "large, oddly shaped things" referred to tables, bbqs and electric pianos... Have to pick my battles these days.

Extremely late followup. So I didn't have time before the move to pull and wrap the drives individually. In fact the movers packed my server when I wasn't paying attention and I had no idea where or how it was packaged.... Thankfully I caught them before they started on my guitars.... The good news is that the server arrived in one piece and has worked fine over the last 6 months. The movers were far more likely to break large and oddly shaped things, it turns out.

I will keep that in mind and definitely try to help where I can. I actually was referring specifically to the official v6 manual, so it is good to be clear that its under LT control.