[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: new hard drive install



Quoting charles kaufman (chuck@grinder.acc.uri.edu):
> Hello again
> 
> On Tue, 29 Jun 1999, David Wright wrote:
> 
> > Quoting charles kaufman (chuck@grinder.acc.uri.edu): 
> > >  "kernel panic:VFS:Unable to mount root fs on 03:03"
> > 
> >
> > > Is there somewhere in the kernel that remembers it used to boot from
> > > /dev/hda3?> 
> 
> 
> >  Yes. When you copy a kernel (e.g. I copy /boot/vmlinuz to
> > c:\loadlin\zimage for loadlin to boot from dos) you need to rdev it.
> > Type    rdev kernel-image    to see what it's set to and
> > rdev kernel-image /dev/hda2    to set it. This saves having to tell it
> > where root is every time you boot it.
> 
> Thanks.
> 
> But the lilo manpage says rdev is no longer needed since the parameters 
> can be set from the lilo prompt.

No, but I answered the question as posed. I would guess that lilo
just modifies the same bytes as rdev does, but on the fly as it loads
the kernel.

> I tried it anyway. With the new drive at /mnt, I did 
> rdev /mnt/vmlinuz /dev/hda2, and
> rdev -s /mnt/vmlinuz /dev/hda3.
> 
> I then then reattached the new drive onto the first ide connector and
> rebooted. It failed in exactly the same way as before.
> 
> In case they contains any hints, here are the messages which immediately
> precede the panic:
> 
> partition check:
> hda: hda1 hda2 hda3
> [MS-DOS FS Rel.12, FAT 12, check=n,conv=b,uid=0,gid=0,umask=022]
> [me=oxff,cs=32385,#f=255,fs=65409,fl=65409,ds=33024,de=65535,data=37215,
> se=65635,ts=-1,ls=65535,rc=0,fc=4294967295]
> Transaction block size=512
> UMSDOS Beta 0.6 (compatability level 0.4 fast msdos)
> 
> the lines from [MSDOS..   to Transaction..  are then repeated,
> and then it says 
> Kernel panic : VFS Unable to mount root fs on 03:03.

I think that may change everything. Allowing for typos, because you
copied that off the screen, did it really say FAT 12? It looks as
though it's either misread the partition table (perhaps it got the
geometry wrong or something) or the kernel lacks some necessary
functionality to handle the new disk. What does lsmod show when you
have the disk on /mnt. Is it using a module to get at that disk?
Could your partitions be misnumbered in some way? 

Either way, I think you may need more expert help than I can provide.

Cheers,

-- 
Email:  d.wright@open.ac.uk   Tel: +44 1908 653 739  Fax: +44 1908 655 151
Snail:  David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA
Disclaimer:   These addresses are only for reaching me, and do not signify
official stationery. Views expressed here are either my own or plagiarised.


Reply to: