[SLE] 6.2 CD unbootable in SCSI drive
I flubbed a lilo so now my SCSI HD won't boot my old 6.1 SuSE. I don't have my old 6.1 CDs anymore, but I do have a 6.2 set. Unfortunately the CD Won't boot in my SCSI CDROM drive attached to a Adaptec 2940U2W controller. Problem #1: How to get it to boot? According to the manual the Adaptec driver should be compiled into the kernel, so it should be bootable on this setup, right? The good news is that I was able to boot from the 6.2 floppy. The bad news is that Yast keeps failing to read the packages on the CD. The last few lines on console 3 are: [...] Mounting of inst-sys returns 0 Program aborted! Tue Feb 29 18:23:11 2000 ERROR: Unknown Error!, DETAIL: 0 FILE: PkgRetriever.cc LINE: 578 YaST return code is 256 (errno = 2) I happen to have a removable IDE HD that I've been using for backups. I put this into another system and copied the files off the first CD to it, thinking I could do a HD install. That fails with the same error. So, Problem #2: How do I get YaST to read the packages? -John -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
John Grant wrote:
I flubbed a lilo so now my SCSI HD won't boot my old 6.1 SuSE. I don't have my old 6.1 CDs anymore, but I do have a 6.2 set. Unfortunately the CD Won't boot in my SCSI CDROM drive attached to a Adaptec 2940U2W controller. Problem #1: How to get it to boot? According to the manual the Adaptec driver should be compiled into the kernel, so it should be bootable on this setup, right?
Have you ever booted a CD before? Being able to boot a CD is not necessarily a function of the kernel, but more about whether or not your CD drive and SCSI BIOS support bootability. Of course, if they both do, then to subsequently access the devices (after booting) the kernel will need the correct driver.
The good news is that I was able to boot from the 6.2 floppy. The bad news is that Yast keeps failing to read the packages on the CD. The last few lines on console 3 are:
[...] Mounting of inst-sys returns 0 Program aborted! Tue Feb 29 18:23:11 2000 ERROR: Unknown Error!, DETAIL: 0 FILE: PkgRetriever.cc LINE: 578 YaST return code is 256 (errno = 2)
I happen to have a removable IDE HD that I've been using for backups. I put this into another system and copied the files off the first CD to it, thinking I could do a HD install. That fails with the same error.
So, Problem #2: How do I get YaST to read the packages?
Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I flubbed a lilo so now my SCSI HD won't boot my old 6.1 SuSE. I don't have my old 6.1 CDs anymore, but I do have a 6.2 set. Unfortunately the CD Won't boot in my SCSI CDROM drive attached to a Adaptec 2940U2W controller. Problem #1: How to get it to boot? According to the manual the Adaptec driver should be compiled into the kernel, so it should be bootable on this setup, right?
Have you ever booted a CD before? Being able to boot a CD is not necessarily a function of the kernel, but more about whether or not your CD drive and SCSI BIOS support bootability. Of course, if they both do, then to subsequently access the devices (after booting) the kernel will need the correct driver.
You may have to go into the 2940 bios and turn on the cdrom boot option. I allways turn it off as it will boot from the cd before it boots from the harddrive. This gets annoying after doing an install becuse you forgot to take out the cd. it should prompt you to enter the bios. I think it is ctrl. c or a. *--------------------------------* | Chris Large clarge@macn.bc.ca | | http://gone for now | *--------------------------------* -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Chris Large said:
I flubbed a lilo so now my SCSI HD won't boot my old 6.1 SuSE. I don't have my old 6.1 CDs anymore, but I do have a 6.2 set. Unfortunately the CD Won't boot in my SCSI CDROM drive attached to a Adaptec 2940U2W controller. Problem #1: How to get it to boot? According to the manual the Adaptec driver should be compiled into the kernel, so it should be bootable on this setup, right?
Have you ever booted a CD before? Being able to boot a CD is not necessarily a function of the kernel, but more about whether or not your CD drive and SCSI BIOS support bootability. Of course, if they both do, then to subsequently access the devices (after booting) the kernel will need the correct driver.
You may have to go into the 2940 bios and turn on the cdrom boot option. I allways turn it off as it will boot from the cd before it boots from the harddrive. This gets annoying after doing an install becuse you forgot to take out the cd.
it should prompt you to enter the bios. I think it is ctrl. c or a.
Been there, done that. I have no problem getting to the BIOS(s), though getting them to do what I want is sometimes a bit vexing. I currently have the motherboard set up to boot from "SCSI,A,C", and booting from CD enabled. The SCSI BIOS set to boot from ID 0 (the CDROM). The SCSI BIOS shows that both the CD and the HD are visible on the SCSI chain. Everything seems set up correctly AFAICT. I've also tried various other boot options in the MB BIOS. It has options like "A,C,SCSI", "C only", "C,A,SCSI", "SCSI,A,C", "SCSI,C,A", and "CDROM,C,A". I've tried all these (and more) with no luck. It looks like perhaps the CD-ROM drive itself does not support booting off it. It's a fairly recent vintage (~1 year) Yamaha CRW6416S, anyone else have problems booting from this drive? -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Chris Reeves said:
John Grant wrote:
I flubbed a lilo so now my SCSI HD won't boot my old 6.1 SuSE. I don't have my old 6.1 CDs anymore, but I do have a 6.2 set. Unfortunately the CD Won't boot in my SCSI CDROM drive attached to a Adaptec 2940U2W controller. Problem #1: How to get it to boot? According to the manual the Adaptec driver should be compiled into the kernel, so it should be bootable on this setup, right?
Have you ever booted a CD before? Being able to boot a CD is not necessarily a function of the kernel, but more about whether or not your CD drive and SCSI BIOS support bootability. Of course, if they both do, then to subsequently access the devices (after booting) the kernel will need the correct driver.
No, I've never booted this system from CD. The system is put together from parts of other systems, and the current (well, former at this point) bootable HD was created on a system that had an IDE CD-ROM drive. The motherboard BIOS has options for booting from "CDROM", "SCSI", "A", "C", "D", and "LS/ZIP". "CDROM" I use on another system with the same BIOS to boot from the IDE CD. "SCSI" used to boot from the HD, but now just gives me the infamous "01 01 01 ..." error from lilo. "A" boots from floppy. "C", "D", etc. aren't applicable.. I don't have a LS or ZIP drive, or a bootable IDE drive in the system. However, I have tried booting from "C" and even with IDE completely disabled I get the LILO error, so your guess is as good as mine as to what the BIOS is _really_ doing. In this case I might expect the system to come back with a message about no bootable drives found, but it's obviously trying to boot from SCSI anyways. (Just once I would like someone to develop a BIOS that I didn't have to threaten and cajole to get it to do what I wanted. :) ) The SCSI BIOS can be told which SCSI id to boot from. I have the CD on ID 0 and the HD on ID 1, but no matter which one I put it on I get the "01 01 ...". FWIW, the BIOS versions are 2.01.0 for the SCSI BIOS and Award 4.51PG for the motherboard's. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Tue, 29 Feb 2000, John Grant wrote:
The motherboard BIOS has options for booting from "CDROM", "SCSI", "A", "C", "D", and "LS/ZIP". "CDROM" I use on another system with the same BIOS to boot from the IDE CD. "SCSI" used to boot from the HD, but now just gives me the infamous "01 01 01 ..." error from lilo. "A" boots from floppy. "C", "D", etc. aren't applicable.. I don't have a LS or ZIP drive, or a bootable IDE drive in the system.
The SCSI BIOS on many host adapters requires the boot order in the system BIOS to have "A" as the first boot device. The host adapter then will move the bootable CD to "A" and boot off of it if a bootable CD is detected in the drive. I had a bit of trouble getting my Toshiba 32x SCSI CD to boot with my Advansys host adapter till I changed the system boot order to "A" "C" "SCSI" and have not had a proble since
However, I have tried booting from "C" and even with IDE completely disabled I get the LILO error, so your guess is as good as mine as to what the BIOS is _really_ doing. In this case I might expect the system to come back with a message about no bootable drives found, but it's obviously trying to boot from SCSI anyways. (Just once I would like someone to develop a BIOS that I didn't have to threaten and cajole to get it to do what I wanted. :) ) The SCSI BIOS can be told which SCSI id to boot from. I have the CD on ID 0 and the HD on ID 1, but no matter which one I put it on I get the "01 01 ...". FWIW, the BIOS versions are 2.01.0 for the SCSI BIOS and Award 4.51PG for the motherboard's.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- Ray Schwamberger Linux Technician Atipa Linux Solutions -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Ray Schwamberger said:
On Tue, 29 Feb 2000, John Grant wrote:
The motherboard BIOS has options for booting from "CDROM", "SCSI", "A", "C", "D", and "LS/ZIP". "CDROM" I use on another system with the same BIOS to boot from the IDE CD. "SCSI" used to boot from the HD, but now just gives me the infamous "01 01 01 ..." error from lilo. "A" boots from floppy. "C", "D", etc. aren't applicable.. I don't have a LS or ZIP drive, or a bootable IDE drive in the system.
The SCSI BIOS on many host adapters requires the boot order in the system BIOS to have "A" as the first boot device. The host adapter then will move the bootable CD to "A" and boot off of it if a bootable CD is detected in the drive. I had a bit of trouble getting my Toshiba 32x SCSI CD to boot with my Advansys host adapter till I changed the system boot order to "A" "C" "SCSI" and have not had a proble since
I have another (older) system with an Advansys "ABP940U" controller as well so that was the first way I tried it on this system. The way I back up my systems is to copy them to a removable IDE drive, which messes up the BIOS's view of the drive order, which gives LILO indigestion. Usually I leave it at "SCSI,A,C", unless I need to boot off floppy or CD. That way I can do whatever I want with the IDE drive(s) and it doesn't seem to affect the BIOS's view of what the first drive is, so lilo remains happy. (At least that's what seems to be happening.. people say SCSI is voodoo, but from my point of view it doesn't even come close to dealing with the BIOS.) Since the removable IDE (hardware) module has it's own independant power switch so with IDE compiled as a module I can even add/remove the drive to/from a running system. As long as I'm careful to umount/rmmod before powering down the drive this seems to not cause any problems. So far anyways (knock, knock). If I have the luxury I prefer to shutdown though; it doesn't seem to be required, but it makes me feel better. :) -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (4)
-
chris.reeves＠iname.com -
clarge＠macn.bc.ca -
jmgrant＠primenet.com -
rschwamberger＠atipa.com