JorgeB

Disk still appears to be failing, it's not even giving a valid SMART report, good news is that the emulated disk1 is mounting so you just need to replace that disk then assign it to the disk1 slot to rebuild.

Fist thing I would try would be a different PSU.

rsync with --delete will delete on the destination any files that don't exist on source but IIRC it will leave the empty folders, you can delete those after, if that's OK you can use: rsync -av --delete /mnt/share/ dest_IP:/mnt/share/ Double check paths are correct before running, or do a dry run. Another option is to run a sync utility in a Windows PC, like syncbackfree, it will be probably be a little slower but it will also delete the empty folders, or use rsync first then this to delete the empty folders.

Remove -n or nothing will be done, if it asks for -L use it.

Are you going to copy the data manually as mentioned or using ddrescue? For ddrescue you use the devices identifier, /dev/sdX for both source and destination.

Disk appears top be failing, don't format anything, replace/swaps cables and post new diags after array start.

Diags are after rebooting, so we can't see what happened, probably a problem with the SAS2LP since they are known to drop disks without a reason and the disk looks healthy. It does to me.

Check filesystem on those disks.

Did you run memtest like asked?

Like mentioned in the link above the DOS/Windows package includes the firmware, Linux package is needed just for the flashing utility. Also as mentioned do it with the array stopped, and it won't affect the data.

Diags are after rebooting so we can't see what happened, start by updating the LSI firmware since all p20 releases except the latest one have known issues, then re-enable the disks and if it happens again grab diags before rebooting.

Except for limiting the total bandwidth that won't be a problem, i.e., that by itself is not a reason for having stability issues, you can only use the available motherboard lanes, can't do anything to try and use more than the available number.

Checksum errors mean btrfs is detecting data corruption, start by running memtest.

El controlador Asmedia no se puede inicializar: Mar 4 02:04:44 Tower kernel: ahci 0000:01:00.0: can't change power state from D3hot to D0 (config space inaccessible) Aunque el error no es el mismo, puede intentar ver si esto ayuda: https://forums.unraid.net/topic/97628-solved-unraid-on-qnap-ts-453b-mini/?do=findComment&comment=900555

Taking a look at the diags, and although you didn't follow my instructions, it would have still worked but you ran into same bug again, like mentioned above you can't remove a pool device and then change the number of pool slots, this shouldn't be allowed, and it won't be in rc3, since by doing that the unassigned device is not deleted from the pool.

Start by running memtest, also see here.

Unlikely that USB related issues would power off the server.

Doesn't matter now if you nuked it but the pool was 2 devices, not 3, that's the members I said to use, the original ones: Data Metadata System Id Path RAID1 RAID1 RAID1 Unallocated -- -------------- --------- -------- --------- ----------- 1 /dev/nvme1n1p1 770.00GiB 5.00GiB 32.00MiB 156.48GiB 2 /dev/sdf1 770.00GiB 5.00GiB 32.00MiB 156.48GiB -- -------------- --------- -------- --------- ----------- Total 770.00GiB 5.00GiB 32.00MiB 312.96GiB Used 400.38GiB 1.56GiB 144.00KiB Then you'd remove the SSD and only after that add the new device.

Change the onboard controller from IDE to AHCI/RAID.

Is disk3 not mounting? Might be a filesystem issue, you can post current diags.

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

You can add setterm -blank 0 to /boot/config/go

You can copy as much data as possible to another array disk(s), still recommend first connecting it to onboard Intel SATA since the SASLP usually crashes/drops the disk when it encounters a read error.

Make sure system notifications are enable.

Disk5 dropped offline so there's no SMART, probably because of the controller, but it does appear to be failing, suggest connecting it to the onboard SATA ports (swap with another disk) and then and since parity isn't valid run ddrescue to try and recover as much data as possible. Pparity looks healthy, though would recommend getting rid of that SASLP controller since they are not recommended for a long time, replace it with an LSI HBA.