On Sun, 19 Mar 2000, you wrote:
> I managed to get one of those blocking errors again and I performed a mk2fs to fix
>it. However, all my data is gone from that
> drive. Is there a program or a way to recover any data that might still be on there?
>
> Seve
mke2fs would likely make any data quite unrecoverable. There is a procedure
for recovering deleted files which sometimes works, but your partition is truly
gone south.
Next time you receive a blocking error, do this
e2fsck -b 8193 -c /dev/xyz
where xyz xould be hda3, sdb7, or whichever partition you are having trouble
with Also the 8193 can be 1+8192*n for any n that is within the area of the
partition so 16385, or 24577 might work -- the -c is to check for bad blocks,
so have some tea or coffee or fruit juice and a short novel available while the
check completes.
If this blocking error is occurring frequently....
1. Make sure you are shutting down properly.... I am sure you are.
2. SERIOUSLY consider a new drive. Or a new motherboard with a better
controller for the drive.
If your Drive is Western Digital IDE.... Well, my case is made. WD blows off
the CRC check so the integrity of the data going onto it isn't checked. This
worked under PIO, and sortof works under UDMA/UDMA33, but the timing
requirements for UDMA 3 and 4 along with the fact that many are now using
advanced processor code.... Well, it doesn't work any more. Another drive
that seems to have integrity problems with certain chipsets and advanced
processor code is the large Seagate IDE (8.4G up). These are HARDWARE PROBLEMS
that are revealed or exacerbated by 586 and 686 code.
Civileme
