tucansam

Will preclear securely overwriite data on a disk, for example one that is being disposed of or resold? Thanks.

Diags attached. Drive is not even weeks old, went into a red x state out of nowhere. Tempted just to reboot and rebuild parity, but I can't get SMART to run on it as its disabled. I may just replace it with a spare and then test it in another system. ffs2-diagnostics-20221107-1852.zip

Failing to start and giving me this: -- auth-user-pass credentials.conf comp-lzo verb 1 crl-verify crl.rsa.2048.pem ca ca.rsa.2048.crt disable-occ Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2022-11-05 19:00:29.107208 [info] Host is running unRAID 2022-11-05 19:00:29.173033 [info] System information Linux 6c771cbf28b0 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux 2022-11-05 19:00:29.253826 [info] OS_ARCH defined as 'x86-64' 2022-11-05 19:00:29.323327 [info] PUID defined as '99' 2022-11-05 19:00:29.403108 [info] PGID defined as '100' 2022-11-05 19:00:29.504147 [warn] UMASK not defined (via -e UMASK), defaulting to '000' 2022-11-05 19:00:29.582532 [info] Permissions already set for '/config' 2022-11-05 19:00:29.666134 [info] Deleting files in /tmp (non recursive)... 2022-11-05 19:00:29.755806 [info] VPN_ENABLED defined as 'yes' 2022-11-05 19:00:29.827421 [warn] VPN_CLIENT not defined (via -e VPN_CLIENT), defaulting to 'openvpn' 2022-11-05 19:00:29.902021 [info] VPN_PROV defined as 'pia' 2022-11-05 19:00:30.542531 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn 2022-11-05 19:00:30.644726 [crit] VPN configuration file /config/openvpn/openvpn.ovpn does not contain 'remote' line, showing contents of file before exit... client dev tun resolv-retry infinite nobind persist-key cipher aes-128-cbc 1 tls-client remote-cert-tls server auth-user-pass credentials.conf comp-lzo verb 1 crl-verify crl.rsa.2048.pem ca ca.rsa.2048.crt disable-occ -- Was running not ten minutes ago, and no changes made.

I have been watching sab for a while now, and I can confirm that it hasn't updated in several months. When I click the dockers tab, and list my dockers, all have updated over a period of a few months, except sab. I happened to have a slow start today, and decided to check the log, and saw this: -- 2022-11-01 15:45:40.993548 [info] Host is running unRAID 2022-11-01 15:45:41.059912 [info] System information Linux eba860994300 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux 2022-11-01 15:45:41.133026 [info] OS_ARCH defined as 'x86-64' 2022-11-01 15:45:41.209668 [info] PUID defined as '99' 2022-11-01 15:45:41.304346 [info] PGID defined as '100' 2022-11-01 15:45:41.408257 [warn] UMASK not defined (via -e UMASK), defaulting to '000' 2022-11-01 15:45:41.482371 [info] Permissions already set for '/config' 2022-11-01 15:45:41.564422 [info] Deleting files in /tmp (non recursive)... 2022-11-01 15:45:41.662756 [info] VPN_ENABLED defined as 'no' 2022-11-01 15:45:41.728683 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE 2022-11-01 15:45:41.811815 [info] Starting Supervisor... 2022-11-01 15:45:42,612 INFO Included extra file "/etc/supervisor/conf.d/sabnzbdvpn.conf" during parsing 2022-11-01 15:45:42,612 INFO Set uid to user 0 succeeded 2022-11-01 15:45:42,618 INFO supervisord started with pid 7 2022-11-01 15:45:43,621 INFO spawned: 'start-script' with pid 68 2022-11-01 15:45:43,625 INFO spawned: 'watchdog-script' with pid 69 2022-11-01 15:45:43,626 INFO reaped unknown pid 8 (exit status 0) 2022-11-01 15:45:43,638 DEBG 'start-script' stdout output: [info] VPN not enabled, skipping configuration of VPN 2022-11-01 15:45:43,639 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-11-01 15:45:43,639 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-11-01 15:45:43,639 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23111085713744 for <Subprocess at 23111085708848 with name start-script in state RUNNING> (stdout)> 2022-11-01 15:45:43,639 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23111085713696 for <Subprocess at 23111085708848 with name start-script in state RUNNING> (stderr)> 2022-11-01 15:45:43,639 INFO exited: start-script (exit status 0; expected) 2022-11-01 15:45:43,640 DEBG received SIGCHLD indicating a child quit 2022-11-01 15:45:43,650 DEBG 'watchdog-script' stdout output: -- What concerns me is that somehow the VPN is not starting. Plus I'm worried, and confused, as to why its not updating. I have made zero changes to sab, other than updating it (when it worked), and am not sure how to proceed. Options welcome, thanks.

