Hi Anders, this HD is OK, I can read all other directories, only the specific one is bad, which is my home, unfortunately... It seems as if the kernel crashed when the was writing something important... vok On Monday 03 May 2004 09:57, Anders Johansson wrote:

On Monday 03 May 2004 09.44, Volker Krueger wrote:

...

Dear all

deutsche uebersetzung unten...

Please don't cross post. If you want to send to two lists, send two mail

...

recently, my kernel crashed. After booting up, I was not able to access my filesystem anymore:

/bin/ls: reading directory .:Input/output error

Ouch, that looks suspiciously like a dead hard drive. I don't think that error would arise from a mere corrupted file system.

If you're lucky, you may be able to find some diagnostic tool like SeaTools from Seagate, hutils from Samsung or some other, depending on the make of your drive, that can fix it.

Hi Anders, yes, this is of course correct: It may be a bad block. However, the correlation between the crash, which was due to experimenting with a Firewire camera (it had already happened a number of times!) with the final crash of the home is also apparent... But whatever it may be, there are a number of error messages in /var/log/messaged: first *a lot* of boot-up messages, also from the previous crashes about missing inodes is_tree_node: node level 0 does not match to the expected on 1 vs-5150: search_by_key: invalied format found in block 598507. Fsck? They are always the same and they are repeated quite often. after the fist number of crashes, the home was always readable again, but the last one finally did it... Any idea if an fscheck could do the job? Any hints for senseful parameters? thanks in advance, best, vok On Monday 03 May 2004 10:06, Anders Johansson wrote:

On Monday 03 May 2004 09.59, Volker Krueger wrote:

...

Hi Anders,

this HD is OK, I can read all other directories, only the specific one is bad, which is my home, unfortunately...

It seems as if the kernel crashed when the was writing something important...

Considering the error, I'm prepared to put money on bad blocks on the drive.

My advise is still to find some diagnostic utility suitable for the particular make of drive you have, and run it. I'm pretty sure it will tell you what's happened, and - if you're lucky - fix it.

If you can read /var/log/messages on that system, I think you'll find a lot of error messages relating to the I/O error as well

Hi Anders, I really apprechiate your help!!!! I have tried reiserfsck --fix-fixable which then suggested to run reiserfsck --rebuild-tree what I am doing now. It looks as if it will take about an hour... :-) I'll send a message, if that helped. best, vok On Monday 03 May 2004 10:27, Anders Johansson wrote:

On Monday 03 May 2004 10.17, Volker Krueger wrote:

...

Hi Anders,

yes, this is of course correct: It may be a bad block. However, the correlation between the crash, which was due to experimenting with a Firewire camera (it had already happened a number of times!) with the final crash of the home is also apparent...

But whatever it may be, there are a number of error messages in /var/log/messaged:

first *a lot* of boot-up messages, also from the previous crashes about missing inodes

is_tree_node: node level 0 does not match to the expected on 1 vs-5150: search_by_key: invalied format found in block 598507. Fsck?

They are always the same and they are repeated quite often.

after the fist number of crashes, the home was always readable again, but the last one finally did it...

Any idea if an fscheck could do the job? Any hints for senseful parameters?

Well, the problem is that with errors like that, the partition wouldn't be mounted, as the system will refuse to mount a partition with file system errors. If the partition isn't mounted, then the I/O error is coming from the root partition, not /home.

You can try reiserfsck with something like --fix-fixable or --rebuild-tree, those may fix the partition errors, but I really doubt that that is related to the I/O error. The only times I've seen I/O errors like that is when the disk has in some way been physically bad