JorgeB

It does appear to be fixed for 1st posts, still happended for a moved post though, didn't yet test after flagging a spammer.

Not really, /mnt/user is working and don't see any shfs errors, is it the same if you boot in safe mode?

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Run it without -n or nothing will be done.

Please post the diagnostics: Tools -> Diagnostics

Problem was caused by one of the cache devices dropping offline: Apr 4 18:50:50 M1171-NAS kernel: ata1: softreset failed (1st FIS failed) Apr 4 18:50:50 M1171-NAS kernel: ata1: limiting SATA link speed to 3.0 Gbps Apr 4 18:50:50 M1171-NAS kernel: ata1: hard resetting link Apr 4 18:50:55 M1171-NAS kernel: ata1: softreset failed (1st FIS failed) Apr 4 18:50:55 M1171-NAS kernel: ata1: reset failed, giving up Apr 4 18:50:55 M1171-NAS kernel: ata1.00: disabled There's a known issue with the onboard SATA controller in some Ryzen boards, look for a BIOS update, or use an add-on controller.

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

The problem is the filesystem in the destination disk: Apr 3 20:28:07 Tower kernel: REISERFS error (device md9): vs-5150 search_by_key: invalid format found in block 232203785. Fsck? Apr 3 20:28:07 Tower kernel: REISERFS (device md9): Remounting filesystem read-only Also good idea to convert all reiserfs disks to xfs, reiserfs is not recommended for v6.

It's fine with the usual warning that since they can't be trimmed write performance might degrade over time.

Is that a hard drive or an SSD?

Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. Also there might be a fix for this in v6.9.2.

Remove this line from config/share.cfg: shfs_logging="1" I seem to remember this could cause issues.

Please post the diagnostics: Tools -> Diagnostics

See here and if it continues to crash try this.

Correct, newer kernel can detect previously undetected corruption, user should downgrade, backup cache and the upgrade and re-format.

Tested passed so disk is good for now, pending sectors are false positives.

First run a correcting check, then a non correcting one, post new diags if there are still sync errors.

This is a Linux/LSI issue, not Unraid, at the time I tried with Arch Linux and it had the same problem, which is not surprising since Unraid uses a standard kernel. Also, very easy to flash an LSI, you can do it using Unraid.

Fractal Design launched an upgraded tray, there's also an adapter for existing trays.

It's logged as a disk problem and the SMART test failed so it should be replaced.

I believe the clear stats button is not working with v6.9, so you'd need to reboot, or possibly stop/star the array.

Try this and then post that log after a crash.

SMART test passed so disk is OK for now, recommend replacing/swapping cables just to rule them out and keep monitoring.

Apr 1 08:33:13 Vault emhttpd: unclean shutdown detected A few sync errors after an unclean shutdown are expected, if you haven't yet run a correcting check. Still showing some ATA errors, you should replace cables.

Start by posting the diagnostics: Tools -> Diagnostcis

Looks more like a connection problem, replace cables on that disk and try again. If you mean the UDMA_CRC errors those are a connection problem, usually the SATA cable.