Is exactly the reason remote support/suggestions given based upon descriptions of issues with very little to go upon other than what is shared about logs/debug is difficult.
It's also the reason that those 'one click wonder' installs (clickandbuilds seen in paths) create problems if one happens to pick/read the wrong documentation for updating or upgrading a moodle.
So if your data directory was in the folder I suggested you erase, then sorry bout that. Site was already broken anyway and my suggestion put the final nail in the coffin. Usman did mention moodledata which you could have checked from your config.php file because that line requires full path to where that resides.
However, depending upon provider and services offered customers, there is one last hope. Many providers do backup customer spaces and can restore those backups for the customer. If those backups were a month or so ago you loose whatever has been done from the time of that backup up to time it crashed, but having something is better than nothing.
'SoS', Ken