Jump to content

NAStyBox

Members
  • Content Count

    313
  • Joined

  • Last visited

Community Reputation

27 Good

About NAStyBox

  • Rank
    Advanced Member

Recent Profile Visitors

1111 profile views
  1. Thank you. That's the exact definitive answer I was looking for. Not my favorite, but it's reality and helps with the decision making process for sure.
  2. Nothing really. The only difference is this is a headless machine. Typically a Win7 media center server is just a Win7 box connected to a TV that serves out to extenders over the network. When I bought unraid I tested Win7 as a vm with extenders on all TVs. This allowed me to get the PC out of my family room. It all worked the day it went live, and did for several months. Somewhere along the line it started botching the playback of recordings. Live TV is still fine, but an upgrade to Unraid, and I'm not sure which one, killed my ability to DVR. The media center machine was the reason for switching to Unraid. Before then I had the media center PC with its own drives, and my NAS was a little 4 drive Netgear appliance. So now I'm left with of course 3 choices. Rack another box to run VMs since Unraid is broken for my purposes by design, roll back unraid to an earlier release and live with stagnant code for the foreseeable future, or toss Unraid and upgrade to a hardware raid with SSD caching. The latter being a little expensive for a home solution, but I'm hooked on the cache drive thing. Spoiled, so to speak. I think I'll go with option 1 for now, and wait to see if the unraid problem is corrected inadvertently in later releases. Because drive space is still much more scalable than Freenas, which was always my second choice and is capable of running the Win7 VM correctly. It's a shame adding drive space to Freenas is a project, whereas adding it to Unraid is basically plug and play. WHYYYYY? lol
  3. No. Because then I'll have to field questions about everything else in the environment, lectures on better ways to stream video, and why am I doing it that way? Why don't I do it this way? Which will only piss me off and solve nothing, lol. The issue is beyond a shadow of a doubt with unraid VMs, that didn't sprout up until after I built this machine. That much I did prove. As for whether or not it's libvirt I won't know until it's rolled back. The only reason I asked about rolling back libvirt is they have made changes to their code that would affect video. So I figured that would be a great place to start. If there's a better way to roll back the entire VM portion of the unraid code, all the better.
  4. @Squid do you know if this is possible? Is there a way to roll back the VM piece to what it was in the 6.3.4 release of unraid? Because that worked fine. I don't know about the other pieces because I haven't researched it all yet, but libvirt definitely screwed around with video in the later releases. That's when the problem started. The whole time I was blaming my old cat 5 wiring and let it go, until I realized 1, it used to work fine with the same wiring, and 2. after testing I narrowed down the issue to the VM, which continued to reproduce the issue even after reinstalling windows into a new VM instance.
  5. I'm not sure who they are. But yeah, I've officially tried everything. My last two attempts were cycling through all the NetKVM driver versions, no help. Then I went on to change machine types, and figured out Windows Media Center won't work with digital signals using the Q35 machine types. I also uninstalled all the plug-ins, and grew a new appreciation for the CA plugin as it took me only 10 minutes to put them back, lol. But oh yes, I know. I worked in software support for a long time. Any problem will require reversing whatever gets changed. But if you look at the libvirt releases you can see where they screwed around with video in the later releases. Coincidence? Maybe. But the easiest way to find out is rolling back the version, or at least I think so. https://libvirt.org/news.html
  6. I posted this in anticipation of next steps. I'm not quite there yet, but getting there. I have a situation where I purchased unraid based on the fact that it could run a specific Windows 7 VM effectively. I haven't changed anything else in the environment that would lead to the problem I'm seeing, and after doing much testing have been able to trace the problem back to the VM, which has been rebuilt and still has the issue. I have tried absolutely everything to counteract this sporadic freezing issue with video playback, but the fact remains when I first started trying to address it I touched a Windows VM that had not been updated since the original install over a year ago, and the equipment pulling the feed is hardware (Windows Media Center extender) that also did not change. So when evaluating all of the pieces and parts to the issue, the only thing that did change is unraid, which I've updated regularly because I've seen other issues with it that I've hoped to address with those upgrades. Unfortunately, the only release that I know didn't have this problem is Unraid v.6.3.4. I know that because when I wrote my signature I wasn't having the problem. So if I don't start hacking up the product, I'm forced to revert the entire install to 6.3.4. Rather than do that I'd like to try and revert the piece of unraid that is likely the culprit, which is libvirt, or something in the VM portion of the product that I can't change . So if the folks at unraid would like to lend a hand, I really need to know three things. 1. What version of libvert was packaged with 6.3.4 2. What other packages(and versions of those packages) would comprise the VM portion of the product? 3. How would I be able to roll back the entire VM/KVM portion of the product to the equivalent of 6.3.4, yet still maintain all of the rest of the progress made between then and 6.6.1? This is one of those things I just have to get fixed because it feeds live tv to every tv in my home, along with DVR service. If I can't, I only have two options. Either build another Windows physical machine to feed my 7 WMC extenders and have two boxes running, or move to another solution entirely. I'd hate to waste the electric on the second box, and I've already evaluated every other consumer level NAS solution. Unraid is by far the best option for performance and scalability, with the only Achilles heal being security, which doesn't matter very much because it's behind a firewall and in a home.
  7. The best I know is yum, and that's not an option here. Let's say I wanted to roll back libvirt. How would I go about doing that in the CLI? I want to get to 3.10
  8. AH HAH!!! I think I just got down to libvirt. That HAS TO be the change in code. So I said I ran another WMC machine, and connected it to an extender, right? Worked fine. That wasn't a great test. All it did was test my network. Just now I remembered OTA recordings have no copy protection at all, so the .wtv files will play on any machine. I was able to reproduce the issue using an OTA recording for playback with my normal setup. Just now I played the same file I tested with, but on another Win7 machine, over the network. In other words from the unraid array. WORKED FINE!!! Then I went into the registry of that machine, and pointed its recording directory to that network share.(you can't do it from the gui because MS says network shares don't work, a policy they made up when everyone had 100mb networks) Then I attached an extender again. WORKED FINE!!!
  9. I'm having an issue and my hopes aren't high for getting any assistance with it. So before I look at other NAS solutions again I want to try and roll back the box to a much earlier release. Where can I download 6.3.4 or earlier?
  10. Nope, no CPU or memory issues. This VM was sized to handle 7 streams at once. Three more than Microsoft said it could do. When it was first built it could stream live tv to 7 tvs in the house, and playback 7 recordings without incident. Auto-updates are always turned off, so it was running the same code I built it with when the problem started. The only thing I upgraded was unraid. The signal comes from three HDHomeRun boxes. The oldest is an original HDHomeRun OTA box. Even that worked fine at the initial build. The other two are one Prime, and one of the more recent OTA boxes, I forget the model. I've tested with recordings from all 3. There is definitely a hiccup somewhere. It happens whether the recording is sitting on the array, or on cache/ssd. I verified that recently. That's what prompted me to swap NICs. I also have one PC in the house still running Windows 7. I set up WMC on it, and attached an extender to it. No problems with playback whatsoever, and funny enough that PC was on a wifi N connection. As for the video card, WMC was never developed to utilize a GPU. MSFT orphaned its dev internally before it ever got there. This is some sort of buffer that's choking. I'm almost positive. I've never documented the time to reproduce, but tonight I'll sit and do that by hitting pause when it happens, and documenting the time into the video. It's about the same time every time. What I really wish I could do is roll back to 6.3.4 in a few clicks. Because the problem didn't exist when I wrote my signature. I've never rolled back unraid, so I'm not sure if that's possible without a manual reinstall. I'd have to know for sure because I have nowhere to put 30tb of data and I'm not buying $1200 worth of drives to execute a test.
  11. This is driving me crazy, so I deleted the old thread I posted about this and am gonna try again flooding whomever reads with info. Unraid version is 6.6.1 Stable The scenario is this. I have a Windows 7 VM that exists to act as a Windows Media Center server for numerous extenders throughout the home. All the same model, Ceton Echo. Live TV streaming works fine, which doesn't read from disk. Recording works fine, because if I move around a DVR'd show I can move the stuttering. So the video file itself doesn't have the stuttering recorded. This stuttering is happening when playing back these DVR'd shows, aka video files. To prove to myself that the issue with with the array, I have taken the following steps. Used various different extenders for playback. All have same issue, even the one with the shortest wire to the switch that the NAS box is connected to. Rebuilt the Win 7 VM, and the same issue still occurs As much as I hate to, I installed ALL updates from "Windows Update". No change The NAS box was using one 10gb card into a switch with two 10gb SFP ports. I tried switching those, no help. I tried activating the on-board gigabit NIC, dropping VMs and Docker, switching the NICS, and no help. I tried isolating one extender and the NAS box on a different switch (gigabit to gigabit), and no help. So I've ruled out both the NIC and the switch The Win 7 VM runs off the cache drive, and new recordings go to the cache drive until Mover activates. Whether the recording is on cache or in the array makes no difference. Same stuttering, with about the same cadence. I've attached the diag file, so any help or thoughts would be greatly appreciated. Because my next step is to try and roll back a few releases, and after that rebuild unraid. This problem was not always there, but it seems to be within the unraid code. Everything else has been ruled out either via replacement or rebuild. nas01-diagnostics-20181003-2238.zip
  12. Hah! Looks good. But I'm looking for something more conventional. THANK YOU for posting the CSS file. I had no idea it was that small. Like you I don't mind the layout, but the colors have to go. Which folder does the CSS file reside in?
  13. Try the different variations in Settings > Display Settings with the field "Dynamix Color theme" . But I agree I'm not fond of the themes available. I wish they would give more focus to end user gui customization. For now I use "Azure". It should really have its own icon in "Settings", with options to change colors, fonts, etc. Because that "Azure" setting should be called "Azure through a dirty windshield". Whomever came up with that must have their contrast setting jacked way up on their monitor.
  14. I checked. Not installed anywhere that I can see. Reboots? As part of a maintenance routine. I want VMs to shut down, then Mover, Partity, bounce. Mover for whatever reason does not run well with a Win 7 VM running, and a parity check takes forever. If I drop VMs the parity check speeds up and no hang issues with mover. The problem with this particular Win 7 VM is it's there as a Win7 Media Center server, feeding extenders. So it's intermittently DVRing and writing to disk at random times for 30 to 120 minutes straight. That's probably why dropping it helps.
  15. What happened to Dynamix Schedules? No link to install it. Any other apps that allow scheduling reboots via gui? (a preemptive no-thanks but thanks on the CLI cron jobs)