Re: sid - new lilo installed and boot error - SOLUTION?
Could some one please advise whether this is the best / safest way to recover a bootable system? backup the / partition. reinstall a base system - upgrade this to sid - copy back the / omitting /boot (I actually have /boot on another partition). Thanks for an answer. According to Eric Smith on Wed, Nov 28, 2001 at 01:01:34AM +0100: 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) 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 :( Is it possible to copy the files I need to the /boot directory and recover the boot? 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 root14685 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 root33506 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 -rw-r--r-- 1 root root 587996 Nov 9 13:36 vmlinuz-2.4.14-586 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 root0 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 -- Eric Smith lba32 # Generated by liloconfig # Specifies the boot device boot=/dev/hda3 # Specifies the device that should be mounted as root. # If the special name CURRENT is used, the root device is set to the # device on which the root file system is currently mounted. If the root # has been changed with -r , the respective device is used. If the # variable ROOT is omitted, the root device setting contained in the # kernel image is used. It can be changed with the rdev program. root=/dev/hda3 # Enables map compaction: # Tries to merge read requests for adjacent sectors into a single # read request. This drastically reduces load time and keeps the map # smaller. Using COMPACT is especially recommended when booting from a # floppy disk. compact # Install the specified file as the new boot sector. # If INSTALL is omitted, /boot/boot.b is used as the default. install=/boot/boot.b # Specifies the number of _tenths_ of a second LILO should # wait before booting the first image. LILO # doesn't wait if DELAY is omitted or if DELAY is set to zero. delay=60 # Specifies the location of the map file. If MAP is # omitted, a file /boot/map is used. map=/boot/map # Specifies the VGA text mode that should be selected when # booting. The following values are recognized (case is ignored): # NORMAL select normal 80x25 text mode. # EXTENDED select 80x50 text mode. The word EXTENDED can be # abbreviated to EXT. # ASK stop and ask for user input (at boot time). # number use the corresponding text mode. A list of available modes # can be obtained by booting with vga=ask and pressing [Enter]. vga=ask image=/vmlinuz label=Linux read-only image=/dev/hdc1 label=Windows # 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 -- Eric Smith Fruitcom.com Benelux Phone: +31 70 313 0240 Mobile:+31 6 551 76300
Re: new lilo installed and boot error
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 root14685 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 root33506 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 listingI 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 root0 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
Re: new lilo installed and boot error
According to Donald R. Spoon on Wed, Nov 28, 2001 at 04:28:17AM -0600: See comments in your text copied below. Thank you for a complete and very informative answer - Well I have not managed to Fix the /boot for my 2.4 kernel, i did manage for the previous 2.19 though. I re-installed the kernel-image for 2.4, lilo and mbr The kernel-image complained there was no mbr and I should reinstall that package but that did not give me any mbr in the /boot dir. I am now booting off a 2.19 floppy and have a reasonably working system as we talk. I am sure it will all come right - its just burning a lot of time. The error with 2.4: request-module[block-major-3] root fs not mounted VFS: cannot open root device 303 or 03:3 Please append a correct root= boot option unable to mount root fs on 03:03 or some rant to that effect. Then with some more uninstalling and reinstalling of the above 3 mentioned packages in both kernel falcours i now get a flashing 40 40 over the screen when I try to boot either kernel. So why is this so difficult, I though a package install that you allow to overwrite broken configurations just fixed things and worked ;) Anyway FWIW, here are the tortured results of my efforts: /boot: total 5540 -rw-r--r--1 root root24232 Apr 8 2001 config-2.2.19-ide -rw-r--r--1 root root 613339 Apr 8 2001 vmlinuz-2.2.19-ide -rw-r--r--1 root root 213840 Apr 8 2001 System.map-2.2.19-ide -rw-r--r--1 root root14685 Oct 25 05:31 config-2.2.19pre17 -rw-r--r--1 root root 272592 Oct 25 05:31 System.map-2.2.19pre17 -rw-r--r--1 root root 512 Oct 25 05:38 boot.0300.bak -rw-r--r--1 root root33506 Nov 9 11:20 config-2.4.14-586 -rwxr-xr-x1 root root 587996 Nov 9 14:36 vmlinuz-2.4.14-586 -rw-r--r--1 root root 382516 Nov 9 14:36 System.map-2.4.14-586 lrwxrwxrwx1 root root 23 Nov 17 22:38 initrd - /boot/initrd-2.4.14-586 -rw-r--r--1 root root 656 Nov 20 01:30 os2_d.b -rw-r--r--1 root root 728 Nov 20 01:30 chain.b -rw-r--r--1 root root 5920 Nov 20 01:30 boot-text.b -rw-r--r--1 root root 7680 Nov 20 01:30 boot-menu.b -rw-r--r--1 root root 5920 Nov 20 01:30 boot-compat.b -rw-r--r--1 root root 7708 Nov 20 01:30 boot-bmp.b -rw---1 root root 512 Nov 27 23:47 boot.0303.1.bak -rw-r--r--1 root root 512 Nov 28 01:46 boot.0303.bak -rw-r--r--1 root root 512 Nov 28 16:51 boot.0300 -rw-rw-r--1 root root 14 Nov 28 16:56 bootmess.txt -rw-r--r--1 root root 512 Nov 28 17:21 boot.0303 lrwxrwxrwx1 root root 11 Nov 28 19:59 boot.b - boot-menu.b -rw-r--r--1 root root 3407872 Nov 28 21:46 initrd-2.4.14-586 -rw---1 root root 6144 Nov 28 21:48 map.old lrwxrwxrwx1 root root 11 Nov 28 23:42 vmlinuz-2.2.19pre17 - vmlinuz.old -rw---1 root root 5120 Nov 29 2001 map /: lrwxrwxrwx1 root root 23 Nov 28 21:46 /vmlinuz.old - boot/vmlinuz-2.4.14-586 lrwxrwxrwx1 root root 24 Nov 28 23:45 /vmlinuz - /boot/vmlinuz-2.2.19-ide /etc/lilo.conf: boot=/dev/hda3 root=/dev/hda3 compact install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label=hohohoh read-only Thanx Don for your help - wish it was alla lot easier though. 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
sid - new lilo installed and boot error
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) 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 :( Is it possible to copy the files I need to the /boot directory and recover the boot? 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 root14685 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 root33506 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 -rw-r--r-- 1 root root 587996 Nov 9 13:36 vmlinuz-2.4.14-586 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 root0 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 -- Eric Smith lba32 # Generated by liloconfig # Specifies the boot device boot=/dev/hda3 # Specifies the device that should be mounted as root. # If the special name CURRENT is used, the root device is set to the # device on which the root file system is currently mounted. If the root # has been changed with -r , the respective device is used. If the # variable ROOT is omitted, the root device setting contained in the # kernel image is used. It can be changed with the rdev program. root=/dev/hda3 # Enables map compaction: # Tries to merge read requests for adjacent sectors into a single # read request. This drastically reduces load time and keeps the map # smaller. Using COMPACT is especially recommended when booting from a # floppy disk. compact # Install the specified file as the new boot sector. # If INSTALL is omitted, /boot/boot.b is used as the default. install=/boot/boot.b # Specifies the number of _tenths_ of a second LILO should # wait before booting the first image. LILO # doesn't wait if DELAY is omitted or if DELAY is set to zero. delay=60 # Specifies the location of the map file. If MAP is # omitted, a file /boot/map is used. map=/boot/map # Specifies the VGA text mode that should be selected when # booting. The following values are recognized (case is ignored): # NORMAL select normal 80x25 text mode. # EXTENDED select 80x50 text mode. The word EXTENDED can be # abbreviated to EXT. # ASK stop and ask for user input (at boot time). # number use the corresponding text mode. A list of available modes # can be obtained by booting with vga=ask and pressing [Enter]. vga=ask image=/vmlinuz label=Linux read-only image=/dev/hdc1 label=Windows # 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
