trurl

Drive has disconnected.

Shutdown, check connections, restart, post new diagnostics

Copy current config folder.

Create new install and see if it will boot. May need to do "manual install method".
https://docs.unraid.net/unraid-os/getting-started/set-up-unraid/create-your-bootable-media/

Copy your config to the new install.

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/boot-and-startup-failures/#recovering-from-a-lost-boot-drive-and-unknown-parity-drives

Maybe correct this now and see if that fixes your problem. Looks like there is only 50G on there currently. Copy it to the array.

You will have to stop the array, click on the drive to get to its settings, and Erase the partitions. Set it to btrfs or ZFS. Start the array and format it. Make sure it is the only drive listed for formatting.

That suggests you somehow added 1.57TB to the formatted emulated empty disk.

If you stop and replace the disk, it will rebuild that added 1.57TB onto the new disk. But whatever was on the disk before you formatted it is gone.

Your log is full of GPFs. I suspect memory.

Have you done memtest recently?

Looks like there were problems with cache
Jan 21 19:51:37 Lovenest kernel: PANIC: zfs: rt={spa=cache vdev_guid=9190427880482758334 ms_id=12 ms_allocatable}: removing nonexistent segment from range tree (offset=400003009d08000 size=3000) https://docs.unraid.net/unraid-os/troubleshooting/common-issues/data-recovery/

Seems like the disk is the problem then. Maybe original died, and replacement has some problem as well.

Can you see either disk in another system?

You can rebuild 2 drives at the same time. Both parity, then 2 data drives, etc.

Probably not very risky since you will still have the original data drives.

You must always have good (enough) backups of course.

Parity is not a substitute for backups.

You must not attempt to run any computer unless memory is working perfectly. Everything goes through RAM. The OS and other executable code, your DATA. EVERYTHING. The CPU can't do anything with anything until it is loaded into RAM.

Since you have already connected "anonymously" Windows is probably using those credentials (probably something related to your Windows user name) instead of any others you may have created.

Delete all credentials to your server in credential manager, then recreate the credential you want to use and try again.

Speed isn't really much of concern for backup since once its done it only needs updates instead of whole backup.

I would just set it up as an "ordinary" Unraid array, then after initial backup taken you can add and build parity if you want.

You can Acknowledge those by clicking the SMART warning (👎) for the drive on the DASHBOARD page, and it will warn again if it increases.

SMART for disk1 is otherwise OK, and disabled/emulated disk1 is mounted.

Yes, you need to rebuild.

yes, also check power connection.

Make sure all cables have plenty of slack. Connectors should sit squarely and firmly on connection. Don't bundle data cables.

Emulated disk8 is mounted and nearly full. Should be OK to rebuild to a new drive.

I don't recommend naming your pool "pool"..

SSDs don't belong in the array.

You could create another pool for the 2TB.

Or you could add it to the existing pool and choose "Single" profile to combine their capacity.

Start in normal mode and post new diagnostics.

So in addition to NTFS, it probably has multiple partitions. And Unraid was only accessing one of the partitions so you were also missing space.
You must Erase the partitions before reformatting. You should see that option on the same disk page where you choose its filesystem.

Disk5 does have 8 reallocated but none pending so that should be fine, except for the obvious problems communicating with the drive. (UDMA...)

Emulated disk5 is mounted so should be OK to rebuild after you fix the connections.

Seems you don't have disks 1,3,4, I guess that is expected? So you have dual parity but only 2 data drives?

You can just reformat it to make it mountable again.

It wouldn't be if it shouldn't be.

If you have fixed your connection problems, since you have dual parity, you can rebuild parity and disk6 at the same time.

Stop the array, set parity to not assigned, leave disk6 not assigned, start the array.
Stop the array, assign parity and disk6, start the array to begin rebuilding both.

Attach Diagnostics ZIP to your NEXT post in this thread.

Preserve All, but since it is not the drive that was assigned to that slot, you will still have to assign it. And you must let it rebuild parity.