I've got two servers, and 8-disk and a 17-disk. I understand that the array only functions as fast as the slowest drive. Over the last few months I've upgraded disks across both servers, and now am running 5900+ rpm NAS disks and 7200 rpm NAS and standard disks. Both servers contain an LSI 92xx series controller -- an 8-port and a 16-port. Both LSIs are in x8 slots on the motherboards. The 16-drive system has two parity disks on motherboard SATA3 ports, member disks on the LSI. The 8-drive system has one parity disk and all members on the LSI. For parity syncs and rebuilds, the 8-disk system averages 150MB/s. As I write this, its rebuilding the array using a new (to it) 8TB Seagate Archive, which is arguably to worst disk in the history of disks, and its currently doing 178MB/s. Conversely, the 17-disk system is currently rebuilding a new HGST 12TB 7200rpm NAS disk, and its doing 49MB/s. The last time a parity sync was done (finished overnight) it reported an average of 109MB/s. Wondering what is causing the reduced throughput on the larger array. I'm slowly doing new-configs on the larger system to remove the last remaining 8TB archives in favor of 12TB HGSTs, and will eventually have ever disk in the system on the LSI, with only a couple of NVMe disks for cache and dockers. Could the MB SATA3 ports be the bottleneck? Thanks.

The PS I am using is a Seasonic gold, ten months old. I don't believe it to be a power issue. The random reboots I am experiencing during a parity check came as soon as I added two 12TB parity disks and a 12TB member disk. I'm not sure where to start troubleshooting this particular issue. Removing the extra disks I mentioned above will allow me to remove an extra HBA that is running an external enclosure... I am slowly trying to eliminate variables. I was hoping to be able to get that all out of the system before I move on, as that stupid setup has caused me nothing but major issues since Day 1.

Thanks. Unfortunately I can't get a parity check to complete (the reboot issue I am trying to figure out) so I'm worried about doing it because I don't think a parity sync will work right now.

