-=Striker=-

Not sure that I can offer any help, but after upgrading to the latest Unraid (6.12.3) on Thursday last week, it's happened to me twice where my Docker has "failed to start" even though it was running fine (up until it wasn't) and all it takes is a reboot to get it going again. No disks are 100% full. I don't see any obvious errors occurring on my cache drive. SMART tests pass. Will try scrubbing. Just thought I'd add on to your post in case the issue is related.

All of my 2TB drives were installed at the same time. They were all part of my original array and initial foray into Unraid, so I don't think they would be formatted differently. It's probably OK, just looking for some reassurance that i'm not going to FUBAR my whole array somehow and cause myself headaches in the next few days....

Yup, I know I'll need to rebuild parity. I was just concerned that there were other files there of some importance that I would lose when pulling the drives and rebuilding. If it's just overheard, then that's fine and there should be no issue. Just seems odd that it isn't the same amount of overhead per drive which is why I was concerned.

So I've run Unbalance on four 2TB drives that I want to remove from my array and it's moved all of the visible data on to the desired 8TB drives, however in the summary screen, there is indication that there is 14 - 24GB left on each of my 2TB drives. What is this data? I can't see it (i've also tried ls -a -R -s from the command line which also returns no results). I'm concerned about what will happen if I remove these drives from my array. Is there some necessary data on there or is it safe to remove them?

Hi RiDDiX and thanks for the reply! I'm only passing through two Hauppague Colossus video capture cards. Otherwise everything is just standard VM components. Eventually I would like to pass through a FireWire card and a couple of USB devices, but they aren't allocated to the VM yet. Is it normal for the VM to use that much RAM to run the virtual hardware?

Hi Everyone, I'm trying to setup a Windows 10 virtual machine to run some hardware that requires 32 bit drivers. I'd like to maximize the available memory to this system which should be 4GB (as that is the limit of a 32bit system). I've created the VM and assigned the 4GB (as both the min and max available). When I boot Windows and check the RAM, it says 4GB installed 2GB Available. In my experience this is usually because RAM is being allocated to run an onboard video card, but that is with physical hardware, not a VM. Not sure why this would be happening. I've done some searching on these forums and I haven't found anything, but to be fair, there is ALOT of content on here so I may be missing it. Apologies if this has already been asked and I'm not finding the answer on my own. Any ideas why I can't get access to the full 4GB of RAM? Thanks!

Hi @ich777, Just following up to see if you've had a chance to look into FireWire support? I see a new build of Unraid Kernel Helper was released, but I don't see an option to include FireWire support in the build. Thanks!

I'm hoping someone here has some ideas, because I've been banging my head against the wall for hours and not getting allot of sleep. I was using Firewire support from the Unraid DVB package and things were working great. I was able to use Firewire inside a docker container to channel change some STB's. Recently, the Unraid DVB package stopped working and I need to find a different way to support Firewire so I can control my STB's. I've reached out to @ich777 to implement Firewire in his Unraid Kernel Helper similar to how it was supported in Unraid DVB, however I thought having a second method of trying to solve this wouldn't be a bad thing in case he is unable to offer the same support. So I know all the hardware can work as it has been working up until about a week ago. Since it last worked, I have upgraded to the Unraid 6.9 rc2 build so I could checkout the Unraid Kernel Helper based on some initial searching that it might be a replacement for Unraid DVB. I could revert to the last stable build of Unraid if that would help. I have created an Ubuntu VM and I have successfully passed through two of my onboard USB controllers and the HDPVR tuners plugged into those USB ports are working in the VM. So, I know (or at least I think I know) how to pass through hardware by editing the VM XML. I have done the same for my PCI based Firewire card. I'm attaching a copy of my VM XML incase i'm not doing the pass-through properly. The Firewire card is in its own IOMMU group: In the Linux VM however, I am not getting the Firewire behavior I want/need. I have four STB's connected, but I only see /dev/fw0. I would expect to see fw1, fw2, and fw3 as well. In the software I am using, SageTV, the Firewire control is not working properly for the fw0 device either. I'll be the first to admit that I don't know much about Linux, so I'm fumbling about and Firewire is old tech, so the info online is dodgy at best. I've seen posts that people have setup similar systems in the past, so I know this approach is possible and my hardware should support it. I just need some help connecting the dots. Any and all help is greatly appreciated! VM XML.txt

I totally understand. With my above comment, I wasn't suggesting that these need to be included in the DVB package again, I was simply stating that it had been done previously in case referencing a code check-in (if that's even accessible to you) would be of benefit. Also that based on the previous comments, it appears to be something that was a simple broad stroke inclusion of general driver support, so hopefully it isn't a huge investment of effort and time for you to implement. If including it through the Unraid Kernel Helper makes more sense, I'm onboard with that!

I can also add that the devices I'm connecting are Motorola DCX3200m digital cable boxes. Also, I don't know how much light it sheds, but in this thread, @CHBMB indicates that he enabled FireWire support in Unraid DVB kernel on February 9, 2017. If you (@ich777) would prefer to continue this in the Unraid Kernel Helper thread, i'm happy to move the conversation over there!

Here is the output from LSPCI: This is the card I ordered from Amazon incase the above info isn't enough: https://www.amazon.ca/gp/product/B00006B8EQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 I tried installing the Unraid-Kernel-Helper (both the docker container and the plugin), however when I go to Unraid Settings, launch the UKH plugin, and click on the 1-IQN tab, it just start constantly flickering and I have to close the browser tab.

thanks! I found a similar thread and was able to do some recovery. I also had the Community Application Backup installed that helped me do a restore, so most things came back, I can rebuild the rest.

I am attempting to get FireWire support working again since Unraid DVB has been deprecated and this driver package was suggested to me as the logical replacement. However, I've review this thread and I don't see anything specifically pertaining to FireWire support being offered by this package. Nevertheless, I've upgraded to Unraid 6.9 rc2, installed, and tried all four options (rebooting each time), but my FireWire card is never detected. Can anyone offer any insights on this? Right now, I use FW to do channel changing on some Motorolla STB units and if I can get the basic driver support going again, all should be good. All help is appreciated!

I can confirm that these settings work for me. How do these compare to the settings you're using? Maybe post a screenshot?

So I've been going through the forums and there seems to be a known issue of a cache pool being created in RAID1 for the data but single disk mode for the meta data. This thread describes a very similar issue to what I am having now. What doesn't make sense, is that in this thread it is stated that this was a known issue in 6.7+ but resolved in 6.8.1 rc. I created my cache pool using 6.8.3 so the bug fix should have been in place, but perhaps it has regressed?