jimbobulator

While true, there are various individuals that constantly monitor it, with a stick behind their back! I figured as much, which is why I asked here rather than start editing. It took some serious effort to restrain the OCD documentation monkey portion of my personality... I didn't want to be the new guy that started screwing with everything.

I've been seeing issues with 0.1.96 on W8 (not 8.1) and misc. lockups and VM reboots. Too early to tell if it's related to the virtio drivers or not as I haven't seen anything reproducible.

The wiki page here: https://fedoraproject.org/wiki/Windows_Virtio_Drivers has direct download links populated, which were not there last night when I was poking around... The stable release is 0.1.96. Latest release is going to 0.1.103.

They must have been actively updating the virtio driver website last night when I downloaded them. The wiki page here: https://fedoraproject.org/wiki/Windows_Virtio_Drivers now has direct download links populated, which were not there last night when I was poking around. Indeed the stable release is 0.1.96. Latest link is going to 0.1.103.

Alright, lesson learned and now I have network. Perhaps another good wiki improvement would to explicitly point out that virtio drivers need to be installed for various things for windows. Seems obvious to me now but wasn't on the first pass, especially coming from Xen when most of this just worked. Thanks for the quick response! Keep up the good work. As a side note, I noticed the unraid 6 manual in the wiki is publicly editable. I assume that because it's the official manual you don't want people messing with it, right?

I downloaded 0.1.96, which I think is the latest stable version. I had to poke around their directory structure until I found this. The folder I found this in also had a "virtio-win.iso" with the same filesize as the "virtio-win-0.1.96.iso". I grabbed the one with the version number on it. See here: Oh. How did I miss that? This isn't doing much for my technical credibility... I might have been too impatient for it to parse the xml and populate the template settings when I was trying to find the advanced button - the button doesn't appear until the template is populated. It takes like 2-3 seconds. You should install AMD64 and you shouldn't have had to click "show incompatible". Can you screenshot this if you're having problems for me so I can see exactly where you went and how? I'm sure I'll be messing with this again in the near future, I'll make a note to capture a screenshot or figure out that I just didn't know what I was doing and mis-remembered how it went... Edit your VM by clicking the pencil symbol. When you do, click that toggle I showed in my screenshot to turn on advanced, look at the network section. What is entered under bridge? The bridge shown in the VM manager config is virbr0. I previously had a bridge enabled at the unraid level for Xen. Bridge is disabled but it's still showing xenbr0 as the bridge name. Here's my network.cfg: # Generated settings: USE_DHCP="yes" IPADDR="192.168.1.150" NETMASK="255.255.255.0" GATEWAY="192.168.1.1" DHCP_KEEPRESOLV="no" DNS_SERVER1="192.168.1.1" DNS_SERVER2="" DNS_SERVER3="" BONDING="no" BONDING_MODE="1" BRIDGING="no" BRNAME="xenbr0" BRSTP="yes" Now I'm wondering if I need to install virtio network drivers too? Anything else I'm missing?

I figured out Xen on unraid a year ago and messed with passthrough and other painful things. It was good, if not a bit finicky with my particular hardware. Today I loaded up KVM and installed a W8 VM for testing, and my first impressions are quite good. Webgui is great. I'm impressed that I have a VM up and running without touching the command line, a configuration file, or spending more than an hour messing around. I only used the WebGUI so far a and haven't resorted to editing a configuration file yet. All done on b15. I used the incomplete wiki/manual as a guide (although it was all mostly self explanatory). Some feedback [*]The virtio drivers linked from the wiki are now deprecated. I had to bounce around a bit to find an ISO, and I'm not sure I got the latest. [*]The wiki doesn't explain that you need to install the virtio storage drivers so that VM will actually see your vdisk. [*]In VM manager, if you don't specify a vdisk filename in the path, it creates a generic vdisk1 file. This could be explained better in the wiki and tooltips. I assumed it would name after the VM name. General comments / issues [*]I have no advanced view available in the WebGUI. [*]For my W8 VM, I ended up installed a virtio driver in the amd64 folder rather than x86 (using an intel 4th gen i5). I had to click on the option to show drivers that are incompatible with the hardware. [*]My VM has no network access. I have no bridge configured in unraid and assumed based on the description in the wiki that unraid would set up NAT and act as a DHCP server for my VMs. Stopping for now.

