Hi Dan,
My recovery goes rather well...
Does the badblocks count or anything ? With me it counted.
You have to write the bad block no's to a file and feed that to the
reiserfschk.
I didn't completed a full badblock check coz I knew the badblocks could
only be at the beginning of the lvm 'array', but I excpect it to take as
long as a reiserfsck --tree-rebuild.
If you don't see anything counting -- start worrying.
Good luck to you to.
I have still 18 hours to go... I realy hope I can mount the dam thing
after that and then I can start looking for the bad disk.
And I'm not using any type of raid for that data.
kind regardes,
Matthias.
Dan Oglesby wrote:
Matthias Barremaecker wrote:
Hi,
Thanx for your reply.
The data is not THAT importend, all our importend data is backuped 4
times, inc. original (well, 3 times now, since the 1300gig machine is
broke).
I did a bit furtur reasearch and maybe this is something to think
about if you use reiserfs :
I did a bad block check and I have 10 bad blocks of 4096bytes on
1300Gig and ... that is the reason reiserfs will not work anymore.
I guess this sux. I rather have that the data on the bad blocks is
just corupted but the rest is accesseble.
I'm doing a --rebuild-tree with the bad block list. Hopes this works.
Aren't there any tools to substract data from a broken reiserfs
partition ?
kind regardes,
Matthias.
I'm currently in a similar situation: 1TB (RAID-5) ReiserFS filesystem
running on RedHat 7.2 with a Promise SX6000 controller. Everything was
running stock version/firmware/BIOS, and it suddently developed 39 bad
blocks after a power outage.
reiserfsck --rebuild-tree (version 3.6.4, the latest for RH 7.2) failed
to complete after the controller kept hard locking/crashing.
So, I've compiled a plain 2.4.30 kernel (from kernel.org, not RedHat),
updated the BIOS/Firmware on the SX6000, and compiled and installed the
latest reiserfsprogs (3.6.19, I believe?), and have been running
badblocks (non-destructive) for the last four days. Nothing has turned
up so far.
I'm hoping the next time I run a --rebuild-tree, it will be able to
complete. I really do need to get the data off of this filesystem.
Good luck with your recovery.
--Dan
[EMAIL PROTECTED] wrote:
On Sun, 29 May 2005 21:25:54 +0200, Matthias Barremaecker said:
but that sais it is a fysical drive error
Physical drive errors. Your hardware is broken. Isn't much that
Reiserfs
can do about it.
What can I do.
1) Call whoever you get hardware support from.
2) Be ready to restore from backups.
3) If you didn't have RAID-5 (or similar) set up, or a good backup,
consider
it a learning experience.
If your data is important enough that you'll care if you lose it, you
should take
steps to make sure you won't lose it... It's that simple.
(Just for the record, if we have important info, it gets at least
RAID5, a
backup to tape or other device, *and* a *second* backup off-site.
And my shop
is far from the most paranoid about such things.)
--
Matthias Barremaecker, MH.BE - Arta nv
0495 30 31 72
http://mh.be/
SERVER HOUSING per 1HE € 50 per maand
20Gig traffic, 100Mbit netwerk
Center te Antwerpen.
