nasty looking problem on arch64

barry · 2008-09-13 10:17:24

Hi,

I've been recieving the following message over and over in my messages file since last night;

Sep 13 11:12:04 cumberdale ata4: EH complete

After first recieving it I restarted my machine and found that the slash partition was totally corrupted. I've rebuilt now and the error has just reappeared, has anyone seen this before?

Thanks,

Barry

jacko · 2008-09-13 10:53:40

I've rebuilt now and the error has just reappeared, has anyone seen this before?

so you've reinstalled and your still getting the error, is that your point? If that's the case then it surely isn't an arch64 error, much more like a hwd failure.

your not really making to much sense to me. Maybe you could explain your problem a little more in detail? Like where the error is being reported, slash partition? what about it? what fs type is it using? etc...

barry · 2008-09-13 11:00:11

jacko wrote:

I've rebuilt now and the error has just reappeared, has anyone seen this before?
so you've reinstalled and your still getting the error, is that your point? If that's the case then it surely isn't an arch64 error, much more like a hwd failure.
your not really making to much sense to me. Maybe you could explain your problem a little more in detail? Like where the error is being reported, slash partition? what about it? what fs type is it using? etc...

Sorry, just woke up. Never make too much sense in the morning

Last night after noticing the error and rebooting, my ext3 filesystem on the partition that holds / everything was corrupted, I could run some binaries but others couldn't be found. (My /home & /boot are on different partitions and they are fine). One thing I noticed was that on my fallback kernel everything worked perfectly.

The error is being reported in /var/log/messages.log and apart from that error I haven't found anything else relating to it except that my machine isn't performing as well as it usually does. I'm afraid to reboot just now as I suspect things will go haywire again.

barry · 2008-09-13 11:01:21

I should also add that the error is being written to /var/log/messages.log every 2 seconds.

barry · 2008-09-13 11:15:57

Looking over the logs from last night it seems that the machine was fine between 20:30 and 21:37. At 21:35 I upgraded to the latest kernel, rebooted and the error started.

Is there anyway to rollback my kernel version to test this theory?

Allan · 2008-09-13 11:18:20

If you haven't cleared you pacman cache in a while you can downgrade by using

pacman -U /var/cache/pacman/pkg/kernel26-2.6.26.3-1-x86_64.pkg.tar.gz

barry · 2008-09-13 11:22:18

Allan wrote:

If you haven't cleared you pacman cache in a while you can downgrade by using
pacman -U /var/cache/pacman/pkg/kernel26-2.6.26.3-1-x86_64.pkg.tar.gz

Sadly I wiped out the pacman cache after rebuilding

jacko · 2008-09-18 00:26:42

you can always build outdated packages using the arch svn repository.

Arch Linux

#1 2008-09-13 10:17:24

nasty looking problem on arch64

#2 2008-09-13 10:53:40

Re: nasty looking problem on arch64

#3 2008-09-13 11:00:11

Re: nasty looking problem on arch64

#4 2008-09-13 11:01:21

Re: nasty looking problem on arch64

#5 2008-09-13 11:15:57

Re: nasty looking problem on arch64

#6 2008-09-13 11:18:20

Re: nasty looking problem on arch64

#7 2008-09-13 11:22:18

Re: nasty looking problem on arch64

#8 2008-09-18 00:26:42

Re: nasty looking problem on arch64

Board footer