CryoSPARC can't start after system crash

Welcome to the forum @AurelienGG and thanks for posting the resolution. Glad to learn that your database may have survived the storage depletion. Because storage depletion may lead to more severe damage to the database and recovery may be tedious, you may want to continuously monitor available capacity for the database volume/quota especially.

A caution for future visitors facing a similar situation: There are servers that run multiple CryoSPARC instances (subject to certain constraints). The ps command may therefore show processes belonging to different CryoSPARC instances. It is therefore important to ensure that one only terminates processes that belong to the specifically applicable CryoSPARC instance.