JorgeB

NIC driver crashed, if you can try with a different NIC, Intel recommended.

SSD has 4 partitions, make sure there's some available space on all of them, also check that sleep/hibernation is disable in the VM.

Try this and then post that log.

Not in Unraid, unless the IPMI plugin is compatible with Dell, but I don't think so, you should still get a notification there, Dell call's it iDRAC.

SMART looks OK, though SMART for SAS devices has less info, swap cables/slot with a different disk, if it fails again it's likely the disk.

Run a filesystem check, it might find a backup superblock and recover, but very unusual for the superblock to be missing/damaged.

Then swap backplane slot with a different disk to rule that out, if there are more errors it's likely the disk.

Run a test with the diskspeed docker and post the graph here.

Ok, that's much better, assuming the first check was non correct, you should be OK, but I would just run another non correcting check to make sure.

Please use the existing plugin support thread:

Yep

Disk8 will already be new, that procedure won't change data on any of the other data devices.

Don't know, never used it.

Open case isn't good for disk cooling, you need good airflow and fans moving air over and around the disks.

See here, make sure you're using the correct "power supply idle control" setting, also look for a BIOS update.

This will only work if parity is still valid: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, including old disk5 and new disk8, replacement disk8 should be same size or larger than the old one -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk8 -Start array (in normal mode now), ideally the emulated disk8 will now mount and contents look correct, it might not since the array was started without old disk5 so parity won't be 100% valid with it back in, if it doesn't mount hopefully a filesystem check on the emulated disk will fix it -If the emulated disk mounts and contents look correct stop the array -Re-assign disk8 and start array to begin rebuilding.

Replace/swap cables on disk2 to rule them out an run another check.

You need to update to latest v6.9-rc, also see this: https://forums.unraid.net/bug-reports/prereleases/solved-690-beta25-through-690-rc1-syslog-server-broken-error-in-logs-r1003/?do=findComment&comment=12179

Aim for 40C, 45C tops, those are definitely too hot, you need to improve cooling.

Not really a network guy, someone else might be able to help.

Were these consecutive checks? If so I would worry about a different number of sync errors.

Shares set as "prefer" are moved to cache, not array, see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=537383

This isn't an LSI model, it's the chip, the 9300-8i uses that chip but it comes as IT mode only, some other models with the same chip come with RAID firmware instead.

It's still showing as having a duplicate UUID: Jan 15 02:04:51 Tower kernel: XFS (dm-13): Filesystem has duplicate UUID 601cb298-100f-4990-b3ca-347bd2225192 - can't mount

Cache is single device, any share that has files on cache will appear as unprotected, e.g, for appdata: # Share exists on cache,disk1