See comments in your text copied below. Cheers, -Don Spoon-
Eric Smith <[EMAIL PROTECTED]> wrote: > I installed the new lilo and let debconf create a new > lilo.conf and add a boot sector. Before restarting, > however I added an entry for Windows, then /sbin/lilo -v > which reported nothing abnormal. > > However when i tried to reboot, I get: > > unable to mount root fs > add a root= entry (or something to that effect) See my comment on /etc/lilo.conf "boot" command below > enclosed is the relevant lilo.conf which does show the root fs > pointing to /dev/hda3, which is correct (as per original > lilo.conf. > > Here are the contents of the /boot - however I must admit that i > seem to have lost the map file while trying to correct the > problem :( > It isn't lost...you still seem to have it listed. Is it the wrong "map" file?? > Is it possible to copy the files I need to the /boot directory > and recover the boot? > Yes. You will have to boot up using a "rescue" disk, mount /dev/hda3 and "chroot" to that mounted directory. You can then edit your /etc/lilo.conf and re-run lilo to install the new (modified per below) lilo to the MBR. Be careful... your paths will be all screwed up, so use the FULL path to the file you want to run. This mainly applies to running /sbin/lilo. Also, you may have limited choice of editors available...hope you can run vi <grin>. > Thanx > > total 5656 > -rwxr-xr-x 1 root root 1001473 Oct 25 03:31 vmlinuz-2.2.19pre17 > -rw-r--r-- 1 root root 272592 Oct 25 03:31 System.map-2.2.19pre17 > -rw-r--r-- 1 root root 14685 Oct 25 03:31 config-2.2.19pre17 > -rw-r--r-- 1 root root 512 Oct 25 03:38 boot.0300 > -rw-r--r-- 1 root root 33506 Nov 9 10:20 config-2.4.14-586 > -rw-r--r-- 1 root root 382516 Nov 9 13:36 System.map-2.4.14-586 The above is your "map" file for your new 2.4.14 kernel. You can edit your /lilo.conf file to point to this file or just create a symlink in this directory to /boot/map or just copy this file to "/boot/map". I notice that a "map" file already exists further below in this listing....I wouldn't touch anything here until you get some complaints about it on bootup. > -rw-r--r-- 1 root root 587996 Nov 9 13:36 vmlinuz-2.4.14-586 Do you have a symlink in your root directory to the above kernel?? (The new one). A "ls -l" should show "vmlinuz --> /boot/vmlinuz-2.4.14-596". This symlink MUST exist because that is where the "root=/dev/hda3" command in /etc/lilo.conf is saying a kernel resides. > lrwxrwxrwx 1 root root 17 Nov 13 10:55 boot.b -> > /boot/boot-menu.b > -rw-r--r-- 1 root root 3407872 Nov 17 21:38 initrd-2.4.14-586 > lrwxrwxrwx 1 root root 23 Nov 17 21:38 initrd -> > /boot/initrd-2.4.14-586 > -rw-r--r-- 1 root root 7708 Nov 20 00:30 boot-bmp.b > -rw-r--r-- 1 root root 7680 Nov 20 00:30 boot-menu.b > -rw-r--r-- 1 root root 5920 Nov 20 00:30 boot-text.b > -rw-r--r-- 1 root root 5920 Nov 20 00:30 boot-compat.b > -rw-r--r-- 1 root root 656 Nov 20 00:30 os2_d.b > -rw-r--r-- 1 root root 728 Nov 20 00:30 chain.b > -rw-rw-r-- 1 root root 0 Nov 27 22:31 bootmess.txt > -rw------- 1 root root 512 Nov 27 22:47 boot.0303 > -rw------- 1 root root 6656 Nov 27 22:49 map This is the "/boot/map" I was talking about above. > > -- > Eric Smith > > lba32 > # Generated by liloconfig > > # Specifies the boot device > boot=/dev/hda3 This command puts the lilo boot-loader info on the "Superblock" of hda3. I does NOT put it into the MBR. There are occasions (few) where you would want to do this... essentially if you are using another boot-loader and want to call lilo for some reason. On my machine this line reads: "boot=/dev/hda". > --snip-- < > image=/vmlinuz > label=Linux > read-only > > image=/dev/hdc1 > label=Windows I suggest you get rid of the second "image" stanza for Windows and use the notation below...i.e. uncomment the "other" line and make the appropriate edits for the HD used and the "label" you want. > > # If you have another OS on this machine (say DOS), > # you can boot if by uncommenting the following lines > # (Of course, change /dev/hda2 to wherever your DOS partition is.) > # other=/dev/hda2 > # label=dos
