JorgeB

Not overclocking the RAM is a good place to start.

Strange, don't remember seeing similar reports, maybe the devices are entering a lower power state immediately after idle and not showing SMART.

There's filesystem corruption on the pool, you should backup and re-format.

For a default install that's all you need, nerdtools will re-install anything it needs, /private of course only you can know if it's important or not.

There are different apps crashing and btrfs detecting data corruption, start by running memtest.

Pool went read-only because it ran out of space, if you want to fully use the pool capacity with different size devices use the single profile instead of raid0, reboot, see if you can free up some space then run a scrub to see if the errors can be fixed.

Config folder should exist from the beginning, post the output of ls -lh /boot

There's filesystem corruption on the cache device, best bet is to backup and reformat.

Try blacklisting the Radeon driver so it does not load: https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.10.0#Linux_Kernel

Please post the diagnostics.

Please post the complete diagnostics.

Try downgrading the BIOS to 1.6, it worked for another user with the same board: https://forums.unraid.net/topic/129735-solved-upgrade-from-692-to-6111-stuck-at-bzroot-now-what/?do=findComment&comment=1182700

It appears to be a Samba issue, problem started after Unraid updated Samba to 4.7.x, note that the files should still be deleted despite the error, though program might abort after deleting the first one due to the error.

Cache device dropped offline: Nov 19 13:20:07 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Nov 19 13:20:11 Tower kernel: ata1: COMRESET failed (errno=-16) Nov 19 13:20:17 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Nov 19 13:20:21 Tower kernel: ata1: COMRESET failed (errno=-16) Nov 19 13:20:27 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Nov 19 13:20:56 Tower kernel: ata1: COMRESET failed (errno=-16) Nov 19 13:20:56 Tower kernel: ata1: limiting SATA link speed to 3.0 Gbps Nov 19 13:21:01 Tower kernel: ata1: COMRESET failed (errno=-16) Nov 19 13:21:01 Tower kernel: ata1: reset failed, giving up Nov 19 13:21:01 Tower kernel: ata1.00: disabled Check/replace cables.

Maybe you are trying to see the info with the devices in low power mode, grey icon, it won't show when they are like that, same for spun down disks, only when the icon is green.

It's being logged as a disk problem for both, and "Elements in grown defect list" not being zero is not a good sign, run a long SMART test for both.

Nothing relevant logged, this usually suggests a hardware issue.

Set vm.dirty_ratio=2 vm.dirty_background_ratio=1 Yep. You can only use that if the data you are accessing is in a single disk or pool.

Please post the diagnostics.

Flash device is being detected as 0MB, try creating it manually: https://wiki.unraid.net/Articles/Getting_Started#Manual_Install_Method

Make sure the disk shares are being exported, default now is no, shares tab.

This is not a common issue, this thread you revived is from 2019, if the mover could cause this I would expect this issue to be much more common.

Use the 10GbE IP address or just add the Unraid server to the Windows hosts file.

It's not the same issue being discussed here, start by running memtest, if issues persist please start a new thread in the general support forum.

Changed Status to Closed Changed Priority to Other