oblivion2k

Confirmed 3.3v issue, thanks itimpi

I'm starting to think it's a 3.3v issue after all based on what I'm reading online. It's really the only thing that makes sense. I'll tape the pins and report back.

All drives are SATA. Some drives are attached to an LSA card in IT mode. Those drives show up. If I unplug them and plug in the new drives, they don't show up. I haven't had the time or resources to check bios on a normally headless system. I'll see what I can find. If they don't show up in BIOS, what should I do about that? I can't think of any reason why a drive of a certain size would show up, but not a slightly larger drive, at least not on a modern system. My understanding is that that's specifically an issue to WD easystore shucked drives, but correct me if I'm wrong, please. Also, the drives show up normally on other systems, Windows and Linux.

Bought two exos 18tb drives to replace a single, smaller parity drive. Planned to start the array and let it rebuild, then install the old parity drive as a data drive. However, the new disks do not show up as unassigned devices or with lsscsi Troubleshooting steps so far: Created a new config: Disks predictably lost their assignments, but new disks are not visible. Rebooted server: No change. Installed a drive that was previously part of the array to rule out sudden hardware failure on the sata port where one of the new drives will be installed: drive showed up as predicted. Disk swapped back to the new drive, new drive did not show up. Attached both drives to other computers to rule out double-DOA: Both disks show up on both windows and linux mint PCs. Diagnostics attached. serbur-diagnostics-20230723-1501.zip