SEO

I get this error when booting. While it goes on to boot after the ide0
reset, I want to know what it means and if it is anything serious?

Partition check:
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
p6hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
p7 p8 >
/dev/ide/host0/bus0/target1/lun0:hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
blk: queue c01c9644, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c01c9794, I/O limit 4095Mb (mask 0xffffffff)
ide0: reset: success

androtech wrote:
> I get this error when booting. While it goes on to boot after the ide0
> reset, I want to know what it means and if it is anything serious?

<snipped errors>

It means the HD is encountering lots of CRC (read) errors.

As for serious - could be that it's dying, yes.
That's actually the most likely scenario.

Run a HD test proggie on it (which will stress it even more), but FIRST
be sure to backup anything and everything that's important!

Also, if the drive has SMART, emerge "smartmontools" and check the
values - it can tell you the exact number of errors the drive has
encountered, and how often these have occurred.

On Thu, 15 Jan 2004 20:54:04 +0500, androtech wrote:

> I get this error when booting. While it goes on to boot after the ide0
> reset, I want to know what it means and if it is anything serious?
>
> Partition check:
> /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5hda: dma_intr: status=0x51 {
> DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC } hda: dma_intr:
> status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 {
> DriveStatusError BadCRC }
==snip==

What it means is that your system is not properly supporting the dma level
gentoo is trying to boot with. For example, I used to have the same
problem on my system when booting due to incomplete support for dma100 but
since I restricted the drive to a maximum of dma66 I've solved the
problem.

The problem can be caused by a dma66 cable when the system is trying to
set to dma100, or it's especially bad if you've got a second disk as slave
and they are not the same brand. I've seen the same problem with a dma66
maxtor connected as slave to a dma100 IBM and the same thing when I had an
internal iomega zip drive connected to the ibm drive.

maybe you can try the kernel parameter ide=nodma

"androtech" <removethis@thistoo.com> a écrit dans le message de
newsan.2004.01.15.15.54.02.127657@thistoo.com...
> I get this error when booting. While it goes on to boot after the ide0
> reset, I want to know what it means and if it is anything serious?
>
> Partition check:
> /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> p6hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> p7 p8 >
> /dev/ide/host0/bus0/target1/lun0:hdb: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
> hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
> blk: queue c01c9644, I/O limit 4095Mb (mask 0xffffffff)
> blk: queue c01c9794, I/O limit 4095Mb (mask 0xffffffff)
> ide0: reset: success
>

> > I get this error when booting. While it goes on to boot after the ide0
> > reset, I want to know what it means and if it is anything serious?
>
> <snipped errors>
>
> It means the HD is encountering lots of CRC (read) errors.
>
> As for serious - could be that it's dying, yes.
> That's actually the most likely scenario.
>
> Run a HD test proggie on it (which will stress it even more), but FIRST
> be sure to backup anything and everything that's important!
>
> Also, if the drive has SMART, emerge "smartmontools" and check the
> values - it can tell you the exact number of errors the drive has
> encountered, and how often these have occurred.

This is good advice. And check your IDE cables. CRC errors are often
due to bad or mis-seated cables.