Every time I try to copy an .mkv file to my USB drive, I get this error:
Error while copying “archive.mkv”. Error splicing file: Input/output error.
My USB drive is formatted as NTFS; I also tried exFAT, but I got the same error.
I tried using different ports on my PC, yet I still get the same error.
I also tried using the terminal to copy it, but I encountered the same error.
And I can’t use FAT32 because the files are movies larger than 4GB.
Welcome! 
“input/output error” during file transfers to/from a drive often means there’s a hardware issue.
To get more details, open a terminal window and issue the following command to monitor for new messages from the Linux kernel’s ring buffer:
sudo dmesg --ctime --follow-new
Then try to copy a file to your USB drive and share the results from the terminal window (please be sure to paste in a preformatted text block so it’s easy to read).
(post deleted by author)
Since you mentioned the volume on your USB drive being formatted as NTFS, I’m assuming the BTRFS volume listed in the screenshot is your computer’s internal drive (“/dev/nvme0n1p3” is a NVMe flash drive).
Those “csum failed” errors mean that the checksums Btrfs does on every block don’t match what was recorded in the metadata.
The next step is to do a quick check to see how bad the filesystem corruption is. In the terminal window, issue the following command to run a read-only check:
sudo btrfs check --progress --readonly --force /dev/nvme0n1p3
(Read-only mode is the default, so including the “–readonly” flag isn’t required, but it also doesn’t hurt to, and it’s a good habit just in case.)
That’s good, no basic filesystem corruption.
Now have Btrfs verify every block in the volume:
sudo btrfs scrub start /dev/nvme0n1p3
To check the status:
sudo btrfs scrub status /dev/nvme0n1p3
Sorry, I copied a line from my earlier post above and didn’t type over “filesystem” with “scrub”.
So in the first screenshot, there was a bad block for each of the MKV files you tried to copy, which means that both video files are damaged. Good news is that many media players can work around small errors, so it might not be a big deal.
The bad news is that Btrfs couldn’t repair the one bad block it found. Given that at least two bad checksums turned up in the dmesg log. I would run a media scan.
The following command does a read-only check for bad blocks:
sudo badblocks -v -s /dev/nvme0n1p3
(A read/write test is better, but only if you have a backup and also at the cost of extra wear-and-tear on the flash storage.)
Also have the NVMe run a self-test if it supports S.M.A.R.T.:
sudo smartctl -t long /dev/nvme0n1
(You’ll need to install the “smartmontools” package if the command above isn’t found.)
After the estimated time to complete the test has passed, check the status:
sudo smartctl -a /dev/nvme0n1
Depending on the results of the badblocks check and S.M.A.R.T test, you should at least reformat the volume so that the NVMe drive has a chance to remap any bad block(s) with spares if at all possible.
Hi @rf-jox , just a quick note: please copy/paste terminal output instead of using screenshots if/when possible.
Screenshots are not searchable for text, and they are also less accessible for visually impaired users who use screen readers and other such tools.
(Also, images are often used to sneak spam into posts, so posts with them will get flagged by the system’s spam detection—your last post was).
Thanks,
I agree, but it may not be obvious how to do that properly. Especially in rich text mode, the text may be modified when pasting, for example quotes are now curly quotes and double minus is turned into m-dash. And I can’t find any documentation about this either.
It looks like the nvme drive has a temperature issue, 81c is too much.
Could you start a new discussion in Site Help & Feedback and folks can look into it? I usually just use the three backticks method, and that seems to work—but that’s in markdown mode, of course.
Generally nvme drives can have problems with temperatures above 70C, so a temperature of 80C needs to be addressed.
re temperatures:
The drive is reporting a “SMART overall-health self-assessment test result: FAILED!” because of the temperature.
Self-test status: Extended self-test in progress (3% completed). Running an extended read/write self-test forces the SSD controller to work at 100% , which generates massive amounts of heat. I would stop the self-test and not re-run the self-test command because except for increased temperatures, the drive seems entirely healthy:Percentage Used: 2%
Available Spare: 100%
Media and Data Integrity Errors: 0
In your other screenshot, the drive reports 29°C, which is desirable.
You need to improve cooling/air flow in your case to cope with those temperatures above 70°C - or buy a heat sink and stick it onto the NVME. Ideally, the temperature should stay below 65°C, but definitely below 70°C or the drive will die fast.
It is much preferred that the text shown in the above 2 images be copied and pasted as preformatted text instead of being done as screenshots.
When text is posted it can be searched, quoted, and occupies less space for storage than the image.
Preformatted text is done by first pasting the text then highlight it and click the </> button on the toolbar of the text entry window.
OR
by placing a ``` on the line before the pasted text and again on the line following the pasted text.
Preformatted text allows us to see the content exactly as it was formatted on your screen.
Markdown mode is mentioned above which means the button on the left end of the toolbar for the text entry window should look like this.
Is that causing the main problem with my usb drive?
