Re: LILO problems with new HD
* Jon Keating [EMAIL PROTECTED] writes: with that. Can a system boot up without a map file? It seems like it can. Yes, you experienced it :-) But like your problem, I always thought you needed the map file. I know my Only if you want more informative error messages in case of a kernel crash. W/o the map file, it´ll give you only a few addresses. Look for System.map in kernel-source/Documentation/oops-tracing.txt for more information. Cheers, Colin -- Colin Marquardt [EMAIL PROTECTED]
Re: LILO problems with new HD
You were referring to System.map for the error messages, not the /boot/map file used to load the system.
LILO problems with new HD
Hello, I've recently discovered problems with the drive that had the /boot and /home partitions of my Debian box, so I decided to go out and get a new HD in transferring the files, I simply copied /boot/* and /home/* to the new drive, and ran lilo on it. It gave me the message that lilo was installed, and I tried rebooting. Lilo being's to load, but only goes so far as LIL- until it freezes...in the lilo docs, this says that there is some sort of corruption of the map files, or a problem with the map installer. Seeing as these copied files were from a corrupted (suspected at least) disk, I figure that's the problem. Can anyone help me in getting fresh copies of the files that LILO requires for installation? I don't know if they are custom to my setup (untouched slink kernel), or if they are generic files thatI could simply pick up somewhere off of the CD's. thanks in advance!! -lev
Re: LILO problems with new HD
Subject: LILO problems with new HD Date: Sun, Jul 25, 1999 at 09:48:08PM -0700 In reply to:Lev Lvovsky Quoting Lev Lvovsky([EMAIL PROTECTED]): Hello, I've recently discovered problems with the drive that had the /boot and /home partitions of my Debian box, so I decided to go out and get a new HD in transferring the files, I simply copied /boot/* and /home/* to the new drive, and ran lilo on it. It gave me the message that lilo was installed, Is that all you did? What drive partition did you put /boot on? The info you supplied is insufficent for me to help you with. My crystal ball is cracked, sorry. -- DOS Tip #1: Add DEVICE=FNGRCROS.SYS to CONFIG.SYS ___ Wayne T. Topa [EMAIL PROTECTED]
Re: LILO problems with new HD
I've recently discovered problems with the drive that had the /boot and /home partitions of my Debian box, so I decided to go out and get a new HD in transferring the files, I simply copied /boot/* and /home/* to the new drive, and ran lilo on it. It gave me the message that lilo was installed, Is that all you did? What drive partition did you put /boot on? The info you supplied is insufficent for me to help you with. My crystal ball is cracked, sorry. hehe, sorry, I post under the assumption that ppl's balls are in working order ;-D. /boot is hda1...there are three partitions on the drive, none of them extended. this is what I do @ the console: ** silver168:~# lilo -v LILO version 21, Copyright 1992-1998 Werner Almesberger Reading boot sector from /dev/hda Merging with /boot/boot.b Boot image: /boot/linux Added Linux * /boot/boot.0300 exists - no backup copy made. Writing boot sector. ** I'm a little bit confused as to the difference between this command, and 'lilo -v -b /dev/hda1', which gives me the following: ** silver168:~# lilo -v -b /dev/hda1 LILO version 21, Copyright 1992-1998 Werner Almesberger Ignoring entry 'boot' Reading boot sector from /dev/hda1 Merging with /boot/boot.b Boot image: /boot/linux Added Linux * /boot/boot.0301 exists - no backup copy made. Writing boot sector. ** again, when I reboot, and take out the floppy (the way I've been booting for a long time now seeing as my other HD gave me this same problem), I get a LIL-, which the docs say is a problem with the map file. any help would be appreciated :) -lev
Re: LILO problems with new HD
I don't know if we have similiar problems or not. With my system it can't find the map file, but it still boots up, so I'm not sure what the deal is with that. Can a system boot up without a map file? It seems like it can. But like your problem, I always thought you needed the map file. I know my system boots up, but I can't do much w/o the map.
Re: LILO problems with new HD
Subject: Re: LILO problems with new HD Date: Mon, Jul 26, 1999 at 01:21:46AM -0700 In reply to:Lev Lvovsky Quoting Lev Lvovsky([EMAIL PROTECTED]): hehe, sorry, I post under the assumption that ppl's balls are in working order ;-D. /boot is hda1...there are three partitions on the drive, none of them extended. this is what I do @ the console: Ok I guess I have to spend more time to ask specific questions.. sigh You said I simply copied /boot/* and /home/* to the new drive, and ran lilo on it. You didn't say if you updated the /etc/fstab file. You didn't say if you updated /etc/lilo.config to look for the new /boot on a different drive. You didn't say if you changed/removed the old lilo.conf entry that pointed to the OLD location of /boot. You didn't say if you now have 2 drives ( I assume you do as you only copied /boot and /home to the New one) or if there is now only one drive. I have written oncee in an effort to help. I have written a second time to try to help YOU to help yourself. [ snip lilo response that dosen't mean anything without above answere] I _sometimes_ even try to help 3 times, but that doesn't happen often! -- Maintenance-free: When it breaks, it can't be fixed... ___ Wayne T. Topa [EMAIL PROTECTED]
Re: LILO problems with new HD
Ok I guess I have to spend more time to ask specific questions.. sigh You said I simply copied /boot/* and /home/* to the new drive, and ran lilo on it. You didn't say if you updated the /etc/fstab file. yes, /boot, /home, and the swap partition are updated to reside on the new drive...they are workng properly as I type. I wouldn't think that this would effect lilo botting, but either way, everything's fine here. You didn't say if you updated /etc/lilo.config to look for the new /boot on a different drive. well, since the new drive is essentially a copy of the old drive (just bigger), I didn't change anything here. In the process of changing things over, I mounted the new /boot, and /home in temporary directories, copies the dirs and files to them, and then unmounted the old /boot, and /home, and mounted the new ones in their place. I ran lilo after this, assuming that everything would just adjust to the changes. A suspicion is that the map file doesn't properly represent the new, bigger drive, but perhaps I'm wrong on this, as the map installer is part of 'lilo', and maybe it just updates the file after looking @ the new geometry. the following is my lilo.conf: ** boot=/dev/hda root=/dev/sda1 install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/boot/linux label=Linux read-only ** You didn't say if you changed/removed the old lilo.conf entry that pointed to the OLD location of /boot. again, the new drive has the same dir/partition structure (right down the the numbering, so essentially I didn't even change anything in /etc/fstab You didn't say if you now have 2 drives ( I assume you do as you only copied /boot and /home to the New one) or if there is now only one drive. yes, I have one SCSI drive, and one IDE drive...the scsi drive CANNOT boot, as it's hooked up to a non-bios scsi card (which requires drivers to initialize). I have written oncee in an effort to help. I have written a second time to try to help YOU to help yourself. well, hopefully this answers both of our questions... thanks -lev