I'm seeing WebGUI failures pretty regularly now, within a few hours the last couple times. I'm also seeing some segfaults(!) and other weird things (I think) in the syslog, which could be related to docker. Chronology... - I booted into regular (KVM) mode. - Everything seemed ok the next day, so I installed a couple more dockers. Now have PMS, plexWatch, and BTSync (installed but not doing anything yet). - At this point things seemed okay. - Next day I tried moving my docker.img and configuration files to a disk outside the array (currently on disk1). Docker.img moved successfully but issue getting PMS to see the config folder on the other disk for some reason. Reverted to config data on disk1. - WebGUI failed again that night. And now 1-2 times per day. - Since moving my docker.img and playing with the config directory, I'm also now getting segfaults every now and again and other things that look weird in the syslog. some of them appear to be linked to plexwatch. I attached a syslog where the segfaults were first noticed and a couple from today leading up to GUI failures. I'm disabling docker and will run overnight and going to see what happens. Overall I'm not very impressed with the stability of b15 for me. Even if it's issues related to the specific dockers, I'd much rather have a failure in a VM that's isolated from the main OS... logs.zip

Interesting. I'm a bit skeptical though that unraid + one plex docker would consume all 8GB. I ran the same thing for months on end without issues previously albeit with Plex in a linux VM rather than docker. Currently the dashboard tab is showing 14% memory usage.

No need for Xen, so I will try tonight. Note that I haven't replicated the WebGUI failure since the first time, so it may be difficult to say if this resolved things or not. Last night I rebooted the server to get the GUI back, did a bit of work on my dockers, then kicked off another parity check. I thought perhaps the parity check may have had something to do with it, but it completed successfully last night and I still have GUI this morning. One thing I didn't mention is that I put my docker image and docker appdata on disk1 in the array rather than on a cache drive (the eventual plan). I don't know why I didn't put it on the disk I have mounted outside the array. Could this have anything to do with it? I thought perhaps the combination of dockers writing to the array and the parity check coinciding could have somehow helped trigger the GUI failure, but the parity check last night didn't have any impact. Plex was doing more disk activity than normal the night of the failure though as it was re-linking all my media files to a new installation. What's the best way to move my docker container and appdata to another disk? Thanks, James

Upgraded from beta 5a to beta 15 yesterday, and I have to say I am impressed so far. I had a few hiccups with the upgrade, which I documented on the support board, links below. Hopefully nothing serious. Great work LT. Looking forward to some free time to start messing with some KVM VMs. Initially I tried an upgrade, and the server booted with no network access at all, but somehow my VM was booted and running fine (weird). http://lime-technology.com/forum/index.php?topic=39568.0 Tried a fresh install and have reasonable success but the WebGUI died on my overnight. http://lime-technology.com/forum/index.php?topic=39568.0

Oops. I posted this in the wrong board.... If a mod could move it, that would be appreciated. Sorry...

