linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Gelin <patrick.gelin@free.fr>
To: linux-admin@vger.kernel.org
Subject: Badblocs too long...
Date: Tue, 20 Jan 2004 22:10:25 +0100	[thread overview]
Message-ID: <buk55j$j4n$1@sea.gmane.org> (raw)

Hi,

I suspect bad blocs in my Hard disk, so I try the commande:

e2fsck -c /dev/hdb1 (hdb1 not mounted)

it calls badblocks, but it's very very long... after half a day I've checked
only 1/10 of my hard disk (IDE - 20 Go)

1. Is it normal? 

2. Can I do something else? 

Thanks.
-- 
Patrick GELIN
rue du Beau-Site, 3
CH-2300 La Chaux-de-Fonds
Tel: +41 (0)32 / 913 41 48
Email: patrick.gelin@free.fr


             reply	other threads:[~2004-01-20 21:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20 21:10 Patrick Gelin [this message]
2004-01-21  1:35 ` Badblocs too long Axel Siebenwirth
2004-01-21 17:18   ` Patrick Gelin
2004-01-21  1:48 ` chuck gelm net
2004-01-21 17:15   ` Patrick Gelin
2004-01-22 21:24     ` chuck
  -- strict thread matches above, loose matches on Subject: below --
2004-01-21 17:34 Carrión Byron
2004-01-21 18:16 ` Patrick Gelin

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='buk55j$j4n$1@sea.gmane.org' \
    --to=patrick.gelin@free.fr \
    --cc=linux-admin@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).