From: James Wall <wallservices@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Date: Sat, 24 Jul 2010 16:46:18 -0500 [thread overview]
Message-ID: <4C4B5F2A.6000208@gmail.com> (raw)
In-Reply-To: <201007242225.30909.alan.mckinnon@gmail.com>
On 7/24/2010 3:25 PM, Alan McKinnon wrote:
> On Saturday 24 July 2010 21:57:38 KH wrote:
>> Hi there,
>>
>> my server was running strait for 8 month now. I did updates regularly
>> but still used an 2.6.2x kernel. Never switched it of. Now someone from
>> houskeeping pulled the plug for the vacuum cleaner ...
>>
>> Anyway the box won't boot anymore. grub starts up. Kernel boots. Then
>> there is checking root file system (or something like that).The message
>> is that my ext2 file system can not be read. That I might want to try
>> the alternativ superblock by running #e2fsck -b 8193<device>
>>
>> Well, I put the hdd in an external usb and conected it to my
>> workstation. As I thought hda3 (is /dev/sde3) is an ext3 filesystem.
>> Also badblocks and e2fsck did not show any problem with the hdd.
>>
>> /etc/fstab is corect (i hope), too.
>>
>> What am I missing? How can I get the server running, again?
>
> 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
>
>
>
Run e2fsck -f /dev/hda3 to force check a partition. I have had to do
that when my kids yanked all the drives out of a server that I was
setting up. :-)
--
No trees were harmed in the sending of this message. However, a large
number of electrons were terribly inconvenienced.
next prev parent reply other threads:[~2010-07-24 22:03 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
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 [this message]
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=4C4B5F2A.6000208@gmail.com \
--to=wallservices@gmail.com \
--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