Re: [newbie] lilo questions
Anne Wilson wrote: On Saturday 10 January 2004 17:38, mike wrote: Anne Wilson wrote: On Saturday 10 January 2004 16:30, mike wrote: I don't know whether it will be able to set it up correctly with the boot partitions on separate drives, so you may well have to hand edit. Anne That was the problem lilo would not see the other /boot partitions, it only sees the /boot of the OS it was installed. I tried to find a way to get around it but, no luck. Had to mount my hdb drive in /mnt and add an entry in the /etc/fstab, and mount -a . Then edited my lilo.conf like below. image=/mnt/mdk9.1//boot/vmlinuz-2.4.21-0.27mdk label=9.1mdk2421-27 root=/dev/hdb1 read-only optional vga=791 append= devfs=mount hdc=ide-scsi acpi=ht splash=silent initrd=/mnt/mdk9.1//boot/initrd-2.4.21-0.27mdk.img Well all works now. I just won't make the mistake of running lilo on hdb again ;-) Mike Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[newbie] lilo questions
Hello, I kinda borked up my workstation when I did the kernel updates. I have 2 hard drives both on the master ide channel hda and hdb hda has dual boot windows and mdk9.2 and hdb has just mdk9.1 on it. Also hdb used to be hda when its install was done thus it believes it was hda. I added a new hard drive and installed windows and mdk9.2 edited the lilo.conf on mdk9.2 to mount hdb1 (mdk9.1) on /dev/hdb1 in a /mnt/tmp directory like so. image=/mnt/tmp/boot/vmlinuz label=9.1_linux root=/dev/hdb1 initrd=/mnt/tmp/boot/initrd.img append=devfs=mount hdc=ide-scsi acpi=ht vga=791 read-only So anyways cruiseing along at very careless warp speed updated both kernels and over wrote hda's lilo.conf with hdb's lilo.conf so was wondering can I just rewrite my lilo.conf with all the entries from both hda and hdb and run lilo and put and identical copy on both hda and hdb so I can boot hda again and not confuse the issue again? Or do I need to remove lilo from hdb? Mike Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] lilo questions
On Saturday 10 January 2004 16:30, mike wrote: Hello, I kinda borked up my workstation when I did the kernel updates. I have 2 hard drives both on the master ide channel hda and hdb hda has dual boot windows and mdk9.2 and hdb has just mdk9.1 on it. Also hdb used to be hda when its install was done thus it believes it was hda. I added a new hard drive and installed windows and mdk9.2 edited the lilo.conf on mdk9.2 to mount hdb1 (mdk9.1) on /dev/hdb1 in a /mnt/tmp directory like so. image=/mnt/tmp/boot/vmlinuz label=9.1_linux root=/dev/hdb1 initrd=/mnt/tmp/boot/initrd.img append=devfs=mount hdc=ide-scsi acpi=ht vga=791 read-only So anyways cruiseing along at very careless warp speed updated both kernels and over wrote hda's lilo.conf with hdb's lilo.conf so was wondering can I just rewrite my lilo.conf with all the entries from both hda and hdb and run lilo and put and identical copy on both hda and hdb so I can boot hda again and not confuse the issue again? Or do I need to remove lilo from hdb? Mike Mike, early in your lilo.conf there will be a line something like boot=/dev/hde That is usually the hddrive on which you have your windows install, just because windows usually needs to be on the first hdd. Anyway, the drive mentioned in that line is where it's looking to start up. If you have done a default install of 9.1 and 9.2 you will have separate /boot partitions. It can only read one, and you need to know which one it is reading, or to prepare both for reading. The way you do that is to rename config, initrd, kernel and vmlinuz with the kernel version e.g. config would become config-2.4.21-0.13mdk (I think that's the stock 9.1 kernel). Then make sure that both /boot partitions contain copies of each. At present you are telling it to load vmlinuz, for 9.1. The trouble is that vmlinuz may well be pointing to the 9.2 version. Once you have copies of each in your /boot you can change these entries to version specific ones, and all should be well. If I were you I would try booting from CD1, hitting F1 where you get a chance to restore your lilo - you don't need one on each drive. That should at least get you in again, then you can look at what changes if any need making to make both versions available. I don't know whether it will be able to set it up correctly with the boot partitions on separate drives, so you may well have to hand edit. Anne -- Registered Linux User No.293302 Have you visited http://twiki.mdklinuxfaq.org yet? Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] lilo questions
Anne Wilson wrote: On Saturday 10 January 2004 16:30, mike wrote: Hello, I kinda borked up my workstation when I did the kernel updates. I have 2 hard drives both on the master ide channel hda and hdb hda has dual boot windows and mdk9.2 and hdb has just mdk9.1 on it. Also hdb used to be hda when its install was done thus it believes it was hda. I added a new hard drive and installed windows and mdk9.2 edited the lilo.conf on mdk9.2 to mount hdb1 (mdk9.1) on /dev/hdb1 in a /mnt/tmp directory like so. image=/mnt/tmp/boot/vmlinuz label=9.1_linux root=/dev/hdb1 initrd=/mnt/tmp/boot/initrd.img append=devfs=mount hdc=ide-scsi acpi=ht vga=791 read-only So anyways cruiseing along at very careless warp speed updated both kernels and over wrote hda's lilo.conf with hdb's lilo.conf so was wondering can I just rewrite my lilo.conf with all the entries from both hda and hdb and run lilo and put and identical copy on both hda and hdb so I can boot hda again and not confuse the issue again? Or do I need to remove lilo from hdb? Mike Mike, early in your lilo.conf there will be a line something like boot=/dev/hde That is usually the hddrive on which you have your windows install, just because windows usually needs to be on the first hdd. Anyway, the drive mentioned in that line is where it's looking to start up. If you have done a default install of 9.1 and 9.2 you will have separate /boot partitions. It can only read one, and you need to know which one it is reading, or to prepare both for reading. The way you do that is to rename config, initrd, kernel and vmlinuz with the kernel version e.g. config would become config-2.4.21-0.13mdk (I think that's the stock 9.1 kernel). Then make sure that both /boot partitions contain copies of each. At present you are telling it to load vmlinuz, for 9.1. The trouble is that vmlinuz may well be pointing to the 9.2 version. Once you have copies of each in your /boot you can change these entries to version specific ones, and all should be well. If I were you I would try booting from CD1, hitting F1 where you get a chance to restore your lilo - you don't need one on each drive. That should at least get you in again, then you can look at what changes if any need making to make both versions available. I don't know whether it will be able to set it up correctly with the boot partitions on separate drives, so you may well have to hand edit. Anne Thanks Anne, that answers some of my questions. So I could boot from install cd restore my hda lilo.config, then boot to hda and then hand edit all the entries I want ie both hda and hdb and all the kernels old and new with devices like root=/dev/hda root=/dev/hdb and associated partitions, images,initrd,etc. and run lilo and of course check make sure all is working. Then possible boot to hdb (9.1) and remove lilo from 9.1? Or due you just leave that lilo.config alone? What due you and the others due with 2 linux OS's on the same box as a general rule? Mike Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] lilo questions
On Saturday 10 January 2004 17:38, mike wrote: Anne Wilson wrote: On Saturday 10 January 2004 16:30, mike wrote: If I were you I would try booting from CD1, hitting F1 where you get a chance to restore your lilo - you don't need one on each drive. That should at least get you in again, then you can look at what changes if any need making to make both versions available. I don't know whether it will be able to set it up correctly with the boot partitions on separate drives, so you may well have to hand edit. Anne Thanks Anne, that answers some of my questions. So I could boot from install cd restore my hda lilo.config, then boot to hda and then hand edit all the entries I want ie both hda and hdb and all the kernels old and new with devices like root=/dev/hda root=/dev/hdb and associated partitions, images,initrd,etc. and run lilo and of course check make sure all is working. Yes - I forgot to mention that you must run sbin/lilo whenever you have made changed. See below about configuration Then possible boot to hdb (9.1) and remove lilo from 9.1? Or due you just leave that lilo.config alone? Just leave it alone, it will do no harm. To help you see how my multiboot is set up here is a section of my lilo.conf. It should help you see what I mean: boot=/dev/hde map=/boot/map keytable=/boot/uk.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw disk=/dev/hde bios=0x80 image=/boot/vmlinuz-2.4.21-0.13mdk label=Mandrake91_13 root=/dev/hdf1 initrd=/boot/initrd-2.4.21-0.13mdk.img append=devfs=mount hda=ide-scsi acpi=off read-only image=/boot/vmlinuz-2.4.21-0.16mm-mdk label=Mandrake9.1MM root=/dev/hdf1 initrd=/boot/initrd-2.4.21-0.16mm-mdk.img append=devfs=mount hda=ide-scsi acpi=off read-only image=/boot/vmlinuz-2.4.21-0.26mdk label=Mandrake91_26 root=/dev/hdf1 initrd=/boot/initrd-2.4.21-0.26mdk.img append=devfs=mount hda=ide-scsi acpi=off read-only image=/boot/vmlinuz label=failsafe root=/dev/hdf1 initrd=/boot/initrd.img append=devfs=nomount hda=ide-scsi acpi=off failsafe read-only other=/dev/hde1 label=windows table=/dev/hde Don't worry about the fact that mine is talking about hde and hdf - that's a peculiarity of the way this motherboard handles the drives. Yours will simply be hda and hdb. Anne -- Registered Linux User No.293302 Have you visited http://twiki.mdklinuxfaq.org yet? Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[newbie] lilo questions
I had a few questions about lilo (see my post about upgrading the kernel to find out how they came up)... When I initially installed Mandrake 5.3, my system was all-SCSI--my hard drives, CD-ROMs, zip, jaz, etc. were all on a Diamond Fireport 40 Dual board. This worked fine. After I got that up and running, I heard about vmware, and decided it'd be cool to play with it. I hooked up an IDE drive to store the vmware data, set it to mount in the right place (/home/danb/vmware), etc. Everything continued to work just fine. Then, last night, I decided to upgrade my kernel. I built the new kernel, copied it into /boot, and edited lilo.conf. When I ran lilo, though, I got an error message to the effect that /dev/sda3 (which is where linux boots from) was not on the first disk--and when I rebooted, it stopped at "LI". After a few hours of messing around, I got the system to boot from a boot floppy, but lilo still gave the same error. Once I unplugged the IDE drive, lilo installed without a problem, the system booted, and everything worked fine. When I hooked the IDE drive back up, it still worked fine--the system still booted, recognized the drive, etc (though I didn't try running lilo again). Is this just the way lilo works? Will I need to unplug my IDE drive every time I want to change my lilo settings? Or is there some way around this? Thanks for any help! -- Dan Brown, KE6MKS, [EMAIL PROTECTED] Meddle not in the affairs of dragons, for you are crunchy and taste good with ketchup.
Re: [newbie] lilo questions
"Payne-Tingleff, Sam" wrote: I believe your BIOS sets the IDE drive as the primary disk by default. If there is no IDE present it will attempt to boot off a scsi disk. Thanks for the response. My BIOS is set to (and does) boot SCSI drives first. It loads System Commander, from which I choose Win98, Linux, etc. Lilo is installed in the superblock of /dev/sda3. Might it help if I told the BIOS to not probe for IDE disks at all? This drive is only used for storage; I don't need to boot from it at all. If I did that, would Linux see the drive at all? Worth trying, I suppose... -- Dan Brown, KE6MKS, [EMAIL PROTECTED] Meddle not in the affairs of dragons, for you are crunchy and taste good with ketchup.
