SD Card Issues with M11/M11M Since Firmware 2.0.2

[LBJ2]

Advertisement (gone after registration)

18 minutes ago, Edax said:

I am also on MacOS Sonoma 14.3.1 on both my M1 MBP and M1 Mac Studio.

Getting corrupted .DNG's started within 5 minutes after installing FW 2.0.2; very easy to reproduce by cycling through "take pictures, card into computer, card back to camera, take pictures, card into computer....". With the fix, which is in the meantime automated by a utility called BlueHarvest, I simply cannot get corrupted .DNG's anymore. Not in IN=SD, not in DNG+JPG only on SD, ...

Let's see if it holds for a week or so, after that I will contact the mothership support.

 

Good to know it's easy for you to force the .fseventsd corruption on your system. That means Leica should be able to reproduce easily too. I'm in good shape with M11 v 2.0.2 without issue of using the SD card back and forth between the Mac Studio & MBP under normal usage. But I will not be pushing it with rapid "cycling through" as you describe. 

Thanks again for isolating this into some details others might benefit from and Leica tech can potentially use to fix. Looking forward to your findings a week from now. 

 

[Advertisement]

The Leica Q3 is available for pre-order at B&H Photo Video and Adorama

[ianforber]

5 hours ago, Edax said:

Today I made MAJOR progress in analysing and finding a fix for the corrupt .DNG on SD file issue that plagued me since installing FW2.0.2 on November 29th.

The fix that seems to work for me so far: “do not put an SD card in the M11(-P) that contains the hidden .fseventsd folder that is re-created by MacOS every time immediately after the card is inserted into the Mac SD reader”.

This can be done in multiple ways:

1. Get rid of your Macs and switch to Windows. No .fseventsd folder. No I am not going this route myself.
2. Always reformat a card before putting it into the M11 (Not what I want in my workflow).
3. Switch the write-protect tab to locked before putting the SD card into the Mac, and switch it to unlocked before putting the card back into the camera. Not exactly nice: easy to forget and these tabs will malfunction one day (as already happened to one of my Sandisk cards).
4. Directly after putting the file into the Mac, open the SD card with Finder, switch (if not already into that mode) to hidden files view mode (shift-command + “.”), and delete the .fseventsd directory. This is what I am going to do myself until Leica supplies us with .fseventsd - agnostic firmware.
5. Write a smart automation that deletes the directory on card insert and post it here.

 

Good spot. Out of interest, what action are you taking after initially connecting the SD card to the computer? I extract the SD card from a camera that’s been switched off and already have Capture One open. I click on the “import” tab, pick all files and import them. I then eject the SD card mounted on the desktop, insert it back into the camera, switch the camera on, wait a couple of seconds, navigate to the format card bit of the menu, format the card and then switch the camera off. I don’t think I’ve ever switched the camera back on again within 5 minutes or so. Definitely often longer than that (days or weeks) with the camera doing the usual few seconds checking before becoming fully ready  

No idea if this makes any difference to the contents of the .fseventsd directory and/or how the camera reacts to it but I’m one of the lucky ones who has never had a problem wit their M11

 

[Edax]

41 minutes ago, ianforber said:

Good spot. Out of interest, what action are you taking after initially connecting the SD card to the computer? I extract the SD card from a camera that’s been switched off and already have Capture One open. I click on the “import” tab, pick all files and import them. I then eject the SD card mounted on the desktop, insert it back into the camera, switch the camera on, wait a couple of seconds, navigate to the format card bit of the menu, format the card and then switch the camera off. I don’t think I’ve ever switched the camera back on again within 5 minutes or so. Definitely often longer than that (days or weeks) with the camera doing the usual few seconds checking before becoming fully ready  

No idea if this makes any difference to the contents of the .fseventsd directory and/or how the camera reacts to it but I’m one of the lucky ones who has never had a problem wit their M11

Using your workflow I also do not have any problems.

I also extract the card from the camera, and put the card into the computer slot. With LR Classic open or not. After ingesting the pictures with auto card eject, I put the card back into the camera and do NOT format it in camera; already ingested pictures remain on it. I only format the SD card after the backup of the computer's pictures disk is out of the house.

