JorgeB

It's up to you, if it's an auto check due to unclean shutdown you can cancel since if there were errors found you need to run a correcting check, and if there weren't you can run one later.

It will for sure until you re-start the array.

With Unbalance it's normal, since it's copying from array disk to another array disk, turbo write doesn't work for that.

No, turbo write should be as fast as your slowest disk at that position, assuming there are no controller bottlenecks, I can write at 200MB/s+ to some of my servers.

https://forums.unraid.net/topic/50397-turbo-write/

There already some bug reports about that.

See if downgrading to v6.9.1 helps, there are some known issues with v6.9.2 and spin down.

You can also check the system event log in the BIOS (or the IMPI event log) as there should be more info on which is the affected DIMM slot, then replace or remove that DIMM.

#1 reason for unexpected sync errors is RAM related, if just downclocking didn't fix it it could be a bad DIMM.

Are all de 28 drives connected to the expander? I remember reading that you could only connect 24 devices to these despite the extra ports.

There's is but you'll need to do a parity check, it will take as long.

Run memtest.

There's no mount option, that means no filesystem is being detected, you're trying an SMB mount, that won't work for this, post output of: fdisk -l /dev/sdf

If it's not being detected anymore yes.

You might need to downgrade back to v6.8 but try this first, with the array started: btrfs-check --clear-space-cache v1 /dev/md1 then btrfs-check --clear-space-cache v2 /dev/md1 Re-start array and see if it mounts, if it still doesn't post new diags.

Yes, unassign disk, start/stop array, re-assign disk and start array, but only rebuild on top if the emulated disk is mounting and contents look correct.

NOTE: split from FAQ thread, please don't reply in that thread. If the pool is raid1 you can first remove one device then add anther one.

Diags are after rebooting so can't see anything about the flash drive but there are some strange repeating SATA link down warnings: May 31 10:37:03 afterdark kernel: ata4: SATA link down (SStatus 0 SControl 300) May 31 10:37:03 afterdark kernel: ata3: SATA link down (SStatus 0 SControl 300) May 31 10:37:04 afterdark kernel: ata5: SATA link down (SStatus 0 SControl 300) May 31 10:37:04 afterdark kernel: ata6: SATA link down (SStatus 0 SControl 300) May 31 10:37:04 afterdark kernel: ata4: SATA link down (SStatus 0 SControl 300) May 31 10:37:04 afterdark kernel: ata3: SATA link down (SStatus 0 SControl 300) May 31 10:37:04 afterdark kernel: ata5: SATA link down (SStatus 0 SControl 300) May 31 10:37:04 afterdark kernel: ata6: SATA link down (SStatus 0 SControl 300)

Yes, just make sure the emulated disk is still mounting before rebuilding on top.

There are constant controller errors with that disk, try replacing/swapping cables/slot with another one and rebuild.

SMART looks fine, please post complete diagnostics (tools -> diagnostics) it might give more clues.

No, you could add them as UD devices if you share them over the network.

GUI only allows a share to use one pool, you'd need to manually create the share in the other pools, the share should be configured to use cache=only and you'd need to copy any data to the other pools using the disk shares, but after that all the data in those pools could be access using the user share.

Disk looks fine, try rebuilding again and if it hangs see if you can get the syslog, if you can't get it using the GUI copy it to flash drive then attach here: cp /var/log/syslog /boot/syslog.txt

You have something trying to access a user share before the array is started: May 31 13:43:29 Tower emhttpd: error: share_luks_status, 5992: Operation not supported (95): getxattr: /mnt/user/Camera May 31 13:43:29 Tower emhttpd: Starting services...