linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: 2.5.62-mm3 won't mount root
Date: 24 Feb 2003 11:04:24 -0700	[thread overview]
Message-ID: <1046109864.6615.153.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <20030223230023.365782f3.akpm@digeo.com>

On Mon, 2003-02-24 at 00:00, Andrew Morton wrote:
> 
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.62/2.5.62-mm3/

2.5.62-mm3 won't mount root for me.
2.5.62-bk-current (as of 2 hours ago) works fine.

I get this right after setting the hostname:

Checking root filesystem
/dev/hda1
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock.
   e2fsck -b 8193 <device>

fsck.ext3 : No such file or directory while trying to open /dev/hda1
Failed to check filesystem.  Do you want to repair the errors? (Y/N)
(beware, you can lose data)

Even though this is just a test box, I chickened out and reset the box.

/def/hda1 is ext3:

[steven@spc1 steven]$ df -T
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/hda1     ext3    236M  138M   87M  62% /
/dev/hda9     ext3     20G   13G  6.7G  67% /home
/dev/hda11     jfs    3.9G  2.7G  1.3G  68% /share_jfs
/dev/hda10
          reiserfs    4.0G  254M  3.7G   7% /share_reiser
/dev/hda12     xfs    4.8G  290M  4.5G   6% /share_xfs
/dev/hda8     ext3    236M  4.8M  219M   3% /tmp
/dev/hda6     ext3    2.9G  1.5G  1.3G  54% /usr
/dev/hda7     ext3    479M   66M  389M  15% /var

I tried to build 2.5.62-mm2, but couldn't do to this:

fs/devfs/fs.c: In function `devfs_event':
fs/devfs/fs.c:63: too few arguments to function `call_usermodehelper'
make[2]: *** [fs/devfs/fs.o] Error 1

Steven



--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>

      parent reply	other threads:[~2003-02-24 18:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24  7:00 2.5.62-mm3 Andrew Morton
2003-02-24 12:26 ` 2.5.62-mm3 - no X for me Helge Hafting
2003-02-24 20:16   ` Andrew Morton
2003-02-25  9:45     ` Zilvinas Valinskas
2003-02-25  9:55       ` Andrew Morton
2003-02-25 17:57         ` Dave McCracken
2003-02-25 21:27           ` Andrew Morton
2003-02-25 21:46             ` Dave McCracken
2003-02-25 23:02               ` [PATCH 2.5.62-mm3] objrmap fix for X Dave McCracken
2003-02-26  6:14                 ` Martin J. Bligh
2003-02-26 17:52                   ` Martin J. Bligh
2003-02-26 18:03                     ` Marc-Christian Petersen
2003-02-26 18:24                       ` Martin J. Bligh
2003-03-01  9:31                     ` Anton Blanchard
2003-02-25 18:49         ` 2.5.62-mm3 -Panics during dbt2 run Cliff White
2003-02-25 19:12           ` Andrew Morton
2003-02-25 22:37             ` 2.5.62-mm3 -DBT2 (was) " Cliff White
2003-02-24 18:04 ` Steven Cole [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=1046109864.6615.153.camel@spc9.esa.lanl.gov \
    --to=elenstev@mesatop.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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