sureguy

Where does CA store information about previous dockers? I have a couple dockers that I installed multiple copies of for testing, which I subsequently removed. Now they show up on my previous apps list, but if I delete them the templates that I"m using for my currently used dockers get deleted. If I restore the templates, they re-appear on the list of previous apps. I know this isn't super important, but I'm afraid I'll forget and delete them.

This generally means a write to the disk failed and it needs to be rebuilt.

I figured out a few things for telegraf: Sensors (CPU temperature etc): The docker image doesn't come with lm_sensors - you need to add it: ssh into unRAID and do the following: docker exec -ti telegraf /bin/sh apk update apk add lm_sensors Edit your telegraf.conf and remove the # in front of [[inputs.sensors]] Restart your telegraf docker. Disk Serial Numbers: I set up Influx/Grafana/Telegraf by following PanzerschreckGER's guide here: https://www.reddit.com/r/unRAID/comments/7c2l2w/howto_monitor_unraid_with_grafana_influxdb_and/ An issue with this set up is you cannot monitor drives by Serial number, only sdx (these designations change on reboot requiring reconfiguration of Grafana) or mdx (this precludes monitoring Parity or cache drives). I owe big thanks to danielnelson on the telegraf GIT who helped me figure out getting the HDD serial info working with diskio in telegraf Diskio HDDs by Serial Add the following path to the telegraf docker: https://imgur.com/a/3qZXE Then in telegraf.conf under: [[inputs.diskio]] put device_tags = ["ID_SERIAL"] Restart your telegraf docker HDD Temps by Serial: Change the extra parameters in hddtemp docker: From: Extra Parameters: -e HDDTEMP_ARGS="-q -d -F /dev/sd*" To: Extra Parameters: -e HDDTEMP_ARGS="-q -d -F /dev/disk/by-id/*" Restart your hddtemp docker

Getting an XML Parse error when trying to install manually, using Community Applications I don't get an option to install. Edit - Rebooted - and installation worked - odd

Ahh - I did fat finger something when setting up a docker, and then just removed the folder via ssh. Sorry for the confusion. Removing the appdata.cfg fixed the issue. Thanks for the help and your work.

I don't have an appdata share - I've attached a picture of my shares - unless the "CA Appdata Backup" share is confusing things

phatstore-diagnostics-20180109-2208.zip

I'm receiving an error that my "Default docker appdata location is not a cache-only share" what's strange is I wasn't getting this error before. I'm not using the appdata share, instead I'm using a share called Docker, that is set to cache-only, and is set as the "Default appdata storage location" within Docker advanced settings. I've ignored the error for now, but find it odd that this wasn't an issue previously.

Not sure about the IP address instructions. I just set the HOST field to unRAID's IP address, as that's how I was accessing hydra1. That worked properly. Other than that everything worked fine (migrated install from hydra1 without issue). Thanks for your work.

LimeTech has stated they only support unRAID running directly on the hardware. People have posted work arounds for the issue on this thread. I recommend trying one of those.

I must be missing something as I have two USB devices passed through to my unraid 6.1.3 (booted via plop) running on ESXi 5.5.0.3116895. The log file is full of errors from both usb drives :-( Nov 2 18:04:25 unraid kernel: usb 1-2: reset high-speed USB device number 3 using ehci-pci Nov 2 18:04:26 unraid kernel: sd 4:0:0:0: [sdj] 7975296 512-byte logical blocks: (4.08 GB/3.80 GiB) Nov 2 18:05:01 unraid kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci Nov 2 18:05:01 unraid kernel: sd 3:0:0:0: [sdi] 30529536 512-byte logical blocks: (15.6 GB/14.5 GiB) I can't recall anyone mentioning plop with the dual USB solution. You might want to try the vmdk method to see if it makes a difference.

Unraid under ESXi isn't supported. I run it though. This is apparently a kernel issue, so until its fixed and unraid moves to that kernel you're out of luck unless you use one of the previously mentioned work arounds.

Unraid doesn't include vnc AFAIK

Run a non-correcting parity check

Fat32 and exFAT would be nice, if possible.

The problem with integrating something like this into unRAID is that if the Filesystem driver used destroys the Filesystem on the unassigned device novice users will blame unRAID. Perhaps read only would work with these devices and an option (unsupported, use at your own risk) for write would work?

An update just appeared for this plugin that works with 6.1 - I've mounted and unmounted a drive a couple times, seems to be working properly for me (it's my boot drive - vmdk - for unRAID under ESXi). I'm remote so I can't check anything physical at the moment. Posting this as some people rarely visit their unRAID webui, and may be getting notifications from this thread. Thanks a lot gfjardim!

I'm running 6.1 and was still having issues (I know the plugin doesn't support 6.1 properly), but others seemed to have it running. I was able to fix it by uninstalling the plugin, and then deleting the folder /boot/config/plugins/unassigned.devices - I then rebooted (probably unnecessary), and reinstalled the plugin. The UI for the plugin now works. Hope this helps someone else.

I have this plugin installed on v6.01, but I get no UI for it, even when clicking on the plugin. I've rebooted a couple times, and tried installing RCs, moving back to stable, and removing and reinstalling the plugin. Any thoughts? I've also tested multiple browsers, cleared cache, etc.

This seems to be a kernel issue, rather than an unRAID issue. So it may take some time. Using a $30 card reader (fcr-hs3) fixed it for me, and a second USB device (passed through) fixed it for someone else. If you want the advanced features of unRAID 6 I'd try one of those things, but I can only vouch for the card reader solution.

You need to delete all the files in the share. You can use mc to do this if you're sure that all files should be deleted.

It's good to note that with the addition of the unassigned devices plugin in unRAID 6, you can update unraid 6 final (and some betas) via the menu and then easily mount the VMDK within unraid, and copy bzimage and bzroot to the vmdk from /boot to the mounted VMDK drive. After rebooting you will be on the latest version. IMO there's no need to have someone maintain the VMDK image given how simple this process is now. I guess it would be nice if LT made a vmdk though.

I'm still seeing some issues regarding this (with a card reader that is supported by unraid, and a generic microsd card). To recreate, I simply reboot, and navigate the web-ui until it hangs (basically all menus), it eventually does. And then I get something along the following in my syslog: Jun 26 23:10:06 phatstore kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci It doesn't repeat like it did with a usb flash device, and I don't know if a better microsd card will resolve it, but just thought I'd post as a heads up.

I think this thread should note that some ESXi 5.x and 6.x hosts show USB reset issues with PLOP and USB passthrough on unRAID 6. 2 members have been able to work around this issue by using microsd cards attached to Kingston FCR-HS3 devices,.

ok, thanks for the info.. so you are using reader with flash card(which one? ) and if you have paid licence, then you must transfer your key? I'm using a generic 32GB microsd card, and I transferred my license from a USB flash drive to the key reader via the unRAID web gui.