JorgeB

IIRC the cable on the HP can't be replaced with one of those, the SATA part is part the the backplane.

If it wasn't formatted the only other explanations I can think of are: -the server was hacked and data deleted -cleaning up some docker with a mapping to the user share that deleted everything

I would try the Intel controller, some Samsung SSDs can be weird with some controllers, mostly from AMD, but also Asmedia.

What controller is it connected to? If possible use an Intel AHCI SATA port.

Not really a network guy, but you have IPs from the same range attributed to both NICs, and since they are in a bond I believe that won't work, if Unraid has two or more NICs configured as an active-backup bond you only assign an IP to the first NIC, if you want to use them seperatly you can but need to disable the bond and set IPs from different sub-nets. If yo can't currently access the GUI you can boot using the GUI mode and re-configure the LAN or delete/rename network.cfg and network-rules.cfg both on the flash /config folder and reboot to get the setting back to default.

Disk1 looks completely empty, like if it was formatted, do you remember doing that, possibly because the disk was unmountable?

Currently there's no good driver support for your NIC, it should be included with next beta release (v6.9-beta23) which is expected very soon.

Yep, you need to.

Please post new diags with the array started.

Not limited if you use the LSI IT firmware.

Best bet it to use one of the existing Wiregueard support/config threads.

There are known issues with Realtek and Linux in general, some NICs work reasonably well, others not so much, and it can change with any new release, if you can use Intel NICs.

That NIC should work with the next beta.

Go to Broadcom's support site, it's under legacy.

This isn't a really recommended way of using Unraid, you can do it, but at least make sure you have a way of monitoring the RAID and individual disks health, i.e. make sure you're warned if there's a problem with the RAID or it might be too late when you notice. The cache pool can be used as direct storage, it just dependents on how you configure the use cache setting for your shares, also with 4 devices I would use btrfs RAID10 (or RAID5 if you have good backups).

https://forums.unraid.net/topic/93941-cant-connect-to-network-on-new-unraid-build-maybe-ethernet-driver-issue/?do=findComment&comment=870517

Procedure looks to be all correctly done, and honestly I could never imagine how it could be user error since any deviation from the procedure will abort it or not even work, the sync errors start right after the 8TB mark, and curiously they are not on every block, it's every third one, I'm going to try and duplicate this with similar size disks to see if I can find out what's triggering it, if I can't I'll ask Tom to take a look.

Run without -n or nothing will be done, and if it asks for it use -L

You can find the 9211-8i firmware on broadcom's support site, under legacy.

I can't really understand what happened, and why the pool recovered after a format attempt, I can see wiping a device failed because it was busy, that's likely part of what helped, still most likely you were just lucky, that should never happen.

That's normal with btrsf, it's the the allocated size, btrfs first creates empty data and metadata chunks before writing data there, so there are 90GiB of chunks on disk and 86GiB are used. raid1, so 86GiB x 2 Because the GUI uses GB, not GiB, 86Gib=93GB

You can still swap them with another disk.

Enterprise devices should still maintain good performance even without trim.

It should be mostly dependent on the SSDs used, like mentioned I also haven't noticed any slow on my SSD array so far, I'm using WD Blue 3D SSDs for data and a WD Black NVMe device for parity, what are you using?

SMART attributes look OK but there's a recent device error logged, difficult to say if it's a disk problem just by that, I would suggest replacing/swapping cables on that disk to rule them out and rebuild, if it happens again after that it's likely a disk problem. P.S. also a good idea to update the LSI firmware since it's very old, current release is 20.00.07.00