linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Clements <Paul.Clements@SteelEye.com>
To: sama@inf.ufsc.br
Cc: linux-raid@vger.kernel.org
Subject: Re: Help ! Kernel panic: VFS: Unable to mount root fs on 09:01 - Part II
Date: Fri, 02 May 2003 11:51:30 -0400	[thread overview]
Message-ID: <3EB29402.C5682FC6@SteelEye.com> (raw)
In-Reply-To: 1051874803.3eb255f37597d@webmail.inf.ufsc.br

sama@inf.ufsc.br wrote:
> 
> Hi,
> 
>       I used linux root=/dev/hda2 on lilo prompt. The system returned me:
> 
>             VFS: Mounted root /ext2 filesystem readonly
>              Warning: unable to open an initial console
>              Kernel Panic: No init found. Try passing init= open to kernel.
> 
>       I used linux init=/bin/sh on lilo prompt but, the system returned me
> the same error. Any suggestion ?


Unfortunately, I think you may have lost too much of your root
filesystem for the system to be usable...if you really need to salvage
the data, you might boot up with a rescue CD (use your installation CD),
then fsck the root partition and see if you can mount it...you might be
able to pull your data off...

--
Paul 


>             Thanks,
> 
>          Roberto Samarone Araujo
> 
> > /dev/hda2 should be /boot directory ? I've tried /dev/hda3 / directory and
> > the same error appeared.
> >
> >           Thanks,
> >
> >       Roberto Samarone Araujo
> >
> >
> > > "Roberto Samarone Araujo (RSA)" wrote:
> > >
> > > > RAMDISK: Compressed image found at block 0
> > > > invalid compressed format (err=1),6. Freeing initrd memory: 484 freed
> > >
> > > Looks like your initrd image got fried...I believe that's where raid1
> > > should have gotten loaded and your array autostarted (if this is United
> > > Linux 1.0/Conectiva)...
> > >
> > > try booting with "linux root=/dev/hda2" at the lilo prompt
> > >
> > > it still might not work though...
> > >
> > > good luck...
> > >
> > > --
> > > Paul
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2003-05-02 15:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02 11:26 Help ! Kernel panic: VFS: Unable to mount root fs on 09:01 - Part II sama
2003-05-02 15:51 ` Paul Clements [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EB29402.C5682FC6@SteelEye.com \
    --to=paul.clements@steeleye.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=sama@inf.ufsc.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).