Veah

It sounds like you are looking for 'New Config' and preserving data. Have used it several times for individual arrays. Not 100% sure if it would work right bringing drives from 2 different array. Seems like it should, but I do not recommend chancing it without some further confirmation.

Real head scratcher. Maybe @JorgeBhas seen something like this?

Looking again at pic, You got no parity... Is there data on drive 2? If not, just do a new config.

Sorry tried to edit. My connection seems bad enough that it's hard to forum

Ah. Apologies. Start the array at that point Edit: Unassigned drive there and start it. Should fire up with emulated data. Then stop it and assign the new drive.

Bottom of main tab is a little checkbox and button to format the drives listed to what you want.

Nothing spinning sounds like no power. Even without data cable they should spin up

Any remote location you can login to your server from (ie phone browser), you can shut it down. Big button on the dashboard. Was there something more particular you were looking for?

As far as UR is concerned, those 12TB drives do not exist. Check sata and power cables. They should pop right in without doing anything special.

Post diagnostics if possible.

Long shot: switch your ipvlan/macvlan setting.

Yes. That drive is not staying connected (edit: it has a problem rather which could be a failing drive. Run smart on it) for some reason. That needs solved. Parity reviews all the drives together so if there is a lame duck, it will hold up the whole process

It's possible your MB nic is bad. Are there any bios nic settings you can poke around with?

Give beta 7.0 a shot. Built in support for the GPU with different kernel. It's easy to roll back as long as you don't change some pool related zfs stuff.

It sure sounds like a cable or connection. What worked fine? Did plugging into a different switch establish a connection? If me, I would be putting new ends in the cable and a different port on the router/sw.

Put the 2 back and remove the 2 good ones u tested good. Then run it. If errors pop back up, then it's the memory or channel (MB)

I see this error alot: Oct 27 11:19:38 FatMan kernel: ata4.00: failed command: READ FPDMA QUEUED Think that is this drive: [4:0:0:0] disk ATA WDC WD30EFRX-68E 0A80 /dev/sdf /dev/sg5 Check it's data and power cables. If using power splitters, try and replace with direct power cable.

Check for latest fw on card and update MB bios.

Are the home laptops connected as guest or public networks?

If we presume memory and cpu are good and also MB and PSU cause can't test other known good, that leaves settings (in bios) or overheating. Another stretch with all the memory tests... Maybe one of the memory slots. Could test that by 2 tests one on ch.A and another on ch.B.

Ran into similar when UR was assigned the integrated nic only to eth0 leaving the x540 that I had connected physically to switch disconnected. Manually setting the x540 port as eth0 was my corrective action. I CAN see how the bonding solution above would get things talking but it would not be optimized; rather a temporary workaround.

That sounds like some sort of address assignment problem. Have a look at DHCP settings and also verify all other devices on network have unique IP addresses.

Quick test change DNS to something like 208.67.220.220 or 1.1.1.1 and give it a try

It sounds like you replaced it with new parity drive. If so, unRAID will rebuild that from scratch. Nothing you need to hang onto after that parity build is complete. Maybe hang onto it a few days to see if your new drive fails, but that's all I can think to hold it for.

Yes. Format it for any use you want.