Re: [expert] LILO no longer works
This probably won't work. Check what other's say about this (obviously) but i think that / is seperate from the MBR and so formatting / will do nothing for how your machine is(n't) booting. Although when you have exausted the possible, start probing the impossible. What you need is some hardware/harddrive guru to tell you what kind of geometry-of-your-drive info you have to set up explicitly in LILO/GRUB/whatever. Have you posted all the information possible on your hd setup? Should you upgrade your motherboard bios? When you have exausted the possible. dunno :-) j --- Jay DeKing [EMAIL PROTECTED] wrote: Sorry, that didn't work either. I tried it with both LILO and GRUB, with the same results as always. The next step, I guess, is to boot up with the install CD and do an install/update. Since I have most of the programs and data on partitions separate from /, I shouldn't lose too much stuff when it makes me format / itself. Thanks, Jay Charles A Edwards wrote: I'll give you something else to try. Boot your system with a win98 start-up disk and fdisk /MBR. Remove the win98 disk and insert your Mandrake boot disk. Reboot your system. Your system should now boot to Linux before Win rewrites the boot record. Use sbin lilo or grub sh to install the one of your choice, either should now be able to fully install and be operational. Charles (-: Forever never goes beyond tomorrow. -- There is a fine line between 'hobby' and 'mental illness'. __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
Re: [expert] LILO no longer works
Yes, I realize that formatting / won't affect the MBR (especially since / is on hdb), but when I installed Mandrake last time it did give me a working GRUB setup. I'm not sure why the stand-alone GRUB and LILO utilities can't seem to do this, but they obviously are not up to the task for some reason. My motherboard (and everything else in the machine) is only about 6 months old, and I've kept up-to-date on all BIOS and firmware for everything I have, from the system board down to the CD drives, and all devices in between. The thing that really gets me is, the only thing that has changed is the contents of hda. Wait a minute ... that's not entirely true; the partition sizes have changed. hda1 was only 2GB in size before. The partition table was trashed, which is what precipitated the reformatting, and after a lot of mucking about I decided to fdisk the whole drive. I made the whole 30GB a single partition, formatted it, then fdisk'd it into two 15GB partitions and formatted them. Overkill? Sounds like it, but it was apparently necessary. Formatting the partitions individually didn't get the thing working. I've been working on my own hardware for over 10 years, and have never been through such an ordeal except in the bad old days of 20MB Seagate drives. (Harkening back to a recent thread in this group -- the drive that gave me all of this trouble is a Maxtor, six months old. My 30GB WD [hde] performed valiantly and flawlessly though all of this.) Jay John Wolford wrote: This probably won't work. Check what other's say about this (obviously) but i think that / is seperate from the MBR and so formatting / will do nothing for how your machine is(n't) booting. Although when you have exausted the possible, start probing the impossible. What you need is some hardware/harddrive guru to tell you what kind of geometry-of-your-drive info you have to set up explicitly in LILO/GRUB/whatever. Have you posted all the information possible on your hd setup? Should you upgrade your motherboard bios? When you have exausted the possible. dunno :-) j --- Jay DeKing [EMAIL PROTECTED] wrote: Sorry, that didn't work either. I tried it with both LILO and GRUB, with the same results as always. The next step, I guess, is to boot up with the install CD and do an install/update. Since I have most of the programs and data on partitions separate from /, I shouldn't lose too much stuff when it makes me format / itself. -- There is a fine line between 'hobby' and 'mental illness'.
Re: [expert] LILO no longer works
Sorry, that didn't work either. I tried it with both LILO and GRUB, with the same results as always. The next step, I guess, is to boot up with the install CD and do an install/update. Since I have most of the programs and data on partitions separate from /, I shouldn't lose too much stuff when it makes me format / itself. Thanks, Jay Charles A Edwards wrote: I'll give you something else to try. Boot your system with a win98 start-up disk and fdisk /MBR. Remove the win98 disk and insert your Mandrake boot disk. Reboot your system. Your system should now boot to Linux before Win rewrites the boot record. Use sbin lilo or grub sh to install the one of your choice, either should now be able to fully install and be operational. Charles (-: Forever never goes beyond tomorrow. -- There is a fine line between 'hobby' and 'mental illness'.
RE: [expert] LILO no longer works
I'll give you something else to try. Boot your system with a win98 start-up disk and fdisk /MBR. Remove the win98 disk and insert your Mandrake boot disk. Reboot your system. Your system should now boot to Linux before Win rewrites the boot record. Use sbin lilo or grub sh to install the one of your choice, either should now be able to fully install and be operational. Charles (-: Forever never goes beyond tomorrow. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jay DeKing Sent: Friday, May 11, 2001 10:20 PM To: Civileme Cc: [EMAIL PROTECTED] Subject: Re: [expert] LILO no longer works I have had to boot Linux with a floppy ever since I was forced to reformat my Win98 drive (hda1). Before the unfortunate incident which precipitated the reformatting, I had been using grub - very happily. Now, I have gone through grub-install many times since then, which gives me a Stage1 Read Error every time. I have also tried lilo (both graphical and command-line methods) and klilo. Both of them give me screens full of 10 10 10 10 ... ad infinitum. Every time I look for an answer, I am always told the proper method for installing GRUB and/or LILO. While I am thankful for the advice, I have gone through both procedures, carefully, in letter-perfect fashion many, many times, with precisely the same results every time. My fstab, lilo.conf, and menu.lst have not changed since I had to reformat; they should not need to, since the drives are configured exactly the same way as they were when GRUB worked. The last time somebody asked me to post my menu.lst file so they could see if anything was wrong with it, I never heard another word about it. So, either there was nothing interesting about it or I was forgotten. Imagine my pleasure when I saw a new idea (Civileme's - see below)! I tried it, and ... guess what? A screen full of 10 10 10 10 ... ad infinitum. Sigh. So, here is my menu.lst file again: timeout 5 color black/cyan yellow/cyan i18n (hd1,0)/boot/grub/messages keytable (hd1,0)/boot/us.klt altconfigfile (hd1,0)/boot/grub/menu.once default 4 title linux kernel (hd1,0)/boot/vmlinuz-secure root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy vga=788 title linux-up kernel (hd1,0)/boot/vmlinuz root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy title failsafe kernel (hd1,0)/boot/vmlinuz root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy failsafe title hack kernel (hd1,0)/boot/vmlinuz-hack root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy vga=788 initrd (hd1,0)/boot/initrd-hack.img title windows root (hd0,0) map (0x81) (0x80) map (0x80) (0x81) makeactive chainloader +1 And my lilo.conf: boot = /dev/hda map = /boot/map timeout = 200 prompt vga = normal read-only image = /boot/vmlinuz-secure label = linux append = hdg=ide-scsi hdd=ide-floppy root = /dev/hdb1 image = /boot/vmlinuz label = linux-up append = hdg=ide-scsi hdd=ide-floppy root = /dev/hdb1 image = /boot/vmlinuz label = failsafe append = hdg=ide-scsi hdd=ide-floppy failsafe root = /dev/hdb1 image = /boot/vmlinuz-hack label = hack append = hdg=ide-scsi hdd=ide-floppy root = /dev/hdb1 other = /dev/hda1 label = windows table=/dev/hda Oh great Linux masters, can you help ? Thanks Jay DeKing Civileme wrote: If you do NOT have reiser, then the mbr is probably damaged with respect to the new Mobo. To fix this use the 7.1 install CD, hit F1, type rescue without the quotes, and ... when the system comes up # mount /dev/hdax /mnt ## where x is the number for your / partition # chroot /mnt # /sbin/lilo EVEN if you were using grub, which you obviously were not. You should then be bootable from the hard disk, take out the CD and type # reboot Civileme -- There is a fine line between 'hobby' and 'mental illness'.
Re: [expert] LILO no longer works
I have had to boot Linux with a floppy ever since I was forced to reformat my Win98 drive (hda1). Before the unfortunate incident which precipitated the reformatting, I had been using grub - very happily. Now, I have gone through grub-install many times since then, which gives me a Stage1 Read Error every time. I have also tried lilo (both graphical and command-line methods) and klilo. Both of them give me screens full of 10 10 10 10 ... ad infinitum. Every time I look for an answer, I am always told the proper method for installing GRUB and/or LILO. While I am thankful for the advice, I have gone through both procedures, carefully, in letter-perfect fashion many, many times, with precisely the same results every time. My fstab, lilo.conf, and menu.lst have not changed since I had to reformat; they should not need to, since the drives are configured exactly the same way as they were when GRUB worked. The last time somebody asked me to post my menu.lst file so they could see if anything was wrong with it, I never heard another word about it. So, either there was nothing interesting about it or I was forgotten. Imagine my pleasure when I saw a new idea (Civileme's - see below)! I tried it, and ... guess what? A screen full of 10 10 10 10 ... ad infinitum. Sigh. So, here is my menu.lst file again: timeout 5 color black/cyan yellow/cyan i18n (hd1,0)/boot/grub/messages keytable (hd1,0)/boot/us.klt altconfigfile (hd1,0)/boot/grub/menu.once default 4 title linux kernel (hd1,0)/boot/vmlinuz-secure root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy vga=788 title linux-up kernel (hd1,0)/boot/vmlinuz root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy title failsafe kernel (hd1,0)/boot/vmlinuz root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy failsafe title hack kernel (hd1,0)/boot/vmlinuz-hack root=/dev/hdb1 hdg=ide-scsi hdd=ide-floppy vga=788 initrd (hd1,0)/boot/initrd-hack.img title windows root (hd0,0) map (0x81) (0x80) map (0x80) (0x81) makeactive chainloader +1 And my lilo.conf: boot = /dev/hda map = /boot/map timeout = 200 prompt vga = normal read-only image = /boot/vmlinuz-secure label = linux append = hdg=ide-scsi hdd=ide-floppy root = /dev/hdb1 image = /boot/vmlinuz label = linux-up append = hdg=ide-scsi hdd=ide-floppy root = /dev/hdb1 image = /boot/vmlinuz label = failsafe append = hdg=ide-scsi hdd=ide-floppy failsafe root = /dev/hdb1 image = /boot/vmlinuz-hack label = hack append = hdg=ide-scsi hdd=ide-floppy root = /dev/hdb1 other = /dev/hda1 label = windows table=/dev/hda Oh great Linux masters, can you help ? Thanks Jay DeKing Civileme wrote: If you do NOT have reiser, then the mbr is probably damaged with respect to the new Mobo. To fix this use the 7.1 install CD, hit F1, type rescue without the quotes, and ... when the system comes up # mount /dev/hdax /mnt ## where x is the number for your / partition # chroot /mnt # /sbin/lilo EVEN if you were using grub, which you obviously were not. You should then be bootable from the hard disk, take out the CD and type # reboot Civileme -- There is a fine line between 'hobby' and 'mental illness'.
[expert] LILO no longer works
Hello everyone; I have a LM 7.1 system on a which the motherboard had to be replaced. The system worked fine. While the motherboard was out, I put the (IDE) drive into another system (LM8) as a secondary drive. The primary drive in this system is SCSI. I was able to access the IDE drive okay after putting the proper entries into fstab and mounting it. Then I get the new motherboard back, and I put the drive back with it again, and it won't boot. I get LI.. the first two letters of LILO, and that's it. I thought it might be the manner the motherboard was addressing the drive, so I tried LBA, Large, CHS and Auto, and always get the same result. Anyone have any ideas? Thank you in advance for any light you can shed on this problem. I really don't want to re-install the system if I don't have to. Bruce Endries Bruce Endries Consulting (607) 433-2677 [EMAIL PROTECTED]
Re: [expert] LILO no longer works
Bruce Endries wrote: Hello everyone; I have a LM 7.1 system on a which the motherboard had to be replaced. The system worked fine. While the motherboard was out, I put the (IDE) drive into another system (LM8) as a secondary drive. The primary drive in this system is SCSI. I was able to access the IDE drive okay after putting the proper entries into fstab and mounting it. Then I get the new motherboard back, and I put the drive back with it again, and it won't boot. I get LI.. the first two letters of LILO, and that's it. I thought it might be the manner the motherboard was addressing the drive, so I tried LBA, Large, CHS and Auto, and always get the same result. Anyone have any ideas? Boot from floppy and rerun /sbin/lilo See also http://sdb.suse.de/en/sdb/html/kgw_lilo_errmsg.html Pierre Thank you in advance for any light you can shed on this problem. I really don't want to re-install the system if I don't have to. Bruce Endries Bruce Endries Consulting (607) 433-2677 [EMAIL PROTECTED] -- Support Linux development: http://www.linux-mandrake.com/donations/ Last reboot reason: 01/03/27: winter storm 6hr power outage
Re: [expert] LILO no longer works
This was answered on the Caldera list earlier this month(maybe). It's a drive geometry error(can't see or recognize the drive), the solution was to try the linear option in lilo to fix it. Randy Donohoe Mediocrity sucks. - Original Message - From: Bruce Endries [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 10, 2001 8:38 PM Subject: [expert] LILO no longer works Hello everyone; I have a LM 7.1 system on a which the motherboard had to be replaced. The system worked fine. While the motherboard was out, I put the (IDE) drive into another system (LM8) as a secondary drive. The primary drive in this system is SCSI. I was able to access the IDE drive okay after putting the proper entries into fstab and mounting it. Then I get the new motherboard back, and I put the drive back with it again, and it won't boot. I get LI.. the first two letters of LILO, and that's it. I thought it might be the manner the motherboard was addressing the drive, so I tried LBA, Large, CHS and Auto, and always get the same result. Anyone have any ideas? Thank you in advance for any light you can shed on this problem. I really don't want to re-install the system if I don't have to. Bruce Endries Bruce Endries Consulting (607) 433-2677 [EMAIL PROTECTED]
Re: [expert] LILO no longer works
On Thursday 10 May 2001 17:38, Bruce Endries wrote: Hello everyone; I have a LM 7.1 system on a which the motherboard had to be replaced. The system worked fine. While the motherboard was out, I put the (IDE) drive into another system (LM8) as a secondary drive. The primary drive in this system is SCSI. I was able to access the IDE drive okay after putting the proper entries into fstab and mounting it. Then I get the new motherboard back, and I put the drive back with it again, and it won't boot. I get LI.. the first two letters of LILO, and that's it. I thought it might be the manner the motherboard was addressing the drive, so I tried LBA, Large, CHS and Auto, and always get the same result. Anyone have any ideas? Thank you in advance for any light you can shed on this problem. I really don't want to re-install the system if I don't have to. Bruce Endries Bruce Endries Consulting (607) 433-2677 [EMAIL PROTECTED] Did you have reiser partitions on the drive? In particular was / reiser? If so, you must now update to 8.0 and then back up your data to ext2 and reinstall 7.1. If your data is mostly in /home, then I think it will be best to actually install 8.0 then back it up Alternatively you can use your other system for the backup. If you do NOT have reiser, then the mbr is probably damaged with respect to the new Mobo. To fix this use the 7.1 install CD, hit F1, type rescue without the quotes, and ... when the system comes up # mount /dev/hdax /mnt ## where x is the number for your / partition # chroot /mnt # /sbin/lilo EVEN if you were using grub, which you obviously were not. You should then be bootable from the hard disk, take out the CD and type # reboot Civileme