BTW I have an M11-P.

So far so good; with the "fix" no corrupted files yet...

[marchyman]

On 2/26/2024 at 6:32 AM, Edax said:

The fix that seems to work for me so far: “do not put an SD card in the M11(-P) that contains the hidden .fseventsd folder that is re-created by MacOS every time immediately after the card is inserted into the Mac SD reader”.

Minor nit... I don't think the files are created unless you open a Finder window for the card.  However, I'm not 100% sure of that.

I do not have those files on my card which has not been formatted since being purchased.  However, in my workflow I never open a Finder window to see the contents of the card.   I run a script from a terminal window command line.  The script copies image files from the card, compares the copies to make sure there were no errors, then removes the image files before ejecting the card.  Remove does NOT go through a trash folder which would otherwise be added to the card as a hidden folder named .Trashes/ that would need to be emptied.

I'm guessing my workflow happens to be another way to keep the card clean of junk files.

[Edax]

38 minutes ago, marchyman said:

Minor nit... I don't think the files are created unless you open a Finder window for the card.  However, I'm not 100% sure of that.

 

 

On my systems I get this HIDDEN .fseventsd folder on the SD cards without opening a Finder window.

Edited February 27, 2024 by Edax

[marchyman]

28 minutes ago, Edax said:

I get this HIDDEN .fseventsd folder on the SD cards without opening a Finder window.

Interesting.  And thanks for the correction.   I wonder what the difference in our setup is?  Some Finder option?

[hdmesa]

Advertisement (gone after registration)

36 minutes ago, Edax said:

On my systems I get this HIDDEN .fseventsd folder on the SD cards without opening a Finder window.

How would you know without opening a Finder window or using search, which also adds those files to the card?

[Edax]

10 minutes ago, hdmesa said:

How would you know without opening a Finder window or using search, which also adds those files to the card?

Eject the card, set it on write protect, and put it back in the Mac and inspect it.

Also, the utility BlueHarvest every time on insert sees the hidden folder and deletes it (with no Finder windows open).

[Edax]

24 minutes ago, marchyman said:

Interesting.  And thanks for the correction.   I wonder what the difference in our setup is?  Some Finder option?

Just to be sure, did you check for a HIDDEN .fseventsd folder on your card(s)?

[Stevejack]

Curious on this; I always format the card in-camera when I first insert it, I don't download images and put the card back in and keep shooting with it. Every session starts with a fresh format in the M11 and I still get the corrupt DNG issue.

 @Edax Is what you're saying that just having the .fseventsd folder on the card when it's first inserted into the camera will cause an issue, which will remain even after the card has been formatted in-camera? 

 

[erudolph]

FWIW, on a Mac you can, through Settings, tell Spotlight not to index the SD card.  However, mounting the card will create that invisible folder even if you’ve excluded the card from indexing.  What I’m unsure of is, whether if you don’t look at the contents of the card via Mac’s Finder, whether the file will be created.

[Edax]

6 hours ago, Stevejack said:

Curious on this; I always format the card in-camera when I first insert it, I don't download images and put the card back in and keep shooting with it. Every session starts with a fresh format in the M11 and I still get the corrupt DNG issue.

 @Edax Is what you're saying that just having the .fseventsd folder on the card when it's first inserted into the camera will cause an issue, which will remain even after the card has been formatted in-camera? 

 

No that is not what I say; I expect that the in-camera format prevents corrupted DNG's. There are of course other causes for corrupted DNG's, e.g. freezes that prevent finishing writing to the card. 

Some strange thing I noticed:

After formatting a card in the M11-P MacOS will create the hidden .fseventsd folder at card insert; but after formatting a card by SD Card Formatter on Mac MacOS will create the hidden .fseventsd AND .spotlight_v100 folders at card insert.

[Stevejack]

9 minutes ago, Edax said:

No that is not what I say; I expect that the in-camera format prevents corrupted DNG's. There are of course other causes for corrupted DNG's, e.g. freezes that prevent finishing writing to the card. 

 

