Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Error reading block x (Attempt to read block...) (fwd)

 On Wed, Mar 05, 2008 at 07:35:32AM -0500, Scott R. Ehrlich wrote: 
> >As long as you're always going to say "Y", just manually run "fsck 
> >-y". 
> I haven't run fsck in a few years, and never on a current RedHat-based 
> distro, in this case, CentOS 5.   After the Error Reading/Force Rewrite 
> prompts, what other questions might I be asked, to know if automatic yes 
> responses are safe, or if I need to continue a manual check. 

Unless you're a file system hacker, pretty much the only answer you 
should ever give to fsck's questions is yes.  Jerry is right though, 
your disk is failing.  Once the fsck is completed, back up everything 
you can, and replace the disk.  Modern disks have a huge percentage of 
the disk surface reserved for bad block replacement (called the spare 
block pool), and the fact that you're seeing bad blocks almost 
certainly means that the spare block pool is exhausted, meaning your 
disk has TONS of bad blocks.  It's only going to get worse... 

Derek D. Martin   GPG Key ID: 0xDFBEAD02 
This message is posted from an invalid address.  Replying to it will result in 
undeliverable mail due to spam prevention.  Sorry for the inconvenience. 

Discuss mailing list 
[hidden email]

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /