FS corrupted after burning image to SD card

[ChrisO]

Hi

I dd the Armbian_25.11.1_Rock-5c_trixie_current_6.12.58_minimal.img to a SD card (/dev/sdc) and then run a
fsck -f /dev/sdc1 and got errors:
sudo fsck -f /dev/sdc1
fsck from util-linux 2.39.3
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry '.' in ??? (1065) is duplicate '.' entry.
Fix<y>? 
....

Tried few SD cards, same result.
Tried those SD cards with other images, i.e. Armbian_24.8.4_Rock-5c_bookworm_vendor_6.1.75_minimal.img
no problems.
Could anybody verify this behavior?

Thanks
Chris

 

Armbian_25.11.1_Rock-5c_trixie_vendor_6.1.115_minimal.img image generates the same problem.

Edited 15 hours ago by ChrisO
typo, added a sentence

[laibsch]

Images shall only be written with imaging tools that validate burning results.  This saves you from corrupted SD card contents.

 

Approved Tools:

• USBImager a lightweight cross-platform imaging tool
• Balena Etcher an electron / node.js based cross-platform imaging tool (may contain spyware)

[Werner]

6 hours ago, laibsch said:

Balena Etcher

This is not recommended. https://docs.armbian.com/User-Guide_Getting-Started/#flash-to-sd-card

[ChrisO]

I do verify what is written to the SD card. It's a homegrown script I have used for at least ten years. It's not the cause of my problem.

And as for all those shiny clicky-clickity tools, no thanks! I prefer to know what is going on on my computer.

 

Any comments on my question, anyone? If anybody could write one of the images using his his preferred/recommended imaging tool and run fsck on the resulting partition it would help me much.

Thank you.

Edited 1 hour ago by ChrisO

[Werner]

May I ask why you do this fsck? Is there a problem with the image like not booting?