Can not copy large iso files to flash drive

Serrg · 2020-09-09 19:50:18

I have faced a strange problem. I need to copy a large iso file on my new usb flash drive. I created ntfs partition here by the folowing command:

mkfs.ntfs path to my device

It was done without any errors.

But, when i try to copy file with size 5GB it copies it "too fast", my DE writes that copying is finished. I press to "unmount my drive", but flash indicator has been continue working. If i remove my flash drive i get this dmegs errors:

[2030.446176] blk_update_request: I/O error, dev sdc, sector 9915808 op 0x1:(WRITE) flags 0x4000 phys_seg 3 prio class 0
[ 2030.446201] blk_update_request: I/O error, dev sdc, sector 9916048 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0
[ 2030.446280] blk_update_request: I/O error, dev sdc, sector 9916288 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0
[ 2030.446296] blk_update_request: I/O error, dev sdc, sector 9916528 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0
[ 2030.446333] blk_update_request: I/O error, dev sdc, sector 9916768 op 0x1:(WRITE) flags 0x4000 phys_seg 3 prio class 0
[ 2030.446350] blk_update_request: I/O error, dev sdc, sector 9917008 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0
[ 2030.446372] blk_update_request: I/O error, dev sdc, sector 9917248 op 0x1:(WRITE) flags 0x4000 phys_seg 3 prio class 0
[ 2030.446380] blk_update_request: I/O error, dev sdc, sector 9917488 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0
[ 2030.446397] blk_update_request: I/O error, dev sdc, sector 9917728 op 0x1:(WRITE) flags 0x4000 phys_seg 3 prio class 0
[ 2030.446405] blk_update_request: I/O error, dev sdc, sector 9917968 op 0x1:(WRITE) flags 0x4000 phys_seg 3 prio class 0

also, partition after removing is corrupred. i need to recreate it again to get it work. I habve also tested with ext4 partition. But resulting file is corrupted (sha256 sum) and is differ from original file.

What can i do, to fix this problem?

[ 2034.702851] usb 1-6.2: new high-speed USB device number 16 using xhci_hcd
[ 2034.794355] usb 1-6.2: New USB device found, idVendor=0781, idProduct=5581, bcdDevice= 1.00
[ 2034.794360] usb 1-6.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2034.794364] usb 1-6.2: Product:  SanDisk 3.2Gen1
[ 2034.794367] usb 1-6.2: Manufacturer:  USB
[ 2034.794370] USB Mass Storage device detected
[ 2034.796094] scsi host6: usb-storage 1-6.2:1.0
[ 2035.800851] scsi 6:0:0:0: Direct-Access      USB      SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
[ 2035.801453] sd 6:0:0:0: Attached scsi generic sg3 type 0
[ 2035.801892] sd 6:0:0:0: [sdc] 60063744 512-byte logical blocks: (30.8 GB/28.6 GiB)
[ 2035.802766] sd 6:0:0:0: [sdc] Write Protect is off
[ 2035.802771] sd 6:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 2035.803286] sd 6:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 2035.847434]  sdc: sdc1
[ 2035.849635] sd 6:0:0:0: [sdc] Attached SCSI removable disk

Last edited by Serrg (2020-09-09 20:02:00)

WorMzy · 2020-09-09 19:59:57

You created an ntfs partition with mkfs.ext4?

Please try again. This time with the exact command you used to make the filesystem, a more specific description of how you "try to copy file", how you try to unmount it, and how you verify it's corrupted.

https://bbs.archlinux.org/viewtopic.php?id=57855

Serrg · 2020-09-09 20:01:41

WorMzy wrote:

You created an ntfs partition with mkfs.ext4?
Please try again. This time with the exact command you used to make the filesystem, a more specific description of how you "try to copy file", how you try to unmount it, and how you verify it's corrupted.
https://bbs.archlinux.org/viewtopic.php?id=57855

sorry, my error. i have create ntfs partition by "mkfs.ntfs", i have updated my post. To create a partition i used:

fdisk /dev/sdc

then i create a new partition.

to create ntfs-filesystem:

mkfs.ntfs /dev/sdc1

How i get this error: i copy iso-file in "caja" to my flash drive. After it finished, i unmount my usb-flash drive in file manager, than try to connect again. I get this message in caja: "Can not mount partition. It's corrupted"

Last edited by Serrg (2020-09-09 20:24:59)

Mortimer Houghton · 2020-09-09 20:15:51

Are you trying to create a bootable USB or just store the iso file?

Serrg · 2020-09-09 20:16:52

Mortimer Houghton wrote:

Are you trying to create a bootable USB or just store the iso file?

no, just store iso file.

loqs · 2020-09-09 20:37:06

After you have copied the file try executing `sync` before trying to unmount then mount the drive.

Serrg · 2020-09-09 21:47:36

