![]() To be clear, no other files I download via the browser or other mechanisms resulted in corrupted files. While using the terminal and the mv command, the files always copied 100% perfectly i.e. I discovered that using the Finder to copy files nearly always corrupted the files. The only things the files had in common with the problem was that they were downloaded using torrent and they were being moved to another drive after download. I tried different drives but they all had issues. ![]() I started observing this same issue with video files that were downloaded both with qBittorent and Transmission. Just sharing my experience for the record. ![]() I guess I could downgrade the qBittorrent to see if the problem fixes. I don't have another mac to try, so I can't tell. I was just stating that the problem wasn't resolved by upgrading to the newest macOS. If I proceed to copy the file instead to the SAME HDD, the size on the disk then matches up correctly to the byte sizes and then I can copy the files to an external HDD or a NAS without any issues and the file isn't corrupt and my md5 checksum is the same. If I copy that file to an external HDD or a NAS, the file becomes corrupt and the movie won't play correctly or be heavily pixelated. Sorry, your sentence sounds for me like "since the problem wasn't solved by macOS upgrade then it wasn't the problem with macOS".īyte sizes are correct yes but the total size on the disk is wrong initially. I concluded the sentence out by saying "and the problem is still there." Maybe I didn't notice something again, but both files are in the same folder, and the full file name is not visible.Īnd no it does NOT solve the problem at all. Also I can't see what kind of copying you're talking about. Before the copy shows 1.92 and after the copy shows 1.98.īut the sizes in bytes are the same.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |