I would have been posting more Raspberry Pi posts, but my latest Made-in-UK 512MB board seems to have a raft of problems. Left to its own devices, it will happily corrupt any SD card I put in it. This is some fairly typical dmesg output:<\/p>\n
I’m not alone in having this problem; it’s reported by other people at Raspberry Pi \u00e2\u20ac\u00a2 PI freezes<\/a> and Filesystem corruption on the SD card – Stack Exchange<\/a>. I don’t see any solutions or responses from the Foundation<\/a> yet.<\/p>\n Update<\/strong>: for no reason I can explain, setting\u00c2\u00a0 I would have been posting more Raspberry Pi posts, but my latest Made-in-UK 512MB board seems to have a raft of problems. Left to its own devices, it will happily corrupt any SD card I put in it. This is some fairly typical dmesg output: [36218.109865] mmc0: final write to SD card still running [36228.126345] […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[7],"tags":[2510,2577],"class_list":["post-7992","post","type-post","status-publish","format-standard","hentry","category-computers-suck","tag-raspberrypi","tag-sdcard"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pQNZZ-24U","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/posts\/7992","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/comments?post=7992"}],"version-history":[{"count":3,"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/posts\/7992\/revisions"}],"predecessor-version":[{"id":7994,"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/posts\/7992\/revisions\/7994"}],"wp:attachment":[{"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/media?parent=7992"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/categories?post=7992"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scruss.com\/blog\/wp-json\/wp\/v2\/tags?post=7992"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}[36218.109865] mmc0: final write to SD card still running
\n[36228.126345] mmc0: Timeout waiting for hardware interrupt - cmd12.
\n[36228.127534] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900
\n[36248.152121] mmc0: final write to SD card still running
\n[36258.163655] mmc0: Timeout waiting for hardware interrupt - cmd12.
\n[36258.164865] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900
\n[36269.084446] mmc0: final write to SD card still running
\n[36279.101766] mmc0: Timeout waiting for hardware interrupt - cmd12.
\n[36279.102953] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900
\n[36309.899006] mmc0: Timeout waiting for hardware interrupt - cmd25.
\n[36309.899047] mmc0: resetting ongoing cmd 25DMA before 4096\/4096 [84]\/[96] complete
\n[36309.902774] mmcblk0: error -110 transferring data, sector 1721928, nr 848, cmd response 0x900, card status 0xc00
\n[36309.902964] mmc0: DMA IRQ 6 ignored - results were reset
\n[36309.903200] end_request: I\/O error, dev mmcblk0, sector 1722649
\n[36309.903227] end_request: I\/O error, dev mmcblk0, sector 1722656
\n...
\n[36309.903462] end_request: I\/O error, dev mmcblk0, sector 1722768
\n[36309.903823] Aborting journal on device mmcblk0p2-8.
\n[36310.460263] journal commit I\/O error
\n[36310.653420] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:327: Detected aborted journal
\n[36310.667118] EXT4-fs (mmcblk0p2): Remounting filesystem read-only<\/code><\/p>\nover_voltage=2<\/code> in the \/boot\/config.txt<\/code> file seems to make this problem go away. For me, at least.<\/p>\n","protected":false},"excerpt":{"rendered":"