Home > Kernel Hda > Kernel Hda Command Error Status=0x51 Driveready Seekcomplete Error

Kernel Hda Command Error Status=0x51 Driveready Seekcomplete Error

I was right. Is it worth searching for a solution or should I just reinstall FC6 ? If you don't run cpu monitor and/or dont check TOP often, you might never notice this and my guess is whatever is going on is going to bother any realtime process. I mean I can live without my cdrom drives untill this get fixed but I worry about the /var/log/messages getting huge and my brand new hardware ^^. his comment is here

I 've been reading other forums with people with the same problem and they reverted to Kernel 2.6.18. Current Customers and Partners Log in for full access Log In New to Red Hat? However it BURNS fine (audio, data, movie DVDs....) and reads /rips fine as well?>!?>!?! Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community.

However you might want to slow it down (to udma0 as example). Knowledgebase Portal Home Knowledgebase Hard Drives Drive errors in the system log (status=0x51, error=0x04) Categories Backups & Storage 1 Bandwidth 3 Control Panels 4 Database 4 woot!

mchnz6th February 2007, 10:21 AMBad CD in the CDROM drive? wintermute0006th February 2007, 02:14 PMYeah its a real downside to 'nix, using really new hardware often causes grief - I too had to muck around with AHCI settings etc. Posts: 2,163 Rep: Glad to hear that. Is there an easy way to recompile the current kernel from the headers, with the same configuration but including the JMicron modules?

All Rights Reserved. Not sure if this is a kernel issue or a hal daemon issue, but it's repeatable and probably causes other invisible problems. So I did "hda=noprobe hdc=noprobe" in my kernel line + turned on ACHI mode in BIOS, and finally they came up as SATA drives tweakable via hdparm. However in my case I want to use my graphic card to play games but if i revert to 2.6.18 and try to reinstall the kmod-nvidia, yum forces me to install

Either your system is using a mode not supported by your hdd, or the system can't tell you what mode it is using. PIO modes : pio0 pio1 pio2 pio3 pio4 DMA modes : mdma0 mdma1 mdma2 UDMA modes : udma0 udma2 udma3 *udma4 ... comcor Seniorius Lurkius Registered: Jun 5, 2003Posts: 3 Posted: Mon May 10, 2004 8:22 pm FWIW, I had a system whose drive gave me the same errors for the longest time Red Hat Customer Portal Skip to main content Main Navigation Products & Services Back View All Products Infrastructure and Management Back Red Hat Enterprise Linux Red Hat Virtualization Red Hat Identity

NOte I don't have anything plugged into the Jmicron controller (ie the 2 purple ports on the left of the main column of 4 SATA ports). Having trouble installing a piece of hardware? Nothinman Ars Tribunus Angusticlavius Registered: Jan 14, 2000Posts: 8782 Posted: Tue May 11, 2004 7:08 pm quote: Going back to 2.6.5. We cannot use a CD-ROM drive.

All rights reserved Use of this Site constitutes acceptance of our User Agreement (effective 3/21/12) and Privacy Policy (effective 3/21/12), and Ars Technica Addendum (effective 5/17/2012) Your California Privacy Rights The this content I 've been reading other forums with people with the same problem and they reverted to Kernel 2.6.18. Sooo my guest would be to force a DMA mode; udma2 is the fastest it seems to support, so if you like the best performance it would be the correct choice. However I dont know what this option exactly does and I dont understand why this error is spamming the syslog when I dont use the nodma option.

Please visit this page to clear all LQ-related cookies. I think I saw around google it was a cable issue. All Rights Reserved. × Close Title Loading... weblink Thanks!

Thanks again. Inside the Makefile the JMicron module is mentioned however: obj-$(CONFIG_BLK_DEV_JMICRON) += jmicron.o Could it be that it's just not being compiled? What could be the cause of this ?

It's just a bit sucky because it slows the disk down quite a bit - I discovered the read test with hdparm: hdparm -t /dev/hda..

b.) I also get tje DMA invalid errors, but it doesnt' seem to do anything. It just took more time to start. wintermute00028th April 2007, 09:36 AMAnyone had any luck?? I never liked Maxtor anyway...Your smarctl output was interesting though:quote: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE199 UDMA_CRC_Error_Count 0x0008 159 001 000 Old_age Offline - 262 Spacing is

I noticed yesterday that the new stable kernel is 2.6.20 on kernel.org, and so I hope that this will find it's way into FC6 such as the 2.6.19 kernel did, hopefully The kernel changelog did mention something about the JMicron controllers, I still feel that it's something to do with the module names changing and the correct ones are not being loaded Open a Support Case Contact Support Policies and Warranties Documentation Products BIG-IP LTM BIG-IP AAM BIG-IP AFM BIG-IP Analytics BIG-IP APM BIG-IP ASM BIG-IP DNS BIG-IP GTM BIG-IP Link Controller BIG-IP check over here I'm in exactly the same boat as you with the kmod-nvidia problem.

It starts about 5 minutes after I log into a session. Half_Elf View Public Profile View LQ Blog View Review Entries View HCL Entries Visit Half_Elf's homepage! I attach a bootup log in case anybody can help! at least it would be my first guess.

Interesting. Maybe it's just your DMA settings that are too intensive, you could try to slow this down with hdparm. [WARNING : below commands can be dangerous. The compact flash media drive can perform only programmed input/output data transfer operations.

Was this resource helpful in solving your issue? some of the voltage levels seem a bit low...

Half_Elf View Public Profile View LQ Blog View Review Entries View HCL Entries Visit Half_Elf's homepage! Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log no idea where to start looking.... Gives me this:fs/xfs/support/debug.o CC fs/xfs/support/move.omake[3]: *** No rule to make target `fs/xfs/support/qsort.s', needed by `fs/xfs/support/qsort.o'.

Find all posts by DukeNuke2 #3 01-25-2009 sbn Registered User Join Date: May 2008 Last Activity: 27 August 2011, 4:32 PM EDT Posts: 38 Thanks: 0 Thanked 0