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

["Kristian Erik Hermansen" <user=152@nabble.blu.org>]

 On Wed, Mar 5, 2008 at 9:06 AM, Derek Martin <[hidden email]> wrote: 
>  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... 

Actually, I would have backed up before performing the fdisk.  Doing 
the fdisk operation is destructive.  You lose information that might 
have been helpful to recovery in the future.  Just my two cents.  I 
have hosed a few file systems in weird ways by just naively "fixing" 
the corruption... 
-- 
Kristian Erik Hermansen 
-- 
"It has been just so in all my inventions. The first step is an 
intuition--and comes with a burst, then difficulties arise. This thing 
gives out and then that--'Bugs'--as such little faults and 
difficulties are called--show themselves and months of anxious 
watching, study and labor are requisite before commercial success--or 
failure--is certainly reached" -- Thomas Edison in a letter to 
Theodore Puskas on November 18, 1878 

-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and is 
believed to be clean. 

_______________________________________________ 
Discuss mailing list 
[hidden email] 
http://lists.blu.org/mailman/listinfo/discuss