Hi just a quick addition:
I ran this: desktop lordvan # dd if=/dev/discs/disc2/part6 of=/dev/null bs=8k 1192384+0 records in 1192384+0 records out 1209296+0 records in 1209296+0 records out 1275725+0 records in 1275725+0 records out 1326505+0 records in 1326505+0 records out 1790232+0 records in 1790232+0 records out 2255571+0 records in 2255571+0 records out 2447343+0 records in 2447343+0 records out 6220163+1 records in 6220163+1 records out as you see it produced no errors at all so the HDD can be read fine. any idea what could cause the problem? Thanks, THomas On Fri, 2005-10-14 at 20:08 +0400, Vitaly Fertman wrote: > Hello Thomas! > > On Friday 14 October 2005 19:21, Thomas Raschbacher wrote: > > Hi, > > > > I had to run reiserfsck on my usb hdd because there were some problems. > > It told me to rebuild the tree (because I couldn't mount it I coudlnt' > > backup things and I didn't have enough space (50GB) spare for a disk > > image). > > > > attached my logfiles and (where i remembered to save it the stdout > > output) > > > > It alwasy aborts at the same place. > > > > (i did the same for another partition and there after running reiserfsck > > --rebuild-tree about 10 times it worked out ok but this one seems to be > > a problem ..) > > > > reiserfsck 3.6.19 (2003 www.namesys.com) > > Linux version 2.6.12-gentoo-r6 ([EMAIL PROTECTED]) (gcc version > > 3.4.3-20050110 (Gentoo 3.4.3.20050110-r2, ssp-3.4.3.20050110-0, > > pie-8.7.7)) #1 Thu Jul 21 20:21:20 BST 2005 > > (i can provide kernel config file if needed) > > > > Please let me know if ther'es anything I can do as there's quite a bit > > of data on that drive. > > it is possible to check how reiserfsck works, you can extract > the fs metadata and fsck them on another compter. this does > not require you to have 50M as there are not real data: > debugreiserfs -p /dev/discs/disc2/part6 | bzip2 -c > part6.bz2 > go to another computer: > touch part6.image > bunzip2 -c part6.bz2 | debugreiserfs -u part6.image > reiserfsck --rebuild-tree part6.image -l logfile > > if it finishes successfully, the problem is in your hardware. > As the same block number repeats and there is also a failed > block read, the problem is likely to be IO related. > > it fsck fails on your metadata, I would like to have a look > at part6.bz2. > -- -----BEGIN GEEK CODE BLOCK----- GCS/CC/E/M/MU/S d- s: a--- C++++(++) UL++++ P+ L++++ E W+++ N+++ o-- K w-- O M-- V- PS+ PE-- Y++ PGP+++ t+++ 5+ X- R tv b++++ DI- D+ G++ e-->+++++ h-- !r z- ------END GEEK CODE BLOCK------
signature.asc
Description: This is a digitally signed message part
