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 did a Google search on the phrase "buffer I/O error on device sr0" and the responses all seem to point to a problem with reading the CD/DVD. See, for example, this thread where x_terminat_or_3 says:
Originally Posted by x_terminat_or_3
It means that there is an area that is unreadable on your cd/dvd.
Try burning the image again to a brand new cd/dvd
I would also suggest (if possible) verifying the md5s (sha1, signature, or whatever is available) of your downloaded iso image as well as verifying the md5s of the files on the CD itself (after burning a new one). For the second, many CD will have a boot option for that (it may say something like "verify integrity" instead of mentioning MD5). As far as my fist suggestion, I don't know if an error in the iso image can cause this error, but (IMHO) vefifying the downloaded image is always a good idea.
I had that issue when I tried to boot from an ubuntu disk I'd burnt with Windows/Nero. I assumed a bad burn and tried to burn it a couple of times more to new blanks with the same result. Burning the exact same image file to disk with cdrecord on linux ( I didn't redownload) I didn't have a problem.
Interestingly, I've never had any issues burning slackware disks, or any others for that matter with nero before, it seemed to be something specific to that ubuntu image that it didn't like. I've no idea why.
On my el' cheapo Ebay USB-CDROM I get the same error-then I ran a CD Cleaner through it and everything was fine-I have to clean it often too.
That's probably not your problem-just my experience with that error.
Ok, I just tried a freshly downloaded Ubuntu ISO burned from my mac, and I still get these errors. Could this be the CD drive on the pc that is loading the CD? When I burned the ISO with Toast on my mac, and if I verify it, it will come out 100% ok! ?
Could this be the CD drive on the pc that is loading the CD?
It could be. That's the problem -- trying to isolate the fault. If mint provicdes a "verfication" option (at boot), try that. If you have some other running system on that computer, you might be able to use that other system to verify the md5 sums of the the indivual files (to check whether the CD drive is reading the files accurately).
====="Ok, did it again but this time with an Ubuntu CD, and I still get the same prob. Would the next step be to run the verification step, and if it passes then, what do I do then?"====
If you run verification step and it gives a "passing grade" to your media by all means proceed to install using the same media. If the same issue reappears then this time "we are certain that the issue is no longer caused by the dvd" right? At least you have isolated the problem from that possibility.
blackhole54 may be right that the problem arose from the hardware.
By the way, under what hardware environment did you install Mint? Please post it here so that we can give you specific suggestions.
Usually Mint installs a kernel with SMP support, which often needs some switching when installing over an aged hardware. But we could not say any further here since we do not know what hardware you were using.