Copying files USB to USB

garyn

Member
Joined
Jan 12, 2026
Messages
94
Reaction score
82
Credits
886
I'm having issues copying files (drag/drop in Nemo) from a SD USB to another SD USB memory card both in separate USB 3.0 ports (one on MoBo the other in a USB expansion adapter card's port).

Aside from being painfully SLOW (13 gigs in 5+ hours) I get, ERROR splicing file:Input/output error

While the popup is on screen if I drag the file from the source to the destination it WILL copy the file (in this case a video file) in its entirety and I verify that it is at the destination, then I select skip from the popup.

This is a recent (not the slow copy speed that's been a pain forever) issue.




linux copy error1.jpg
 
Last edited:


Be careful, any I/O error like that usually mean that reading or writing was not successful, and you can lose your data. Don't rely on a copy you just made, until you determine which device is at fault (or a USB ports etc).

please show last lines from
sudo dmesg
with the error you have described, paste relevant lines here.

Also, show
inxi --disk
result, with both devices still connected.
 
dmesg Many hundreds of these...

RGP=0
[90550.178802] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.53 LEN=70 TOS=0x00 PREC=0x00 TTL=64 ID=32443 DF PROTO=UDP SPT=42625 DPT=53 LEN=50
[90550.178824] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.53 LEN=70 TOS=0x00 PREC=0x00 TTL=64 ID=32443 DF PROTO=UDP SPT=42625 DPT=53 LEN=50
[90550.178890] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.53 LEN=70 TOS=0x00 PREC=0x00 TTL=64 ID=54911 DF PROTO=UDP SPT=45886 DPT=53 LEN=50
[90550.178901] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.53 LEN=70 TOS=0x00 PREC=0x00 TTL=64 ID=54911 DF PROTO=UDP SPT=45886 DPT=53 LEN=50
[90550.178947] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.53 LEN=70 TOS=0x00 PREC=0x00 TTL=64 ID=38263 DF PROTO=UDP SPT=37781 DPT=53 LEN=50
[90550.178957] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.53 LEN=70 TOS=0x00 PREC=0x00 TTL=64 ID=38263 DF PROTO=UDP SPT=37781 DPT=53 LEN=50
[90550.179070] [UFW AUDIT] IN= OUT=wlx9cefd5f76117 SRC=2607:fb91:0ca0:910b:f5bd:3908:e7ba:8c47 DST=2607:fb91:0ca0:910b:0000:0000:0000:003b LEN=90 TC=0 HOPLIMIT=64 FLOWLBL=55827 PROTO=UDP SPT=41583 DPT=53 LEN=50
[90550.179084] [UFW ALLOW] IN= OUT=wlx9cefd5f76117 SRC=2607:fb91:0ca0:910b:f5bd:3908:e7ba:8c47 DST=2607:fb91:0ca0:910b:0000:0000:0000:003b LEN=90 TC=0 HOPLIMIT=64 FLOWLBL=55827 PROTO=UDP SPT=41583 DPT=53 LEN=50
[90550.179224] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.53 DST=127.0.0.1 LEN=98 TOS=0x00 PREC=0x00 TTL=1 ID=17875 DF PROTO=UDP SPT=53 DPT=45886 LEN=78
[90550.179238] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.53 DST=127.0.0.1 LEN=98 TOS=0x00 PREC=0x00 TTL=1 ID=17875 DF PROTO=UDP SPT=53 DPT=45886 LEN=78
[90550.179344] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.53 DST=127.0.0.1 LEN=86 TOS=0x00 PREC=0x00 TTL=1 ID=17876 DF PROTO=UDP SPT=53 DPT=37781 LEN=66
[90550.179355] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.53 DST=127.0.0.1 LEN=86 TOS=0x00 PREC=0x00 TTL=1 ID=17876 DF PROTO=UDP SPT=53 DPT=37781 LEN=66
[90550.185435] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.53 LEN=67 TOS=0x00 PREC=0x00 TTL=64 ID=63733 DF PROTO=UDP SPT=54976 DPT=53 LEN=47
[90550.185451] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.53 LEN=67 TOS=0x00 PREC=0x00 TTL=64 ID=63733 DF PROTO=UDP SPT=54976 DPT=53 LEN=47
[90550.185494] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.53 LEN=67 TOS=0x00 PREC=0x00 TTL=64 ID=54749 DF PROTO=UDP SPT=53349 DPT=53 LEN=47
[90550.185502] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.53 LEN=67 TOS=0x00 PREC=0x00 TTL=64 ID=54749 DF PROTO=UDP SPT=53349 DPT=53 LEN=47
[90550.185533] [UFW AUDIT] IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.53 LEN=67 TOS=0x00 PREC=0x00 TTL=64 ID=28623 DF PROTO=UDP SPT=31077 DPT=53 LEN=47
[90550.185540] [UFW AUDIT] IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=127.0.0.1 DST=127.0.0.53 LEN=67 TOS=0x00 PREC=0x00 TTL=64 ID=28623 DF PROTO=UDP SPT=31077 DPT=53 LEN=47
[90550.185624] [UFW AUDIT] IN= OUT=wlx9cefd5f76117 SRC=2607:fb91:0ca0:910b:f5bd:3908:e7ba:8c47 DST=2607:fb91:0ca0:910b:0000:0000:0000:003b LEN=87 TC=0 HOPLIMIT=64 FLOWLBL=665002 PROTO=UDP SPT=37879 DPT=53 LEN=47
[90550.185634] [UFW ALLOW] IN= OUT=wlx9cefd5f76117 SRC=2607:fb91:0ca0:910b:f5bd:3908:e7ba:8c47 DST=2607:fb91:0ca0:910b:0000:0000:0000:003b LEN=87 TC=0 HOPLIMIT=64 FLOWLBL=665002 PROTO=UDP SPT=37879 DPT=53 LEN=47
[90550.185721] [UFW AUDIT] IN= OUT=wlx9cefd5f76117 SRC=2607:fb91:0ca0:910b:f5bd:3908:e7ba:8c47 DST=2607:fb91:0ca0:910b:0000:0000:0000:003b LEN=87 TC=0 HOPLIMIT=64 FLOWLBL=1014491 PROTO=UDP SPT=60816 DPT=53 LEN=47
[90550.185727] [UFW ALLOW] IN= OUT=wlx9cefd5f76117 SRC=2607:fb91:0ca0:910b:f5bd:3908:e7ba:8c47 DST=2607:fb91:0ca0:910b:0000:0000:0000:003b LEN=87 TC=0 HOPLIMIT=64 FLOWLBL=1014491 PROTO=UDP SPT=60816 DPT=53 LEN=47
[90550.185800] [UFW AUDIT] IN= OUT=wlx9cefd5f76117 SRC=2607:fb91:0ca0:910b:f5bd:3908:e7ba:8c47 DST=2607:fb91:0ca0:910b:0000:0000:0000:003b LEN=87 TC=0 HOPLIMIT=64 FLOWLBL=130377 PROTO=UDP SPT=35585 DPT=53 LEN=47
[90550.185805] [UFW ALLOW] IN= OUT=wlx9cefd5f76117 SRC=2607:fb91:0ca0:910b:f5bd:3908:e7ba:8c47 DST=2607:fb91:0ca0:910b:0000:0000:0000:003b LEN=87 TC=0 HOPLIMIT=64 FLOWLBL=130377 PROTO=UDP SPT=35585 DPT=53 LEN=47
[90550.206570] [UFW AUDIT] IN=wlx9cefd5f76117 OUT= MAC=9c:ef:d5:f7:61:17:5e:e1:a0:e5:4c:cb:86:dd SRC=2606:4700:0000:0000:0000:0000:6810:0351 DST=2607:fb91:0ca0:910b:f5bd:3908:e7ba:8c47 LEN=1248 TC=0 HOPLIMIT=53 FLOWLBL=396657 PROTO=UDP SPT=443 DPT=56383 LEN=1208
[90550.209199] [UFW AUDIT] IN=wlx9cefd5f76117 OUT= MAC=9c:ef:d5:f7:61:17:5e:e1:a0:e5:4c:cb:86:dd SRC=2606:4700:0000:0000:0000:0000:6810:0351 DST=2607:fb91:0ca0:910b:f5bd:3908:e7ba:8c47 LEN=1248 TC=0 HOPLIMIT=53 FLOWLBL=396657 PROTO=UDP SPT=443 DPT=56383 LEN=1208


gn@HP-Z2-SFF-G4:~$ inxi --disk
Drives:
Local Storage: total: 2.64 TiB used: 417.36 GiB (15.4%)
ID-1: /dev/sda vendor: Golden Memory model: 1TB size: 953.87 GiB
ID-2: /dev/sdb vendor: Western Digital model: WD5002ABYS-02B1B0
size: 465.76 GiB
ID-3: /dev/sdc vendor: Seagate model: Expansion+ size: 931.51 GiB
type: USB
ID-4: /dev/sde vendor: Generic model: SD MMC size: 233.2 GiB type: USB
ID-5: /dev/sdi vendor: Generic model: Mass-Storage size: 119.75 GiB
type: USB
 
PS there are no errors on either memory stick using check file system in "disks" application
 
Some SD cards have a micro switch on the side.

If switched to the locked position that will cause an error to save data onto it.

The micro switch has to be switched to the unlocked position.

Take a magnifying glass and check switch position.

1779634443350.png
 
To filter out firewall events, type:
Code:
sudo dmesg | grep -v UFW
See if you can spot any I/O errors, especially at the end of the log.

Code:
ID-4: /dev/sde vendor: Generic model: SD MMC size: 233.2 GiB type: USB
ID-5: /dev/sdi vendor: Generic model: Mass-Storage size: 119.75 GiB
type: USB
These two are your suspects, right? 233 GiB SD card, and 120 GiB USB device?
 
Not a lock issue, and if I drag the same file it failed on to the target drive it copies 100%.
 
Not a lock issue, and if I drag the same file it failed on to the target drive it copies 100%.
Don't know what that means, I am still waiting for dmesg results and for /dev/sd* letter confirmations.
 
ID-4: /dev/sde vendor: Generic model: SD MMC size: 233.2 GiB type: USB
ID-5: /dev/sdi vendor: Generic model: Mass-Storage size: 119.75 GiB
type: USB
I've run into some defective USB sticks, and I'm not the only one here. First thing I noticed was Generic. What brand are they?

Are the USB contacts gold-plated? If not, that's often a sign of a poor quality drive. I suggest you stay away from them.

We only use Sandisk, PNY, and other well-reviewed drives.
 
The lock issue was opined that the SD card was physically locked, I'm not using a card adapter. They're all new Sandisk and contacts are gold plated.

The 250Gb is /dev/sde1
The 129 is dev/sdi1
 
The lock issue was opined that the SD card was physically locked, I'm not using a card adapter. They're all new Sandisk and contacts are gold plated.

The 250Gb is /dev/sde1
The 129 is dev/sdi1
Is there anything in dmesg command I gave you? Especially I/O errors? After filtering out firewall messages?

If you want to know if both cards are 100% reliable, prepare them for full format, there's a linux tool which writes data to entire surface of the disk and then reads everything back and verifies if everything has been read correctly. You can do them in separate time, one by one. The test will also check USB adapter, and USB port, ability to work reliably from start to finish. Test will take several hours, as long as it takes to fully write entire card and then read back from it.
 
I've run into some defective USB sticks, and I'm not the only one here. First thing I noticed was Generic. What brand are they?

Are the USB contacts gold-plated? If not, that's often a sign of a poor quality drive. I suggest you stay away from them.

We only use Sandisk, PNY, and other well-reviewed drives.
To my understanding, he is using microSD to USB adapters, generic chinese ones is my guess (I use them too, but mine are USB 2.0 slow ones). They shouldn't fail that often due to their simple structure, but who knows.
 
what filesystem format are the drives? fat32 has a 4GB file size limit.
 
It's Fat32 but the file sizes are all small less than 200MB, most less than 75MB, ther's a long way to go before I get to the 2TB volume size limit.

I'm NOT using adapters and they're Sandisk
 
SD cards are very, very slow for writes. Writing 120GB to one will take a long time, because they can't write data as fast as a USB 2.0 port, however quickly the computer can deliver it. There is no way around that, the maximum write speed of the SD card is finite and fixed, other than switching to SSDs, which can write many gigabytes in seconds.

I'm not clear on exactly how you're trying to copy the files when they fail. You say if you drag and drop they copy fine. Are you using ctrl-c/ctrl-v, cp in a terminal, or what?
 
It's Fat32 but the file sizes are all small less than 200MB, most less than 75MB, ther's a long way to go before I get to the 2TB volume size limit.

I'm NOT using adapters and they're Sandisk

The volume size is one thing, the max file size is another. But if the largest is 200MB, you should be good.
:)
 
