-=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 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.

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?

OK, it is definitely something to do with these cables, I think that pin3 issue is the problem. I swapped from using a sata power connector directly off the PSU, to using a molex to sata converter (i found a post on another forum that says this is effectively the same thing as doing the pin3 mod), then connected the sata power to the drive and it shows up in WebOS! To answer the previous question, i am using a 1200 watt enermax platimax psu. Thank you everyone for the helpful input! I think this gets me going again!

OK, i don't know what the Pin 3 mod is. Could you please explain a little further what is involved? Alternatively, it might just be a matter of purchasing different cables? Are there ones that you would recommend? I was thinking of getting rid of these cables anyway as i don't like how bulky they are with the sata power connector directly on them, i'd rather have something with more of a pigtail style connector for the power.

I'm using a Coolermaster Cosmos case, it doesn't have a backplane, i'm connecting the drives directly to the LSI card. The cables are only one way as there is an SFF-8087 connector that connects to the controller which then splits to four SFF-8482 connectors. You can see the cables here: https://www.amazon.ca/gp/product/B013G4FEGG/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1 After connecting the four connectors to the drives, i've connected sata power connectors to the back to power the drives. I can feel the drives spinning when the system is powered on, but they don't appear in the WebOS.