I am in the process of upgrading my old 8.1 system to the latest version. I want to go through each version in order to minimize my chances of problems along the way (I have all of the boxed sets). So, I started with step 1 today -- upgrade 8.1 to 8.2. Well, that fouled up right off of the bat and completely hosed my system. I chose the installation option of doing a backup before proceding and it went off into never never land. Eventually, I powered down the machine and re-booting but it was pretty much trashed. I figured the effort to try to get that cleaned up would be more trouble than it was worth. So, I used a 3rd party system recovery tool to get my original 8.1 back and then made a second pass at the upgrade (and this time I skipped that backup step). Well, it worked, but only partially. I do have 8.2 up and running, but I was unable to complete the installation of all of the new software components, which I assume includes some new YaST components that I’ll need. I got through the first CD but that’s it. After that, you have to re-boot and finish the installation from your booted system using the remaining CDs (2-5). Unfortunately, for some reason I can no longer access my CD device once I reboot. The Installation CD system read CD1 just fine, but once I’m booted up in my new 8.2, it is inaccessible. So, I was unable to get any of the updates on cds 2-5. I tried going back and reinstalling to pick those up but the same thing keeps happening. It re-boots, asked for CD2, then says it can’t read it. I kept getting some error about unable to read the CD device. When I enter cdrecord –scanbus, here’s what it says – linux:~ # cdrecord -scanbus Cdrecord 1.11a28 (i686-suse-linux) Copyright (C) 1995-2002 Jörg Schilling cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. linux:~ # So, right now I cannot read a CD. The message above mentions SCSI, though I do not have a SCSI device. I have occasionally seen messages relating to SCSI in the past, but I just ignored them. I think I may have somehow initially picked that option when I first got SuSE (the 8.1 version I am coming from). Here’s my fstab. I have a Samsung CD RW DVD R device – # Updated by Storix System Installation /dev/hda2 / ext3 defaults 1 1 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/sda1 /media/sda1 auto noauto,user,exec 0 0 /dev/sda2 /media/sda5 ext2 noauto 0 0 proc /proc proc defaults 0 0 usbdevfs /proc/bus/usb usbdevfs noauto 0 0 /dev/hda1 swap swap pri=42 0 0\ The comment at the top was evidently placed in there when I used Storix to recover the system after that first failed installation attempt. I did go back through this entire process a second time -- recovering with Storix and re-installing 8.2 again. Same thing. One thing I noticed, though, is that after the Storix restore and before upgrading to 8.2, the cdrecord –scanbus seemed to show good output. 0,0,0 showed Samsung as the device. So it looks like the upgrade to 8.2 is where this is getting hosed. But it could also be that the Storix restore introduced some glitch that doesn’t show up until I do the upgrade. I can’t go back to the way it was before that Storix restore unless I do a YaST restore. That’s a very long, drawn out process and I’m hoping I can just somehow get this CD glitch fixed and move on without having to go through that. The rest of my system seems to be working just fine. Any help greatly appreciated. Yours truly, Greg Wallace