HDC errors

[Nicholas Marsh]

Why does fedora give a seek error on my system durring every boot.

hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04
hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdd: drive_cmd: error=0x04Aborted Command

nick marsh
[e-mail]

[Robert L Cochran]

I get the same messages on my Sony Vaio PCG-F350. I disabled the 
graphical boot so I could see the kernel messages. Got to see them with 
a test release. So much for graphical booting...

Bob

Nick Marsh wrote:
> Why does fedora give a seek error on my system durring every boot.
>
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04
> hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdd: drive_cmd: error=0x04Aborted Command
>
> nick marsh
> [e-mail]
>
> --
> fedora-test-list mailing list
> [e-mail]
> http://www.redhat.com/mailman/listinfo/fedora-test-list

[ByteEnable]

On Sun, 2003-09-28 at 20:29, Robert L Cochran wrote:
> I get the same messages on my Sony Vaio PCG-F350. I disabled the 
> graphical boot so I could see the kernel messages. Got to see them with 
> a test release. So much for graphical booting...
>
> Bob
>
> Nick Marsh wrote:
> > Why does fedora give a seek error on my system durring every boot.
> >
> > hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > hdc: drive_cmd: error=0x04
> > hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > hdd: drive_cmd: error=0x04Aborted Command
> >
> > nick marsh
> > [e-mail]

This means that the IDE driver had problems communicating with the IDE
controller.  Probably CRC error's (bad cable, bad hardware).  I'm
guessing that it probably starts out in DMA mode, then gets these errors
and reverts to PIO mode, thats why it goes away.  Do a hdparm -i
/dev/hdc and see what mode you are running in.

Byte

[Jamie Guinan]

On Sun, 28 Sep 2003, Robert L Cochran wrote:
> I get the same messages on my Sony Vaio PCG-F350. I disabled the 
> graphical boot so I could see the kernel messages. Got to see them with 
> a test release. So much for graphical booting...

That's your memory-stick slot, it looks like an IDE drive to the
system, but only works if there's a stick present.   Its safe to ignore, 
and you can later pop in a stick and mount it.  Alternative is to boot 
with "hdc=none" (IIRC), but then you don't get to mount a memstick.

-Jamie
> Bob
>
> Nick Marsh wrote:
> > Why does fedora give a seek error on my system durring every boot.
> >
> > hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > hdc: drive_cmd: error=0x04
> > hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > hdd: drive_cmd: error=0x04Aborted Command
> >
> > nick marsh
> > [e-mail]
> >
> > --
> > fedora-test-list mailing list
> > [e-mail]
> > http://www.redhat.com/mailman/listinfo/fedora-test-list

[Dax Kelson]

On Sun, 2003-09-28 at 18:20, Nick Marsh wrote:
> Why does fedora give a seek error on my system durring every boot.
>
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04
> hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdd: drive_cmd: error=0x04Aborted Command

This is the smartd daemon (started at boot time) checking your CDROM
drive's S.M.A.R.T. status.

S.M.A.R.T. only applies to hard drives, hence the (annoying) error
message.

The culprit is the "DEVICESCAN" in your /etc/smartd.conf file.

You can't simply remove it though, since then the other example lines
will be used.

My solution (since I only have one IDE hard disk) is to modify my
/etc/smartd.conf file to *only* have the following two lines:

# First (primary) ATA/IDE hard disk.  Monitor all attributes
/dev/hda -a -m [e-mail]

I'm CCing those those well intentioned people who responded to your
message as well so they will know the true cause of this.

Dax Kelson
Guru Labs

[ByteEnable]

On Mon, 2003-09-29 at 01:06, Dax Kelson wrote:
> On Sun, 2003-09-28 at 18:20, Nick Marsh wrote:
> > Why does fedora give a seek error on my system durring every boot.
> >
> > hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > hdc: drive_cmd: error=0x04
> > hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > hdd: drive_cmd: error=0x04Aborted Command
>
> This is the smartd daemon (started at boot time) checking your CDROM
> drive's S.M.A.R.T. status.
>
> S.M.A.R.T. only applies to hard drives, hence the (annoying) error
> message.
>
> The culprit is the "DEVICESCAN" in your /etc/smartd.conf file.
>
> You can't simply remove it though, since then the other example lines
> will be used.
>
> My solution (since I only have one IDE hard disk) is to modify my
> /etc/smartd.conf file to *only* have the following two lines:
>
> # First (primary) ATA/IDE hard disk.  Monitor all attributes
> /dev/hda -a -m [e-mail]
>
> I'm CCing those those well intentioned people who responded to your
> message as well so they will know the true cause of this.
>
> Dax Kelson
> Guru Labs

Well,  I do not get those errors on my system.

Byte

[joe]

Dax Kelson wrote:
> My solution (since I only have one IDE hard disk) is to modify my
> /etc/smartd.conf file to *only* have the following two lines:
>
> # First (primary) ATA/IDE hard disk.  Monitor all attributes
> /dev/hda -a -m [e-mail]
>
> I'm CCing those those well intentioned people who responded to your
> message as well so they will know the true cause of this.

Thanks Dax, that's a useful tip -

Joe

[Kevin McConnell]

--- Dax Kelson  wrote:
> I'm CCing those those well intentioned people who
> responded to your
> message as well so they will know the true cause of
> this.

Funny how 3 people give 3 different answers, isn't it?

=====
Kevin C. McConnell --RHCE # 805299480800193 since July 2, 1999-- <Red Hat Certified Engineer>
Freedom in software, now freedom in life.
http://www.freestateproject.org/

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

[Robert L Cochran]

Yep. it's funny!

Bob

Kevin McConnell wrote:
> --- Dax Kelson  wrote:
> > I'm CCing those those well intentioned people who
> > responded to your
> > message as well so they will know the true cause of
> > this.
>
> Funny how 3 people give 3 different answers, isn't it?
>
> =====
> Kevin C. McConnell --RHCE # 805299480800193 since July 2, 1999-- <Red Hat Certified Engineer>
> Freedom in software, now freedom in life.
> http://www.freestateproject.org/
>
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
>
> --
> fedora-test-list mailing list
> [e-mail]
> http://www.redhat.com/mailman/listinfo/fedora-test-list

[Christoph Wickert]

> Kevin McConnell wrote:
> > Funny how 3 people give 3 different answers, isn't it?

Ok, here is the 4th: Depends on your Kernelconfig
> > CONFIG_IDEDISK_MULTI_MODE:
> > If you get this error, try to say Y
> > here:
> >
> > hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> > hda: set_multmode: error=0x04 { DriveStatusError }
> >
> > If in doubt, say N.

There ist also another thead about this called "Re: Anyone seeing data
corruption like bz#91932"

Christoph

[Kevin McConnell]

--- Christoph Wickert 
wrote:
> Ok, here is the 4th: Depends on your Kernelconfig
> > > CONFIG_IDEDISK_MULTI_MODE:
> > > If you get this error, try to say Y
> > > here:

Yep... even better. I used to have an old seagate HD
that was succeptible to that and that patch was the
only thing that saved it.
> There ist also another thead about this called "Re:
> Anyone seeing data
> corruption like bz#91932"

That's great.... I only hope that the original bug
filer isn't filing this bug over an error that's
occurring because of smartd running into a cdrom. That
would be irony, wouldn't it?

=====
Kevin C. McConnell --RHCE # 805299480800193 since July 2, 1999-- <Red Hat Certified Engineer>
Freedom in software, now freedom in life.
http://www.freestateproject.org/

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com