jknight

No thoughts on this?

They are actually Win 7 installs, if that matters

Both my Win10 VM's stopped working over the last day. They worked fine yesterday and I made no changed to anything. Now, when I fire up either of the VM's, I am greeted with windows message "Would you like to initialize network connectivity in the background?" It does not matter if i say yes or no, it can't be repaired. I do get the message that "The system seems to lack either network cards or network drivers". The network settings seem to be fine to me. but I don't understand much of it. I have tried turning off and then back on the network bridging and rebooted the server, but neither did anything. Any suggestions on what to look for?

That was it! Cirrus it is. Thanks so much.

Thanks. I did try populating the required fields, create and launch the VM, and the windows install would get past the first "loading files" screen, get to the windows logo, and then freeze up. I tried different settings, and finally found that changing the Hyper-V to false (I think, I am going off memory here), and it got a bit further, but it still gets stuck on the windows logo, though the logo looks like its alive (its glowing brigher and dims), but never gets past that part. So I don't know whats going on, and though maybe I was missing something. When I created VMs in the 6.0 or 6.1, I found a guide here with lots of steps including setting up the networking it needed. Your steps make it seem super simple now, but something isn't going right.

Hi. is there a guide on how to set up a windows 7 VM (using the template) for 6.2? I had found one a while ago using an older version, and I can't find it, and I am guessing its different now. Thanks - Jeff

Its been running fine. UnRaid came up no problems and my VM env is working.

I have ordered the ASRock C226M WS. I will reply back when its up and running.

Thanks. So the ASRock C226M is the same price, and it appears to fully support ECC memory, but only has 6 SATA ports. I supposed that tradeoff is OK since I can add a SATA card, which I already have. So the ASRock C226M is probably a better board to use?

Hi all. I bought a Dell T20 for the virtualization, but it only supports 4 drives, and I can't find a SATA card that works reliably with it (even the Dell recommended one). Plus the case is kinda small. So I am going to get a new motherboard and keep the CPU and memory from that system, but I want to keep the price low. I think that the ASRock H87WS-DL will work well and its about $110. It has 8 SATA ports and can handle ECC memory according to ASRocks website. I I will put putting on this board these parts from the Dell system: Xeon E3-1225 v3 Hynix HMT451U7BFR8A-PB 4GB DDR3 PC3-12800 1600MHz ECC CL11 Server Memory Anyone see any issues with this before I order? Or an alternate suggestion that is similar in price? I use the system for unRaid, VM and plan to do something like Plex. Thanks much! - Jeff

So I put the SSD on the motherboard SATA port and one of the hard drives on the add-in cards sata port, and the hard drive then went down a while later. So it appears to be the card. I have ordered a new Sata card.

it was run after the reboot when everything is running fine. I can wait until after it happens again and re-run it. I have replaced drives over the years, so maybe that accounts for why its up to 14. I only have 5 drives in there now including the parity and cache drives. I will check if its on the sata card or motherboard and if its not on the motherboard, I will move it there. Its running in PowerEdge T20 with with a Xeon E3-1225

Here is the diagnostic file. Thanks so much for your help! tiki-diagnostics-20160404-1244.zip

I have the 850 EVO, and don't see new firmware for that, but I will check. I will also check on the AHCI, but I am at work and can't check until I get home.

Thanks. So I switch it over to XFS it ran fine for a few days, and then it went into read-only mode again. Any other ideas? Could it be a bad drive?

I copied off the data, reformatted in xfs, and put the data back on. Hopefully it will behave better now.

Thanks. I tried that, and it didn't find any problems either.

Thanks! It is btrfs, so I ran scrub, with the default -r, and it found no errors: total bytes scrubbed: 68.25GiB with 0 errors. Anything else to try? It's a smaller drive, so I can move th data off and rebuild the drive.

Hi. Not sure this is the right form and if not, I will move. I have UnRaid, which I love, and I recently upgraded my system to handle VMs, and I bought a Samsung 850 EVO 250GB SSD drive to host the VM files, and created a Win7 VM. It runs great for maybe 1-5 days and then the hard drive seems to go into a read only mode. I can browse stuff on the drive, but cannot change anything. of course the VM crashes because its read only. I have to reboot UnRaid (I reboot within Unraid GUI), and when it comes up everything is fine, and then a few days later it happens again. Any ides on what I should check?

I got the PEXSAT32 card today, and it works and VM works too. So I am happy now.

It's not unraid with the problem, it's between the computer and the card. I have already ordered the card, so will report back on how it works. If not, I will try the one you mentioned. Thank much for your help!

Dell support said these cards are probably not supported and that's why they don't work. I had figured PCIe cards/slots were pretty universal. For now I will try the one they recommend, the PEXSAT32, and hope that works with Unraid/VM. Fingers crossed!

Here is what is written on the chip. Silicon Image Sil3132cnu Q2w794.1-1 Ad02kx2 And the sticker on the back of the card is Sd-sa2pex-2ir, and yes, I have the invoice from monoprice. So should I try updating the bios to the non-raid version. A part of me is wondering if the motherboard is bad and not seeing PCI boards that are plugged in. I think I will borrow a couple of boards from work and plug them in to see if they work.

I checked and I did order the card from MonoPrice on 2/28/2011. Not sure if that helps.

How do I check the chipset? Read whats written on the chips themselves? And I have never changed their firmware? Do you think upgrading that might help? And for the PEXSAT32, is there a fix for this problem if I do run into problems?