Veah

May want to have a fresh flash drive handy. Containers dipping in and out have been precursors for mine failing. Let's see what some others may glean from your log.

Have a look around for an AMD Epyc cpu/mobo combo. Sweet spot for me are cpu 7xx2 number indicating gen 2. Pcie lanes for days and low power consumption if keeping to 24 cores or less.

Change your DNS from 192.168.1.1 to cloudfare, Google, 9s... See if you still have the problem. If the problem goes away, it is your dns setting within 192.168.1.1. if problem persists, there is another network issue at hand. Dns servers: 1.1.1.1 8.8.8.8 9.9.9.9 208.67.222.222

Your server won't have that gpu once it is passed thru.

If eBay is available to you, check there. You should be able to do it for $50 for a reputable brand used (I see Trendnet now), or a new something straight from China which has worked out ok for me previously. Anyway, good luck.

This is a confusing architecture. Is it possible to get a cheap 2.5G switch? If so, go gateway/router > 2.5G SW > 2.5G server nic. Also connect 2.5G SW > 2.5G pc nic. Shut off the PC wifi. Shut off server 1G nic. I believe that will get you to where you want to go.

Get an Intel. All the others can be a bit of a gamble especially with freebsd type things like pfsense. I use a 540 that showed up with no issue and they are not too pricey these days.

Move your licensed USB to new hardware and set it up.I f you have another pc and a USB drive dock, could plug in the old drives individually and move that data to your new unRAID via network. Or populate new unRAID with old drives and swap them out individually starting with parity. That could take quite a long time for the disk rebuilds. Or... I think I saw a Spaceinvaderone video a while back outlining a scenario where he was able to populate a drive then install it in an array by tweaking something and some voodoo magic, not 100% sure on that one tho.

Some would use the SSD as a cache drive. What you have will not break anything though.

Do you know for certain that the new hdd is powering up? Can you hear/feel it spin up? Problem following from lsa to mb connector makes me think power delivery. Edit: double check all the cables

Can you see it from command line by using ip a? Here's a link to some ifconfig commands to set your IP. Maybe some old fashioned cli is what you need. https://www.thegeekstuff.com/2009/03/ifconfig-7-examples-to-configure-network-interface/ Unfortunately I don't know enough to do more than point you where I would look. Good luck.

That is handy to save on the building time after installing. Should get you to where you want to go. Now if I had only waited 6 more minutes, I'd not have typed up the above. hehe

If you want to reuse the disk, it has to have some format type. Just format it to match the filesystem you intend to use it on. NTFS, FAT, FAT32, ... there's a bunch. I use XFS for unraid storage and btrfs for my nvme 'worker' drives. If putting it back in your unraid system, wait until your current parity is finished rebuilding then pop your disk back in. Treat it like a new drive and let unraid format it for you. Will be like a new drive added to the array. Or replace a current drive, it works the same.

I had something similar when installing more nics. I got through it by checking the iommu boxes on all the nics I do not want to use for unRAID itself. After the obligatory reboot, I was able to see the nic I was looking for. It was almost like my system only wanted to display 2 nics in the network config section.

Try setting up some junk containers and see what their speeds check in at. Their behavior might give some insight. Easy enough to remove them after you see what your speeds are. Maybe a libretest container to see if those speeds only change when going out of network. Kinda brainstorming to help get an idea.

I run nzbget through a VPN and have not noticed a difference. I keep it throttled at 120Mbps.

Create the new share 'Media' Use a file manager, I like the simplicity of Dolphin (now deprecated) open up your split window and cut/paste from your original locations '/tv' to '/Media/tv' Super important to use Cut, not Copy. Provided you do not limit which disks are used in the creation of the share, the paste should be super fast as entire files are not being moved, only header information is changed. Give it a test on a few large files.

Yes. Each time a disk changes you need to let it rebuild. After adding the first 16TB drive, your rebuild time is going to go through the roof. If you are in a hurry to be complete, there are probably better methods out there.

I think I have it. Had to take mine offline to double check what I am saying. First remove the second parity drive by stopping the array and unassigning it. Your current state will be 1 parity + 7-4TB drives Edit: Swap out parity drive to 16TB drive. Let it rebuild. Your current state will be 1 rebuilt 16TB parity + 7-4TB drives Swap out Disk 1 in your array using the steps I mentioned in first post. Your current state will be 1 rebuilt 16TB parity + 1-16TB + 6-4TB drives. Swap out Disk 2 in your array using the steps I mentioned in first post. Your current state will be 1 rebuilt 16TB parity + 2-16TB + 5-4TB drives. Get the Unbalance app Use the Unbalance to move all your data from Disks 3-7 to Disk 1 and 2. Your current state will be 1 rebuilt 16TB parity + 2 16TB + 5-4TB drives (Disks 3-7 being empty) Properly disable and remove Disks 3-7 Your Final state will be 1 rebuilt 16TB parity + 2-16TB drives.

Ok I think I misunderstood. You are trying to go from 9 drives to 3... Ignore what I posted. Give me a few min to think this through. Question: what size are your parity drives? They need to be the largest. I only use a single parity and I gather that's what most people do. Might consider that. Is the final configuration going to be parity + 3 16T drives?

I would swap them one at a time. **Method involves 3 parity rebuilds** 1. Identify a single drive to upgrade. 2. Stop the array. 3. Unassign drive that you are replacing 4. Shutdown system. 5. Remove old drive and replace with new one. 6. Turn on system. 7. Assign new drive. 8. Turn on array. 9. Allow parity to rebuild it. Do that for each drive. GL

Haha. I love how you basically zoomed the camera out a bit for that. Admittedly, I did try an unbound container from the apps plugin to go alongside a PiHole container... I could not get it to work right. I was able to get it working using the pfsense unbound but it was flaky on the pfsense side and I had to periodically restart the unbound service. I stumbled upon some walkthroughs that got me where I am now and it seems to be doing the trick.

Whatever it was, I am glad it is working better. This UnRaid can be so fun, addicting and frustrating all at once.

^^ This works. I now run PiHole on a VM (Ubuntu) because I was most easily able to integrate Unbound into it for that recursive <3

I am probably way off but this reminds me when I had something similar. Turned out my network interfaces were being reassigned to different system nics so my assigned IPs were getting hosed. Good luck.