JorgeB

It's difficult to say, it can be good for weeks or months to come, or it can give more issues tomorrow.

Tools -> Diagnostics

That is mostly useless, it only changes if there's failing now attribute. Disk passed a recent extended SMART test, so it's fine for now (or it was at that time) and the pending sector is a "false positive", but SMART is showing some issues, likely will have more problems in the near future.

Click on disk1 and make sure fs is set to auto or btrfs, if it's not that post the diags.

Maybe, but that number on the SMART report can also be wrong, possibly a firmware issue.

Please post the diagnostics: Tools -> Diagnostics

Both on the syslog and on the SMART report error is consistent with a disk problem, but it's not definite, also sometimes they are intermittent, but SMART doesn't look very good, healthy WD drives should have 0 for Raw read error rate. Just unassign it and start the array, of course if a disk fails in the meantime...

Possibly, unless there was an unclean shutdown, if not something is wrong, only acceptable result after a parity check are 0 sync errors.

Jul 5 00:00:01 Arthur kernel: md: recovery thread: check P ... Jul 5 00:00:01 Arthur Plugin Auto Update: Checking for available plugin updates Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=0 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=8 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=16 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=24 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=32 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=40 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=128 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=136 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=144 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=152 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=160 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=168 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=176 Jul 5 00:00:02 Arthur kernel: md: recovery thread: P corrected, sector=184 Jul 5 00:00:03 Arthur Plugin Auto Update: unassigned.devices.plg version 2020.07.03a does not meet age requirements to update Jul 5 00:00:03 Arthur Plugin Auto Update: Community Applications Plugin Auto Update finished Jul 5 01:00:16 Arthur crond[1699]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Jul 5 02:15:21 Arthur kernel: md: recovery thread: P corrected, sector=2147483640 Jul 5 02:15:21 Arthur kernel: md: recovery thread: P corrected, sector=2147483648 Jul 5 02:15:21 Arthur kernel: md: recovery thread: P corrected, sector=2147483656 Jul 5 02:15:21 Arthur kernel: md: recovery thread: P corrected, sector=2147483664 Jul 5 02:15:21 Arthur kernel: md: recovery thread: P corrected, sector=2147483672 Jul 5 02:15:21 Arthur kernel: md: recovery thread: P corrected, sector=2147483680 Jul 5 04:03:01 Arthur root: /etc/libvirt: 924.2 MiB (969101312 bytes) trimmed on /dev/loop3 Jul 5 04:03:01 Arthur root: /var/lib/docker: 12.9 GiB (13809070080 bytes) trimmed on /dev/loop2 Jul 5 04:03:01 Arthur root: /mnt/cache: 1.2 TiB (1309510852608 bytes) trimmed on /dev/sdd1 Jul 5 04:40:01 Arthur apcupsd[9285]: apcupsd exiting, signal 15 Jul 5 04:40:01 Arthur apcupsd[9285]: apcupsd shutdown succeeded Jul 5 04:40:04 Arthur apcupsd[15213]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded Jul 5 04:40:04 Arthur apcupsd[15213]: NIS server startup succeeded Jul 5 04:56:01 Arthur kernel: md: recovery thread: P corrected, sector=4294967280 Jul 5 04:56:01 Arthur kernel: md: recovery thread: P corrected, sector=4294967288 Jul 5 04:56:01 Arthur kernel: md: recovery thread: P corrected, sector=4294967296 Jul 5 04:56:01 Arthur kernel: md: recovery thread: P corrected, sector=4294967304 Jul 5 04:56:01 Arthur kernel: md: recovery thread: P corrected, sector=4294967312 Jul 5 04:56:01 Arthur kernel: md: recovery thread: P corrected, sector=4294967320 Jul 5 08:03:28 Arthur kernel: md: recovery thread: P corrected, sector=6442450920 Jul 5 08:03:28 Arthur kernel: md: recovery thread: P corrected, sector=6442450928 Jul 5 08:03:28 Arthur kernel: md: recovery thread: P corrected, sector=6442450936 Jul 5 08:03:28 Arthur kernel: md: recovery thread: P corrected, sector=6442450944 Jul 5 08:03:28 Arthur kernel: md: recovery thread: P corrected, sector=6442450952 Jul 5 08:03:28 Arthur kernel: md: recovery thread: P corrected, sector=6442450960 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934560 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934568 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934576 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934584 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934592 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934600 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934608 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934616 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934624 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934632 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934640 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934648 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934656 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934664 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934672 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934680 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934688 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934696 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934704 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934712 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934720 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934728 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934736 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934744 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934752 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934760 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934768 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934776 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934784 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934792 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934800 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934808 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934816 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934824 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934832 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934840 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934848 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934856 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934864 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934872 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934880 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934888 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934896 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934904 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934912 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934920 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934928 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934936 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934944 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934952 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934960 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934968 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934976 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934984 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589934992 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935000 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935008 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935016 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935024 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935032 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935040 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935048 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935056 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935064 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935072 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935080 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935088 Jul 5 10:01:24 Arthur kernel: md: recovery thread: P corrected, sector=8589935096 Jul 5 10:01:24 Arthur kernel: md: recovery thread: stopped logging

If the backplane doesn't have an expander it's won't make any difference, i.e., if each disks connects to the HBA direclty, with a SAS expander the type of expander (SAS1, 2 or 3) and if it's linked using single or dual channel to the HBA can make a difference.

Looks more like an actual disk problem, you should run an extended SMART test. P.S: were all those sync errors expected?

Yes, you can set the general thresholds on Settings -> Disk Settings and you can also set custom thresholds for each assigned device if needed by clicking on it on the main page, e.g., for SSDs.

You can use the USB tool: https://unraid.net/download

Data on array devices won't be touched after a new config, and if you know which drive was parity you can check parity is already valid, device order doesn't matter with single parity.

It's logged as an actual disk problem, but since it passed the extended test it's OK for now, keep monitoring, you'll need to clear the errors to stop getting the failed report. Cache temp is normal if it's after some writes, you can set a custom temp warning for it.

You are passing through the Marvell controller to both the Ubuntu and Windows VMs, so as soon as you start either that controller will no longer be available to Unraid, dropping both devices.

That won't work, at least pretty sure it won't. This will: https://www.amazon.com/Internal-Non-Raid-Adapter-Desktop-Support/dp/B07T3RMFFT

That's normal, you'd likely have more errors on the next check/read, that disk should be replaced.

Remapping happens on writes only, errors usually happen during reads.

You need to re-create the docker image.

Yep, the larger the disk, the larger the overhead.

It's normal for newer xfs file systems, they use more space for reflink support and such.

Correction, like mentioned in the other thread the disk doesn't spin up, but the GUI stops showing the correct status, and once it spins up due to being accessed this command does prevents the disk from spinning down again.

Note: I also see some read activity right after running it, so Unraid it's interpreting this as the disk being accessed: