Is my microSD really bricked?

griimnak

griimnak

You're a slave to the money then you die
Jul 20, 2013
955
794
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:
  • Formatting on windows with built-in format
  • Formatting on windows with Raspberry PI recommended format tool
    You must be registered for see links
  • Formatting on windows with fat32.exe
  • Formatting on Linux (Arch) with fdisk, cfdisk, gparted, parted.
dmesg | tail
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

fsck /dev/mmcblk0
Bash: 
[root@revenge griimnak]# fsck /dev/mmcblk0
fsck from util-linux 2.32

// freezes

fdisk --list
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

cfdisk /dev/mmcblk0
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

Is there anything else i could do to completely reset and clean every superblock / partition on the microsd? Or is it really bricked
 
Sort by date Sort by votes
G

GarettM

Posting Freak
Aug 5, 2010
833
136
I would just clear it, then reformat it :p the sd card shouldn't be bricked
Code: 
sudo dd if=/dev/urandom of=/dev/mmcblk0p1 bs=8192
then reformat it with either diskpart or fdisk
 
Upvote 0 Downvote
griimnak

griimnak

You're a slave to the money then you die
Jul 20, 2013
955
794
Ecko said:
It's not bricked, you have broken superblocks. Give me output of:
Code: 
dumpe2fs /dev/mmcblk0p1 | grep -i backup
Click to expand...

Code: 
[griimnak@revenge ~]$ sudo dumpe2fs /dev/mmcblk0p1 | grep -i backup
[sudo] password for griimnak:
dumpe2fs 1.44.1 (24-Mar-2018)

// blank, cancelled after 10 minutes. how long should it take?

GarettM said:
I would just clear it, then reformat it :p the sd card shouldn't be bricked
Code: 
sudo dd if=/dev/urandom of=/dev/mmcblk0p1 bs=8192
then reformat it with either diskpart or fdisk
Click to expand...

Code: 
[griimnak@revenge ~]$ sudo dd if=/dev/urandom of=/dev/mmcblk0p1 bs=8192

// blank for 5 minutes, still running as i post this
 
Upvote 0 Downvote
G

GarettM

Posting Freak
Aug 5, 2010
833
136
griimnak said:
Code: 
[griimnak@revenge ~]$ sudo dumpe2fs /dev/mmcblk0p1 | grep -i backup
[sudo] password for griimnak:
dumpe2fs 1.44.1 (24-Mar-2018)

// blank, cancelled after 10 minutes. how long should it take?



Code: 
[griimnak@revenge ~]$ sudo dd if=/dev/urandom of=/dev/mmcblk0p1 bs=8192

// blank for 5 minutes, still running as i post this
Click to expand...
Don't cancel the dd command i should have stated if you do you can brick your sd card, it will take a few minutes as your writing 32GB of random data, this will clear the sdcard and should make it so you can reformat it
 
Upvote 0 Downvote
Ecko

Ecko

23:37 [autobots] -!- eckostylez [[email protected]]
Nov 25, 2012
1,396
960
GarettM said:
Don't cancel the dd command i should have stated if you do you can brick your sd card, it will take a few minutes as your writing 32GB of random data, this will clear the sdcard and should make it so you can reformat it
Click to expand...
If there are bad superblocks he's still going to have the same problem. Wiping it like this can make things worse.
 
Upvote 0 Downvote
griimnak

griimnak

You're a slave to the money then you die
Jul 20, 2013
955
794
Ecko said:
... why are you cancelling it. run it in screen, detach, then

Code: 
ps auwfx | grep dumpe2f | awk '{print $2}' | xargs strace -s 8192 -fvt -p
verify it's actually doing something before ctrl+c
Click to expand...
I cancelled the dd command, wasn't doing anything.
(fdisk still the same after cancel)

back to Eckos request,

Code: 
[griimnak@revenge ~]$ sudo dumpe2fs /dev/mmcblk0p1 | grep -i backup
[sudo] password for griimnak:
dumpe2fs 1.44.1 (24-Mar-2018)


ps auwfx | grep dumpe2f | awk '{print $2}' | xargs strace -s 8192 -fvt -p
Code: 
strace: Can't stat '1495' : No such file or directory
 
Upvote 0 Downvote
griimnak

griimnak

You're a slave to the money then you die
Jul 20, 2013
955
794
Ecko said:
Sorry, it's trying to strace your grep and code block messed it up:
Code: 
ps auwfx | grep dumpe2f[s] | awk '{print $2}' | xargs strace -s 8192 -fvt -p
ignore strike through
Click to expand...
Bash: 
[root@revenge griimnak]# ps auwfx | grep dumpe2fs
root      1320  0.0  0.0  21148  1152 pts/0    D+   16:44   0:00  |           \_ dumpe2fs /dev/mmcblk0p1
root      1514  0.0  0.0  10880  2252 pts/1    S+   16:51   0:00              \_ grep dumpe2fs
 
Upvote 0 Downvote
griimnak

griimnak

You're a slave to the money then you die
Jul 20, 2013
955
794
Code: 
[root@revenge griimnak]# strace -s 8192 -fvt -p 1320
strace: Process 1320 attached



// no additional output after 2 minutes
 
mZyzBvT.png
 
Upvote 0 Downvote
griimnak

griimnak

You're a slave to the money then you die
Jul 20, 2013
955
794
Ecko said:
Code: 
sudo mkfs.ext4 -S /dev/mmcblk0

good luck
Click to expand...
/salute

all in boys
 
Code: 
[root@revenge griimnak]# sudo mkfs.ext4 -S /dev/mmcblk0
mke2fs 1.44.1 (24-Mar-2018)

// ..

Code: 
[root@revenge griimnak]# ps | grep mke2fs
[root@revenge griimnak]# pstree | grep mke2fs
[root@revenge griimnak]# strace -p 1374
strace: Process 1374 attached
wait4(1375,
 
Upvote 0 Downvote
griimnak

griimnak

You're a slave to the money then you die
Jul 20, 2013
955
794
Code: 
[root@revenge griimnak]# ps auwfx | grep mkfs.ext4
root      2697  0.0  0.0  80084  5448 pts/0    S+   17:00   0:00  |           \_ sudo mkfs.ext4 -S /dev/mmcblk0
root      2698  0.0  0.0  21248  1148 pts/0    D+   17:00   0:00  |               \_ mkfs.ext4 -S /dev/mmcblk0
root      3110  0.0  0.0  10880  2268 pts/1    S+   17:20   0:00              \_ grep mkfs.ext4
[root@revenge griimnak]# strace -s 8192 -fvt -p 2697
strace: Process 2697 attached
17:21:10 restart_syscall(<... resuming interrupted poll ...>

) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:21:30 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:21:30 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:24 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:24 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:24 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:24 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:24 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:24 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:24 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:24 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:24 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:24 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:24 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:24 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:24 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:24 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:24 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:24 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:24 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:24 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:25 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:25 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:25 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:25 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:25 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:25 restart_syscall(<... resuming interrupted restart_syscall ...>) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
17:22:25 --- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
17:22:25 restart_syscall(<... resuming interrupted restart_syscall ...>
rip?
 
Upvote 0 Downvote
griimnak

griimnak

You're a slave to the money then you die
Jul 20, 2013
955
794
It finally finished but it said
Code: 
unable to mount root

yeah the PI definitely cooked this card lol, it still has root boot and media volumes but everything is screwed
 
Upvote 0 Downvote

Users who are viewing this thread

Total: 2 (members: 0, guests: 2)
☀️  Switch to Light Theme

Latest posts

Top