Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Mainly Devuan with some Tiny Core, Fatdog, Haiku, & BSD thrown in.
Posts: 5,172
Rep:
You appear to have a compressed file of your backup, 2014-09-01.tar.bz2, so either uncompress it or use the same tool you built it with to extract the files you want. (See man bzip2)(bunzip2 --help at the command line for a quick reference.)
(bunzip2 -d 2014-09-01.tar.bz2 should uncompress your backup in the directory you are in.)
Edit: Then use tar to extract individual files, or all files, (tar -xfv 2014-09-01.tar). (See man tar)
You appear to have a compressed file of your backup, 2014-09-01.tar.bz2, so either uncompress it or use the same tool you built it with to extract the files you want.
I thought along the same line for a moment. But then I reconsidered it and couldn't explain why cp should bother about the type and contents of a file. Obviously, the file being copied is 2014-09-01.tar.bz2, and the first message line tells me that the file isn't readable. For me, that looks like a corrupt CD/DVD, which isn't all that unusual.
However, I'm a bit confused about the second message line failed to extend '/user/2014-09-01.tar.bz2', which suggests that cp tried to modify (extend) the file in some way - though it was only specified as the source!
I think what the error message means is that cp copied some data but can't copy/extend the rest.
If cdrom is bad if you have skill try cleaning the lens or ask for service.
You can clean the cd/dvd with a soft cloth made wet by distilled water in spiral fashion from inward to outward. After that let it dry so that moisture is not present.
Then see if it works.
I think what the error message means is that cp copied some data but can't copy/extend the rest.
yes, you're right, the second message is about the target file. I should've seen it - after all, I even quoted the message refering to the /user directory! ;-)
So the first message means the source file can't be read, and the second means the target file cannot be completed as a consequence.
Quote:
Originally Posted by veerain
If cdrom is bad if you have skill try cleaning the lens or ask for service.
I guess a bad media is more likely than a bad drive.
I'm trying to recover ~/.skype.
I agree that media is possibly the cause. *BUT* not 6 different dvds!
And since I have 100s of backup dvds that have .skye on them, I think that
6 is a fair sample.
There is something more profound involved.
Where in /var/log?
What I do (or rather what cron does) is - - -
1) copy /home to an external drive
2) tar the directory
3) bunzip2 the image
then I burn the image to dvd with k3b
At the moment I have 2 concerns
1) I can't recover .skype
2) all my back up dvds seem to be useless.
All of this was done using MEPIS (latest was wheezy derived)
now 2 years old.
usually in /var/log/messages, but can be configured.... But you can easily check if something was written at the time of i/o error
you can try another drive too.
Feb 26 13:12:40 palantir kernel: [93626.009070] attempt to access beyond end of device
Feb 26 13:12:40 palantir kernel: [93626.009071] sr0: rw=0, want=3516196, limit=2097151
Feb 26 13:15:21 palantir kernel: [93786.032112] attempt to access beyond end of device
Feb 26 13:15:21 palantir kernel: [93786.032115] sr0: rw=0, want=3516140, limit=2097151
root@palantir:/var/log# exit
exit
/var/log $ ulimit
unlimited
/var/log $
The Errno = 5. (and not errno.h)
I went back 4 years to find a dvd that worked - thats another 6 I've tried.
I have dvds of movies older than this which still play, so why is Debian 7.8
taking such an offence to my backup data. The ones I tried were .gz
tar files: the one I found to work was simply a tar image.
What I noticed was the drive was mounted, but appeared to be empty.
So I rebooted. Then found GRUB in a mess. So after I recovered
GRUB I found gparted showed the drive as unrecognisable. After
install gpart (what ran for some hours) it siad there were
file systems on the drive. Hence I reformatted it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.