My Machine is tripping...

[stogma]

Hi all,

I have got a machine, obvious really isn't it, which is a relatively good one, every now and again it just crashes itself and then won't boot until you issue a "e2fsck /dev/sdb2" check....this leads me to believe that sdb2 has got errors on it, but, the error mesgs are pretty encrypted and it doesn't tell me what went wrong?

Is there anywhere I can look to tell me what happened or anyway I can repair this drive?

It usually goes down every 6 or so days and it is remotely stored so to get it rebooted and re-checked it is starting to cost me a buckload of £££.

cheers in advance, James.


------------------
A closed mouth gathers no feet.

[pbharris]

hello,
are the messages like 'inode missing -fixed' ?
Is there anything running in cron which could be causing this?

------------------
I don't use Linux because I hate Windows (which I do) I use Linux because I like it.
pbharris_359@yahoo.com

[idealego]

It could be a bad cable to your hard drive.

Has it always done this? Or was there a certain point where it started?

[stogma]

It hasn't started from day one which is why I don't think it is a cable error. I have scanned the /var/log/messages file and the only problem that arises on boot up is: Nov 19 14:29:47 mail kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended

So I am beat, the only way I can find the errors is to wait until it falls over again but I am getting pistol whipped in a big way each time it goes down from my boss.

In my /etc directory i have got:
cron.d
cron.daily
cron.hourly
cron.monthly
cron.weekly
crontab

which one should I look in?

cheers guys!