JorgeB

No, that cannot be rename, you can create/rename user shares since they are just any top level folder.

Are the disks detected y the boards BIOS? If not they also won't be detected by Unraid, and you likely have a hardware problem, or the 3.3v SATA pin issue, google that.

You can either replace the disk or shrink the array so that disk is eliminated.

Please post new diags if you didn't reboot after the scrub.

Enable the syslog server and post that together with the complete diagnostics after a crash.

Yes.

Nope, that's it.

If it still crashes then it's a different issue.

You can take a look at the syslog for any call traces, but ipvlan has been solid for now.

Try changing network config to defaults, i.e., enable DHCP, then disable bonding and set the DNS servers to 208.67.222.222 and 208.67.220.220 instead of using your router.

It's a possibility, then you can test the other disk with more time.

You should be able to keep using the server, reboot to clear the errors and avoid high i/o like parity checks/rebuilds.

Unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), start array and post new diags.

Nothing relevant logged that I can see, did you check internet is still working on other devices when you see that?

It's logged as a disk problem but SMART looks mostly OK and the extended test passed, I would keep if for now, but any more errors on the next parity checks would recommend replacing.

It's logged as a disk problem and SMART is showing some issues, run an extended SMART test.

Could be a power/connection problem, but I would suspect more a controller issue, Marvell controllers are not recommend for Unraid, if possible replace it with one of these.

Sep 6 21:44:17 Lawson-NAS kernel: nvme nvme1: I/O 908 QID 8 timeout, aborting Sep 6 21:44:17 Lawson-NAS kernel: nvme nvme1: I/O 916 QID 8 timeout, aborting Sep 6 21:44:17 Lawson-NAS kernel: nvme nvme1: I/O 917 QID 8 timeout, aborting Sep 6 21:44:17 Lawson-NAS kernel: nvme nvme1: I/O 918 QID 8 timeout, aborting Sep 6 21:44:17 Lawson-NAS kernel: nvme nvme1: I/O 919 QID 8 timeout, aborting Sep 6 21:44:47 Lawson-NAS kernel: nvme nvme1: I/O 908 QID 8 timeout, reset controller Sep 6 21:45:17 Lawson-NAS kernel: nvme nvme1: I/O 8 QID 0 timeout, reset controller Sep 6 21:45:50 Lawson-NAS kernel: blk_update_request: I/O error, dev nvme1n1, sector 1068352 op 0x0:(READ) flags 0x80700 phys_seg 27 prio class 0 Sep 6 21:45:50 Lawson-NAS kernel: blk_update_request: I/O error, dev nvme1n1, sector 1836344 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 Sep 6 21:45:50 Lawson-NAS kernel: blk_update_request: I/O error, dev nvme1n1, sector 1837776 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0 Sep 6 21:45:50 Lawson-NAS kernel: blk_update_request: I/O error, dev nvme1n1, sector 2003208 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Sep 6 21:45:50 Lawson-NAS kernel: blk_update_request: I/O error, dev nvme1n1, sector 1838768 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Sep 6 21:45:50 Lawson-NAS kernel: blk_update_request: I/O error, dev nvme1n1, sector 146702808 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0 Sep 6 21:45:50 Lawson-NAS kernel: blk_update_request: I/O error, dev nvme1n1, sector 2263264 op 0x0:(READ) flags 0x80700 phys_seg 13 prio class 0 Sep 6 21:45:50 Lawson-NAS kernel: blk_update_request: I/O error, dev nvme1n1, sector 1068960 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0 Sep 6 21:45:50 Lawson-NAS kernel: blk_update_request: I/O error, dev nvme1n1, sector 84863328 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 0 Sep 6 21:45:50 Lawson-NAS kernel: blk_update_request: I/O error, dev nvme1n1, sector 84862880 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Log shows issues with one of the NVMe devices, power cycle the server and try again.

Run a correcting scrub on the pool and post the results.

That indicates a network related issue, could be NIC, NIC driver, cables, switch, network config etc

Besides the warranty, Red/Red Plus are 5400rpm, Red Pro are 7200rpm.

Btrfs is detecting data corruption, start by running memtest.

Not seeing any obvious issues in the logs. Shares are just top level folders, if there's a 'NAS' folder in any of the disks a new share will be create with the default settings.

Assuming the pool is still mounting just copy anything important elsewhere, then re-format and restore the data, you can use for example the Dynamix File Manager plugin to easily copy the files.

It that is removed it's possibly a power/connection problem, much less likely it could also be a board problem.