When things are not actively monitored, features stopped working without knowing. This has to be find out. At least all Armbian distributions have the same kernel, regardless of its upstream origin - Debian X,Y,Z and Ubuntu A,B,C ... have same kernel. But of course kernels versions go up all the time. I am not managing this that deep / specific. Where to search? On this forum. I am sure that this was already brought up.

@LanMarc77, I think you meant to tag @laibsch there What you're saying sounds like it could be a good option.

Actually, the connections on the cable harness appear to be good as well as all the capacitors. They are not expanded and they are not leaking--and no, I am not certain. I did not consider that it might be a board issue because I sniffed the board, there were no unusual odors when the system is powered up. Visually nothing appeared burnt. The failure occurred randomly after functioning for 4+ years. It has always been connected to an Online UPS that supports AVR, and Pure Sinewave on my server rack. I am not proficient at soldering, nor do I have a microscope, soldering iron or any of the required accessories to attempt a repair. For testing purposes, yesterday, I supplied power using an external power source from a USB enclosure and it worked. SATA Ports 1 and 2 are both functional, it is definitely related to power. I am meeting with my CEO tomorrow to discuss purchasing a new NAS type system. Leaning towards an HPE MicroServer Gen11. Going from a fantasic little affordable unit to an actual server that is going to cost around CAD$4,000 (price includes HDDs). YIkes. Thank you to everyone that took the time to read and reply though. I appreciate you, your time, and your suggestions. I was hoping I could just buy a cable and move on lol.

Alright, let's give a real quick overview where the code for A20 comes from. Let's focus on current. First stop. Board config: https://github.com/armbian/build/blob/main/config/boards/bananapipro.csc -> BOARDFAMILY="sun7i" Next stop. Family config: https://github.com/armbian/build/blob/main/config/sources/families/sun7i.conf -> No sources defined. However there are includes. Next stop. Includes: https://github.com/armbian/build/blob/main/config/sources/families/include/sunxi_common.inc -> No kernel source URL defined. Therefore kernel comes from mainline (kernel.org to say). However a version is tagged: v6.12.43 So we know: Linux source comes from unmodified mainline and the version is 6.12.43 Next stop. Patches: https://github.com/armbian/build/tree/main/patch/kernel/archive/sunxi-6.12 -> vendor family = sunxi, kernel major.minor is 6.12 All these patches are applied on top of the kernel source from kernel.org. And yes, that's a lot. I think sunxi is the worst family regarding number of additional patches to make stuff work. Next component is u-boot. https://github.com/armbian/build/blob/main/config/sources/families/include/sunxi_common.inc -> BOOTBRANCH:-"tag:v2024.01" so uboot is tagged to this version. So we know: U-Boot source comes from unmodified mainline and the version is v2024.01. And BOOTPATCHDIR="${BOOTPATCHDIR:-"u-boot-sunxi"}" which means here we find the patchset put on top of that version. Let's check. https://github.com/armbian/build/tree/main/patch/u-boot/u-boot-sunxi -> folders starting with board_ are applied only if the target board is being built. All remaining paches are always applied. There are more definitions of stuff appling for multiple families, whole architectures or even all boards regardless of architecture but in this case they are not important. Just including for the sake of completion/information: https://github.com/armbian/build/blob/main/config/sources/armhf.conf https://github.com/armbian/build/blob/main/config/sources/common.conf Good luck.

@grendel Sure you're certain you need a new cable harness? A few years ago, I replaced the HDD power switches myself, they’re just small smd transistors. 1 and 2 (Channel A) power on simultaneously, followed by 3, 4, and 5 (Channel B). There’s a built-in delay between the two channels to help manage voltage spikes that occur during HDD initialization — Channel A starts first, then Channel B.