Recent answers to Scrounger can not open any of my 20 possible session restore fileshttps://support.mozilla.org/mk/questions/13359302021-05-13T06:50:38-07:00I guess that's comforting for the future at least.
2021-05-13T06:50:38-07:00jscher2000https://support.mozilla.org/mk/questions/1335930#answer-1412632<p>I guess that's comforting for the future at least.
</p>Interesting, the C: drive seems to be in good health, 94% life left, no warnings in CrystalDiskInfo
2021-05-13T04:22:43-07:00yorick_123https://support.mozilla.org/mk/questions/1335930#answer-1412609<p>Interesting, the C: drive seems to be in good health, 94% life left, no warnings in CrystalDiskInfo
</p>Wow, I'm surprised that most of those files also are unusable. Perhaps part of your hard drive is go2021-05-13T01:34:12-07:00jscher2000https://support.mozilla.org/mk/questions/1335930#answer-1412570<p>Wow, I'm surprised that most of those files also are unusable. Perhaps part of your hard drive is going bad. You can use the "Unstructured URL List" button to extract readable links from the file as a reference, but it doesn't sound as though the file could be swapped in for the current file to restore that session.
</p>Thanks, with Shadow Explorer I found 9 more files, the first 3 url's were able to be extracted but a2021-05-13T00:44:33-07:00yorick_123https://support.mozilla.org/mk/questions/1335930#answer-1412565<p>Thanks, with Shadow Explorer I found 9 more files, the first 3 url's were able to be extracted but at line 56, i have a variety of symbols for a long time, but then they suddenly all turn to nul symbols until the end of the file. 99% of that line is a nul symbol on the previous.jsonlz4. One of the few that were able to open in the scrounger. On exporting from the scrounger I get this error message now: <em>Not saving due to failure parsing JSON: SyntaxError: JSON.parse: bad control character in string literal at line 1 column 23892 of the JSON data</em>
</p>Null symbols are a bad sign. Sometimes you get that when reconstructing deleted files using Recuva. 2021-05-12T09:07:50-07:00jscher2000https://support.mozilla.org/mk/questions/1335930#answer-1412475<p>Null symbols are a bad sign. Sometimes you get that when reconstructing deleted files using Recuva. I haven't heard of that in a normal crash scenario. Even if a crash wipes out recovery.jsonlz4, usually the other files are fine. Very strange.
</p><p>So depending on how long you had most of those tabs open, another option would be to mine your last Windows restore point for session history files. To avoid further data loss, don't use System Restore! You can use a utility program to look in your restore points and export possibly useful files to a convenient location (i.e., not directly back into the profile folder). See:
</p><p><a href="https://support.mozilla.org/questions/1332315" rel="nofollow">https://support.mozilla.org/questions/1332315</a>
</p>In Notepad++ it has an endless list of nul symbols. In Visual Studio Code it has an endless list of 2021-05-12T08:55:26-07:00yorick_123https://support.mozilla.org/mk/questions/1335930#answer-1412473<p>In Notepad++ it has an endless list of nul symbols. In Visual Studio Code it has an endless list of question marks in a diamond shape. In Notepad It does not show anything. It really starts to feel like it's all lost. I got some important pages back by scrolling through all history but missing about a hundred tabs now.
</p>If you make a copy of one of the smaller files and change its file extension to .txt and try viewing2021-05-12T06:37:40-07:00jscher2000https://support.mozilla.org/mk/questions/1335930#answer-1412430<p>If you make a copy of one of the smaller files and change its file extension to .txt and try viewing it in Notepad, what does the beginning of the file look like? This is what I would expect (I've redacted some of the data in the middle, as you can see). mozLz40 is critical to proper decoding, and you should be able to see a bit of the JSON data despite the compression. (The unprintable control characters are not shown by Notepad.)
</p><p><img src="https://user-media-prod-cdn.itsre-sumo.mozilla.net/uploads/images/2021-05-12-13-35-51-5e1e43.png">
</p>I don't think so
2021-05-12T06:26:57-07:00yorick_123https://support.mozilla.org/mk/questions/1335930#answer-1412425<p>I don't think so
</p>Hmm, that's shouldn't happen with intact files. I'm not sure why all of them have corrupted headers.2021-05-12T05:56:07-07:00jscher2000https://support.mozilla.org/mk/questions/1335930#answer-1412415<p>Hmm, that's shouldn't happen with intact files. I'm not sure why all of them have corrupted headers. Is it possible the files were modified by another program?
</p>Thank you for the quick reply. The console gave this error with all the files I could open:
Error: u2021-05-12T02:18:07-07:00yorick_123https://support.mozilla.org/mk/questions/1335930#answer-1412379<p>Thank you for the quick reply. The console gave this error with all the files I could open:
Error: uncaught exception: Invalid header (no magic number) - Data: I:\Firefox\1\recovery.jsonlz4
</p>Sorry to hear about that. The Scrounger should also work in Chrome and the new Edge, if you want to 2021-05-12T01:21:15-07:00jscher2000https://support.mozilla.org/mk/questions/1335930#answer-1412373<p>Sorry to hear about that. The Scrounger should also work in Chrome and the new Edge, if you want to try it there.
</p><p>If the Scrounger can't decompress the file and show you its raw JSON-format contents, you can do it manually through the Browser Console tool (Ctrl+Shift+J). The script and a necessary setting for that are here:
</p><p><a href="https://gist.github.com/jscher2000/4403507e33df0918289619edb83f8193" rel="nofollow">https://gist.github.com/jscher2000/4403507e33df0918289619edb83f8193</a>
</p>