Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • How are you powering the Pi? How are you shutting down? Have you tried a second card? Commented Sep 21, 2016 at 20:26
  • Sudo shutdown. Wait a minute after the last led. Remove the power and the card. I use the oficial power supply 2.5A Commented Sep 21, 2016 at 20:27
  • O didn't try other sd but this sd only gived problems after updating the raspbian, never before or writing other things. Commented Sep 21, 2016 at 20:30
  • If you are consistently "seeing errors" using dd, that is not filesystem corruption, that is a physically damaged/defective/defunct card. Commented Sep 21, 2016 at 21:26
  • 2
    You might also want to make explicit exactly what you mean by "seeing errors" using dd. My last comment applies if you are literally getting I/O errors reported while running dd, because the nature of the data involved is completely meaningless to it. You can take a card filled with destroyed data and dd as much of it off as you want, and likewise take random junk and dd it to a card, and there should be no errors reported. If there are, it means somewhere along the line there are hardware problems (or possibly software bugs, but hardware failure is more likely in this case). Commented Sep 21, 2016 at 22:03