EX4200 VC won't commit after a member core dump

I've got a 3 member virtual-chassis EX4200 that won't commit its config. This morning, member0 rebooted and dumped core immediately after a commit was performed. Console showed a lot of this, repeatedly:

I=16105
UNEXPECTED SOFT UPDATE INCONSISTENCY

CLEAR? yes

along with:

DIRECTORY CORRUPTED I=8205 OWNER=0 MODE=40755
SIZE=512 MTIME=Jun 14 02:58 2013 
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

SALVAGE? yes

There are also some errors having to do with FIPS failures before the boot finished. Now when I attempt to commit, I get:

# commit check 
fpc1: 
configuration check succeeds
fpc0: 
2020-10-22 11:57:46 EDT: Running FIPS Self-tests
veriexec: /boot/loader: No such file or directory/sbin/kats/file_integrity: cannot open /boot/loader: No such file or directoryFailed SHA1 checksum of /boot/loader@ 1603382266 [2020-10-22 11:57:46] fips-error[1690]: FIPS Error 1: File integrity test failedAbort trap (core dumped)
2020-10-22 11:57:47 EDT: FIPS Self-tests Failed
error: configuration check-out failed
fpc1: 
error: remote commit-configuration failed on fpc0
fpc2: 
configuration check succeeds
fpc1: 
error: configuration check-out failed

I also ran a disk check and I'm seeing 'bad read' errors:

% nand-mediack -C
Media check on da0 on ex platforms
Zone 06 Block 0186 Addr 18ba00 : Bad read
Zone 06 Block 0502 Addr 19f600 : Bad read
Zone 06 Block 0523 Addr 1a0b00 : Bad read
Zone 06 Block 0700 Addr 1abc00 : Bad read
Zone 06 Block 0807 Addr 1b2700 : Bad read

I am pretty sure I need to re-install Junos from USB and format the disk in the process, but is there any safe way to commit pending changes without doing this in the meantime?