htpcnewbie

I have powerdown plugin installed and rebooted using the powerdown plugin. Where can I find the previous log? Not as standard. They are if you have installed the Powerdown plugin.

Upgraded from rc5 to rca remotely using the built-in plugin. For the first time ever, I noticed about 6 of 11 disks not available (not found) after the reboot. Appears as though one of my SATA connector board was not detected. Decided to reboot again and now everything is okay. The madsonic docker which had to be rebuilt the first time after a reboot (due to DNS issue) works now without the docker rebuild. Do not know the root cause why many of my disks went missing the first time reboot after the upgrade. Are previous logs stored on the unraid usb before a 'powerdown reboot' is called?

Can the kvm run independent of array status? this is a powerful feature of the version 6. The kvm mount does not run from user share anyway. I can see a situation where there are users who want to use unraid for the virtualization feature by itself. Couple this with dockers and unassigned drives and that's a great solution for many situations. Now if we can decouple docker from array status... Yeah that's a rough edge we need to smooth out. There is an option to write the 'factory cleared' signature to the disk if you know it's already cleared. Ok, it was my mistake because I haven't updated my preclear script and it turns out I need v1.15 for 64bit unraid 6. But I think having all the dockers and KVM depend on (main) array being online should be addressed too… it's especially bad when you're doing multiple array start-stop when changing drive configuration, migrating from reiser to xfs, etc (which all I've gone through the past months).

Did anyone give a try with igpu pass through with the updated kvm libraries on rc5?

monkeystar - When you say the kvm is taking over the unraid, did you mean that the unraid is inaccessible on the LAN? I am not sure about the KVM going off though. Anyways, give this a try. In your kvm xml what is your network setting? if it is br0, it needs to change to vbr0. In my case this particular setting was working until b12 and the unraid would be unreachable on LAN until I rebooted it. Check this post here for more details. If this is not the issue, sorry I cannot be of more help now.

Seems to affect certain server grade motherboards. Mine looks okay ...

Squid, thank you. That helped!!

The user templates are stored in the config directory. I added the community repositories plugin and used the templates from there to create all the dockers fresh in rc3. I also remember that going from rc2 to rc3, the dockers had to be redone. I think it may be better if someone knowledgeable confirms this before you start on the effort. It was already enabled. Is there a listing of all pertinent docker related files in unraid? I'd like to make manual backup of them before I mess around. I only know of the docker.img, /boot/config/docker.cfg and the individual docker's appdatas... what about the listing of all the docker settings? (port and directory mapping, etc).

Go to settings and click on enable docker.

This may be unrelated to rc5 but I remember seeing this in one of beta releases. A plugin update (community repositories) failed due to no space in /var/log. How do I fix this? Filesystem Size Used Avail Use% Mounted on tmpfs 128M 128M 0 100% /var/log /dev/sda1 30G 6.8G 23G 24% /boot /dev/md1 2.8T 1.9T 903G 68% /mnt/disk1 ... .. /dev/sdp1 676G 488G 185G 73% /mnt/cache shfs 32T 21T 12T 64% /mnt/user0 shfs 33T 21T 12T 64% /mnt/user /dev/loop0 20G 5.0G 14G 27% /var/lib/docker /dev/loop1 1.4M 116K 1.2M 9% /etc/libvirt

binhex- I am having a startup problem with madsonic every time my server is rebooted (docker set to auto-start). I have to re-pull the image and it is fine after that. I have copied the logs below and other than a child quit I do not see an obvious error. Any suggestion? 2015-06-08 20:13:11,423 DEBG 'start' stdout output: Started Madsonic [PID , /config/madsonic_sh.log] 2015-06-08 20:13:11,423 INFO success: start entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-06-08 20:13:11,423 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47627819378592 for <Subprocess at 47627819378088 with name start in state RUNNING> (stderr)> 2015-06-08 20:13:11,423 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47627819378232 for <Subprocess at 47627819378088 with name start in state RUNNING> (stdout)> 2015-06-08 20:13:11,423 INFO exited: start (exit status 0; expected) 2015-06-08 20:13:11,424 DEBG received SIGCLD indicating a child quit root@Tower:/mnt/disk/SSD2/apps/madsonic# EDIT: Here is the command when I click on edit and then start the docker, this way it works fine. root@localhost:# /usr/bin/docker run -d --name="binhex-madsonic" --net="host" -e SSL="yes" -e TZ="America/New_York" -p 4040:4040/tcp -p 4050:4050/tcp -v "/mnt/disk/SSD2/apps/madsonic":"/config":rw -v "/mnt/user/MUZIK":"/media":ro binhex/arch-madsonic

I had the exact same issue as you are describing, no issue in logs but the server was unreachable from outside. Everything seemed to be working fine except for this network issue. The solution in my case was to change the network in the xml file from br0 to virbr0. Loosely speaking, it seemed like the br0 network from the kvm was taking over the unraid network. If you create a temporary kvm, you can copy off this network portion into your current xml. Someone with better knowledge about this can chime in if necessary. Let me know if you want me to copy that portion of code here... Edit: here is the code that replaced the br0 network in my old xml file that fixed the issue for me. <source bridge='virbr0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/>

I started with a clean folder. After the first time it was setup, I copied the previous sabnzbd.ini file.

Do you have a VM created from b12 or prior?

I had the same errors for sabnzbvpn docker but mine wouldn't transfer any data. It turned out to be a bad docker image (github.com issue). Pulling the docker again after a while fixed this issue.

I have an asrock z97 extreme 4 motherboard. After moving from beta 12 (or maybe 15), all my USB 3 ports that are attached to an on board usb Intel controller are not recognized. I was passing the entire usb controller which has both usb 2 and 3 ports to my kvm and the USB 3 ports do not work anymore (usb 2 ports on the same controller works). I have confirmed that these usb 3 ports do not work even with stock unraid without plugins (in safe mode). I was initially speculating that my 7 month old motherboard had gone bad... Any other suggestions to debug the whether it is the kernel issue? I am currently on rc4. I've got an ASRock motherboard as well. Mine is an AMD board. I think you are probably right that something changed at the unRAID Linux level with the drivers. I've got a screen shot below of my unRAID VM configuration, showing the devices in use. I also have a screen shot of the DirectPath system-wide configuration, showing devices that are dedicated to particular VMs. In my case, I have a storage controller dedicated (Passed-through) the the unRAID VM, but the USB I'm using is just assigned at run-time, and not dedicated (Passed-through) to the Unraid VM. That DirectPath screen shot does show that I have other items passed through to other VMs. Good Luck! John

The Lan port connects to localip: port similar to if there was a universal VPN client. The allocated ip is required for only for ip's connecting from wan. Would love this too! Question. How do you access the webgui if you have a random unknown ip?

Is there a guide to install pfsense on unraid? I know few people who have asked for this and would be interested myself.

I had similar errors a week ago due to a corrupted image from github.com. Binhex can confirm whether that issue is reoccurring now.

Great work guys, Thank you for coordinating and getting a plugin out for the user community.

Upgraded from rc2 through update, everything went good. Hoping the strange VM issues and emhttp/network disconnects are addressed with this release. Thank you LT quickly trying to address known issues.

I am noticing a strange behavior with rc2 for my Win 8.1 KVM. When the KVM is set to auto-start and/or a restart from within the windows, some usb devices are not functioning. For eg, my htpc keyboard keys are not working while the attached trackpad is working. If I 'destroy' and start the vm, all are working as expected. I have tested this twice for each scenario. I haven't encountered this issue for any of the previous releases Would a log of the KVM provide information?

binhex - I couldn't find the config file which lists the auto-start docker config and has the corresponding templates in them. Copied below is the folder structure I found. For now, I am on rc2 and have created all the dockers from scratch using the templates. Wasn't hard at all except that it took time to wait and create each docker manually. root@Tower:/boot/config/plugins/dockerMan# ls -lrt total 624 -rwxrwxrwx 1 root root 563570 Sep 30 2014 dockerMan-2014.09.29.tar.gz* drwxrwxrwx 12 root root 16384 Apr 21 22:15 templates/ -rwxrwxrwx 1 root root 459 May 11 10:50 template-repos* drwxrwxrwx 2 root root 16384 May 16 15:54 templates-user/ drwxrwxrwx 2 root root 16384 May 16 15:56 images/ There will be a file on your flash drive, have a look in the flash share on your unraid system there should be a config folder and then a subdir called dockerman and I think from memory your configured templates are stored in there somewhere, then open the offending file with notepad++ and change it back to bridge then save and reboot

Upgraded from b15 to rc2 directly. Had some oddities of dockers not connecting to Internet first time. Had to change docker from host to bridge, start and back to docker/vice-versa and everything is good now. Win 8.1vm running good so far. I am hoping the see stability without emhttp connection issues I was seeing with b15. Thank you!

I have a strange issue created by me and need help fixing this. I changed the delugevpn connection mode from bridge to host and my entire emhttp is down (shares and http://tower cannot be accessed). I am unable to find a way to change this auto-start docker setting to bridge mode again. Is there a config file I can change while booting into safe mode which will enable me to change this particular auto-start docker config from 'host' to 'bridge'? P.S. Also posted this in the binhex support thread but posting here in the hopes to get a quicker answer.