Re: bad blocks in under 2.5 years! So much for HP ...
From: Ben Myers (_at_)
Date: 11/03/05
- Next message: Dances With Crows: "Re: psaux port and 2.6 kernels - Mouse doesn't work?"
- Previous message: Jean-David Beyer: "Re: bad blocks in under 2.5 years! So much for HP ..."
- In reply to: milkyway: "bad blocks in under 2.5 years! So much for HP ..."
- Next in thread: ray: "Re: bad blocks in under 2.5 years! So much for HP ..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 03 Nov 2005 14:31:31 GMT
Regardless of the make of drive or the operating system in use, bad blocks are a
symptom of a failing drive, so replace the drive.
Whether a Linux utility, or Windows sucky scandisk, or a mnufacturer's
diagnostic utility, bad blocks are NEVER repaired. The best that can be done is
to scavenge the data from the bad block as best as possible (potentially with
dropped bits), then assign the block number to a spare block, copying the
scavenged data to the replacement block.
I'll leave it to Suse experts to suggest how to back up any important data from
the failing drive, should you need to do so.
What brand of drive is it, anyway? I'm still trying to figure out which make of
notebook drive has respectable reliability, which seems to be sliding downhill
everyday... Ben Myers
On 2 Nov 2005 23:12:01 -0800, "milkyway" <d0mufasa@hotmail.com> wrote:
>Hello,
>
>I have a Suse Linux system. I have had a HP Pavilion laptop (zv5000)
>for a little more than 2 years and the hard drive appears to be faulty
>- after only 2 years ;-/
>
> I have been able to run the Suse Rescue program to get some kind of OS
>up and going:
>
> Linux Rescue 2.6.4-52 .. i686 i686 i386 GNU/Linux
>
>I get the following error:
>
> reiserfs_read_locked_inode: i/o failure occurred trying to find
>stat
>
>which is exactly like the problem stated in this thread:
>
>http://groups.google.com/group/alt.os.linux.suse/browse_frm/thread/fac1040564d7c1cf/0a0c77087bd58d65?lnk=st&q=reiserfs_read_locked_inode&rnum=5#0a0c77087bd58d65
>
>The advice I have been seeing online specifies to get a list of bad
>blocks and then running a command upon them (the bad blocks) as
>specified on this page:
>
>http://www.namesys.com/bad-block-handling.html
>
>**My problem: I do not know how to get the outuput of the list of
>"badblocks" to a file.
>
>**My question is: Is there some way to repair the blocks by using just
>*one* command on the entiere hard disk system? In otherwords, can I do:
>
> command_name /dev/hda
>
>and then have *all* the bad blocks repaired?
>
>-OR-
>
>is there a way to get this list to a file?
>
>-OR-
>
>Is there another way to address this problem?
>
>I am soooo disappointed with this laptop. I have another laptop from
>Compaq (a 1700) that is *much* older and I never had any problems
>whereas with this HP, it goes out a little after 2 years.
>
>TIA
>
- Next message: Dances With Crows: "Re: psaux port and 2.6 kernels - Mouse doesn't work?"
- Previous message: Jean-David Beyer: "Re: bad blocks in under 2.5 years! So much for HP ..."
- In reply to: milkyway: "bad blocks in under 2.5 years! So much for HP ..."
- Next in thread: ray: "Re: bad blocks in under 2.5 years! So much for HP ..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
