f3 icon indicating copy to clipboard operation
f3 copied to clipboard

F3READ termination rendered the card in read-only file system

Open rdlf4 opened this issue 2 years ago • 3 comments

I purchased a microsd card on Aliexpress. The card concluded F3WRITE and then I proceeded to execute F3READ in order to know if it was what it claimed it is. However, shortly after the process started, it resulted in an error and after that I'm now unable to mount the card and it is read-only file system. So the question is, can I actually make this card work again?

Unfortunately, I couldn't get the output of F3READ. GParted outputs this error message after inserting the card: Unable to read the content of this file system!

Because of this some operations may be unavailable.

Also, I've tried ntfsfix, without success:

sudo ntfsfix /dev/mmcblk0p1
Mounting volume... Error opening '/dev/mmcblk0p1' read-write
NTFS signature is missing.
FAILED
Attempting to correct errors... Error opening '/dev/mmcblk0p1' read-write
NTFS signature is missing.
FAILED
Failed to startup volume: Invalid argument
Error opening '/dev/mmcblk0p1': Read-only file system
Volume is corrupt. You should run chkdsk.

Is there anything that I can do to fix this card or make it write-able again? As a side note, I do have the card adapter tab up, so it isn't because of that (card is not write-protected). Thanks for reading.

rdlf4 avatar May 14 '22 07:05 rdlf4

EDIT1: This is the output of dmesg for "MMC":

[28913.161305] mmc0: cannot verify signal voltage switch
[28913.477121] mmc0: error -110 whilst initialising SD card
[28914.290212] mmc0: cannot verify signal voltage switch
[28914.405112] mmc0: new ultra high speed SDR104 SDXC card at address 59b4
[28914.419635] mmcblk0: mmc0:59b4 LX512 464 GiB (ro)
[28914.422102]  mmcblk0: p1
[28915.347779] mmc0: cannot verify signal voltage switch

rdlf4 avatar May 14 '22 07:05 rdlf4

I think the card is broken. F3 read/write doesn't do anything out of the ordinary y. No storage medium should do what you're reporting after using it as intended.

unfa avatar May 14 '22 09:05 unfa

Try to write to the device itself using the dd tool and try zeroing the device itself(not its partitions), after that you might be able to write onto it, this will destroy everything that was on that device, so do so carefully.

So if my device is /dev/sdb I will run dd if=/dev/zero of=/dev/sdb status=progress

NOTE: /dev/zero just provides infinite zeroes to write to /dev/sdb, dd will write until there's no space left.

If none of that works, it could be a hardware issue, be it the adapter, the USB hub or port the adapter is connected into, or the card itself.

FreezeHeat avatar Jul 27 '22 15:07 FreezeHeat