by Ken Task.
I see some things in course info worthy of note:
scorm (18): 18
SCORM installs usually had one upload a zip and unzip then link to the manifest.xml. Those SCORM's could have been uploaded to a file system repo and then from some reason, course creator, check the box for 'alias'. Have seen courses with SCORMs in courses that have a lot more files than the next bit of info.
Number of files: 1851
Total file size: 1252162926 - which indicates a backup would be around 1.2 Gig - probably higher. SCORM's with videos (mp4's) could be very large.
moosh wasn't gonna fix anything ... just tell us where we might need to look.
And it sure did tell us with the command to check files in the course ... there was an issue ... hmmmm, same one Error writing to the DB.
In the backup process, there are temp tables created which are erased when the session finishes ... sucessfully or in failure.
So when the command to list files error'd about how long in time did it take to error. Almost right away?
In moodledata/temp/backup/ there might be some clues in .log files that are larger then 0 bytes. If there are directories in there by a contenthash name, check them out also. A failed backup won't have a moodle_backup.xml file in there ... nor an .mbz file.
Do logs still say mysql has gone away? Might need to increase max packets even larger ... and look at increasing default value for number of open files.
And mysqltuner said? What recommendations did it make?
What if you made a backup but deselected a SCORM or two when backing up?
'spirit of sharing', Ken