JorgeB

Basically yes, pre-clear is optional.

Please post the diagnostics.

SMART report is incomplete, looks like a disk problem.

If swapping cables didn't help it could be the disk, see if you can get a SMART report or post the diagnostics.

Dec 13 21:48:39 Tower kernel: BTRFS info (device sdg1): bdev /dev/sdh1 errs: wr 22953727, rd 19328774, flush 221212, corrupt 0, gen 0 Dec 13 21:48:39 Tower kernel: BTRFS info (device sdg1): bdev /dev/sdr1 errs: wr 0, rd 0, flush 0, corrupt 65, gen 0 Dec 13 21:48:39 Tower kernel: BTRFS info (device sdg1): bdev /dev/sdb1 errs: wr 50983508, rd 45647922, flush 817018, corrupt 0, gen 0 This shows you had multiple devices dropping offline in the past, probably not a the same time, but you want to be on top of that, the longer it goes without a correcting scrub after a device drops/reconnects the most likely you are to run into issues, Unraid doesn't warn the user if a pool device drops, see here for better pool monitoring, also btrfs raid5/raid6 still has some known issues, I only recommend using it with stable hardware, if your devices keep dropping will run into issues with it, especially if not immediately fixed. I run various raid5 pools without issues, but I keep on top of them and have backups, also keep in mind that no raid is a substitute for backups.

Dec 14 01:11:32 darktower kernel: XFS (md1): EXPERIMENTAL online shrink feature in use. Use at your own risk! Don't know what this is about, first time I see it, try running a file system check.

If you do you'll need to re-start the procedure from the beginning.

Looks like it, no driver was loaded for the controller.

Syslog is full of spam, and because of that the error from the rebuild is missing.

They are not, they have the same exact number of sectors, at lest for the last decade or so, this is certainly on purpose, or you could get into trouble replacing disks for e.g. RAID arrays.

Enable syslog server and post that after a crash.

Unfortunately there's nothing relevant logged, could be a hardware issue, look for a BIOS update, or try different hardware if available, ideally Intel based.

It's fine, the warning happens during the initial balance.

Enable syslog server and post that after a crash.

According to the other posts about that you just need the i915 module loaded for crashing, you you have it.

Did you also set the correct power supply idle control option in the BIOS?

No, you could move any data form emulated disk2 to other disk(s) and then do a new config and re-sync parity. Disk has a lot of pending sectors.

Could be related to this: https://forums.unraid.net/bug-reports/prereleases/69x-610x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-r1674/?do=getNewComment&d=2&id=1674

Was this disk2? Model Family: Seagate Enterprise Capacity 3.5 HDD Device Model: ST10000NM0086-2AA101 Serial Number: ZA2E1Z0F If yes it appears to be failing and needs replacing with a new one.

That's very strange, partition could be damaged, you should re-format.

Partition isn't using the full device capacity, you'll need to resize it or probably better yet, and to make sure all gets solved, is to backup cache, wipe the drives and re-format, then restore the data.

Enable the syslog server and post that after a crash.

Dec 11 11:05:46 SF-unRAID kernel: attempt to access beyond end of device Dec 11 11:05:46 SF-unRAID kernel: sdd1: rw=34817, want=896828480, limit=838860736 This is the main issue, but also a strange one, please post output of: lsblk -b

Enable the syslog server and post that after a crash.