Jump to content

(already fixed) Possible corelation between Dust Detection and virtual loss of photos on data storage device?


Recommended Posts

Advertisement (gone after registration)

I was in the process of preparing the update to the newest firmware for an M10. I checked the menu on the camera if the battery was still full (enough) and noticed, that I had to save the photos from the card first because there were still around 8GB of photos on it. So, to proceed I plugged the card into the reader, as usual, and to my suprise I found absolutely zero photos on the card in the ordinary file explorer. Not wanting to believe that I just lost my photos, I quickly plugged the card into the camera again just to be greeted my a message saying "No media file to display".

The file explorer on the computer only displays the ususal DCIM/100LEICA without any photos in it. The system, however, says that roughly 8GB of space are used.

Filesystem       Size   Used  Avail Capacity iused      ifree %iused  Mounted on
/dev/disk4s1     59Gi  7.8Gi   51Gi    14%   63774     418290   13%   /Volumes/LEICA M

The last time I took a photo with it was just a few days ago (and I saw it in the playback!) and the last thing I did with the camera was the dust detection in the sensor cleaning menu.

Does anyone know something about a possible relation between the dust detection and the virtual "loss" of fiiles?
Does anyone have a hint on what to do next in order to recover the photos?

Thank you all.

Edited by feelssadman
Link to post
Share on other sites

Okay, got a quick update already. I found the photos.
They were in a hidden folder called .fseventsd in the root directory of the sd card.

If someone is experiencing the same problem after dust detection, point them to this thread. I know there is basically no evidence for such a corelation and I doubt that there is one but this is the only thing between seeing the photos on card, dust detection and not seeing them on the card or the computer. I'll try to reproduce the issue somehow but I doubt that I will be able to.

It is utterly unclear to me as to why and how this happened since there was no direct interaction with the data on my part.

Edited by feelssadman
  • Like 1
Link to post
Share on other sites

Sorry to bump my own thread again but I'll just leave this here since it might be related:

 

I assume its related to the filesystem (specifically to macOS and the file system events daemon) and has nothing to do with dust detection.

Edited by feelssadman
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...