Arch Linux

n8jadams

Member

Registered: 2021-08-23

Posts: 49

[SOLVED] MicroSD becoming read only while I'm writing to it

I am having the damnest time copying about 40gb of files with cp to my 256gb microsd card. I have a PNY card reader. I don't think the problem is hardware related though.

What I have done is:

* Use KDE partition manager to partition the drive as FAT32 (or VFAT, doesn't really matter)
* Use KDE Dolphin UI to copy the files onto the drive. It seemingly completes, but at some point the files become corrupted. The first files (filenames a-s for example) are fine, and then the rest of them (t-z) are corrupted.
* Use cp -r. This would work for a while, and then all of a sudden it would spit out a bunch of 'Cannot copy files read file system only' or something to that extent. (I didn't grab the exact error message.) Again this resulted in not all of the files being copied.
* Early on I tried rsync and it would crap out too. Idk what's going on.

What can I do about this? Maybe something with my /etc/fstab to make sure that the write permission never "times out"?

Last edited by n8jadams (2022-03-30 15:53:14)

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: [SOLVED] MicroSD becoming read only while I'm writing to it

Have you ever managed to transfer >40GB of files to that particular card and verify them afterwards?
It sounds like the behaviour you'd get from a fake card...

It might be worth checking with something like...
https://aur.archlinux.org/packages/f3

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

n8jadams

Member

Registered: 2021-08-23

Posts: 49

Re: [SOLVED] MicroSD becoming read only while I'm writing to it

$ sudo f3probe --destructive --time-ops  /dev/sdd
F3 probe 8.0
Copyright (C) 2010 Digirati Internet LTDA.
This is free software; see the source for copying conditions.

WARNING: Probing normally takes from a few seconds to 15 minutes, but
         it can take longer. Please be patient.

Bad news: The device `/dev/sdd' is damaged

Device geometry:
                 *Usable* size: 0.00 Byte (0 blocks)
                Announced size: 250.00 GB (524290048 blocks)
                        Module: 256.00 GB (2^38 Bytes)
        Approximate cache size: 31.00 MB (63488 blocks), need-reset=no
           Physical block size: 512.00 Byte (2^9 Bytes)

Probe time: 3'25"
 Operation: total time / count = avg time
      Read: 12.80s / 131312 = 97us
     Write: 3'12" / 641201 = 300us
     Reset: 1us / 2 = 0us

I guess the card is damaged. That answers my question.

Last edited by n8jadams (2022-03-30 17:40:39)