file lost after power failure
Hi,
I had a power failure today while working on a sheet in MuseScore. Luckily I saved the file shortly before the power failure happened, so I thought. When I started MuseScore again it offered to restore last session. I clicked yes, but nothing happened.
When I checked the file in the filesystem it was shown to be empty (0 bytes). The backup in ~/.local/share/data/MusE/MuseScore/ was also empty. The '.filename.mscz,' backup was there, but it's a very old version. I have saved many times after this version.
Please fix this software so this can never happen again.
MuseScore 1.2 running on Debian 7.0.
Regards,
Lennart
Comments
I'm confused. If you saved the file before it happened, that file should still be there, in the original folder, with the original filename - assuming the OS did its job. Do you perhaps have some sort of non-write-thru caching turned on for your disk?
I'm also confused - I thought the '.filename.mscz,' backup was supposed to refresh every time you saved?
Power failure is always difficult to cope with on computers which is why people invest in uninterruptable power supplies, and is impossible to fix at a programming level.
What has happened is that the power has failed whilst MuseScore was in the act of doing an autosave, and thus nerfed the file.
Maybe you should get onto your power company and try to get compensation out of them?
In reply to I'm also confused - I thought by ChurchOrganist
I think the backup file is only saved once per session, maybe even only once at all.
Bit there is also the autosaved file, the one muscore load after a crash
Thanks for your reponses.
Marc: I'm using Debians default ext4 filesystem on top of Luks encryption. No caching as far as I know.
ChurchOrganist: If I understand you correctly you suggest the file was incompletely autosaved to the musescore directory (the odds for this to happen seem very low to me), and when it offered to restore the session, it overwrote the real file. This is of course not what should happen, it should only load the autosaved version in its memory and let the user decide if he wants to save it to the real file. Especially if the autosaved file is not a valid musescore file. So is this really what happened?
I'm not looking for compensation from anyone.
Regards,
Lennart
In reply to Thanks for your by lennartack
"So is this really what happened?" Nope. Here is my take on it.
You mentioned you saved the score on your machine. That score file should still be, in the location where you stored it and it will not have been overwritten.
MuseScore has an session facility which auto saves your score to a place where a user normally isn't supposed to come. If a session has not been closed properly due to whatever failure, MuseScore will notice the next time it starts and ask you to restart your project based on the score file it has auto saved. This is not the file which you have manually saved yourself. In case MuseScore brings up an empty score, this means that the auto saved file has not saved properly and/or that the file is corrupted. There could be various reasons for this.
To go back to the start: you mentioned you saved your score on your machine. You should be able to find back that file.
In reply to What happened by Thomas
As I mentioned, that file is empty (0 bytes).
In reply to As I mentioned, that file is by lennartack
Ok, read to quickly over it. Sorry about that.
Anyways, we'll keep an eye if we receive similar problem reports, because we haven't received many of these issues before. If you can somehow reproduce it, please come back to us. Thanks!
To clarify: the real file to which I saved several times was not empty at the moment of the power failure. It was also certainly written to disk and not cached as I had rebooted before and the file was there after the reboot. Only after the power failure (and possibly only after MuseScore "restored" the open session) the file became empty.
In reply to To clarify: the real file to by lennartack
Still doesn't make sense. Unkess you hit the save button again, MuseScore would not have created replaced the score you saved with a zero length version. So unless someone can prove otherwise, think the lpmost logical assumption is that this is an OS / disk caching issue, as I suggested earlier. It's the only technical explanation cptht can possibly fit the facts as you've given them.
ignore me, but: are you sure that your score has not been given a different name / extension?
You have made an attempt with Testdisk or Foremost?
In reply to If you're good with pc by Shoichi
Yes, I have just recovered a recent autosaved file with Foremost!
In reply to Yes, I have just recovered a by lennartack
Glad you solved your problem! (Though I wasn't in the discussion. =P) You might want to let the Debian team know this.
In reply to Yes, I have just recovered a by lennartack
Hi, I had the same problem and I didn't know how to fix it. so please let me know how to restore the file. Thx
In reply to How to fix by mhktel
are you saying you read the original problem description and neither of the backup files specifically referred to are present?
In reply to are you saying you read the by Marc Sabatella
Yes the Backup file exist but I don't know how to use a recovery program to restore the file
In reply to Yes the Backup file exist but by mhktel
Rename it, remove the comma at the end.
See: http://musescore.org/en/node/20367
Attach your files, if you want.
In reply to If the file exists: by Shoichi
Thanks !!! the file is restored :D