SD cards are very, very slow for writes. Writing 120GB to one will take a long time, because they can't write data as fast as a USB 2.0 port, however quickly the computer can deliver it. There is no way around that, the maximum write speed of the SD card is finite and fixed, other than switching to SSDs, which can write many gigabytes in seconds.

I'm not clear on exactly how you're trying to copy the files when they fail. You say if you drag and drop they copy fine. Are you using ctrl-c/ctrl-v, cp in a terminal, or what?
If I drag and drop a folder 1 out of 10 fails. If I grab the failed file and drop it in the same destination folder it overwrites the failed copy and copies the whole file fine.
 
Without evidence of I/O error ( no dmesg results), hard to tell what's going on. I asked and got no answer, won't be digging any further without it.

OP is saying he doesn't use any adapter yet his interface is USB, so I don't what he connected his SD cards to.
 
I responded in post 3 on the Dmesg request, did you need ALL of it? When I do I get an error that the message is too long.

I'm NOT using the little full sized adapter cards with the little switch (below) like was opined in post #5. I have several card readers that I'm using to read them.

1779712238093.png
 
I responded in post 3 on the Dmesg request, did you need ALL of it? When I do I get an error that the message is too long.

I'm NOT using the little full sized adapter cards with the little switch (below) like was opined in post #5. I have several card readers that I'm using to read them.

View attachment 32054
I told you in post #6 how to filter it.

So you are indeed using USB chinese adapters to translate from microSD to USB, I asumed this in post #12. They can introduce their own problems, too.
 


Follow Linux.org

Members online


Top