I am trying to mount a former disk to recover some data, and continue to get i/o error errors. Here's the log after a fresh power cycle on the disk. -- Oct 23 10:23:02 ffs2 kernel: ata5.00: NCQ Send/Recv Log not supported Oct 23 10:23:02 ffs2 kernel: ata5.00: configured for UDMA/133 Oct 23 10:23:02 ffs2 kernel: scsi 6:0:0:0: Direct-Access ATA ST3000VN000-1HJ1 SC60 PQ: 0 ANSI: 5 Oct 23 10:23:02 ffs2 kernel: sd 6:0:0:0: Attached scsi generic sg24 type 0 Oct 23 10:23:02 ffs2 kernel: sd 6:0:0:0: [sdy] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) Oct 23 10:23:02 ffs2 kernel: sd 6:0:0:0: [sdy] 4096-byte physical blocks Oct 23 10:23:02 ffs2 kernel: sd 6:0:0:0: [sdy] Write Protect is off Oct 23 10:23:02 ffs2 kernel: sd 6:0:0:0: [sdy] Mode Sense: 00 3a 00 00 Oct 23 10:23:02 ffs2 kernel: sd 6:0:0:0: [sdy] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 23 10:23:02 ffs2 kernel: sdy: sdy1 Oct 23 10:23:02 ffs2 kernel: sd 6:0:0:0: [sdy] Attached SCSI disk Oct 23 10:23:03 ffs2 unassigned.devices: Disk with ID 'ST3000VN000-1HJ166_W6A0TZ31 (sdy)' is not set to auto mount. Oct 23 10:23:04 ffs2 kernel: ata5: SATA link down (SStatus 0 SControl 300) Oct 23 10:23:09 ffs2 kernel: ata5: SATA link down (SStatus 0 SControl 300) Oct 23 10:23:12 ffs2 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 23 10:23:12 ffs2 kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Oct 23 10:23:12 ffs2 kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Oct 23 10:23:12 ffs2 kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Oct 23 10:23:12 ffs2 kernel: ata2.00: supports DRM functions and may not be fully accessible Oct 23 10:23:12 ffs2 kernel: ata2.00: disabling queued TRIM support Oct 23 10:23:12 ffs2 kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Oct 23 10:23:12 ffs2 kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Oct 23 10:23:12 ffs2 kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Oct 23 10:23:12 ffs2 kernel: ata2.00: supports DRM functions and may not be fully accessible Oct 23 10:23:12 ffs2 kernel: ata2.00: disabling queued TRIM support Oct 23 10:23:12 ffs2 kernel: ata2.00: configured for UDMA/133 Oct 23 10:23:16 ffs2 kernel: ata5: link is slow to respond, please be patient (ready=0) Oct 23 10:23:21 ffs2 kernel: ata5: COMRESET failed (errno=-16) Oct 23 10:23:23 ffs2 kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 23 10:23:23 ffs2 kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Oct 23 10:23:23 ffs2 kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Oct 23 10:23:23 ffs2 kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Oct 23 10:23:23 ffs2 kernel: ata5.00: NCQ Send/Recv Log not supported Oct 23 10:23:23 ffs2 kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Oct 23 10:23:23 ffs2 kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Oct 23 10:23:23 ffs2 kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Oct 23 10:23:23 ffs2 kernel: ata5.00: NCQ Send/Recv Log not supported Oct 23 10:23:23 ffs2 kernel: ata5.00: configured for UDMA/133 -- It won't stay mounted long enough to copy much data off of it. It mounts, I can 'ls' around, I can begin to copy stuff, and then it fails and is no longer communicating (won't show SMART etc). Power cycling it does help, but it drops again shortly after. I'm sure its failing. I'm running an extended SMART test on it now, but I'm not confident it will finish. Here's the SMART data I do have (the CRC errors are legacy I believe and from a bad cable)

I have begun replacing 8TB disks with 12TB disks, and now have a little wiggle room. Several very old 3TB and 4TB disks, four to be exact, need to go -- they are throwing errors and I have just finished copying all data off of them and onto other disks. The four disk are blank. I've read the FAQs and how-to's about doing a New Config. But before I take the plunge and remove four disks at the same time, I figured I'd post here for one final sanity check. What is the preferred procedure for permanently removing these four disks from my array? Thank you.

I've got 16GB and am going to try having plex x-code to /tmp

Have modern SFX PS's caught up to ATX's in terms of build quality, wattage, and bomb-proof-ness? I need to replace a decade-old ATX PS as I'm trying to solve a strange issue that might be PS related. I have room for another ATX, but moving to an SFX would allow me quite a bit more cable management and customization, every little bit of room matters. This would be a 10th gen i7 with 15 spinners and two NVMe SSDs, along with a super lower power VGA card and an LSI HBA. Several fans, nothing major. Cold start power-ons and parity checks are of course my main concern, when power draws are maxed. As an aside, I am reading through this thread now, but any recommendations on a good PS in an appropriate wattage would be appreciated. Thanks.

Turns out unraid has been writing syslogs to my pihole for a while after my last reboot failure, forgot I set that up. After trimming a, 18GB log file, here's the last few hours from when I last interactively logged in, until this morning: Oct 21 16:42:38 ffs2 kernel: eth0: renamed from vethef4de4f Oct 21 16:42:38 ffs2 rc.docker: headphones: started succesfully! Oct 21 16:42:39 ffs2 kernel: eth0: renamed from veth03888e9 Oct 21 16:42:39 ffs2 rc.docker: radarr: started succesfully! Oct 21 16:42:39 ffs2 kernel: eth0: renamed from veth39d4e10 Oct 21 16:42:39 ffs2 rc.docker: sonarr: started succesfully! Oct 21 16:42:40 ffs2 tips.and.tweaks: Tweaks Applied Oct 21 16:42:40 ffs2 unassigned.devices: Mounting 'Auto Mount' Remote Shares... Oct 21 16:42:40 ffs2 sudo: root : PWD=/ ; USER=root ; COMMAND=/bin/bash -c /usr/local/emhttp/plugins/unbalance/unbalance -port 6237 Oct 21 16:42:40 ffs2 kernel: eth0: renamed from veth547d63d Oct 21 16:42:41 ffs2 rc.docker: unifi-controller: started succesfully! Oct 21 16:42:49 ffs2 unassigned.devices: Remote Share '//FFS1/backups' is not set to auto mount. Oct 21 16:50:18 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1.local' 2>&1) took longer than 10s! Oct 21 16:50:47 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1' 2>&1) took longer than 10s! Oct 21 16:51:02 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1' 2>&1) took longer than 10s! Oct 21 16:52:00 ffs2 root: Fix Common Problems Version 2022.10.17 Oct 21 16:54:15 ffs2 kernel: vethef4de4f: renamed from eth0 Oct 21 16:54:24 ffs2 kernel: veth03888e9: renamed from eth0 Oct 21 16:54:36 ffs2 kernel: veth39d4e10: renamed from eth0 Oct 21 17:02:09 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1.local' 2>&1) took longer than 10s! Oct 21 17:05:24 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1.local' 2>&1) took longer than 10s! Oct 21 17:05:39 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1.local' 2>&1) took longer than 10s! Oct 21 17:15:01 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1.local' 2>&1) took longer than 10s! Oct 21 17:16:39 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1.local' 2>&1) took longer than 10s! Oct 21 17:16:53 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1' 2>&1) took longer than 10s! Oct 21 17:18:09 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1.local' 2>&1) took longer than 10s! Oct 21 17:18:38 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1' 2>&1) took longer than 10s! Oct 21 17:19:24 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1.local' 2>&1) took longer than 10s! Oct 21 17:20:52 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1' 2>&1) took longer than 10s! Oct 21 17:22:09 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1.local' 2>&1) took longer than 10s! Oct 21 17:23:43 ffs2 emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Oct 21 17:26:13 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1.local' 2>&1) took longer than 10s! Oct 21 17:27:42 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1' 2>&1) took longer than 10s! Oct 21 17:32:00 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1' 2>&1) took longer than 10s! Oct 21 17:32:10 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1.local' 2>&1) took longer than 10s! Oct 21 17:33:01 ffs2 unassigned.devices: Warning: shell_exec(/sbin/arp -a 'FFS1.local' 2>&1) took longer than 10s! Oct 21 17:39:14 ffs2 sshd[23216]: Connection from 192.168.0.14 port 52014 on 192.168.0.5 port 22 rdomain "" Oct 21 17:39:15 ffs2 sshd[23216]: Postponed keyboard-interactive for root from 192.168.0.14 port 52014 ssh2 [preauth] Oct 21 17:39:16 ffs2 sshd[23216]: Postponed keyboard-interactive/pam for root from 192.168.0.14 port 52014 ssh2 [preauth] Oct 21 17:39:16 ffs2 sshd[23216]: Accepted keyboard-interactive/pam for root from 192.168.0.14 port 52014 ssh2 Oct 21 17:39:16 ffs2 sshd[23216]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0) Oct 21 17:39:16 ffs2 sshd[23216]: Starting session: shell on pts/0 for root from 192.168.0.14 port 52014 id 0 Oct 21 17:48:47 ffs2 sshd[23216]: Connection closed by 192.168.0.14 port 52014 Oct 21 17:48:47 ffs2 sshd[23216]: Close session: user root from 192.168.0.14 port 52014 id 0 Oct 21 17:48:47 ffs2 sshd[23216]: pam_unix(sshd:session): session closed for user root Oct 21 17:48:47 ffs2 sshd[23216]: Transferred: sent 734128, received 9136 bytes Oct 21 17:48:47 ffs2 sshd[23216]: Closing connection to 192.168.0.14 port 52014 Oct 21 21:14:13 ffs2 ntpd[1687]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Oct 21 21:14:13 ffs2 rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] Oct 22 00:00:01 ffs2 kernel: mdcmd (37): check NOCORRECT Oct 22 00:00:01 ffs2 kernel: Oct 22 00:00:01 ffs2 kernel: md: check_array: not started Oct 22 03:10:10 ffs2 ntpd[1704]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Oct 22 03:10:10 ffs2 rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.2002.0 try https://www.rsyslog.com/e/2359 ] Oct 22 06:59:21 ffs2 webGUI: Successful login user root from 192.168.0.24 Oct 22 07:00:01 ffs2 crond[1725]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null Oct 22 07:06:08 ffs2 ool www[32507]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Oct 22 07:06:10 ffs2 rsyslogd: [origin software="rsyslogd" swVersion="8.2002.0" x-pid="483" x-info="https://www.rsyslog.com"] start

I restarted the parity check and woke up to the same condition... a rebooted server. I'll enable syslog and let it try again. The only hardware change I've made in 10 years are disk changes, and I've upgraded two parity and one member disk in the last week.

Parity check started, many hours later I checked on it and came to a server with a GUI but the array was not started. Said the parity check had errors, and after checking uptime it had obviously rebooted. Diags attached on the off chance that there's something useful there. ffs2-diagnostics-20221021-1643.zip

New cables for a bunch of drives. syslog is free of errors after a few minutes, speeds are slowly starting to climb.

Current operation started on Fri 14 Oct 2022 07:31:34 PM MST (today) Total size:12 TB Elapsed time:5 minutes Current position:2.35 GB (0.0 %) Estimated speed:410.1 KB/sec Estimated finish:338 days, 3 hours, 53 minutes LOL!!!!!!!!!!! I'm going to swap cables completely and see what gives.

Disk 20 is 11 months old and I see no SMART errors that are of concern, correct me if I'm wrong. I stopped, powered down, re-seated stuff, and started the reconstruction again. Same speeds are happening.

Not even sure what that means. But Disk20 is not being reconstructed, if it matters.

No change. Current operation started on Fri 14 Oct 2022 04:59:38 PM MST (today) Total size: 12 TB Elapsed time: 1 hour, 53 minutes Current position: 68.7 GB (0.6 %) Estimated speed: 12.5 MB/sec Estimated finish: 11 days, 36 minutes

Current operation started on Fri 14 Oct 2022 04:59:38 PM MST (today) Total size:12 TB Elapsed time:3 minutes Current position:618 MB (0.0 %) Estimated speed:2.8 MB/sec Estimated finish:49 days, 7 hours, 47 minutes -- Current operation started on Fri 14 Oct 2022 04:59:38 PM MST (today) Total size: 12 TB Elapsed time: 14 minutes Current position: 10.2 GB (0.1 %) Estimated speed: 7.0 MB/sec Estimated finish: 19 days, 22 hours, 45 minutes Just replaced my two 8TB reds with two 12TBs, and all went swimmingly. Now replaced a 6TB blue member disk with an identical 12TB, and reconstruct is jumping between 2.8MB/s, jumping to 25MB/s, and sometimes 44MB/s, but never exceeding it, ever. Mostly it settles back down to 2-7MB/s. I was hoping after a few minutes, whatever was maybe happening after a reboot to swap in the new disk would finish, and things would pick up. I'll monitor it again in a few hours, but right now its settled at an amazingly slow speed. Diags. ffs2-diagnostics-20221014-1710.zip

I just popped two 12TB refurbs in, I'm swapping out my 8TB Reds. The new refurbs have 17 hours on them. 17 hours. I'll advise what the other two have once parity is sync'd and I start swapping data drives.

Is there a simple command that will reliably test disk performance, similar to iperf3? Looking at ways to improve array performance, and with recent replies to another thread indicating that unraid only performs as fast as the slowest disk (something I learned long ago and then forgot), I'm left with either looking up the MFG performance specs of each individual disk (20 total, huge mix and match), or just running a benchmark of sorts to see which disks I should start replacing one by one. Thanks.

They have a warranty (90 days), and I'm going to be downgrading the number of disks in my array, so there will be a lot of copy/move and parity build/check sequences to blast the disks to death and test their overall health. Right now I have some WD Reds going on six years of continuous spinning. A few years ago I threw away my last Conner and Maxtor IDE 254MB disks from the dark ages of computing -- they would still power up and read/write data, although they were LOUD, I found some old documents on them from when I was a kid. And I've had dozens of 80s and 90s era unix workstations with 1 and 2GB Barracuda's that ran and ran and ran. Hopefully modern disks have a similar lifespan.

Thank you. Is it still considered best practice to place parity disks on a separate (in my case onboard) controller? I'm looking at reconfiguring to have two m.2 SSDs for docker and cache, two 7200rpm parity disks on the MB SATA, and 14 disks spread evenly across two LSI HBAs in x8 slots. Theoretically.

ok. Combo of 5400 and 7200rpm disks, LSI 92xx series, modern gen9 i5-based, and I'm looking for "in general" best practices for maximizing performance. Using rsync to copy from one disk to another, I get 60-80mbs avg, and if I queue up a second copy at the same time, both transfers drop to 9mbs.