Greetings! The news of Xen support being deprecated pushed me to finally update from 6beta5a to 6beta15 so that I could move my Plex server from a VM to Docker (it worked great and I've been busy, so I just let it go). I jumped in and just tried a direct upgrade by just replacing the main files on the flash and had a issues initially, which I described in a separate post http://lime-technology.com/forum/index.php?topic=39568.0 for posterity, but then went to a clean installation, where the issue below came up. Machine: - MB: Gigabyte H97N-WIFI - PROC: Intel i5-4570 (I think) - RAM: 8GB memory - 3x 3TB Seagate drives - 1x 600GB old western digital drive mounted outside of array (go file) for my old XEN VMs (to be replaced with an SSD cache once I get things stable) Software Info: - UnRAID v6b15 Basic License - Fresh installation - No plugins - Xen boot option - No VMs running at the time, but I had a few domains configured (all stopped because I got my Plex Docker running) - One Docker running, Plex Media Server Problem I got my Plex docker up and running successfully with my old Library copied over, so I stopped my old VM running Plex, kicked off a parity check and went to bed. In the morning, Plex docker was still working, shares are available, SSH works, but no WebGUI. Webpage Not Available. Tried Chrome and IE, cleared cache, still no WebGUI. Syslog attached: - interesting bits most likely near the end - worked on the machine on and off through the day, you can see some of that in the syslog I think - line 1127 was when I left the machine for the night (failed notification authentication, decided to deal with it later) Server is still running this way - I thought I'd ask for feedback first since it might not happen again and we'd miss the chance for diagnostics. I'm relatively useless in Linux based systems but I can handle the command line if the directions are clear. Let me know if there's anything else I can do for troubleshooting/diagnostics. Thanks in advance for the help! 2014.04.27.syslog.zip

Hello, First of all, I didn't do much troubleshooting on this issue and now will have difficulty replicating it for further analysis and troubleshooting. I'm posting in case it's useful in the future or support for issues others are having. If it's interesting enough to LT or anyone with a similar issue, I will try to make time to replicate as I have a backup of the flash that created the issue. Machine: - MB: Gigabyte H97N-WIFI - PROC: Intel i5-4570 (I think) - RAM: 8GB memory - 3x 3TB Seagate drives - 1x 600GB old western digital drive mounted outside of array (go file) for my old XEN VMs Previous Installation: - 6 beta 5a - Xen boot option - 1 linux VM running (PV) just running Plex Media Server - Appdisk mounted outside of array (go file) for VM storage - Appdisk shared through samba manually - powerdown plg installed (2.06 I think) - possibly some other minor tweaks I'm not remembering Problem: I tried updating to beta15 just by replacing the main files (as per the upgrade instructions). I honestly didn't expect it to work given all the changes over the year or so it's been. The server booted and... - Webgui never came up. - I could not SSH/Telnet or even PING the server, or see it in my router's DHCP list. - Shares were not up. - My VM booted and was available to the network. This was a surprise, considering I couldn't access the server itself. - Replicated this over several reboots. - I did plug a screen in and could log in directly to the console, but I didn't have time to mess much further than this. - Shutdown via console or power button (powerdown script) worked, but I didn't grab the syslog before nuking everything and trying a fresh installation... Troubleshooting fail. Sorry. Like I said I was pressed for time so I didn't troubleshoot much. The fresh install has mostly worked (I have a couple other posts on these problems) so I continued with this for now unless there's outrage at my lack of willingness to work on this issue... Thanks!

Worked well for me for a month but admittedly not tested extensively yet. Its also been in a shipping container for a couple months while I moved so I almost forget what I did test.

Thanks. I think I'll put the critical data on an external drive to carry with me, and I will replicate it onto my desktop and laptop so there are multiple copies just in case.

I'm moving overseas and my server will be packed and shipped in a container with the rest of my belongings in a few weeks. Truck, rail, boat, rail, truck or something like that to get from Canada to France. It will be packed by professional movers. That said, I don't necessarily trust them and will be supervising to ensure it's packed well. Any advice on how to go about packing it? Should I package drives separately? I have the original box and Styrofoam the case came in. The server is a Fractal Design Node 304 with 3 drives. No massive heatsinks or anything like that. Thanks!

How is your build going? I'm looking at this board for a new build and curious to hear your thoughts. Not sure if it's on your radar but it does appear to support VT-d (there's a bios setting for it).

If I had to guess I would say that it's probably the power supply that died. If it was running for a very long time without a cold restart, components (probably capacitors) could have slowly aged and worn out. When you power on the computer there is a large peak of inrush current that stresses components far more than normal operation, and those components may not have been able to handle it anymore. The inrush provided the extra push to destroy something and boom! Dead power supply. May have continued running for years had you left it on. You might still have a working system sans power supply.

I can't speak specifically to the Node 304, but my Fractal Define R4 has excellent dust proofing through the built in filters. I didn't open my desktop for 1 year and it's pristine inside. In the same environment, my previous Antec Sonata case filled up with a significant and noticeable dust layer plus heatsink clogging fuzz in a similar time period. If the Node 304 filters in a similar fashion to the Define R4 you should be in good shape provided you clean the filter periodically to keep air flowing (I didn't clean it for that entire year, and the filter was full of dust...).

Meanwhile, I am contemplating adding 2 or 3 graphics cards and reducing as many computer as possible! (That is assuming that the VM's are just about as stable as bare metal when all this is said and done...) I am super excited to start playing with KVM when the latest VM updates are released from LT! Another data point: I'm interested in having a GPU in a small form factor NAS. I am planning a rebuild of my unraid box into a small form factor HTPC style case. Then I'll do some experimenting with passing a GPU through for use as a HTPC and receiving steam streams from my gaming rig running windows. If this goes well, I may eventually turn my gaming rig into the unraid server (either unraid as hypervisor or another hypervisor with virtualized unraid) and use the SFF box as a front end HTPC and receiving steam streams and possibly as also an unraid backup box. I'm looking forward to a simple unified approach to managing VMs in Unraid that doesn't involve a significant amount of messing around. I enjoy the geek stuff but I don't have time for it anymore, otherwise I'd just set up a system on Arch or Debian or whatever and do it all myself. I like the blend of DIY/geek and easy-to-use that unraid currently provides and hopefully will provide with future functionality.

Enabling IGMP Snooping on my router seems to have helped the issue. More testing to verify but I can see the DLNA server on my phone for the first time now. I was having the same issue and IGMP seems to have done the trick. Anyone any idea why Plex on unraid would work fine but in a VM has dodgy DLNA? I have no idea. In my case I think IGMP has something to do with the router deciding which traffic to pass between the wired and wireless LAN, based on my 2 minutes of searching. The VM is on the LAN and the clients are all wireless, so this seems to make sense. However, I previously had Plex running on my W7 machine on the same LAN as the VM, and had no issues seeing the DLNA server on wireless. I think it's something specific to this VM somehow.

Answered no because on my current "production" server, I'm still running unRAID basic. I have a drive (HDD) mounted outside the array to host an application VM. For my new server (in the works), I will be eventually upgrading to a PLUS license, assuming I can get all the virtual machines running how I like. I might use a cache drive if I think I have space to share with VM storage, but honestly I don't see the need for my purposes. In this case the cache/vm storage would be on an SSD. What I really would like to do is have a btfrs raid1 volume mounted outside the array for VM storage, but this is a long way off in my todo list.

I encountered this same issue when working on a new server on the weekend trying to get 6.0-beta5a up and running. I believe what was happening in my case was that the BIOS would detect the USB key and begin booting unraid, but after the unraid kernel takes over, it was unable to find and mount the USB drive. This would only occur when I connected the USB drive to USB ports connected to one particular USB controller on my motherboard (GA-Z77X-UD5H), and it would boot fine from any port on the other two controllers. Mouse and keyboard connected to the rogue USB controller also did not work in unraid. The USB controller that was causing the problem actually has VIA USB hubs connected to them (on the motherboard) as port expanders - perhaps for some reason unraid was not able to deal with these hubs. I can replicate this boot failure by hiding a USB controller from unraid using pciback in the sysconfig file, then connecting the boot drive to the hidden controller. When I get some time I'll check the BIOS to see if there are any settings I missed related to IOMMU... And also cross my fingers for beta6.

Enabling IGMP Snooping on my router seems to have helped the issue. More testing to verify but I can see the DLNA server on my phone for the first time now.