Yeah, unfortunately I'm getting corrupt DNG consistently after always formatting in camera, and the corrupt DNG isn't related to any known freezing (i.e. the camera doesn't freeze on me during the session). 

[Edax]

4 minutes ago, Stevejack said:

Yeah, unfortunately I'm getting corrupt DNG consistently after always formatting in camera, and the corrupt DNG isn't related to any known freezing (i.e. the camera doesn't freeze on me during the session). 

Sorry to hear that. I ordered an OWC card reader with write lock switch, with switch enabled the Mac can never write to the card. Will work with that a few weeks. If corrupted DNG's appear again in that workflow, and no new problem solving firmware arrived in the meantime, I am afraid the M11-P has to go. I bought the thingy to make pictures, not to do forensics.

[Stevejack]

3 minutes ago, Edax said:

Sorry to hear that. I ordered an OWC card reader with write lock switch, with switch enabled the Mac can never write to the card. Will work with that a few weeks. If corrupted DNG's appear again in that workflow, and no new problem solving firmware arrived in the meantime, I am afraid the M11-P has to go. I bought the thingy to make pictures, not to do forensics.

Hope it works out for you - fingers crossed you've found a solution that works on your setup 👍

[RMF]

As per the 2.02 release notes; 

‘Important information regarding the import of DNG files.
In rare cases, the import of DNGs from the SD card to image processing programs like Adobe Photo-
shop and Adobe Photoshop Lightroom would result in damage to the data structure, rendering the
DNGs unreadable. This error will be remedied shortly.”

So they acknowledge the issue (that some are having) in the 2.02 Release notes…. just now waiting on when the “the error will be remedied shortly’ part. 
 

 

.

 

Edited February 28, 2024 by RMF

[Smogg]

15 minutes ago, RMF said:

As per the 2.02 release notes; 

‘Important information regarding the import of DNG files.
In rare cases, the import of DNGs from the SD card to image processing programs like Adobe Photo-
shop and Adobe Photoshop Lightroom would result in damage to the data structure, rendering the
DNGs unreadable. This error will be remedied shortly.”

So they acknowledge the issue (that some are having) in the 2.02 Release notes…. just now waiting on when the “the error will be remedied shortly’ part. 
 

 

.

 

Shortly?😂

[hjddd]

8 minutes ago, Smogg said:

不久？😂

it is purely insanity，  indeed we have been waiting for enough time for this bug 

[Advertisement]

Hallo,

Look here: Interesting Leica gear

[marchyman]

22 hours ago, Edax said:

Just to be sure, did you check for a HIDDEN .fseventsd folder on your card(s)?

Yes, I checked.  I'm an old computer guy.  Because of the "old" part I always have a terminal window (or two or three) open on my desktop.  It is my habit to use commands in a terminal window as often as opening  a finder window.  I used the command 'ls -la' to show all files, including those hidden.

But: I must have checked incorrectly.  <embarrassed face here>.  I just installed the card from my M11 into my mac and ran the command.  Oops... there is indeed a .fseventsd folder on the card.  Sorry for the mis-info above.

 

18 hours ago, erudolph said:

FWIW, on a Mac you can, through Settings, tell Spotlight not to index the SD card.  However, mounting the card will create that invisible folder even if you’ve excluded the card from indexing.  What I’m unsure of is, whether if you don’t look at the contents of the card via Mac’s Finder, whether the file will be created.

It looks like inserting the card is enough to create it.  I removed the folder.  Verified it was removed. Ejected the card.  Re inserted the card.  Checked again from the command line.   The file was there.

 

[bkphoto]

21 hours ago, RMF said:

As per the 2.02 release notes; 

‘Important information regarding the import of DNG files.
In rare cases, the import of DNGs from the SD card to image processing programs like Adobe Photo-
shop and Adobe Photoshop Lightroom would result in damage to the data structure, rendering the
DNGs unreadable. This error will be remedied shortly.”

So they acknowledge the issue (that some are having) in the 2.02 Release notes…. just now waiting on when the “the error will be remedied shortly’ part. 
 

 

.

 

Wow I should start reading the release notes before installing