my sd card is working fine in fat32 mode
but flashing dietpi seems a problem
after booting up i am getting read only error
but in fat32 everything seems fine both read n write
i wiped the card with zeros using aomei partitioner but nothing happened
To solve SD card issues with DietPi:
Check Card Integrity: Test the SD card on another device and run tools like
H2testworF3. Replace if damaged.
Backup Data: Useddto create a backup of the card.
Repair Filesystem: Runfsckon the SD card to fix corruption.
Reflash DietPi: Download the latest DietPi image, flash with Etcher, and verify the write.
Use Quality SD Cards: Opt for reliable brands like SanDisk or Samsung with A1/A2 ratings.
Looks you are running RPi4? Correct? If yes, did you try RPI OS for testing? Does it behave some with your SD card?
till now I just flashed the rasp os on sd card and everything went well
but if I flash dietpi using etcher, etcher shows the .img file is corrupt somehow, I downloaded two times and same error
I have just flashed yet, not run anything
can you flash the image using Rufus? And which image you use?
I used rufus
the flash went well
but on booting it first showed that partition has changed, then i unplugged the pi and plugged,
everything went well but it showed that error again of sd card read only
and i am using this image: DietPi_RPi-ARMv8-Bookworm.img
why did you unplug the device? This is not needed. Usually install process will continue automatically after file system has been altered
I just reflashed rasp os
and I will try it again after some time
I just flashed the image to SD card using Rufus + xz file (not extracted)
System was booting fine and completed first installation without issues.
at which stage of the install process? Can you check kernel error messages once hit by I/O error?
dmesg -l 0,1,2,3
Do you have a different SD card? Or a different PSU? You could try as well using a USB pen stick.
As said on my demo system, initial setup is working fine using SD card. Part with altering system tablet usually takes seconds and installation should continue afterwards automatically. I guess your card already breaks at this point. Therefore your install stuck.
Interesting that I left things there and now I see It has passed that stage and stuck at here
and this error keep coming again and again
and this is the output of dmesg
dmesg: error while loading shared libraries: dmesg: unsupported version 27 or Verneed record
can you check this one after hit by the error? You should be able to exit the install process at this stage
