At Monday, 27 December 2004, Laurent CARON <[EMAIL PROTECTED]> wrote:

>Harland Christofferson wrote:
>
>>an update to my saga is that i was able to run lilo. however, when 
>>trying to boot, i see:
>>
>>request_module{block-major-3]: root fs not mounted
>>VFS: Cannot open root device "303" or 03:03 
>>Please append correct "root=" boot option 
>>Kernel Panic: VFS: Unable to mount root fs on 03:03
>>
>>
>>my root= option is set to /dev/hda3 which is the root partition.
>>
>>suggestions?
>>
>>At Monday, 27 December 2004, Harland Christofferson <[EMAIL PROTECTED]

>
>>com> wrote:
>>
>>  
>>
>>>while getting ready to build a raid 1 array, i accidentally deleted 
>>>the /boot files. the partition is still there however and is still 
>>>flagged as boot partition.
>>>
>>>although i have a boot floppy for this machine, i could not retrieve 
>>>a backup of the /boot partition from another hard disk i have. in 
>>>a novice attempt to resolve this, i copied the /boot partition from 
>>>another machine and reboot.  upon rebooting w/ the boot floppy, i 
>>>ran lilo to try to rebuild the MBR. lilo complains:
>>>
>>>    
>>>
>>>>Added Linux *
>>>>Skipping /vmlinux.old
>>>>Fatal: First sector of /dev/hda1 doesn't have a valid boot signature
>>>>      
>>>>
>>>how can i fix my /boot partition so that the machine can boot 
without 
>>>the files in the boot or root partitions that originally were part 
>>>of this machine?
>>>
>>>harland
>>>
>>>    
>>>
>fdisk -l

Disk /dev/hda: 255 heads, 63 sectors, 4998 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1         4     32098+  83  Linux
/dev/hda2             5        35    249007+  82  Linux swap
/dev/hda3            36      2223  17575110   83  Linux
/dev/hda4          2224      4998   2290187+   5  Extended  
/dev/hda5          2224      3242   8988336   83  Linux
/dev/hda6          3243      4461   8988336   83  Linux
/dev/hda7          4462      4998   4313421   83  Linux

>
>cat /proc/mdstat

Personalities:
read_ahead not set
md0: not active
md1: not active
md2: not active
md3: not active

>
>ls -al /
drwxr-xr-x    2 root root     4096 Nov 28 22:48 bin
drwxr-xr-x    3 root root     1024 Dec 27 10:20 boot
drwxr-xr-x    2 root root     4096 Jan 30  2004 cdrom
drwxr-xr-x   10 root root    24576 Dec 26 06:47 dev
drwxr-xr-x  117 root root     8192 Dec 27 00:15 etc
drwxr-xr-x    2 root root     4096 Jan 30  2004 floppy
drwxr-xr-x   25 root root     4096 Dec 13 09:24 home
drwxr-xr-x    1 root root      268 Jan 30  2004 initrd
drwxr-xr-x    8 root root     4096 Dec  6 23:14 lib
drwx------    2 root root     4096 Jun  6  2004 lost+found
drwxr-xr-x   14 root root     4096 Dec 27 00:08 mnt
drwxr-xr-x    3 root root     4096 Sep  4  2002 opt
dr-xr-xr-x  219 root root        0 Dec 16 06:39 proc
drwxr-xr-x   17 root root     4096 Dec 23 15:22 root
drwxr-xr-x    2 root root     4096 Dec  6 23:14 sbin
drwxr-xr-x    2 root root     4096 Jul 30 18:07 sys
drwxrwxrwt   21 root root    20480 Dec 27 12:00 tmp
drwxr-xr-x   16 root root     4096 Sep 12 08:55 usr
drwxr-xr-x   17 root root     4096 Sep 28 19:08 var
lrwxrwxrwx    1 root root       22 Dec 26 23:58 vmlinuz -> boot/vmlinuz-
2.4.18-k7


the vmlinuz is there b/c i put the link back after i wiped out the 
/boot contents.



>ls -al /boot

-rw-r--r--   1 root root 7020544 Mar 25  2004 System.map-2.2.20
-rw-r--r--   1 root root  409179 Apr 14  2002 System.map-2.4.18-k7
-rw-r--r--   1 root root    7988 Sep  2  2002 boot-bmp.b
-rw-r--r--   1 root root    6204 Sep  2  2002 boot-compat.b
-rw-r--r--   1 root root    7964 Sep  2  2002 boot-menu.b
-rw-r--r--   1 root root    6204 Sep  2  2002 boot-text.b
-rw-r--r--   1 root root     512 Sep  2  2002 boot.0300
-rw-r--r--   1 root root     512 Dec 27 10:58 boot.0301
-rw-r--r--   1 root root     728 Sep  2  2002 chain.b
-rw-r--r--   1 root root   14979 Sep  2  2002 config-2.2.20
-rw-r--r--   1 root root   37096 Apr 13  2002 config-2.4.18-k7
-rw-r--r--   1 root root 2719744 Jan  6  2003 initrd.img-2.4.18-k7
drwx------   2 root root   12288 Aug 26  2002 lost+found
-rw-------   1 root root   49664 Jan  6  2003 map
-rw-r--r--   1 root root   94428 Nov 12 12:37 memtest86+.bin
-rw-r--r--   1 root root     656 Sep  2  2002 os2_d.b
lrwxrwxrwx   1 root root      14 Dec 27 10:46 vmlinuz -> vmlinuz-
2.4.18-k7
-rw-r--r--   1 root root 1005181 Aug 26  2002 vmlinuz-2.2.20
-rw-r--r--   1 root root  643025 Apr 14  2002 vmlinuz-2.4.18-k7


keep in mind, the contents of /boot are the result of a tarball i 
moved on to this machine from another machine. this is not what originally 
was on this machine prior to my mistake.

>
>cat /etc/fstab

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>           <dump> 
<pass>
/dev/hda3       /               ext2    errors=remount-ro       0 
1 /dev/hda2       none            swap    sw               
0       0
proc            /proc           proc    defaults                0 
0
/dev/fd0        /floppy         auto    user,noauto             0 
0
/dev/cdrom      /cdrom          iso9660 ro,user,noauto          0 
0
/dev/hda1       /boot   ext2    defaults                        0 
2
/dev/hda5       /usr    ext2    defaults                        0 
2
/dev/hda6       /var    ext2    defaults                        0 
2
/dev/hda7       /home   ext2    defaults                        0 
2

>
>cat /etc/lilo.conf

# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt', or install a new kernel.  The |
# | computer will most likely fail to boot if a kernel-image      |
# | post-install script or you don't remember to run `lilo'.      |
# |                                                               |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
#    bios=0x81

#disk=/dev/sda
#    bios=0x80

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda1

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda3

# Enable 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.  It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
#       prompt
#       single-key
#       delay=100
#       timeout=100
prompt
timeout=150

# Specifies the VGA text mode at boot time. (normal, extended, ask,
<mode>)
#
# vga=ask
# vga=9
#
vga=normal

# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""

# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
        label=Linux
        read-only
#       restricted
#       alias=1
        initrd=/initrd.img

image=/vmlinuz.old
        label=LinuxOLD
        read-only
        optional
#       restricted
#       alias=2

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
#       label=HURD
#       restricted
#       alias=3





----------------------------------------------------------------------
Zero Crossings, Inc. -- Embedded and Digital Signal Processing Systems

http://www.zerocrossings.com/











-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to