Cmc0619

Let's phone a friend. @limetech are we on the right path here with any of this?

I don't think you'll see them show up as /dev/sdX devices. snuf's analysis looks like he determined that /dev/disk/by-id is what unraid uses and that's what his udev rules create. Does anything show up in the GUI? When I add a new drive it shows up in Unassigned Devices on the main GUI page.

And then a wild coder appears! There are updates to the case I opened on the github. After initial statements that it wasn't possible. An enterprising, sharp coder by the nym of 'snuf' has posted a patch that he believes will get the Fusion IOs visible in Unraid. See my link above for the comments. Unfortunately, I'm away from my home server for 3 weeks. Can anyone try this out and confirm if it works?

I put in a feature request with the guys maintaining the open source driver to change the dev name as that appears to be the only sticking point. Their reply was that they're unable to control the block names. They did give a suggestion about mapping names in udev but I think I read early in this thread that that had already been tried. It looks, to me anyway, like we're reliant on Lime to change the logic of their device identification logic to include the fio* prefixes. Here's the thread on git if anyone is interested in reading their full responses. Link

Well... That's where the awesome Community Applications shines! You can search for nzbhydra and when it comes back with the results you just click 'Get more results from DockerHub', up towards the top of the screen, and then select the docker from the theotherp and configure it appropriately. That being said, it's more of a manual process and I'm super excited for linuxserver.io to come through for us!

So... NZBHydra2 (git) was announced today. The author could definitely use some help on the docker front as the one he released overwrites the config whenever a change is made to the template.

The NMS that LibreNMS forked from, Observium, is a docker available in CA today. Support link: http://lime-technology.com/forum/index.php?topic=38410.0

Looks like there's more to it. I was getting these in my hydra error logs after enabling lxml support: 2016-03-01 21:22:09,906 - ERROR - search_module - Error while processing search results from indexer Binsearch Traceback (most recent call last): File "/config/hydra/nzbhydra/search_module.py", line 292, in execute_queries parsed_results = self.process_query_result(request.content) File "/config/hydra/nzbhydra/searchmodules/binsearch.py", line 115, in process_query_result soup = BeautifulSoup(html, config.settings.searching.htmlParser) File "/config/hydra/libs/bs4/__init__.py", line 156, in __init__ % ",".join(features)) FeatureNotFound: Couldn't find a tree builder with the features you requested: lxml. Do you need to install a parser library? Then I found this link: http://stackoverflow.com/questions/21322948/beautifulsoup-wont-recognize-lxml which says run: "pip install cssselect" in addition to installing lxml so I dipped into bash for my nzbhydra docker, did that, and the errors are now gone during searches with lxml enabled. I didn't do any extensive benchmarking but it does seem faster. And if nothing else I have less ugly tracebacks in my logs now. Probably the right solution

I've been popping in, pre-unRAID, on the tvheadend project for years trying to get it to work every few months or when a new release would come out. I've FINALLY gotten some forward motion while trying the 4.1 docker . 4.0.8 did nothing like the releases before. Any plans to release 4.2? 4.1, while finding all of my services (FINALLY! WHOOOO!), still isn't as user friendly as I'd like it to be and I'm hopeful to see if 4.2 is any better.

This forum software really needs a 'Like' or 'Thank you' button!!!

I have a few requests! Low hanging fruit: A new ps3netsrv would be great. It's a single 50kB statically linked file that hosts PS3 games for modded PS3s. The current docker(https://lime-technology.com/forum/index.php?topic=37859.0) works and hasn't seen any updates of the hosted binary but it'd be nice to be able to share image space. Binary and source is here: http://www.deanbg.com/webMAN_1.43.zip Also Archivo, http://www.tivocommunity.com/tivo-vb/showthread.php?t=532868 / https://github.com/fflewddur/archivo which is software for archiving TiVo recordings would be awesome sitting in one of the RDP based dockers. More ambitious: IncrediblePBX/PIAF http://nerdvittles.com/?p=12292 which are Asterisk distros for phone systems. I currently have to run mine in a VM. Opensim http://opensimulator.org/wiki/Main_Page or even better the Diva distro of Opensim http://metaverseink.com/Downloads.html! This is a open source implementation of SecondLife.

Hi. Just stumbled onto this plugin and got done reading this thread and have seen you ask for help on this a few times in it. I've got an answer for you but I don't think you're going to like it... I use other SNMP products in my day job so I'm not super familiar with Observium but I found all this in 20 minutes of googling. I may have the particulars wrong but this is the basic gist. The short answer is it'd take a hell of a lot. http://postman.memetic.org/pipermail/observium/2015-January/009184.html is basically a statement on the "design ethos" of Observium. What it boils down to is instead of being a buildable framework like other SNMP monitoring tools they'd rather have each monitorable node be a well defined package. This means no throwing random OIDs at the software and having it graph a la MRTG, PRTG, Cactii, Solarwinds, whatever the kids are using these days. It has to be a known, supported piece of hardware that's coded up specific for it. Pretty brain dead in my opinion but whatever, it's their software. It can be done, http://www.maartenmoerman.nl/?p=649, tells you how to do custom OIDs in Observium... If you have the paid version. So I guess they came around. But only if you're paying for the software. The docker is the CE version which is basically the stripped down freeware version and for that, they only support modules that have been written by them and apparently it's an uphill battle to submit code that wasn't written by them. I'll keep the bashing to a minimum but if you google a bit you'll see... Yeah... I'll just leave it there. It's really a shame because you guys have done AMAZING work getting things that matter to Unraid users into OIDs that we can monitor but I doubt they'll be added to Observium. There are other options out there that may be more suited. None of which appear to have a docker available at the moment. Cactii or, even better, librenms(an Observium fork with an Observium migration script!) would probably be a better suited docker for our community.

No change. I ended up returning the AMD setup for an Intel i5 for unrelated reasons (wanted different PCI slot layout). I'm sure it would've been fine with a discreet card; it looked like the hardware acceleration wasn't being detected for some reason.

F8 from 4/09/2015. I was using the 6.0.0b3 OpenELEC template. Done! Thanks for the heads up.

Just to add a data point. Tonight I setup an F2A88XM-D3H mobo with an A8 7600 and I've literally done almost nothing and it works. I enabled IOMMU in the BIOS as it was set to disabled. That's it. I've got Kodi running in a VM using my CPUs GPU as the passthru. I don't even have an add on video card in there. It just takes over the console when it boots. Passed the VM template my USB Logitech dongle that my wireless keyboard talks to and my HDMI ports "sound card" and I'm watching movies. Info reports HVM & IOMMU as enabled. The movies are dropping every other frame and the CPU is at 100% during playback but that's probably related to not having an add-on card. root@nas:/boot/syslinux# cat syslinux.cfg default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append initrd=/bzroot irqpoll <-- This was added from my old board. I should probably take it out... label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest