[SLE] LILO difficulties
Hey GANG and Juergen, Trying to get LILO to work on a dual SCSI disk system. Done this successfully on two other, albeit different mobo's and SCSI HBA's, systems. I can get LILO to work if, and only if, the only SCSI disk active on the bus is the SuSE 6.4 disk. The SCSI HBA I have looks from SCSI ID 6 down to 0 for a bootable disk, which is opposite from the other Adaptec SCSI HBA's I've worked with in the past. The other Adaptec based cards search from ID 0 up to 6. Which means I would like to boot off of SCSI ID-2 (SuSE 6.4 /dev/sdb1), and see SCSI ID-1 (Windows 98 /dev/sda1) simultaneously. I have tried all different types of things, i.e. changing ID's of disks and modifying '/etc/fstab' and '/etc/lilo.conf' (and then re-executing lilo') so that the SuSE OS is at a lower SCSI ID than the Windows 98 OS. Re-compiling kernel, different boot managers (Partition Magic and Blue Sky Inovations Boot Manager) other than LILO to then point to which OS I wish to boot, but still use LILO on the SuSE disk. This system will end up being my packet filter (Firewall), and IP Masquerading host for our home network, so its kind of a relic. It is a 586 with 40 Mbytes of RAM. I am obviously overlooking something, can't see the forest for the trees, since this dual disk/dual boot has worked for me in the past on other systems. Help if you can. jpg Detailed basic rundown of events: ---------------------------------------------------------------------------- I got the plain vanilla SuSE 6.4 installed, with selected packages. However, at reboot I couldn't get LILO to load up the eide kernel. It would halt with: 'LI' Which, from the manual, indicates that something is in error with 'geometry mismatch' or moving '/boot/boot.b' without rerunning lilo. To verify/correct the 'boot.b' boot sector problem, even though I was sure I ran lilo, I booted off of floppy and selected 'Start installed system' on '/dev/sdb1'. No problem. I ran lilo, rebooted and attempted a boot off of the hard drive, same bad results with lilo. So now I thought it was the 'geometry mismatch' thing, I booted off of floppy again I then uncommented out the 'linear' option in lilo.conf, re-ran lilo again, and rebooted; same bad LILO results :( So after rebooting off of floppies, I re-commented the 'linear' option and re-ran lilo, to get back to where I started. I then unplugged the SCSI (windows 98) disk at ID-1, reset the '/etc/fstab' and '/etc/lilo.conf' accordingly to make the SuSE 6.4 disk '/dev/sda1'. This requires a couple of reboots and booting 'Rescue System' to successfully change these puppies, BTW. With just one disk, LILO works! But, although not a show-stopper, it would be nice to have the other SCSI disk available when up in Linux. I put LILO on the back burner, and recompiled my kernel to specifically match my old 586 machine hardwar and with firewalling and ip-masquerading. Installed my new kernel and saw that I now had a new boot sector '/boot/boot.b' file. What the heck, I thought I would see if this fixed the dual SCSI disk problem. So I plugged the windows 98 disk back in, reconfigured '/etc/fstab' and '/etc/lilo.conf' re-ran lilo (from rescue CD and booting from floppies again) and attempted a boot off of the SCSI hard drive partition at /dev/sdb1. Nope, same-old LILO problem, smiling at me. What the hey, I keep asking myself what am I missing? Below are printouts from pertinent files and kernel structures as to what I have currently on my system. And BTW, I still have to boot off of the floppy drive :( System specs: -------------- SCSI HBA = AHA-2920 BIOS v3.0 SCSI DISK ID2 = 2 Gbyte Seagate (SuSE 6.4) SCSI DISK ID1 = 2 Gbyte HP (Legacy Windows 98) $uname -a ------------------------------------------------------------- ------------------------------------------------------------- Linux gatekpr 2.2.14 #1 Fri Mar 17 11:58:46 GMT 2000 i486 unknown $cat /etc/lilo.conf ------------------------------------------------------------- ------------------------------------------------------------- # LILO Konfigurations-Datei # Start LILO global Section # If you want to prevent console users to boot with init=/bin/bash, # restrict usage of boot params by setting a passwd and using the option # restricted. #password=bootpwd #restricted initrd=/boot/initrd boot=/dev/sdb1 #compact # faster, but won't work on all systems. #linear # Generate linear sector addresses. vga = normal # force sane state read-only prompt timeout=100 # End LILO global Section # # SuSE 6.4 on SCSI disk at SCSI ID 2 image = /boot/vmlinuz root = /dev/sdb1 label = linux # # Windows 98 on SCSI disk at SCSI ID 1 #other = /dev/sda1 # label = winblows98 # table = /dev/sda # $cat /etc/fstab ------------------------------------------------------------- ------------------------------------------------------------- /dev/sdb1 / ext2 defaults 1 1 #/dev/sda1 /dos vfat defaults 0 0 /dev/hdd /cdrom auto ro,noauto,user,exec 0 0 /dev/fd0 /floppy auto noauto,user 0 0 none /proc proc defaults 0 0 # End of YaST-generated fstab lines $cat /proc/scsi/scsi ------------------------------------------------------------- ------------------------------------------------------------- Attached devices: Host: scsi1 Channel: 00 Id: 01 Lun: 00 Vendor: HP Model: C3325A Rev: 5172 Type: Direct-Access ANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 02 Lun: 00 Vendor: SEAGATE Model: ST52160N Rev: 0344 Type: Direct-Access ANSI SCSI revision: 02 $fdisk -l /dev/sdb;fdisk -l /dev/sda ------------------------------------------------------------- ------------------------------------------------------------- Disk /dev/sdb: 255 heads, 63 sectors, 263 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 249 2000061 83 Linux /dev/sdb2 250 263 112455 82 Linux swap Disk /dev/sda: 255 heads, 63 sectors, 263 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 263 2112516 b Win95 FAT32 $lsmod ------------------------------------------------------------- ------------------------------------------------------------- Module Size Used by serial 19636 0 (autoclean) memstat 1476 0 (unused) fdomain 12460 1 tulip 30176 1 8390 6052 0 nvram 3340 0 (unused) snippets from '/usr/src/linux/.config ------------------------------------------------------------- ------------------------------------------------------------- # # SCSI support # CONFIG_SCSI=y . . . # # SCSI low-level drivers # CONFIG_SCSI_FUTURE_DOMAIN=y -- 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/faq
On 3 Sep, John P. Griffin wrote:
I can get LILO to work if, and only if, the only SCSI disk active on the bus is the SuSE 6.4 disk.
----------> snip <---------------
Detailed basic rundown of events: ---------------------------------------------------------------------------- I got the plain vanilla SuSE 6.4 installed, with selected packages. However, at reboot I couldn't get LILO to load up the eide kernel. It would halt with:
'LI'
----------> snip <---------------
I then unplugged the SCSI (windows 98) disk at ID-1, reset the '/etc/fstab' and '/etc/lilo.conf' accordingly to make the SuSE 6.4 disk '/dev/sda1'. This requires a couple of reboots and booting 'Rescue System' to successfully change these puppies, BTW. With just one disk, LILO works! But, although not a show-stopper, it would be nice to have the other SCSI disk available when up in Linux.
----------> snip <---------------
What the hey, I keep asking myself what am I missing?
Ok, this is a long shot into the dark, but anyway. Have you tried booting the machine with just the Windrive connected? More specifically. Did you at any time used that disk with Linux/LILO? It might be that for some reason it is always finding that disk and try to start what ever it finds in its boot sector. I know, it shouldn't boot from it, but then again, I have worked to long with computers to ever say "never" again. It could be worth a try. Just to make certain. Good luck. TJo -- This Email is 100% Virus Free! How do I know? Because no Microsoft products were used to generate it! -- 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/faq
Ok, this is a long shot into the dark, but anyway. Have you tried booting the machine with just the Windrive connected? More specifically. Did you at any time used that disk with Linux/LILO? It might be that for some reason it is always finding that disk and try to start what ever it finds in its boot sector. I know, it shouldn't boot from it, but then again, I have worked to long with computers to ever say "never" again. It could be worth a try. Just to make certain.
Good luck.
TJo
Hey TJo, Yep, i did. As a matter of fact that is now how I boot between the two OS's, on the rare occasion I need windows 98. That is, I only plug in the disk for the OS I want to boot. Then I power up the computer, both disk OS's work great this way. As a matter of fact if I put the windows 98 disk first in boot sequence it boots fine with the SuSE 6.4 disk spinning. However cannot say the same for the SuSE OS disk :( Anyway thanks for the suggestion. 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/faq
participants (2)
-
jpg@cvuxgc.cvs.agilent.com
-
tjo@telia.com