From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Taylor Subject: Re: Bad Blocks Date: Thu, 19 Sep 2002 08:03:01 -0700 Sender: linux-admin-owner@vger.kernel.org Message-ID: <5.1.1.6.0.20020919080033.00af4f98@mustang> References: Mime-Version: 1.0 Return-path: In-Reply-To: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" Content-Transfer-Encoding: 7bit To: linux-admin@vger.kernel.org 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'