res wrote:I saved the updates (waited till savings are finished) but unfortunately have not closed all documents ... I put my notebook in Standby status ... I just selected Standby and closed Laptop.
Today early morning I opened laptop (screen) but could not start the notebook. So I had to shut down and newly start.
Thank you for your detailed description.
I need to do some tests to try and replicate what you did but I think the problem arose at the "I could not start the laptop. So
I had to shut down and newly start." step, where I think shutting down caused it.
Saving the document was correct - it does not, or should not, matter that you left the document open because the
saved document is safely written to the disk. That being said, it is always best to shut things down properly and completely because you then know you will be OK.
You say "standby". There are two types:
With
Sleep, the CPU stops working but the memory stays powered and keeps all its contents. When you restart, the CPU starts again and, as the memory is identical to what it was when you put it to sleep, the PC begins immediately.
With
Hibernate, there is a delay while the PC writes the contents of the memory to disk. The CPU then stops and the laptop powers off completely. When you restart, the CPU starts and there is a delay while it copies the memory stored on disk back into the memory. When this has been done, the PC starts. This takes many seconds and is much slower than Sleep.
Which were you using? You can check by Control Panel > Power options.
Assume you were editing fred.odt which was 10kBytes, and then added some text to it. When you saved the added text it was saved into the original fred.odt, which is now 20 kBytes, and is safely stored on the disk. A new temporary file is created which is a copy of the 20 kBytes fred.odt. The temporary file is stored in the temporary folder as something like C:\Users\xxxxxx\AppData\Local\Temp\svct5ltr.tmp\svct7pik.tmp and is an exact copy of the 20 kBytes fred.odt.
As you can see, if you were using
Sleep, you would have lost the memory contents when you shutdown and restarted. However, even if you did this, I cannot see why the 20 kByte fred.odt seems to be broken - it should be perfect. Yet it seems to have been overwritten and corrupted. That has me very confused.
Did AOO offer to recover the file when it started? I am wondering if there a process where, when AOO starts, it somehow thinks it has to write the file to the disk, so it overwrite the good file already stored safely on the disk with rubbish?
A thought - are you using a traditional, rotating hard disk? Or a Solid State Disk (SSD)?
When a file is full of ###### there is no hope - it means the file is completely corrupted and full of NUL characters - there is no user data in it.