Virtual Bad Blocks on OS VD

Some history, first: We had a Predictive Failure on Disk 1. We received a replacement drive from our support vendor; same manufacturer (Seagate Barracuda), size, speed, etc. They even brought a second disk in case of emergency. We took Disk 1 offline, replaced it with one of the replacement drives, and let it rebuild. All seemed well. We decided to be proactive and replace Disk 0, since we had the second spare.

Part of the reasoning for this is that I noticed that we had three different firmware versions on the disks: 3.AQM on the original Disk 1, which showed up in OMSA as not certified. Our original Disk 0 showed firmware 3.AEJ, certified. The two replacement disks showed firmware 3.BKE, which OMSA shows as certified. We thought it might make more sense to have disks with the same firmware, and we could keep the original disk (firmware 3.AEJ, certified) as a spare. (I have looked at Seagate for HDD firmware updates, but nothing seems available.)

Then we started getting the bad blocks error.

I've been to many various support pages (I'm pretty sure I have the "How to Handle Puncturing (Bad Blocks) on Virtual Disks for PowerEdge servers " page memorized!). At this point, I'm trying to figure out if (A) I need to go through the whole process of backing up, deleting and recreating the array, etc., or if there's something I can try before diving that deep.

(B) Is it possible to just go the "Clear bad blocks" route? This seems to be more of a second step, after deleting and recreating the array.

(C) Could I just run a file-level backup, and if that succeeds, then go and clear bad blocks?

(D) Or, perhaps just go back to the original Disk 0 (certified firmware 3.AEJ)? Take Disk 0 offline, pull it out, and insert the old one...

Many thanks in advance. Server room is a long walk away, so I may be running back and forth a lot.