Re: Kernel panic: VFS: Unable to mount root fs on 03:03

From: Ross (Ross_at_nospam.com)
Date: 11/05/03 

Date: Wed, 5 Nov 2003 15:10:54 -0500

When I boot back to Knoppix again, and mount /dev/hda3 to /tmp, I can't see
anything except lost+found.
Under lost+found, there are many files like #20, #21, ...
Where are my files? Did the "fsck -y /dev/hda3" command delete all my files?
Ross

"Ross" <Ross@nospam.com> wrote in message news:bob165$1fv$1@news.storm.ca...
> I have booted Knoppix and run fsck Later when I tried to boot, I get the
> following messages:
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 319k freed
> EXT2-fs warning: checktime reached, running e2fsck is recommended
> VFS: Mounted root (ext2 filesystem).
> Red Hat nash version 3.2.6 starting
> Loading jbd module
> Journalled Block Device driver loaded
> Loading ext3 module
> Mounting /proc filesystem
> Creating root device
> Mounting root filesystem
> ext3: No journal on filesystem on ide0(3,3)
> mount: error 22 mounting ext3
> pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
> Freeing unused kernel mrmory: 220k freed
> Kernel panic: No init found. Try passing init= option to kernel.
> This seems an improvement of some sort.
> Is there anything else you can suggest to try now?
> BTW, I can boot to WinXP without problem.
> Thanks a million,
> Ross
>
> "Sybren Stuvel" <sybrenUSE@YOURthirdtower.imagination.com> wrote in
message
> news:slrnbqffk2.5dc.sybrenUSE@sybren.thirdtower.com...
> > ["Followup-To:" header set to comp.os.linux.]
> > Ross enlightened us with:
> > > My Red Hat Linux 7.2 wasn't properly shutdown. When I power on it
> > > again, I get Kernel panic as below: Kernel panic: VFS: Unable to mount
> > > root fs on 03:03
> >
> > Auch... You could try running Knoppix. From there you can try mounting
> > the partition and/or running fsck on it.
> >
> > Sybren
> > --
> > The problem with the world is stupidity. Not saying there should be a
> > capital punishment for stupidity, but why don't we just take the
> > safety labels off of everything and let the problem solve itself?
>
>

Relevant Pages

  • Re: fsckd - FIXED
    ... filesystem errors on boot, with the "hit control-D to continue or give root ... to fix the errors with fsck. ... filesystem and inability to reboot. ...
    (Debian-User)
  • Re: fsckd
    ... filesystem errors on boot, with the "hit control-D to continue or give root ... to fix the errors with fsck. ... filesystem and inability to reboot. ...
    (Debian-User)
  • Re: Disk Druid - Fedora flame #1
    ... >Gene Heskett wrote: ... > be part of a minimal boot environment. ... >And the root filesystem should be as small as reasonably possible, ... as long as root is trusted. ...
    (Fedora)
  • Re: Disk Druid - Fedora flame #1
    ... What I do as root, ... Root's home directory should contain very little: ... part of a minimal boot environment. ... And the root filesystem should be as small as reasonably possible, ...
    (Fedora)
  • Re: will linux survive the fagmenting/forking
    ... >>boot to the new from the old, ... >>root, mount it accessibly, run lilo, ane bob'syour uncle. ... because grub DOES read the filesystem. ... unless he is really perverse in his choice of root fs. ...
    (comp.os.linux.misc)