Linux-admin Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Taylor <scott@dctchambers.com>
To: linux-admin@vger.kernel.org
Subject: Re: Bad Blocks
Date: Thu, 19 Sep 2002 08:03:01 -0700	[thread overview]
Message-ID: <5.1.1.6.0.20020919080033.00af4f98@mustang> (raw)
In-Reply-To: <F8500ECEBD66D211A3D20008C724A29C01CEFD9D@SR-EDM-EXCH4.edm. ab.ec.gc.ca>

At 07:48 AM 19/09/2002, Abiy,Mike [Edm] wrote:
>I would like to apologize, first, if this happens to be a simple question.
>
>1. How does one test for bad blocks on a hard drive in linux.
>
>2. More important, how does one render a bad block on hard drive unreadable,
>so that the bad block utility that was used( whatever it may be)  and/or
>program does not try to write or read to this same bad block, resulting in
>the same errors happening again and again.
>
>3. This was necessitated by trips to a remote site from remote power bootup
>( sometime it is absolutely necessary to do that) to do a manual fsck,
>because the linux box stops the normal bootup process awaiting manual
>intervention to do manual fsck.
>
>any information on this topic would be greatly appreciated.

Hello Michael,

That could depend on your hardware and file system.  Probably a good idea 
to read 'man fsck'


       reply	other threads:[~2002-09-19 15:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F8500ECEBD66D211A3D20008C724A29C01CEFD9D@SR-EDM-EXCH4.edm. ab.ec.gc.ca>
2002-09-19 15:03 ` Scott Taylor [this message]
2002-09-24  7:54 Bad Blocks Aleksander Kujbida
  -- strict thread matches above, loose matches on Subject: below --
2002-09-24  4:14 Aleksander Kujbida
2002-09-24  4:54 ` Glynn Clements
2002-09-23 14:17 Abiy,Mike [Edm]
2002-09-23 20:33 ` Glynn Clements
2002-09-19 14:48 Abiy,Mike [Edm]
2002-09-19 15:23 ` Jorge R . Csapo

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=5.1.1.6.0.20020919080033.00af4f98@mustang \
    --to=scott@dctchambers.com \
    --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