[CentOS] Kernel Errors Present

Mon Jan 17 13:11:18 UTC 2011
Keith Roberts <keith at karsites.net>

On Mon, 17 Jan 2011, Shade.GE wrote:

> To: CentOS mailing list <centos at centos.org>
> From: Shade.GE <shade.ge at gmail.com>
> Subject: Re: [CentOS] Kernel Errors Present
> 
> Same Problem here, the harddrive (2.5" Samsung HM121HC) running with
> Kernel 2.6.18-194.32.1.el5 (x86_64) produces errors on high load.
> With one step back kernel the errors are gone. Im already changed the
> harddrive with a new one, same errors on the newest kernel.
>
> dmesg output:
>
> hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> ide: failed opcode was: unknown
> hdc: drive not ready for command
> attempt to access beyond end of device
> hdc3: rw=0, want=25863980832, limit=225841770
> attempt to access beyond end of device
> hdc3: rw=0, want=7830939224, limit=225841770
> attempt to access beyond end of device
> hdc3: rw=0, want=31645262224, limit=225841770
> attempt to access beyond end of device
> hdc3: rw=0, want=25863980832, limit=225841770
> attempt to access beyond end of device
> hdc3: rw=0, want=25863980832, limit=225841770
> hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> ide: failed opcode was: unknown
> hdc: drive not ready for command
>
> There are no errors logged in smart, i already try'd with smartctl -t
> long .... no errors. I also did a blocktest on this drive.
> Next step is to change the cables, but i don't think this would be a
> solution, i think it's a kernel IDE / DMA problem.

Check your BIOS settings are corect, and have you enabled 
LBA for this drive?

You might need to enter the C/H/S values by hand, if these 
are not being detected properly. Is the drive jumpered 
properly?

I have got rid of the errors now from my WD 40GB drive, on 
the latest 32 bit kernel.

Also look in /var/log/messages to see how the kernel 
initialises the drive.

As I mentioned in an earlier post, I now use hdparm from the 
rc.local script to reset my drive to UDMA 2. Please check 
the posts I made last week regarding this.

Please also read the man page for hdparm. You can use that 
to get alot of information about your drive, and it's 
current (U)DMA settings.

EG:

[root at karsites ~]# hdparm /dev/hde

/dev/hde:
  multcount    =  2 (on)
  IO_support   =  3 (32-bit w/sync)
  unmaskirq    =  1 (on)
  using_dma    =  1 (on)
  keepsettings =  0 (off)
  readonly     =  0 (off)
  readahead    = 256 (on)
  geometry     = 65535/16/63, sectors = 78165360, start = 0
[root at karsites ~]#
[root at karsites ~]# hdparm -I /dev/hde

/dev/hde:

ATA device, with non-removable media
         Model Number:       WDC WD400BB-00GFA0
         Serial Number:      WD-WMAKA1241735
         Firmware Revision:  09.01B09
Standards:
         Supported: 5 4 3
         Likely used: 6
Configuration:
         Logical         max     current
         cylinders       16383   16383
         heads           16      16
         sectors/track   63      63
         --
         CHS current addressable sectors:   16514064
         LBA    user addressable sectors:   78165360
         device size with M = 1024*1024:       38166 MBytes
         device size with M = 1000*1000:       40020 MBytes 
(40 GB)
Capabilities:
         LBA, IORDY(can be disabled)
         bytes avail on r/w long: 40
         Standby timer values: spec'd by Standard, with 
device specific minimum
         R/W multiple sector transfer: Max = 16  Current = 2
         Recommended acoustic management value: 128, current 
value: 254
         DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 
udma4 udma5
              Cycle time: min=120ns recommended=120ns
         PIO: pio0 pio1 pio2 pio3 pio4
              Cycle time: no flow control=120ns  IORDY flow 
control=120ns
Commands/features:
         Enabled Supported:
            *    SMART feature set
                 Security Mode feature set
            *    Power Management feature set
            *    Write cache
            *    Look-ahead
            *    Host Protected Area feature set
            *    WRITE_BUFFER command
            *    READ_BUFFER command
            *    DOWNLOAD_MICROCODE
                 SET_MAX security extension
            *    Automatic Acoustic Management feature set
            *    Device Configuration Overlay feature set
            *    SMART error logging
            *    SMART self-test
Security:
                 supported
         not     enabled
         not     locked
         not     frozen
         not     expired: security count
         not     supported: enhanced erase
HW reset results:
         CBLID- below Vih
         Device num = 0 determined by the jumper
Checksum: correct
[root at karsites ~]#

HTH

Keith Roberts

-----------------------------------------------------------------
Websites:
http://www.karsites.net
http://www.php-debuggers.net
http://www.raised-from-the-dead.org.uk

All email addresses are challenge-response protected with
TMDA [http://tmda.net]
-----------------------------------------------------------------