Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have created a 'tar' backup on a CD-R using Lone-tar. However when I try to read the directory (tar tvf /dev/hda), it gets almost all the way through the volume but then displays the error:
tar: /dev/hda: Cannot read: Input/output error
This error is repeated many times.
The interesting thing is that if I take the CD-R to an old SCO 5.0.5 system it is able to read the entire volume (tar tvf /dev/cd0) with no errors. I was even able to extract the last file on the volume.
It is almost as if linux is reading past the end of the archive, getting an error, but not processing the last data found.
jschiwal - The CD-R is not mountable, it is being used as if it was a tape. Most of the CD is accessible and the whole CD is accessible under SCO Open Enterprise (5.0.5). It is just the end of the archive that causes the error.
jschiwal - I think it just does not know when to stop. Unfortunately, it ignores the last few files on the CD. I would not mind if it errored out after reading all the files on the CD.
I mentioned before that the CD is readable in SCO (all files and no errors). I am using the same physical drive to do the reading. SCO is running as a virtual machine under the Linux host OS. I have also taken the disk to another machine and read the CD using SCO. It seems to be the linux CD-ROM driver that is having the problem.
Was there more than 650MB of data on the disc? You might want to check the size of the image in your Solaris VM. I'm wondering if this image included an overburned part at the end and if the Linux driver doesn't handle this area. Check if there is kernel documentation for the Linux driver. Some cdrom drivers may have a .txt file in Documentation/cdrom of the kernel source. Also check the Lonetar settings if there is a mention of overburn and disable it if there is. This might prevent the problem in the future.
You might try a test to see if the backups produced are compatible with gnu's tar. Create a smaller backup using the same program but backup up to a file share. Then test the tar file in Linux using the tar command. Verify that the Lonetar program is compatible with gnu's tar program. If it is then I does look like a driver issue.
jschiwal - there was about 250mb of data in the image, so overburn is not an issue. When I added other files to the end of the backup, I was able to access all the needed files. It looks like I will just need to provide my own padding. It still errors out when tar (or lone-tar) reads to the end, but all the files are accessible. I believe that the problem is in reading the disk rather than writing, since I can read it using SCO Unix.
It would be nice if it were cleaner, but for now this will do.
I would not know where to look for the cdrom driver in linux.