daddygrant

Thanks... I figured it out after re-reading some of your previous posts on the matter. What I did. There is minor down time between stopping the array to assign the drive. 1. Unassign old drive 1 from the pool 2. Let cache balance 3.Assigned the new drive into the pool. 4. Let cache balance 5. Unassign old drive 2 from the pool 6. Let cache balance 8. Drink beer and enjoy my new larger single drive.

I factory reset the bios, cleared the cmos and now I'm back in business. Everything is now appearing in Unraid.

@testdasi I appreciate your assistance. See the attached diagnostics. Card = Intel DC P3520 1.2TB level2-diagnostics-20200210-1211.zip

Hey everyone, I am trying to add an Intel NVMe card to my Unraid setup but it's not showing up to the system. I know the card works so I figure there is a configuration issue I need to work around. I have an NVMe m.2 running perfectly fine in the system as well. This is what I've already tried, 1. disabling/enabling all virtualization features 2. Reset the card 3. Swap the card ( I have two ) 4. Move the card to a different slot. Any pointers on where to go next? Uuan

Hey, I'll like to go from my two 480GB SATA SSD cache to a single Intel Enterprise 1.2TB NVMe cache drive. Currently both SATA drives are in a cache pool. I can have all three drives physically connected to facilitate the move. So, I need a sanity check on the fastest method to get this down with minimal down time (I do have backups just in case). Here is what I'm thinking. Method 1 1. Stop array 2. Set Cache from 2 to 3 3. Assign NVMe to slot 3 4. Start array 5. run a balance (Anything special needed?) 6. Stop array 7. Unassign the two SATA drives from cache setting 8. Start array Method 2 (A friend's suggestion due to BTRFS magic ) 1. Stop Array 2. Remove both SATA from Cache assignment 3. Assign NVMe to slot 1 4. Start Array Thoughts?

I love how easy it is to add functionality to unRaid through the strong community applications. Also this platform allows me to reuse all my old drives more efficiently than solutions by QNAP and Synology. In 2020, I would like to see VM backup and restore functionally added via the GUI. Cheers and Thank you.

I found the problem. Oddly enough, the local endpoint information went blank. I re-entered the information and now I'm rocking with LAN access client profile. The client profile for server only access is still not showing traffic.

Interesting thing. I got it working last night from the phone without issue. Easy as pie. But, This morning I added a few more clients and none can connect including my phone that worked fine last night. The clients say connected but that isn't reflected on the server and traffic is not passing. Firewall ports and DDNS are good. Any thoughts?

I turned off the QNAP OpenVPN service and everything is working now. Thank you.

OK. Thank you for confirming my suspicions. I'll disable it and use an openvpn docker for the same duties.

That is correct. The built in one from Qnap.

I'm experiencing something very similar with my QNAP. I moved from unraid and it was working then it was not. I looked at /etc/daemon_mgr.conf but only found "DAEMON53 = openvpn, start, QNAP_QPKG=QVPN /usr/sbin/openvpn --config /etc/openvpn/server.conf --daemon ovpn-server" and not the "stop" other have removed to solve the problem. My logs look good on the container but access is a no go. I'm receiving the error: 192.168.1.54 took too long to respond. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_TIMED_OUT

Updating the firmware fixed everything for me. Thanks for the tip.

Thanks for the suggestion. I haven't tried that but I will.

I updated but had to revert back. My Windows VM with HW GPU pass-through (Quadro P2000) was unable to start. I received the error "internal error: Unknown PCI header type '127' " I also checked the IOMMU Groups and even recreated a VM from scratch but it was still a no go. My system has one video card so I figured it was a reset bug.... I could be wrong.