From: Gerrit Hannaert <degerrit@web.de>
To: Preston Lord <webmaster@t2.net>, reiserfs-list@namesys.com
Subject: Re: Bad Blocks?
Date: Wed, 2 Jan 2002 08:42:34 +0100 [thread overview]
Message-ID: <200201020842.58067.degerrit@web.de> (raw)
In-Reply-To: <1035999303.1204.31.camel@preston>
-----BEGIN PGP SIGNED MESSAGE-----
Often hard drive manufacturers provide utilities to check their disks and
remap bad blocks, I was able to get rid of mine using Maxtor's Powermax or
something. After that you can reiserfsck --rebuild-tree and you should end up
with a mountable fs.
However, you should see this as a temporary measure (to mount your fs, and
make a good backup) - in my experience with this one disk, more bad blocks
keep appearing after a while. (Against my own advice, I'm still using my
disk, though)
Also see http://namesys.com/bad-block-handling.html
Cheers,
- - Gerrit
On Wednesday 30 October 2002 18:35, Preston Lord wrote:
> I am running the latest reiserfsprogs 3.6.4
>
> I came home last week to find my Linux pc was locked up. After rebooting
> the root partition would not mount. All other partitions are fine. I
> have the failed hard drive in another linux pc now and am trying to
> recover the data from the failed partition. When I run
>
> reiserfsck --check /dev/hda5
>
> I get this:
>
> The problem has occurred looks like a hardware problem.
> Check your hard drive for badblocks.
>
> bread: Cannot read the block (16).
>
>
> how can I fix this bad block?
>
> Linux Kernel 2.4.18
>
> Thanks
>
> Preston
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iQCVAwUBPDK59wtVJ+MDouLxAQGS1QP/WuEvM/TwRkHbtueD6P6usviVhMQu7RnE
mfT1fSzpb0cyVOmStIRp1c8KNLhaaZRJs747ZtJjPXJV5lqO7N4cJ8sVa2hm/PwY
uBrFdEA/6cQaWBu2Kt9H3CPOhrrJYWwYXHow3qaYJUhhmAVWphNQEALEQU15A5iG
LPwM7Z3HQpk=
=VqVJ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-01-02 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 17:35 Bad Blocks? Preston Lord
2002-01-02 7:42 ` Gerrit Hannaert [this message]
2002-10-30 22:22 ` Anders Widman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200201020842.58067.degerrit@web.de \
--to=degerrit@web.de \
--cc=reiserfs-list@namesys.com \
--cc=webmaster@t2.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.