<---- template headericclude ----->
kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 9 of 9
  1. #1
    Join Date
    Nov 2007
    Posts
    20
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

    Since a week or two I am having the problem that one of my harddisks (a Samsung HD103UJ) goes offline during heavy workloads. The workload is a series of MPI jobs that run for about half an hour each for six hours. The MPI jobs use all 4 processors on my quad-core system and access 8 1GB files read-only and 8 1GB files read/write heavily. When the problem occurs the xfs filesystem is no longer accessible, and when I reboot the BIOS does not even detect the disk, I have to shutdown and restart the system. The problem is not easy to reproduce: most of the time the batch of jobs finishes, sometimes not with the above eror.

    /var/log/messages shows the error

    ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

    smartd and Samsung hdd diagnostics do not show any errors. Also

    https://bugzilla.redhat.com/show_bug.cgi?id=462425

    suggests it is a kernel problem, but this is for a particular controller.

    I am running FC10 2.6.27.21-170.2.56.fc10.x86_64 on a Shuttle XPC SP35P2 with 8 GB RAM and an Intel Q6600. The SATA controller is Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH).

    Anyone else seen this problem? Any workarounds that are known to work (currently I am running with a CD in my DVD drive as has been suggested).

    Regards,
    Gijsbert

  2. #2
    Join Date
    Nov 2004
    Location
    /dev/zero
    Posts
    39
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I got the same problem for my server and gave an solution on bugzilla:
    https://bugzilla.redhat.com/show_bug.cgi?id=462425#c80
    Since then, no such message anymore.

  3. #3
    Join Date
    Aug 2005
    Posts
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

    Hello,

    I've had the same problem too. I have two IDE and two SATA drives. However I attribute my problem to my SATA drive cables. What I find is a frozen system and one drive light on. The message from /var/log/messages:

    kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    kernel: ata4.00: failed command: SMART
    kernel: ata4.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0
    kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    kernel: ata4.00: status: { DRDY }
    kernel: ata4: link is slow to respond, please be patient (ready=0)

    Short-Term Solution: Power-off, open the case, re-seat the SATA cables, both ends, reboot.

    Solution: New SATA cables

    Hope your problem is as simple to solve.

    Dave

  4. #4
    Join Date
    Dec 2010
    Posts
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

    I received a similar error when booting from a cd of backtrack in an attempt to recover the data from a broken hard drive.

    Output from BackTrack4 boot cd:
    ata1.01 status: { DRDY }
    ata1.01 exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    ata1.01 failed command: read DMA txt


    Ubuntu 10.10 live cd managed to access the drive partially (I/O error whenever we tried to access a the contents of a file). I believe it is a hard disk controller hardware error and not a cable error as the same problem has been recreated using 3 sets of sata cables that work with other sata drives.

    Good luck to you man. =)

  5. #5
    Join Date
    Aug 2009
    Posts
    11,397
    Mentioned
    98 Post(s)
    Tagged
    0 Thread(s)

    Re: kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

    I have been having this same problem on my system. 12 different hard drive, 11 different cables, 4 different controllers, 2 different power supplies. The problem randomly crops up since I installed Fedora 14. Go back to Fedora 13, the problem never occurs.

    What I have found every time I get that message is that there are pending sector reallocations in the drive's SMART table, and in all cases but 1, running different disk utilities on the drive, I found the sector in question to be in the drive's partition information.

    However, all disk utilities have never found an actual problem with the drive. Just some data corruption is all that I have encountered.

    In some cases, just a read from the drive resets the pending reallocation and everything is fine.

    I can do that by running something like "dd if=/dev/sdb of=/dev/null

    Other times, I have had to run HDAT2 or Spinrite on the drive to get it reset.

    The few times I have run into actual data corruption on the drive in the partition table, I was able to run testdisk, have it scan for partitions and write the partition information back to the drive.

    What is interesting is that in NO case was there ever an actual problem with the hard drive. I have run numerous full surface scans, with various utilities and not a single problem has been found. And also, this problem does NOT happen if I go back to Fedora 13.

    One of the easiest ways I have found to get it back right after it completely hangs the system is to boot form Hiren's boot CD, and boot into DOS mode.. Run HDAT2 on the drive from there.

    Then usually after that, I can boot back into Fedora and run testdisk if needed, or boot Hirens boot CD into linux and run testdisk from there if the partition table is corrupted enough to prevent Fedora from booting.

    I have mentioned this problem several times in these forums, and I have noticed that quite a few people seem to be having this same problem.

    The only things in common with all the problems I have encountered have been.. CPU, memory, motherboard, and Fedora 14.
    Last edited by DBelton; 6th December 2010 at 07:48 PM.

  6. #6
    Join Date
    Jun 2011
    Posts
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

    I can told you that fedora does not have the error... i have windows xp... and i have the same problem... my board is IBM of Pentium 4... processor 2.4 one core... and 512 mb ... ati radeon 256 mb...

    I dont know what coul d it be

  7. #7
    Join Date
    Jul 2011
    Posts
    9
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

    Yea, I have something like this with my ASUS P5B motherboards onboard SATA (Fedora 15):

    Jul 16 00:26:51 localhost kernel: [ 0.922743] ata8: SATA max UDMA/133 abar m8192@0xfe8fe000 port 0xfe8fe180 irq 16
    Jul 16 00:26:51 localhost kernel: [ 1.383271] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Jul 16 00:26:51 localhost kernel: [ 1.383904] ata8.00: ATA-7: WDC WD1200JS-00MHB0, 02.01C03, max UDMA/133
    Jul 16 00:26:51 localhost kernel: [ 1.384080] ata8.00: 234441648 sectors, multi 16: LBA48
    Jul 16 00:26:51 localhost kernel: [ 1.384780] ata8.00: configured for UDMA/133
    Jul 16 00:26:51 localhost kernel: [ 3.379453] ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x780100 action 0x6
    Jul 16 00:26:51 localhost kernel: [ 3.379479] ata8.00: irq_stat 0x08000000
    Jul 16 00:26:51 localhost kernel: [ 3.379493] ata8: SError: { UnrecovData 10B8B Dispar BadCRC Handshk }
    Jul 16 00:26:51 localhost kernel: [ 3.379511] ata8.00: failed command: READ DMA
    Jul 16 00:26:51 localhost kernel: [ 3.379531] ata8.00: cmd c8/00:06:b9:23:c3/00:00:00:00:00/e2 tag 0 dma 3072 in
    Jul 16 00:26:51 localhost kernel: [ 3.379551] ata8.00: status: { DRDY }
    Jul 16 00:26:51 localhost kernel: [ 3.379889] ata8: hard resetting link
    Jul 16 00:26:51 localhost kernel: [ 3.840061] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Jul 16 00:26:51 localhost kernel: [ 3.841460] ata8.00: configured for UDMA/133
    Jul 16 00:26:51 localhost kernel: [ 3.841847] ata8: EH complete
    Jul 16 00:26:51 localhost kernel: [ 3.892414] ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x780100 action 0x6
    Jul 16 00:26:51 localhost kernel: [ 3.892761] ata8.00: irq_stat 0x08000000
    Jul 16 00:26:51 localhost kernel: [ 3.893097] ata8: SError: { UnrecovData 10B8B Dispar BadCRC Handshk }
    Jul 16 00:26:51 localhost kernel: [ 3.893425] ata8.00: failed command: READ DMA
    Jul 16 00:26:51 localhost kernel: [ 3.893757] ata8.00: cmd c8/00:01:df:01:00/00:00:00:00:00/e0 tag 0 dma 512 in
    Jul 16 00:26:51 localhost kernel: [ 3.894422] ata8.00: status: { DRDY }
    Jul 16 00:26:51 localhost kernel: [ 3.894750] ata8: hard resetting link
    Jul 16 00:26:51 localhost kernel: [ 4.355233] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Jul 16 00:26:51 localhost kernel: [ 4.356627] ata8.00: configured for UDMA/133
    Jul 16 00:26:51 localhost kernel: [ 4.357015] ata8: EH complete
    Jul 16 00:26:51 localhost kernel: [ 4.400348] ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x780100 action 0x6
    Jul 16 00:26:51 localhost kernel: [ 4.400686] ata8.00: irq_stat 0x08000000
    Jul 16 00:26:51 localhost kernel: [ 4.400991] ata8: SError: { UnrecovData 10B8B Dispar BadCRC Handshk }
    Jul 16 00:26:51 localhost kernel: [ 4.401304] ata8.00: failed command: READ DMA
    Jul 16 00:26:51 localhost kernel: [ 4.401609] ata8.00: cmd c8/00:06:09:20:c3/00:00:00:00:00/e2 tag 0 dma 3072 in
    Jul 16 00:26:51 localhost kernel: [ 4.402224] ata8.00: status: { DRDY }
    Jul 16 00:26:51 localhost kernel: [ 4.402533] ata8: hard resetting link
    Jul 16 00:26:51 localhost kernel: [ 4.862063] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Jul 16 00:26:51 localhost kernel: [ 4.863459] ata8.00: configured for UDMA/133
    Jul 16 00:26:51 localhost kernel: [ 4.863831] ata8: EH complete
    Jul 16 00:26:51 localhost kernel: [ 13.348618] ata8: limiting SATA link speed to 1.5 Gbps
    Jul 16 00:26:51 localhost kernel: [ 13.348964] ata8.00: exception Emask 0x10 SAct 0x0 SErr 0x780100 action 0x6
    Jul 16 00:26:51 localhost kernel: [ 13.349255] ata8.00: irq_stat 0x08000000
    Jul 16 00:26:51 localhost kernel: [ 13.349543] ata8: SError: { UnrecovData 10B8B Dispar BadCRC Handshk }
    Jul 16 00:26:51 localhost kernel: [ 13.349854] ata8.00: failed command: READ DMA
    Jul 16 00:26:51 localhost kernel: [ 13.350153] ata8.00: cmd c8/00:06:b9:23:c3/00:00:00:00:00/e2 tag 0 dma 3072 in
    Jul 16 00:26:51 localhost kernel: [ 13.350745] ata8.00: status: { DRDY }
    Jul 16 00:26:51 localhost kernel: [ 13.351052] ata8: hard resetting link
    Jul 16 00:26:51 localhost kernel: [ 13.811128] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    Jul 16 00:26:51 localhost kernel: [ 13.812536] ata8.00: configured for UDMA/133
    Jul 16 00:26:51 localhost kernel: [ 13.812911] ata8: EH complete
    Which keeps going for quite some time, after which the normal boot proceeds and then all works fine. I've noticed the 3-d line from the end, it is when the speed drops down from 3.0Gpbs to 1.5Gbps that the messages stops.

    Here are my own considerations on the nature of the problem. In fact, this must be EITHER the SATA controller , OR the HDD's own electronics failure. Changing SATA cables hasn't helped. And by the way, each of these cables allows to recognize another HDD or a SATA DVD-writer plugged into ANY of the SATA ports, which turns attention back to the HDD in question.
    In fact, the motherboard NEVER recognizes this HDD in ANY of its SATA ports from the first time, so I have to restart the computer and then it appears. Another one in favour of the explanation involving HDD failure...

    Back to the problem:
    the option, suggested in one of the links, to use
    acpi=off noapic
    causes GNOME 3 to fail to load because of the graphics hardware failure, so this is not an option.

    However, when I remove the "rhgb" option from the kernel command line the error above takes much quicker to stop.

    PS: I might not need to say this, but this problem doesn't happen when booting into FreeBSD, where it works like clockwork.

    ---------- Post added at 07:41 PM ---------- Previous post was at 07:23 PM ----------

    Oh, and BTW, I've found a funny type of SATA cable which seems to work much better in the computers where such things happen (I've encountered at least 2 by now). It is a cable that has the SATA and POWER plugs made into one plug on the HDD side of it, which makes it stick much better as it is held now in 2 different sockets simultaneously. So you might try your luck with such cable. Yea, forgot to add: this problem may be not only due to the SATA cable, but also to the HDD POWER cable plug on the HDD side. Its construction is SO unreliable, that it just gets distorted so that some contacts fail to connect!
    So please make sure your SATA power cable fits well because with all these disk failures the MOST unlikely thing to happen is the SATA controller failure. And the SATA link and power cables are very bad quality construction and cause problems quite often.
    And the kernel patches and other stuff, I would presume, is not actually "fixing" it. I would rather suspect it just puts the SATA link into some inferior working mode while the problem still remains related to hardware rather than to software. Just seeing that it happens for some people and doesn't for other people with absolutely the same hardware.

    Another thing I would try is plug the HDD in question into a different computer and try to boot from it. Thankfully, Linux allows to boot its OS from a HDD plugged into almost any other computer (given it fits the OS architecture). At least you'll see whether or not it is your HDD to blame. Sure, it can be BOTH the HDD and motherboard and is most likely to go away when you upgrade... but that's the last thing we wanna do, right?
    Last edited by KBerger; 15th July 2011 at 08:53 PM.

  8. #8
    Join Date
    Aug 2011
    Posts
    22
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

    no, no.. please don't say it's cable/controller!

    ASUS P5Q3e mobo
    160GB sata disc quite old

    Code:
    Dec  8 20:17:12 montblanc kernel: [40590.880059] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    Dec  8 20:17:12 montblanc kernel: [40590.880064] ata1.00: failed command: FLUSH CACHE EXT
    Dec  8 20:17:12 montblanc kernel: [40590.880070] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
    Dec  8 20:17:12 montblanc kernel: [40590.880071]          res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
    Dec  8 20:17:12 montblanc kernel: [40590.880074] ata1.00: status: { DRDY }
    Dec  8 20:17:12 montblanc kernel: [40590.880079] ata1: hard resetting link
    Dec  8 20:17:22 montblanc kernel: [40600.892060] ata1: softreset failed (device not ready)
    Dec  8 20:17:22 montblanc kernel: [40600.892064] ata1: hard resetting link
    Dec  8 20:17:26 montblanc kernel: [40604.184063] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Dec  8 20:17:26 montblanc kernel: [40604.185418] ata1.00: configured for UDMA/133
    Dec  8 20:17:26 montblanc kernel: [40604.185421] ata1.00: retrying FLUSH 0xea Emask 0x4
    Dec  8 20:17:26 montblanc kernel: [40604.200067] ata1.00: device reported invalid CHS sector 0
    Dec  8 20:17:26 montblanc kernel: [40604.200088] ata1: EH complete
    So I took a sledgehammer to the disk (to wipe it) and bought a new ssd. Bummer for me if it's the controller/cable. Could be cable was loose as I've had no issues with the ssd, despite using same cable, and didn't reseat it at the mobo end during installation.

  9. #9
    Join Date
    Jul 2011
    Posts
    9
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

    So it was the HDD was old, right? Why not.

Similar Threads

  1. Replies: 0
    Last Post: 12th June 2009, 08:27 PM
  2. Replies: 1
    Last Post: 30th May 2008, 10:36 PM
  3. ata5.00 exception Emask...
    By jody in forum Hardware
    Replies: 0
    Last Post: 17th May 2008, 04:25 PM
  4. ata2: exception Emask problem
    By enders in forum Using Fedora
    Replies: 3
    Last Post: 25th March 2008, 11:44 AM
  5. fc8 boot fails 'ata1.00 exception .... frozen'
    By iidbis in forum Installation, Upgrades and Live Media
    Replies: 2
    Last Post: 3rd February 2008, 03:27 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
[[template footer(Guest)]]