On Fri, Jan 15, 1999 at 09:22:37AM -0700, Scott J. Geertgens wrote: > > I recently posted a message about GCC not being able to compile due to > dma_intr and/or read_intr errors. After receiving a response here and > scouring the net I've realized that the problem lies on the drive itself > (bad blocks or similar).
If your drive has bad blocks, and if it has warranty, you may want to return it. Contact your local dealer or vendor. > My question is how do I go about fixing the problem? Will a forced fsck > (fsck.ext2 -f /dev/hdb3) be sufficient? You need to add the "-c" option, see the man page. > I know that when Debian installs, > it gives the option to scan for and mark bad sections of the disk... will > I need to reinstall to insure that no files are sitting on corrupt > sections of the disk? (Re-installing is an option for me). Scanning for bad blocks is very likely corruptive. You should notice how much bad blocks you have, and what files are affected. Run the program twice. If it does find bad blocks on more and more locations, you better go an buy a new drive. > Or is there > anyway to 'recover' the data from those bad block and fix everything > without going to such extemes? Thanks. Not that I know of. Bad blocks are just that, bad. Marcus -- "Rhubarb is no Egyptian god." Debian GNU/Linux finger brinkmd@ Marcus Brinkmann http://www.debian.org master.debian.org [EMAIL PROTECTED] for public PGP Key http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09
