[SuSE Linux] SCSI/IDE mixed system Questions.
Maybe I get a reply back before SuSE 5.3 gets here. Today or Monday I am expecting it. Situation: I am building a totaly new system, most of its built now. System basics: Intel P II 400 / Iwill BD100 Mhz-bus mainboard. Ram: 128Megs PC100 Sdram Video: Xpert@work AGP 8meg OEM / Quantum3D X24Meg (two voodoo2s) Monitor: 17in ViewSonic 17ps Network/Modem: NE2000 Ethernet Card, Hayes Acurra 56K flex external Sound Card: SoundBlaster 64Gold TV/Radio Tuner: Happauge v401 stereo Radio/TV tuner ..now for the catch.. Storage System Devices: IDE: CDROM 24X speed IDE: 6.4Gig Western Digital ..second catch.. SCSI #1 Adapter: FirePort 40-UW With: PlexWriter CDR 12X4 (Ultra scsi) (external) With: Syjet Syquest 1.5Gig removable (Ultra scsi) (external) With: Zip 100 (scsi II) (external) ..third catch.. SCSI #2 Adapter: Adaptec 2940-UW With: IBM 4.5Gig (Ultra Wide Scsi) (internal) ..wow I am done..all of this is in one box.. ..I know most of this set up works already.. The Asking Catch: I have had this system up with one SCSI Host Adapter before and it was with a different CPU and all HardDrives were IDE. Now this new system I am going for broke(boy am I ever) I have put in a UW SCSI HardDrive for use as my Linux Disk. And I have one IDE for winblows(winblows aint worth a scsi hd) Now, I just want to know if this should give me any problems that I should be prepared for. I like to use LILO, and LILO will be on the /mbr of the IDE drive pointing one boot to winblows on the same IDE drive and another to Linux on the SCSI drive.. Should I expect any problems with my plan? Reasons for putting the UW HD on a second SCSI host adapter, is because I have heard that having any other device that is not the same as your fastest device on the SCSI chain will slow it down to that speed. Like I might get rid of the zip on the #1 scsi host adapter, just cause of the CDR. Or put it on, only when needed. And UW is faster than just Ultra devices. I am assuming that this set up will slow Linux boot up/computer boot up, but thats just cause it has to initilize the cards and find whats on it at the given time. 1) LILO will boot from the IDE/mbr to a SCSI Linux native root / (problem?) a) this set up has two SCSI host adapters to figure out.. (problem at boot?) 2) any suggestions? -guess I will find out when 5.3 gets here (soon) ;)- Steve Udell hettar@teleport.com sudell@teleport.com - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Steven Udell wrote:
... cause it has to initilize the cards and find whats on it at the given time.
1) LILO will boot from the IDE/mbr to a SCSI Linux native root / (problem?) a) this set up has two SCSI host adapters to figure out.. (problem at boot?) 2) any suggestions?
-guess I will find out when 5.3 gets here (soon) ;)-
I had some problems with lilo in the mbr whilst trying to boot linux from the second scsi (sdb) drive. After reading the Support-DB, I found that the kernel should be on the same disk. didn't understand it realy, but moved the root partition to the sda drive. lost 60MB for Windooze. ;-)) Jürgen -- ========================================== __ _ Juergen Braukmann mail: brauki@cityweb.de| / / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu| / /__/ / _ \/ // /\ \/ / ========================================== /____/_/_//_/\_,_/ /_/\_\ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
...
prepared for. I like to use LILO, and LILO will be on the /mbr of the IDE drive pointing one boot to winblows on the same IDE drive and another to Linux on the SCSI drive.. Should I expect any problems with my plan?
nope - just the usual: things don't go as expected ;-) ...
1) LILO will boot from the IDE/mbr to a SCSI Linux native root / (problem?) a) this set up has two SCSI host adapters to figure out.. (problem at boot?) 2) any suggestions?
1.) when you run lilo, you'll need to have all devices with images (vlinuzes) on mounted and accessable - not a problem with your setup since you are going to have all the Linux stuff on the SCSI disk anyway. If you would have several linux partitions on the SCSI and wanted to boot into - let's say, a RH on partion 1, a Suse on partition 2, you will need to have both partions mounted in order for lilo to identify the sector addresses of the images to load. 2.) all the images to be booted will need to be accessable from BIOS without OS loaded. I don't think you have a problem there. You would have a problem when you would put a Win$ partition on your SCSI and then add another IDE visible for Win$. I had problems with that - the Win$ arbitrary assigned drive letters and put the new IDE in front of the SCSI, changing the drive letter for the SCSI partition which made all the program pathes wrong for stuff on the SCSI partition. Maybe there is a solution for Win$ to assign drive letters to partitions. I also had problems with new installations of Linuxes on that system. (Caldera, RedH I have tried). The installation setup programs did the installation but then I had to load kernel source and relink the kernal to include SCSI drivers - don't remember which one (RH, CAL). Samartha - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Samartha wrote:
...
prepared for. I like to use LILO, and LILO will be on the /mbr of the IDE drive pointing one boot to winblows on the same IDE drive and another to Linux on the SCSI drive.. Should I expect any problems with my plan?
nope - just the usual: things don't go as expected ;-)
hmmm, It's good to see that there are other folks mixing sczi and ide:-) When I installed Suse on my system (4 ide drives and 1 sczi drive), the only real problem that I had was that Lilo had to be installed on of the first two drives on the system otherwise it wouldn't read all the files associated with the kernel (the map and all of that). I use OS/2's Boot manager to select which os to run (OS/2, Dos, Linux). Lilo is installed on the first partition of the second ide drive. For some reason, if there is an ide drive on the system, that is also the first drive of the system. Although Linux can boot from any partition, the partition that you boot from must be on one of the first two drives of the system. It was that way when I was playing with RH and it also turned out to be that way with Suse 5.1, (something to do with the kernel?). -- cya l8r Leon McClatchey leonmcclatchey@homemail.com Linux User 78912 (Win95 Box) - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
At 07:47 AM 08/29/98 -0700, Steven Udell wrote:
1) LILO will boot from the IDE/mbr to a SCSI Linux native root / (problem?) a) this set up has two SCSI host adapters to figure out.. (problem at
boot?)
2) any suggestions?
#1 issue: does your MB have the capability to define which device to boot from? Some MBs do allow to boot from a SCSI device even when there is an IDE HD and there are some that will boot only from the first IDE HD when such a beast is present. You will have to find this yourself by reading the MB manual. #2 issue: you have two SCSI HBA both with SCSI bios. If you plan to boot from the IDE device then turn off the bios on both HBAs. The SCSI bios is there for boot purpose. Here I am assuming that your MB will insist on booting from the IDE HD. In case your MB does have the capability to boot 1st from a SCSI device then attach the SCSI HD you wish to make the boot device i.e. MBR to your favorite HBA and turn off the SCSI bios on the "other" SCSI HBA. One thing to keep in mind; given that you have a Windows on an IDE hard drive I suggest you keep the IDE HD as the boot device since Windows wants to be on the first primary partition of the first HD device. HTH. -- Arun Khan - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Arun K. Khan wrote:
At 07:47 AM 08/29/98 -0700, Steven Udell wrote: 1) LILO will boot from the IDE/mbr to a SCSI Linux native root / (problem?) a) this set up has two SCSI host adapters to figure out.. (problem at boot?) 2) any suggestions?
#1 issue: does your MB have the capability to define which device to boot from? Some MBs do allow to boot from a SCSI device even when there is an IDE HD and there are some that will boot only from the first IDE HD when such a beast is present. You will have to find this yourself by reading the MB manual.
Yes it does, saying it says I can do this configuration: SCSI,A,C or as such. Saying this, would I be correct to think that I should stick LILO on the root partition of the SCSI drive, have the Bios boot from the SCSI drive, then having LILO have 2 choices: continue loading Linux on the same drive. Or telling LILO that winXX is over there on the IDE /dev/hda1 drive and have it boot it. Thinking this over again, the LILO on the SCSI HD is now the boot HD, eh confusing. So this would say to me that the SCSI disk /dev/sda1 is now the Main First Drive. So my system would think that /dev/hda1.. would now be the secondary drive to the SCSI drive (am I confusing you, I am myself slighly) So in SuSE YAST at first set up..well I will have to check, but if the MB Bios is set to boot the SCSI drive and the SCSI host adapter's BIOS is set to use the SCSI HD as the boot master.. LILO could be installed to the /MBR of that drive. And after my POST/pnp/memory test/SCSI intilzing the first thing that would be read would be the SCSI HD. Which will have LILO on it as well as LINUX. And LILO will present me with some choices.. boot /dev/hda1 or /dev/sda1 ... Picking /dev/hda1 will not even look at the rest of the SCSI drive and then boot what ever OS is on my IDE /dev/hda1 and like Winblow is, it cant read my linux native/swap on the SCSI drive so it will basicly ignore it. **Like all in all the SCSI drive will act like a boot floppy <g> no? yes? **Untill I pick what I want LILO to do? Hope you can figure out what I am saying, I do not know it this plan will work.
#2 issue: you have two SCSI HBA both with SCSI bios. If you plan to boot from the IDE device then turn off the bios on both HBAs. The SCSI bios is there for boot purpose. Here I am assuming that your MB will insist on booting from the IDE HD. In case your MB does have the capability to boot 1st from a SCSI device then attach the SCSI HD you wish to make the boot device i.e. MBR to your favorite HBA and turn off the SCSI bios on the "other" SCSI HBA.
Right, ok, thanks. But I can set the MB bios to boot SCSI,A,C or SCSI,C,A. Does the plan above seem like I have your idea straight on (starting with) "In case your MB does have the capability...."
One thing to keep in mind; given that you have a Windows on an IDE hard drive I suggest you keep the IDE HD as the boot device since Windows wants to be on the first primary partition of the first HD device.
I know this, foul monster of a OS windows is. Steven Udell hettar@teleport.com sudell@teleport.com - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (5)
-
arunkhan＠xnet.com -
brauki＠cityweb.de -
hettar＠teleport.com -
leonmcclatchey＠homemail.com -
samarthal＠pobox.com