JorgeB

When you restarted cache likely came back up online, still recommend using an Intel SATA port for the SSD, if for nothing else so that it can be trimmed.

Check filesystem on disk6: https://wiki.unraid.net/Check_Disk_Filesystems P.S: we don't recommend using reiserfs for many years now, you should convert to xfs.

Tools -> Diagnostics, please attach the complete zip.

Nope, cache is outside parity.

Not without the diagnostics.

Check filesystem on disk6: https://wiki.unraid.net/Check_Disk_Filesystems P.S. reiserfs is not recommended for many years, you should convert to xfs.

All is well, pre-fail you see is just the type of the attribute, the important part is the failed column (and the values themselves).

Please use the existing plugin support thread:

Your cache device dropped offline, suggest not connecting it to the HBA, use one of the onboard Intel SATA ports, swap with another disk if needed.

Unraid doesn't disable a disk without a write error, write errors can be caused by many things, post new dags if it happens again, hopefully it will catch the issue next time.

It's still there, make sure you're on "menu view" (upper right).

Having the same issue transferring to an UD share means it's not a general share issue/config, you could still try a brand new install, or a trial flash and see if the problem remains, if yes it's not likely on Unraid side.

It's a known issue, workaround for now here: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta25-available-r990/?do=findComment&comment=10098

Disk5 looks healthy, what do you mean by this: Where are you seeing the disk is failing?

There are some recovery options here, but that filesystem went bad in way that suggests there could be a hardware problem, like bad RAM, you should run memtes.

Please post the diagnostics: Tools -> Diagnostics

Please don't double post:

Please post the diagnostics: Tools -> Diagnostics

It appears to be a device problem: Aug 17 08:08:32 Daniz-unRAID kernel: BTRFS info (device sdq1): disk space caching is enabled Aug 17 08:08:32 Daniz-unRAID kernel: BTRFS info (device sdq1): has skinny extents Aug 17 08:08:32 Daniz-unRAID kernel: sd 8:0:15:0: [sdq] tag#7434 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Aug 17 08:08:32 Daniz-unRAID kernel: sd 8:0:15:0: [sdq] tag#7434 Sense Key : 0x3 [current] Aug 17 08:08:32 Daniz-unRAID kernel: sd 8:0:15:0: [sdq] tag#7434 ASC=0x11 ASCQ=0x0 Aug 17 08:08:32 Daniz-unRAID kernel: sd 8:0:15:0: [sdq] tag#7434 CDB: opcode=0x28 28 00 01 58 fa 80 00 00 20 00 Aug 17 08:08:32 Daniz-unRAID kernel: blk_update_request: critical medium error, dev sdq, sector 22608512 op 0x0:(READ) flags 0x1000 phys_seg 2 prio class 0 Aug 17 08:08:32 Daniz-unRAID kernel: BTRFS error (device sdq1): failed to read block groups: -5 Aug 17 08:08:32 Daniz-unRAID kernel: BTRFS error (device sdq1): open_ctree failed You can try cloning the device first with ddrescue, though it usually works better with spinners, there are also some recovery options here but they are not much likely to work on failing devices.

Disk look perfectly fine, though wait for the extended test to finish to confirm.

Run a btrfs scrub on that device, it will list the corrupt files on the syslog, those files need to be deleted/replaced.

That looks like a virtual IPMI device, it shouldn't count if there's no image loaded there, check the IPMI settings.

You're using a RAID controller, that's not recommended, we recommend a regular HBA, you can use that controller but need to create a JBOD/RAID0 volume for each disk on the controller BIOS, note that if you replace it with a different model in the future Unraid won't find the existing disks.

Start by booting in safe mode and running the server as a basic NAS without dockers/VMs for a couple of days, if it still crashes likely that it's likely a hardware problem, if it doesn't start turning the services on one by one.

It would be my #1 suspect, it uses the same driver as the SASLP/SAS2LP that have known issues with Unraid v6, most often dropping disks without a reason.