Menu
Forums
All threads
Latest threads
New posts
Trending threads
New posts
Search forums
Trending
What's new
New posts
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Upgrades
Log in
Register
What's new
Search
Search
Search titles only
By:
All threads
Latest threads
New posts
Trending threads
New posts
Search forums
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Community
Technology
Technology Q&A
Is my microSD really bricked?
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="griimnak" data-source="post: 432320" data-attributes="member: 35695"><p>Alright so, I have a 32gb sandisk microSD that was formatted for use with the raspberry pi. </p><p>One night I did a sudo apt update && sudo apt upgrade, let it run and left on all night by accident. The next morning, the pi wouldn't boot and my windows pc would reject the card and freeze my explorer. I read online and have concluded that it is most likely bricked.</p><p></p><p>I have tried:</p><ul> <li data-xf-list-type="ul">Formatting on windows with built-in format </li> <li data-xf-list-type="ul">Formatting on windows with Raspberry PI recommended format tool <a href="https://www.sdcard.org/downloads/formatter_4/" target="_blank">https://www.sdcard.org/downloads/formatter_4/</a></li> <li data-xf-list-type="ul">Formatting on windows with fat32.exe</li> <li data-xf-list-type="ul">Formatting on Linux (Arch) with fdisk, cfdisk, gparted, parted.</li> </ul><p>dmesg | tail</p><p>[CODE=BASH]</p><p>[ 1739.001813] mmcblk0: error -110 transferring data, sector 3293460, nr 2, cmd response 0x900, card status 0xd00</p><p>[ 1744.616714] mmcblk0: error -110 transferring data, sector 3293460, nr 2, cmd response 0x900, card status 0xd00</p><p>[ 1744.616901] print_req_error: 89 callbacks suppressed</p><p>[ 1744.616905] print_req_error: I/O error, dev mmcblk0, sector 3293460</p><p>[ 1744.616914] buffer_io_error: 1008377 callbacks suppressed</p><p>[ 1744.616918] Buffer I/O error on dev mmcblk0p5, logical block 138, lost async page write</p><p>[ 1744.616985] JBD2: recovery failed</p><p>[ 1744.616996] EXT4-fs (mmcblk0p5): error loading journal</p><p>[ 1744.635081] FAT-fs (mmcblk0p6): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.</p><p>[ 1750.035760] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400e00</p><p>[/CODE]</p><p></p><p>fsck /dev/mmcblk0</p><p>[CODE=BASH]</p><p>[root@revenge griimnak]# fsck /dev/mmcblk0</p><p>fsck from util-linux 2.32</p><p></p><p>// freezes</p><p>[/CODE]</p><p></p><p>fdisk --list</p><p>[CODE=BASH]</p><p>Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors</p><p>Units: sectors of 1 * 512 = 512 bytes</p><p>Sector size (logical/physical): 512 bytes / 4096 bytes</p><p>I/O size (minimum/optimal): 4096 bytes / 4096 bytes</p><p>Disklabel type: dos</p><p>Disk identifier: 0x026e9e81</p><p></p><p>Device Boot Start End Sectors Size Id Type</p><p>/dev/sda1 * 2048 625141759 625139712 298.1G 83 Linux</p><p></p><p></p><p>Disk /dev/mmcblk0: 29.7 GiB, 31914983424 bytes, 62333952 sectors // micro sd</p><p>Units: sectors of 1 * 512 = 512 bytes</p><p>Sector size (logical/physical): 512 bytes / 512 bytes</p><p>I/O size (minimum/optimal): 512 bytes / 512 bytes</p><p>[/CODE]</p><p></p><p>cfdisk /dev/mmcblk0</p><p>[CODE=BASH]</p><p> Disk: /dev/mmcblk0</p><p> Size: 29.7 GiB, 31914983424 bytes, 62333952 sectors</p><p> Label: gpt, identifier: B77F93AC-A1B8-E84A-90AE-F0630F7EA707</p><p></p><p> Device Start End Sectors Size Type</p><p>>> /dev/mmcblk0p1 2048 62333918 62331871 29.7G Linux filesys</p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p></p><p> ┌──────────────────────────────────────────────────────────┐</p><p> │Partition UUID: CEA2437B-629C-F24F-A39A-3FDC20FD8BC5 │</p><p> │Partition type: Linux filesystem (0FC63DAF-8483-4772-8E79-│</p><p> └──────────────────────────────────────────────────────────┘</p><p></p><p></p><p> Type "yes" or "no", or press ESC to leave this dialog.</p><p></p><p>yes // freezes</p><p>[/CODE]</p><p></p><p>Is there anything else i could do to completely reset and clean every superblock / partition on the microsd? Or is it really bricked</p></blockquote><p></p>
[QUOTE="griimnak, post: 432320, member: 35695"] Alright so, I have a 32gb sandisk microSD that was formatted for use with the raspberry pi. One night I did a sudo apt update && sudo apt upgrade, let it run and left on all night by accident. The next morning, the pi wouldn't boot and my windows pc would reject the card and freeze my explorer. I read online and have concluded that it is most likely bricked. I have tried: [LIST] [*]Formatting on windows with built-in format [*]Formatting on windows with Raspberry PI recommended format tool [URL]https://www.sdcard.org/downloads/formatter_4/[/URL] [*]Formatting on windows with fat32.exe [*]Formatting on Linux (Arch) with fdisk, cfdisk, gparted, parted. [/LIST] dmesg | tail [CODE=BASH] [ 1739.001813] mmcblk0: error -110 transferring data, sector 3293460, nr 2, cmd response 0x900, card status 0xd00 [ 1744.616714] mmcblk0: error -110 transferring data, sector 3293460, nr 2, cmd response 0x900, card status 0xd00 [ 1744.616901] print_req_error: 89 callbacks suppressed [ 1744.616905] print_req_error: I/O error, dev mmcblk0, sector 3293460 [ 1744.616914] buffer_io_error: 1008377 callbacks suppressed [ 1744.616918] Buffer I/O error on dev mmcblk0p5, logical block 138, lost async page write [ 1744.616985] JBD2: recovery failed [ 1744.616996] EXT4-fs (mmcblk0p5): error loading journal [ 1744.635081] FAT-fs (mmcblk0p6): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 1750.035760] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400e00 [/CODE] fsck /dev/mmcblk0 [CODE=BASH] [root@revenge griimnak]# fsck /dev/mmcblk0 fsck from util-linux 2.32 // freezes [/CODE] fdisk --list [CODE=BASH] Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x026e9e81 Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 625141759 625139712 298.1G 83 Linux Disk /dev/mmcblk0: 29.7 GiB, 31914983424 bytes, 62333952 sectors // micro sd Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes [/CODE] cfdisk /dev/mmcblk0 [CODE=BASH] Disk: /dev/mmcblk0 Size: 29.7 GiB, 31914983424 bytes, 62333952 sectors Label: gpt, identifier: B77F93AC-A1B8-E84A-90AE-F0630F7EA707 Device Start End Sectors Size Type >> /dev/mmcblk0p1 2048 62333918 62331871 29.7G Linux filesys ┌──────────────────────────────────────────────────────────┐ │Partition UUID: CEA2437B-629C-F24F-A39A-3FDC20FD8BC5 │ │Partition type: Linux filesystem (0FC63DAF-8483-4772-8E79-│ └──────────────────────────────────────────────────────────┘ Type "yes" or "no", or press ESC to leave this dialog. yes // freezes [/CODE] Is there anything else i could do to completely reset and clean every superblock / partition on the microsd? Or is it really bricked [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Community
Technology
Technology Q&A
Is my microSD really bricked?
Top