fireplex

It won't work with that board. You need IPMI. You might be able to get a pci addon card. I would suggest you try the dynamix temp plugin. OK thanks for letting me know Sent from my Nexus 5 using Tapatalk

Hello, I have just installed this onto my system running 6.1.9 and Asrock Z77 Pro 4 but cannot see any sensors listed on the tools -> ipmi page, do I need to configure something first ? Thanks.

Tried this ?

OK thanks, will take a look.

OK, so just copy those two files only? They include the Linux kernel etc? Everything that could affect KVM ? Unfortunately I cannot find my 6.1.3 download and its not on the webpage any more so have emailed support for a copy. Cheers.

Yes, using the stock unraid files bzroot & bzimage files.

I'm trying to troubleshoot a strange DVB-T/S corruption problem I an having in my VMs. The system did run fine, at some point something has changed and now after around 8 to 10 minutes I keep getting severe disruption on the recorded streams captured via my TV cards. I've changed recording drive from SSD cache to HDD and still same issue. I've changed back the motherboard to the original thinking that was the recent change I made but the same issue is there. I also switched back to a Windows 7 VM from 10 but still the same issue. The only other thing I can think is I upgraded from 6.13 to 6.1.6/7. Question - can I just install 6.1.3 safely over my existing config ? Thanks.

I am having an issue with high I/O wait times and would like to analyze this in more detail. The only way I know how is via iostat, I was hoping this was part of nerdpack but it isn't. Can anyone advise how to install iostat onto unRAID ? Thanks!

OK thanks, so just need to apply to any existing systems only that don't have these settings in place.

Does the contents of this post still stand as the recommended setup ?

Glad it worked (sort of), mine connects to an X10 CM12U automation controller and no issues so far.

I'm passing through my serial port fine to a Windows 10 VM, try this xml:- <serial type='dev'> <source path='/dev/ttyS0'/> <target port='0'/> </serial> obviously you need to ensure /dev/ttyS0 is your serial port on the server. It appeared as COM2 for me in Windows.

OK, managed to fix it. BTW I just updated straight to 2015.12.30 today so looks like the bug is still there.

I have just updated the local master plugin only and had this same error. Now I cannot access the unRAID GUI at all, just get the above error.... Any idea how I can recover from this big problem?

Try this: #!/usr/bin/bash while true do ping -c 5 <your router IP>/dev/null if [ $? -ne 0 ]; then echo Network is down at date echo Taking interface down ifconfig eth0 down sleep 10 echo Bringing interface up ifconfig eth0 up sleep 60 echo Completed recovery at date fi sleep 10 done

There is clearly a serious bug here but it only seems to affect a small number of users, must be based around certain HW and SW configurations.

I was already running with a static setup anyway and tried the STP and bonding options but made no difference fort me.

Sounds like same issue as http://lime-technology.com/forum/index.php?topic=39890.0

No, never got it fixed. Just have to be careful what graphically I do in a VM via RDP. Also knocked up a script to restart the network when it fails.

@Fireplex any luck yet? I will try and push and update soon. Sorry for the dealy, I've been working heavily on Emby development and deploying an asterisk server. OK, had another look at this and sussed it out. Turns out I was using my router as my DNS server under unraid network settings. And my router is configured to use OpenDNS. And my OpenDNS is blocking i.imgur.com !! Changed to google's DNS servers and all fine now. Sorry for wasting your time.

Hi,I ran a smart test of my cache drive (SSD) and it was fine, I'm using it for recordings from my PVR and for my Windows VMs so get's a lot of use and they have all been OK and 100% stable. I deleted the docker.img and recreated as per previous update but it didn't help. My config folder is on /mnt/cache/docker/<configs> solely on the cache drive. I agree something is messing up my docker but have no idea what

My cache drive is xfs cannot find any scrub option for that.

Well it died again overnight in the same fashion as before and won't restart Think I'll go back to a different solution dockers don't seem very successful for me.

Yes it is

OK, deleting the Zoneminder container & image didn't help, ended up starting from scratch and disabled dockers, removed it's .img and started again (yours is the first docker I have tried so not a big dela). All OK now, hopefully won't happen again.