loqs wrote:

After you have copied the file try executing `sync` before trying to unmount then mount the drive.

i have tried, no results!

i get this message "Error mounting /dev/sdc1. Unknown error when mounting /dev/sdc1. "

loqs · 2020-09-09 21:53:20

What if you perform the format , mount , copy, unmount , mount again all from the command line?

Last edited by loqs (2020-09-09 21:53:43)

Zod · 2020-09-09 21:54:37

If it were me, I would start over from scratch and do the whole operation from the command line.

Recreate the partition and put a file system on it then retry the copy using the command line.

See if it's the DE or something else.

Edit: RATS! Ninjad.

Last edited by Zod (2020-09-09 21:55:23)

Serrg · 2020-09-09 22:21:06

loqs, Zod

So, i have triied to copy iso-file from console. i used cp

path to iso file path to storage device

it was finished without any errors.

Then i try to unmount device.

umount /dev/sdc1

Hmm, something really wrong here. I have been waited for 5 minutes, but usb storage was succesfully unmounted. And now a don't get any errors, everything works well.

It's very intersting: why unmounting is so long? What causes this problem?

I also have tested copyng this file on my internal hdd with ntfs partition created on Arch. Unmounting from DE works well.

loqs · 2020-09-09 22:28:07

cp does not ensure the data is written to disk, the block and filesystem layers can delay actual data writing. The unmount command requires the outstanding data be written to disk hence the delay.

GaKu999 · 2020-09-09 22:36:00

My grain of salt.

If have an usb that is annoying and another that’s just broken.

The first one copies really fast, but that’s a fluke, the data just gets cached and it’s on the process of being written, usually after a while of finishing...
So I have to wait for it.

The second one is not fast, but after the same behavior it freezes in place, somehow kidnapping the respective process for the write, and nothing can be done except removing it from the computer.
Since it’s broken no amount of wait is enough, it just fails somewhere on the ~5GB rank.

You seem to have the first case, so patience is the solution.

Last edited by GaKu999 (2020-09-09 22:36:57)

Serrg · 2020-09-09 22:37:56

loqs wrote:

cp does not ensure the data is written to disk, the block and filesystem layers can delay actual data writing. The unmount command requires the outstanding data be written to disk hence the delay.

Thank you for help! I also want to know: does it mean that DE also uses cp during file copy?

GaKu999 · 2020-09-09 22:39:31

Serrg wrote:

loqs wrote:
cp does not ensure the data is written to disk, the block and filesystem layers can delay actual data writing. The unmount command requires the outstanding data be written to disk hence the delay.
Thank you for help! I also want to know: does it mean that DE also uses cp during file copy?

Writes are the same, maybe the DE uses a method to wait for the process.
An example of processes that wait is dd.

loqs · 2020-09-09 22:54:03

GaKu999 wrote:

An example of processes that wait is dd.

Not by default see the dd options fsync and fdatasync.
Edit:
I doubt the DE is using the copy command. The C write and fwrite functions can produce the same result.

Last edited by loqs (2020-09-09 23:03:04)

GaKu999 · 2020-09-09 23:07:09

loqs wrote:

GaKu999 wrote:
An example of processes that wait is dd.
Not by default see the dd options fsync and fdatasync.

It still freezes on me when it finishes, until there’s no more cached data, so it’s effectively waiting...
Idk if this is usb shenanigans, HDDs are so responsive compared to the IO locks the usbs cause...

Arch Linux

#1 2020-09-09 19:50:18

Can not copy large iso files to flash drive

#2 2020-09-09 19:59:57

Re: Can not copy large iso files to flash drive

#3 2020-09-09 20:01:41

Re: Can not copy large iso files to flash drive

#4 2020-09-09 20:15:51

Re: Can not copy large iso files to flash drive

#5 2020-09-09 20:16:52

Re: Can not copy large iso files to flash drive

#6 2020-09-09 20:37:06

Re: Can not copy large iso files to flash drive

#7 2020-09-09 21:47:36

Re: Can not copy large iso files to flash drive

#8 2020-09-09 21:53:20

Re: Can not copy large iso files to flash drive

#9 2020-09-09 21:54:37

Re: Can not copy large iso files to flash drive

#10 2020-09-09 22:21:06

Re: Can not copy large iso files to flash drive

#11 2020-09-09 22:28:07

Re: Can not copy large iso files to flash drive

#12 2020-09-09 22:36:00

Re: Can not copy large iso files to flash drive

#13 2020-09-09 22:37:56

Re: Can not copy large iso files to flash drive

#14 2020-09-09 22:39:31

Re: Can not copy large iso files to flash drive

#15 2020-09-09 22:54:03

Re: Can not copy large iso files to flash drive

#16 2020-09-09 23:07:09

Re: Can not copy large iso files to flash drive

Board footer