JorgeB

No, it does when you type "diagnostics" on the console.

Yep.

Yep, no driver for that NIC, you can make a request, LT is usually quick to add them, if one is available for current Unraid kernel.

That's not a scrub, it's a file system check, there's also a GUI option for the scrub, corrupt files, if any, will be listed in the syslog.

Login on the console, then type "diagnostics" and upload the file here.

Any diags manually downloaded on the console will also be saved there.

It's not an LSI, it's a PMC Sierra pm80xx, there's a known issue with the new driver for those, you'll need to downgrade and wait for a new driver, or replace it with an LSI.

Those are not unclean shutdown logs, at least there's no shutdown logged, opened the same file twice, and only one shows an unclean shutdown, see reply below by trurl.

You should run a scrub to identify the corrupt files, most likely both copies will be corrupt, and in that case it can't be fixed, but you can delete them and restore from backups.

When Unraid needs to force a shutdown it will generate diags on the flash drive (logs fodler), attach the latest ones.

Please post the diagnostics: Tools -> Diagnostics (after booting in v6.9)

If SMART is filing it's another problem, you should post the complete diags.

Lots of CRC_UDMA errors, that's a connection problem, start by replacing the SATA cable.

No, this is bug.

Still not working in v6.9.2, bumping one last time in case it was missed.

Changed Status to Closed Changed Priority to Other

This is a general support issue, problem is the onboard SATA controller, quite common with some Ryzen boards: Apr 9 07:51:21 Ragnarok kernel: ahci 0000:01:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0xbf38a000 flags=0x0000] it then ends up dropping multiple cache devices: Apr 9 07:52:27 Ragnarok kernel: ata2: reset failed, giving up Apr 9 07:52:27 Ragnarok kernel: ata2.00: disabled ... Apr 9 07:52:52 Ragnarok kernel: ata5: reset failed, giving up Apr 9 07:52:52 Ragnarok kernel: ata5.00: disabled BIOS update might help, if it doesn't best bet (other than getting a different board) is to use an ad-don controller.

Please don't cross-post.

Scrub will only detect data corruption, file system might still fail to mount after upgrading, you might need to backup and start over or try to fix it with fsck (only after it's backed up).

Btrfs is detecting data corruption, this suggests a hardware issue, like bad RAM, and not that surprising since it's a known issue with Ryzen and overclocked RAM.

Please post the diagnostics: Tools -> Diagnostics

If booting in safe mode doesn't help you should create a bug report.

If the first check was non correct this is expected.

You can also use the terminal built-in the WebGUI. Use /dev/sdb1, also note that using a raid volume for cache is a very bad idea, btrfs should have direct access to the actual devices.