fatty-insecurity5877

I was able to find the device log but can't seem to locate it now... It was complaining about possible corruption and to run fsck. I took the drive out and tried doing a scan and repair on a Windows machine, but that failed. I have since replaced the drive with a smaller one (the one I was having issues was a brand new Samsung 128gb, now using 32GB Kingston) and as of now, no issues. There were a lot of what appeared to be junk files on the other drive with very odd timestamps and names. Not entirely sure how corruption would have occurred so soon, this build has only been running for 4 days.

I searched and have not found another instance of this, but when I include backing up the flash drive, it makes it read-only every time a backup is run. Is this normal/expected behavior. My understanding is this is calling the native flash backup function which does NOT have this behavior, so unclear on what is causing this behavior. Thank you Update: I just tried the built in flash backup utility again and it also makes the drive read only after a backup.