Filesystem UncorrectableError for IDE disk on 2.6.26?

2009-06-19 Thread Glyn Astill

Hi chaps,

Just upgraded an etch machine to lenny, and with it I've gone from the 2.6.18-6 
kernel up to 2.6.26-1 kernel.

I'm seeing the following errors under heavy disk activity:

Jun 18 18:08:05 xglyn2 kernel: [14214.048193] ide: failed opcode was: unknown
Jun 18 18:08:11 xglyn2 kernel: [14220.846157] hdc: dma_intr: status=0x51 { 
DriveReady SeekComplete Error }
Jun 18 18:08:11 xglyn2 kernel: [14220.846157] hdc: dma_intr: error=0x40 { 
UncorrectableError }, LBAsect=26482377, sector=26482370


Previous to using 2.6.26-1 I did try 2.6.26-2 (both 686) and that gave me tons 
of these errors upon boot up. I thought going back to the 2.6.26-1 version had 
resolved the issue but it's obviously just less severe.

Anyone seen similar or got any ideas?

btw, the heavy disk activity is loading 80GB postgres database - I've switched 
back to 2.6.18 to try this again but I suspect it'll be fine.

Glyn





--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Filesystem UncorrectableError for IDE disk on 2.6.26?

2009-06-19 Thread Douglas A. Tutty
On Fri, Jun 19, 2009 at 09:11:07AM +, Glyn Astill wrote:
 
 Just upgraded an etch machine to lenny, and with it I've gone from the
 2.6.18-6 kernel up to 2.6.26-1 kernel.
 
 I'm seeing the following errors under heavy disk activity:
 
 Jun 18 18:08:05 xglyn2 kernel: [14214.048193] ide: failed opcode was:
 unknown Jun 18 18:08:11 xglyn2 kernel: [14220.846157] hdc: dma_intr:
 status=0x51 { DriveReady SeekComplete Error } Jun 18 18:08:11 xglyn2
 kernel: [14220.846157] hdc: dma_intr: error=0x40 { UncorrectableError
 }, LBAsect=26482377, sector=26482370
 
 
 Previous to using 2.6.26-1 I did try 2.6.26-2 (both 686) and that gave
 me tons of these errors upon boot up. I thought going back to the
 2.6.26-1 version had resolved the issue but it's obviously just less
 severe.
 
 Anyone seen similar or got any ideas?
 
 btw, the heavy disk activity is loading 80GB postgres database - I've
 switched back to 2.6.18 to try this again but I suspect it'll be fine.

If you get the same errors if you boot again with the 2.6.18 kernel,
then I'd say the disk was dying.  However, if you don't get the errors
with the the old kernel but do with the new, then the new kernel isn't
working with either the disk or the IDE controller.  If the latter,
bummer.  Since I run old hardware, I hate upgrading to a new kernel
because it likely means that more of my hardware has to be migrated away
from linux to one of the BSDs.

Doug.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org