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

Re: Kernel Panic was: System is too Big; son of make menuconfig



You might try tomsrtbt (http://www.toms.net/rb/), which has ext3
support in recent versions, so you should be able to mount the
partition.  It sounds like it is very likely corrupted, so you should run
e2fsck.  But yes, you might be facing a re-install (been there, done
that).

I've found tomsrtbt to be a pretty useful tool.  From the FAQ:

1) tomsrtbt is

        "The most GNU/Linux on one floppy disk"

        for:

                rescue recovery panic & emergencies

                tools to keep in your shirt pockets

                whenever you can't use a hard drive

        Tomsrtbt stands for:

"Tom's floppy which has a root filesystem and is also bootable."

 
On Sat, Oct 12, 2002 at 02:39:22PM -0700, Michael Olds wrote:
> JT,
> 
> Yes, I think this is the problem. See previous of mine (sorry to be flooding
> the board with these updates...flailing around in the dark here). What I
> don't see is how to get out of it...I think I am facing a hitabrickwall
> re-install here, yes?
> 
> Best Wishes!
> Mike Olds www.buddhadust.org
> 
> 
> 
> -----Original Message-----
> From: James Tappin [mailto:james@tappin.me.uk]
> Sent: Saturday, October 12, 2002 2:32 PM
> To: debian-user@lists.debian.org
> Subject: Re: Kernel Panic was: System is too Big; son of make menuconfig
> 
> 
> On Sat, 12 Oct 2002 14:24:31 -0700
> Michael Olds <MikeOlds@pacbell.net> wrote:
> 
> > > ...root fs not mounted
> > > VFS: Cannot open root device "307" or 03:07
> > > Please append a correct "Root=" boot option
> > > Kernel panic: VFS: unable to mount root FS on 03:07
> >
> > IMHO this means, that it wants to mount /dev/hda7 as root FS but
> > can't find it. 03 is the major number of the device and 07 the
> > minor number. This is /dev/hda7.
> 
> Or possibly an unsupported filesystem. If your kernel has ext3 or
> reisferfs as a module and the root filesystem is of this type, then unless
> you have an initrd (initial ram disk) file to provide the module you will
> be in big trouble.
> 
> Options in this case (1) make a suitable initrd, (2) compile the
> filesystem into the kernel.
> 
> James
> 
> --
> James Tappin,             O__      "I forget the punishment for using
> james@tappin.me.uk       --  \/`    Microsoft --- Something lingering
> http://www.tappin.me.uk/            with data loss in it I fancy"
> 



Reply to: