public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: KH <gentoo-user@konstantinhansen.de>
Subject: Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Date: Sun, 25 Jul 2010 09:49:17 +0200	[thread overview]
Message-ID: <201007250949.17739.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4C4BC447.6010803@konstantinhansen.de>

On Sunday 25 July 2010 06:57:43 KH wrote:
> > You said you ran e2fsck and it was OK. What was the command?
> >
> > 
> >
> > Normally with an e2fsck on a journalled fs, the app will replay the
> > journal  and make a few minor checks. This takes about 4 seconds, not
> > the 40 minutes it takes to do a ful ext2 check.
> >
> > 
> >
> > I think you might need to fsck without the journal. I know there's a way
> > to do  this but a cursory glance at the man page didn't reveal it. Maybe
> > an ext user will chip in with the correct method
> >
> > 
> > 
> > 
> 
> Hi,
> 
> I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3
> /dev/sde3 . Yes, it only took some seconds.

It's been a long time since I used ext3 so some of this might be wrong.

An fsck that takes a few seconds is using the journal, which might not uncover 
deeper corruption. You should try disabling the journal (I couldn't find the 
way to do that though), but this will also work:

Boot of a LiveCD, mount your root partition somewhere using type "ext2" and 
fsck it. This will invalidate the journal but that's OK, it gets recreated on 
the next proper boot. Let the fsck finish - it will take a while on a large 
fs.

When done, reboot as normal and see if the machine boots up properly.


-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2010-07-25  7:53 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-24 19:57 [gentoo-user] Problems booting my server - ext2 - e2fsck KH
2010-07-24 20:21 ` Alan McKinnon
2010-07-24 22:04   ` Robert Bridge
2010-07-25  4:57   ` KH
2010-07-25  7:49     ` Alan McKinnon [this message]
2010-07-25  8:18       ` Dale
2010-07-25 13:57         ` Mick
2010-07-28  8:50           ` KH
2010-07-28 13:42             ` Mick
2010-07-28 13:53               ` Bill Longman
2010-07-28 14:04                 ` Mick
2010-07-28 14:27                   ` Bill Longman
2010-07-28 14:46                     ` Mick
2010-07-28 15:18                   ` KH
2010-07-28 15:30                     ` Bill Longman
2010-07-28 16:35                       ` KH
2010-07-28 18:54                         ` Mick
2010-07-28 19:29                           ` Bill Longman
2010-07-28 15:21                 ` KH
2010-07-28 13:45             ` Bill Longman
2010-07-28 14:56               ` KH
2010-07-28 15:27                 ` Bill Longman
2010-07-28 16:37                   ` KH
2010-07-28 18:14                     ` Bill Longman
2010-07-29 11:39                       ` Peter Humphrey
2010-11-28 16:16                         ` Peter Humphrey
2010-07-25 15:24         ` covici
2010-07-25 20:10           ` Alan McKinnon
2010-07-25 20:08         ` Alan McKinnon
2010-07-26  1:05           ` Bill Kenworthy
2010-07-26 10:54             ` William Kenworthy
2010-07-26 11:02               ` Mick
2010-07-26 14:11                 ` Peter Humphrey
2010-07-26 15:13                   ` Mick
2010-07-26 16:44                     ` Peter Humphrey
2010-07-26 18:04                       ` Alex Schuster
2010-07-26 20:46                         ` Mick
2010-07-26 23:56                           ` Peter Humphrey
2010-07-26 14:16               ` Dale
2010-07-24 20:25 ` Alan McKinnon
2010-07-24 21:46   ` James Wall
2010-07-25  5:12     ` KH

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=201007250949.17739.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@konstantinhansen.de \
    --cc=gentoo-user@lists.gentoo.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