/dev/nvme0n1p5 79G ?
/dev/sdb2 (partition)
start: 1000001
end: 249737215
size: 248737215 (118.61 GiB) ?
size is not logical. must be an error somewhere
That’s ok, I think?
nvme0n1 is in my computer and I make p5 79G
ok 2 differents things sdb is your sdcard and nvme your pc.
what i understand is that you have deleted and recreated the same partition and after a third partition sdb3 with not enough space. just erase all and create a single partition 120 gib fat32
the same error
And due to manufacturer issue or so, the whole space is not int but 118.61GiB
dont understand your error, post the error message. good news your sdcard is not dead because :
Partition table: msdos
Partition Type Start End Flags Partition Name File System Label Mount Point
/dev/sdb1 Primary 62500 1000000 lba fat16 BOOT_MNJRO
/dev/sdb2 Primary 1000001 249737215 ext4 ROOT_MNJRO saisissez ou
the log (error)
last idea : fsck before with gparted
make on stage after one , first have a complet 119 gib unformatted space in gparted and a new table partition. Create partition fat 32 and not ext4 only after.
Create Primary Partition #1 (ext4)
use mkfs if gparted is not the solution.
I’ve had a similar error with an USB-stick stubbornly refusing to repartition and concluded it is broken in my case.
SD-Cards have a little tab to write-protect them, check you did not accidently push it.
Micro sd cards have no such tab, I think.
Also, it’s ok to modify the content of the old files, or create new file. The change can be saved. So the sdcard is not write-protected.
Very weird things. Just happened after I disconnected the power while upgrading.
I’m not very sure what you instructions mean. My English is bad.
Do you mean run fsck first, delete all partitions and create a new partition table with gparted then create one fat32 partition with all space with mkfs?
I did as what I said. Here’s the results.
➜ ~ sudo fsck /dev/sdb1
fsck from util-linux 2.38.1
fsck.fat 4.2 (2021-01-31)
Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
[12?q]? 1
*** Filesystem was changed ***
The changes have not yet been written, you can still choose to leave the
filesystem unmodified:
1) Write changes
2) Leave filesystem unchanged
[12?q]? 1
/dev/sdb1: 310 files, 7073/58557 clusters
➜ ~ sudo fsck /dev/sdb1
fsck from util-linux 2.38.1
fsck.fat 4.2 (2021-01-31)
Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
[12?q]? 1
*** Filesystem was changed ***
The changes have not yet been written, you can still choose to leave the
filesystem unmodified:
1) Write changes
2) Leave filesystem unchanged
[12?q]? 1
/dev/sdb1: 310 files, 7073/58557 clusters
➜ ~ sudo fsck /dev/sdb2
fsck from util-linux 2.38.1
e2fsck 1.46.5 (30-Dec-2021)
ROOT_MNJRO: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? yes
fsck.ext4: unable to set superblock flags on ROOT_MNJRO
ROOT_MNJRO: ********** WARNING: Filesystem still has errors **********
➜ ~ sudo fsck /dev/sdb2
fsck from util-linux 2.38.1
e2fsck 1.46.5 (30-Dec-2021)
ROOT_MNJRO: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? yes
fsck.ext4: unable to set superblock flags on ROOT_MNJRO
ROOT_MNJRO: ********** WARNING: Filesystem still has errors **********
➜ ~
nothing changes …
Then I use gparted for a new partition table, nothing changes and no error.
I don’t know which partition should I format so I try to format the ext4 to fat32. But as usual no error and nothing changes.
I have contacted SanDisk. They said it’s physical damage and will get a new one for me.
I did not expect a micro sd card to be so fragile.
I’ll backup the partition table and the data inside to my computer. And flash into the new one.
I’ll let you know if it goes well.
2 Likes
I copied the data to the new sd card.
Everything is fine now.
Thanks for your patience and help 
2 Likes