Thank you for your reply.
I have a feeling this may just be something on your end, since I haven’t heard of any reports of issues like this.
Yes I’m not disagreeing with this, still trying to figure out.
Here’s my answer to your questions:
- I created the images about 10-7 weeks ago. Since then I didn’t touch them, nor checked on them, so last I saw them intact was 7 weeks ago. However, there were like 3 more images I created 5 weeks ago, and they weren’t affected.
Try checking the creation time and last modified time of those files - and see if they match up to any pattern as to when you saw them last intact.
- Too bad I deleted the corrupted files and replaced them with new ones, so there is no way to know now.
- The images were around 600-700KB.
- Too bad I didn’t notice the file size of the corrupted ones.
- My laptop uses both SSD and HDD, but the images were on the HDD. I’ll run the disk check up. Thanks for the tip.
- No I haven’t used any other program with this vault. This is specifically set aside for Obsidian.
There is a chance that this happened, but you just don’t know about it yet. I would suggest making backups of not just your vault, but also other important stuff on the same disk just in case it’s an early sign of disk failure.
I can assure you I thoroughly checked everything else on the disk, and even my whole computer. Nothing else was affected.
Don’t worry I already had backups for all the important stuff. I didn’t have backups for Obsidian because it was just some of my learning notes. Everything else is safe.
I just made backups for Obsidian after this on Google Drive. But I’m wondering if they go wrong again, will Google Drive upload the corrupted files instead of keeping the healthy ones.