LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 04-28-2011, 02:42 PM   #1
kdelover
Member
 
Registered: Aug 2009
Posts: 311

Rep: Reputation: 36
what does these messages mean ?


I see this message related to my hard drives a lot on most of my machines.I dont quite understand what is it ? Do i need to be worry about it or its some random message?

LAPTOP
Quote:
[ 3105.704528] ata2.00: exception Emask 0x10 SAct 0x0 SErr 0xd0002 action 0xe
[ 3105.704537] ata2.00: irq_stat 0x40000001
[ 3105.704545] ata2: SError: { RecovComm PHYRdyChg CommWake 10B8B }
[ 3105.704552] sr 1:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00
[ 3105.704576] ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 3105.704579] res 51/24:03:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
[ 3105.704586] ata2.00: status: { DRDY ERR }
[ 3105.704599] ata2: hard resetting link
[ 3106.650332] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 3106.659504] ata2.00: configured for UDMA/100
[ 3106.661888] ata2: EH complete

my dmesg on desktop is filled with these messages
Quote:
[ 808.896736] ata3.01: failed command: READ DMA
[ 808.896744] ata3.01: cmd c8/00:00:18:75:22/00:00:00:00:00/f0 tag 0 dma 131072 in
[ 808.896745] res 51/84:00:18:75:22/84:01:03:00:00/f0 Emask 0x30 (host bus error)
[ 808.896749] ata3.01: status: { DRDY ERR }
[ 808.896752] ata3.01: error: { ICRC ABRT }
[ 808.896763] ata3: soft resetting link
[ 809.172474] ata3.01: configured for UDMA/100
[ 809.172545] ata3: EH complete
[ 813.935638] ata3.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 813.935643] ata3.01: BMDMA stat 0x46
[ 813.935647] ata3.01: failed command: READ DMA
[ 813.935654] ata3.01: cmd c8/00:68:60:a8:22/00:00:00:00:00/f0 tag 0 dma 53248 in
[ 813.935655] res 51/84:68:60:a8:22/84:01:03:00:00/f0 Emask 0x30 (host bus error)
[ 813.935659] ata3.01: status: { DRDY ERR }
[ 813.935662] ata3.01: error: { ICRC ABRT }
[ 813.935673] ata3: soft resetting link
[ 814.211382] ata3.01: configured for UDMA/100
[ 814.211414] ata3: EH complete
 
Old 04-28-2011, 03:08 PM   #2
falcon56215
Member
 
Registered: Jan 2002
Location: Tennessee
Distribution: Xubuntu Natty on Lenovo R61i Thinkpad
Posts: 108

Rep: Reputation: 16
I found this on another forum... maybe it can be of some help?

"DRDY ERR messages actually seems to be reported as a kernel bug in a lot of systems which seems to relate a lot with Ubuntu and to a smaller extent Debian. I am investigating this because this is something that has started happening with me recently. I would recommend the following (You will require a bootable CD for some of this and you may need it due to disk issues for all of this. The Ubuntu desktop install CD works well without making you install anything):

Put "options libata noacpi=1" in /etc/modprobe.d/options.conf

Run "e2fsck -f -c -v /dev/sda1" but replace /dev/sda1 with the partitions causing the error. As far as I know, e2fsck needs a partition with the file system so this probably won't work on the whole disk. If it does work on the whole disk, you still need to run it on the partitions anyways. You need a bootable CD for this.

Edit the file /boot/grub/menu.lst and on the line that starts with "# kopt" add "noapic" to the end of the line. The # at the start is important and does not act like a comment. Do not remove the #.

This does not affect the disk but if you change "splash" to "nosplash" and remove the word "quiet" from /boot/grub/menu.lst on the line that starts with "# defoptions" Then it will not have an image when you boot ubuntu but instead will give you more verbose output.

On Ubuntu, after you change anything inside /boot/grub/menu.lst you must run /usr/sbin/update-grub"
 
Old 04-28-2011, 03:30 PM   #3
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4853Reputation: 4853Reputation: 4853Reputation: 4853Reputation: 4853Reputation: 4853Reputation: 4853Reputation: 4853Reputation: 4853Reputation: 4853Reputation: 4853
Before doing anything, backup your data. Then get the diagnosis tool of your harddisks manufacturer and test your harddisk. Most of the time I have seen something like that the harddisk was dying.
 
Old 04-29-2011, 07:06 AM   #4
falcon56215
Member
 
Registered: Jan 2002
Location: Tennessee
Distribution: Xubuntu Natty on Lenovo R61i Thinkpad
Posts: 108

Rep: Reputation: 16
I would have thought that, except he says it is happening across multiple machines... and it seems rather unlikely that all the drives went bad at the exact same time. But backing up data is always a good idea.
 
Old 05-02-2011, 04:43 AM   #5
jimux
LQ Newbie
 
Registered: Mar 2007
Posts: 11

Rep: Reputation: 1
The message "status: { DRDY ERR }" means that the kernel device driver is not correctly handshaking with the storage device. It is more likely that the kernel module used to contact the device is buggy than the disk is faulty, or that active power management is causing the disk to take too long to spin up and the resulting messages are interpreted by the kernel as the disk being full. Commonly the fault is noticed when sata1 disks (1.5Ghz) are used because they tend to have smaller on board buffers than sata2 (3Ghz) disks.

Start by checking that the queue_depth parameters are the same for both disk and motherboard.
Quote:
TM800@/]# cat /sys/devices/platform/pnx833x-sata/host1/target1:0:0/1:0:0:0/queue_depth
1
TM800@/]# hdparm -I /dev/sdb | grep depth
Queue depth: 32
TM800@/]#
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Postfix: User messages are okay; but error messages themselves seem to be bouncing jgombos Linux - Server 3 03-03-2007 03:21 PM
Redirecting the kernel messages to file other than /var/log/messages jyotika_b83 Linux - General 3 04-28-2005 07:39 PM
From where am i getting error messages to /var/log/messages? prabhuacsp Programming 3 02-16-2005 09:59 AM
/var/log/messages full of these messages. Should I be concerned? mdavis Linux - Security 5 04-16-2004 11:08 AM
syslog and firestarter - log messages to another file than messages mule Linux - Newbie 0 08-07-2003 04:35 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 08:10 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration