JorgeB

That's a RAID controller, didn't notice in the OP, it's not recommended for Unraid, you want a HBA in IT mode, that one can still work if you create a raid0/jbod for each disk in the controller BIOS, but again, not recommended.

Please post the diagnostics: Tools -> Diagnostics

Those won't be using shfs, try enabling disk shares, then read directly from a disk share, e.g. \\tower\disk1

That's strange, make sure you grab the diags if it happens again. Same HBA is performing normally for me, if there's an issue I would suspect some kernel/Samba change first, do you have devices connect to other controllers you could test?

You did a new config, that's not part of rebuilding a disk, it's likely still possible to recover using the invalid slot command.

You should also run an extended SMART test, since there are recent UNC @ LBA errors.

Best bet is a file recovery util, like UFS explorer.

Don't recommend USB for array/pool devices, they tend to be very bad at error handling and drop devices frequently.

Very unlikely to be a drive problem.

Please post the complete diagnostics after you get the partition error.

Syslog rotated and is spammed with same error over and over, can't see the start of the problem, please reboot and post new diags once these start: Oct 5 20:55:45 ****** emhttpd: error: share_luks_status, 6411: Operation not supported (95): getxattr: /mnt/user/appdata

Unlikely, do you know what filesystem it was using originally?

Multi-pools only for now, multi-arrays hopefully in the future.

It's logged as a disk problem, and since it looks like it's a white label drive probably a good idea to replace it.

https://wiki.unraid.net/Shrink_array There are two ways of shrinking the array, both describe above, for this use the first one.

That's a JMB585, it uses the standard AHCI driver, I have multiple of those controllers working with beta30: [197b:0585] 04:00.0 SATA controller: JMicron Technology Corp. Device 0585 [14:0:0:0] disk ATA TOSHIBA HDWD260 0A /dev/sdp 6.00TB [15:0:0:0] disk ATA TOSHIBA HDWD260 0A /dev/sds 6.00TB [16:0:0:0] disk ATA TOSHIBA HDWD260 0A /dev/sdv 6.00TB [17:0:0:0] disk ATA TOSHIBA HDWD260 0A /dev/sdy 6.00TB [18:0:0:0] disk ATA TOSHIBA HDWD260 0A /dev/sdz 6.00TB Full diags might give more clues.

No NIC is being detected, check BIOS to make sure NIC is enable.

Looks like a hardware problem, possibly there's some issue with the NVMe device or it's a compatibility issue, if you can try a different NVMe device or try that device in another computer/OS.

Type "diagnostics" on the console and then attach them here.

Redo the flash drive, backup current one, re-create using the USB tool and restore only the config folder.

Yep, disk is failing, and xfs_repair will abort on a read error, best bet is to clone it with ddrescue then run xfs_repair.

This suggests a disk problem, please post SMART report.

Can confirm this bug, if disk shares are set to auto pool shares are still exported, never noticed before since I always have disk shares enable. For now you can go to Settings -> Global Share Settings and set "Enable disk shares" to "No"

Haven't needed one for years, so not up to date on them, a google search should find many options.

It's not possible to expand because of the existing small partition in the end, you'd need to move that partition before with a partition utility app.