LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Ubuntu (https://www.linuxquestions.org/questions/ubuntu-63/)
-   -   pdf Error splicing file: Input/output error (https://www.linuxquestions.org/questions/ubuntu-63/pdf-error-splicing-file-input-output-error-4175455720/)

PeterUK 03-26-2013 08:41 PM

pdf Error splicing file: Input/output error
 
Hi I am having problem copy a file across.

I have a pdf file which is 64.8MB which I can open and see but when I ma backing up to another driver it just would not copy it. giving the following error:

Error splicing file: Input/output error

I have tried to compress it in different formats which it does fine but when decompresser it just does not open.

I even try to copy it across in the same driver and it will not work.

How do I fix this? Thanks

PeterUK 03-26-2013 09:17 PM

Update:

I try to split the file with "split" and "cat" and it does not work. I should also add that I tried with another file so check how to use it and it works with another pdf file but not with the one that give error.

I also split and cat the file in the same drive and it does not work. I noticed too that the file is not decompress to the right size.

This is very strange as I can open and see the file, like its working.

jschiwal 03-26-2013 11:53 PM

Quote:

Originally Posted by PeterUK (Post 4919597)
Hi I am having problem copy a file across.

I have a pdf file which is 64.8MB which I can open and see but when I ma backing up to another driver it just would not copy it. giving the following error:

Error splicing file: Input/output error

I have tried to compress it in different formats which it does fine but when decompresser it just does not open.

I even try to copy it across in the same driver and it will not work.

How do I fix this? Thanks

I assume you meant drive instead of driver.

A read/write error indicates a problem with the storage media. Either a bad drive, or a filesystem problem. If the problem was in writing a slice, then the original pdf may be OK, but there is a problem with the destination.

One thing you could try is to cat the file to /dev/null. If this is successful, the pdf file is good, and you need to check the health of the destination. If you were using slice, with the destination on the same filesystem as the pdf, then you probably want to perform a backup before the drive goes belly up.

PeterUK 03-27-2013 11:04 AM

Quote:

Originally Posted by jschiwal (Post 4919661)
I assume you meant drive instead of driver.

A read/write error indicates a problem with the storage media. Either a bad drive, or a filesystem problem. If the problem was in writing a slice, then the original pdf may be OK, but there is a problem with the destination.

One thing you could try is to cat the file to /dev/null. If this is successful, the pdf file is good, and you need to check the health of the destination. If you were using slice, with the destination on the same filesystem as the pdf, then you probably want to perform a backup before the drive goes belly up.

Sorry yes I meant drive.

Could you please elaborate what to do? (check the heath and cat)? Thanks

jschiwal 03-28-2013 04:34 AM

"cat filename >/dev/null"

If there is a read error while the file is being read, the drive that the pdf is on may be bad.
If there isn't an error, you can copy the pdf to another drive.

I don't understand why you were splitting a 65 MB file to copy it. It isn't that large.

PeterUK 03-29-2013 02:37 PM

Quote:

Originally Posted by jschiwal (Post 4920392)
"cat filename >/dev/null"

If there is a read error while the file is being read, the drive that the pdf is on may be bad.
If there isn't an error, you can copy the pdf to another drive.

I don't understand why you were splitting a 65 MB file to copy it. It isn't that large.

I will try this as soon as I get the other drive back on.

I am trying to back up this pdf file from the main hard drive to the back up drive (USB) But I try to copy in different drive through USB and in the same drive (different partition) without any success, but I can still opened and browser like its fine.

PeterUK 04-02-2013 02:21 AM

Quote:

Originally Posted by jschiwal (Post 4920392)
"cat filename >/dev/null"

If there is a read error while the file is being read, the drive that the pdf is on may be bad.
If there isn't an error, you can copy the pdf to another drive.

I don't understand why you were splitting a 65 MB file to copy it. It isn't that large.

Hi Jschiwal!

I have tried "cat filename >/dev/null"

And I've got:
Code:

cat: filename: Input/output error
What to do next? Thanks

PeterUK 04-04-2013 01:47 AM

I have got tired of waiting so I tried new things I have used "ddrescue"

And did make a file I can copy across.

The log file said:

Code:

# Rescue Logfile. Created by GNU ddrescue version 1.11
# current_pos  current_status
0x035E4C00    +
#      pos        size  status
0x00000000  0x034BE000  +
0x034BE000  0x00002000  -
0x034C0000  0x00091000  +

And the terminal:

Code:

Initial status (read from logfile)
rescued:        0 B,  errsize:      0 B,  errors:      0
Current status
rescued:    67962 kB,  errsize:  20480 B,  current rate:        0 B/s
  ipos:    56511 kB,  errors:      3,    average rate:    98354 B/s
  opos:    56511 kB,    time from last successful read:    8.4 m

Now how could I know what has changed from the original file without going page by page of course. Thanks


All times are GMT -5. The time now is 06:55 AM.