Ata Bus Error Linux
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings
Dmesg Ata Bus Error
and policies of this site About Us Learn more about Stack Overflow the bus error in linux terminal company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges how to solve bus error in linux Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works:
Linux Bus Error Core Dumped
Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Is my hard drive dying? up vote 8 down vote favorite 2 Im gettings strange error messages in the terminal. This is the output of dmesg: [ 3317.715990] ata4.00: exception Emask 0x10 SAct 0x78 SErr 0x400000 action 0x6 frozen [ 3317.716113] ata4.00:
Ata Bus Error Ubuntu
irq_stat 0x08000000, interface fatal error [ 3317.716199] ata4: SError: { Handshk } [ 3317.716262] ata4.00: failed command: WRITE FPDMA QUEUED [ 3317.716341] ata4.00: cmd 61/00:18:3f:14:13/04:00:00:00:00/40 tag 3 ncq 524288 out [ 3317.716342] res 40/00:34:17:05:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) [ 3317.716502] ata4.00: status: { DRDY } [ 3317.716563] ata4.00: failed command: WRITE FPDMA QUEUED [ 3317.716634] ata4.00: cmd 61/00:20:3f:18:13/04:00:00:00:00/40 tag 4 ncq 524288 out [ 3317.716635] res 40/00:34:17:05:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) [ 3317.716795] ata4.00: status: { DRDY } [ 3317.716856] ata4.00: failed command: WRITE FPDMA QUEUED [ 3317.716926] ata4.00: cmd 61/80:28:3f:1c:13/01:00:00:00:00/40 tag 5 ncq 196608 out [ 3317.716927] res 40/00:34:17:05:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) [ 3317.717087] ata4.00: status: { DRDY } [ 3317.717185] ata4.00: failed command: WRITE FPDMA QUEUED [ 3317.717293] ata4.00: cmd 61/28:30:17:05:13/01:00:00:00:00/40 tag 6 ncq 151552 out [ 3317.717293] res 40/00:34:17:05:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) [ 3317.717606] ata4.00: status: { DRDY } [ 3317.717705] ata4: hard resetting link [ 3318.208111] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3318.211624] ata4.00: configured for UDMA/133 [ 3318.211637] ata4: EH complete [ 4120.100879] ata4.00: exception Emask 0x
Assigned to Milestone elementary OS Edit Invalid Undecided Unassigned Edit You need to log in emask 0x10 (ata bus error) to change this bug's status. Affecting: elementary OS Filed here
Failed Command Identify Packet Device
by: Davide Aguiari When: 2016-04-29 Completed: 2016-09-25 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex write fpdma queued ata bus error Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Undecided Assigned to http://superuser.com/questions/438998/is-my-hard-drive-dying Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description System: HP Omen 15-5003nl OS: Linux Elementary Freya 0.3.2 64bit (and Windows 10 64bit) SSD: SanDisk A110 SD6PP4M-256GB-1006 SSD Firmware: A200906 Kernel: 3.19.0-58-generic and 4.4.6-040406-generic and https://bugs.launchpad.net/bugs/1576634 others (see after) I recently upgraded my SSD firmware and it fixed a serious ahcpi freeze bug on Windows partition (http://h30434.www3.hp.com/t5/Notebook-Boot-and-Lockup/HP-Omen-system-hangs/td-p/4990788). Sometimes the system freezed some seconds with Linux OS too, so I hoped to resolve all problems with this new firmware. On the contrary, now my dmesg is full of: 5/4/2016 00:40:26 Dago kernel [ 322.113563] ata5.00: exception Emask 0x10 SAct 0x20000000 SErr 0x50000 action 0xe frozen 5/4/2016 00:40:26 Dago kernel [ 322.113567] ata5.00: irq_stat 0x00400000, PHY RDY changed 5/4/2016 00:40:26 Dago kernel [ 322.113569] ata5: SError: { PHYRdyChg CommWake } 5/4/2016 00:40:26 Dago kernel [ 322.113572] ata5.00: failed command: WRITE FPDMA QUEUED 5/4/2016 00:40:26 Dago kernel [ 322.113575] ata5.00: cmd 61/48:e8:00:3e:7e/01:00:16:00:00/40 tag 29 ncq 167936 out 5/4/2016 00:40:26 Dago kernel [ 322.113575] res 40/00:e4:00:f7:32/00:00:19:00:00/40 Emask 0x10 (ATA bus error) 5/4/2016 00:40:26 Dago kernel [ 322.113577] ata5.00: status: { DRDY } 5/4/2016 00:40:26 Dago kernel [ 322.113580] ata5: hard resetting link 5/4/2016 00:40:27 Dago kernel
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow http://askubuntu.com/questions/143975/what-do-i-do-if-grub-sometimes-freezes-and-or-i-get-ata-bus-error-in-my-logs the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join https://ubuntuforums.org/showthread.php?t=1669308 them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top What do I do if Grub bus error sometimes freezes and/or I get “ATA bus error” in my logs? up vote 0 down vote favorite My machine one day started inconsistently to fail to boot. I found that Grub was (sometimes) unable to load either the kernel or the ramdisk (it said "out of Disk"). It got to the point where I could only boot with the Grub command line and attempt to load them manually - after serveral failed attempts, it eventually ata bus error succeeded. In my kernel logs, I found numerous "ATA bus error"s, and noticed that the disk was operating at ATA 33 instead of ATA 133. I did a full check of the disk (using the vendors bootable tool) and it came up clean (despite very large numbers of 'seek errors' - seems those are normal for my disk!). I wasted a heap of time looking for Grub bugs and worrying about hardware failures when eventually I noticed a suggestion to check the cables.... grub2 disk share|improve this question asked May 30 '12 at 4:37 drevicko 1,35251634 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted In the end, it seems it was cables. Following the suggestion in a bug report, I changed the SATA cable, used a different SATA power plug from my power supply (insufficient power is a possible culprit), and made sure the SATA cable wasn't near any other power cables (possible electical interference from other, especially power, cables). It works fine now. I've since put the original SATA cable back in, and it still works. I'll switch power cables soon, and try dangling the SATA cable near other power cables... Likely the SATA cable was either dislodged or a bad connection developed due to humidity or some such. share|improve this answer answ
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Hardware [ubuntu] ATA bus error Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 2 of 2 Thread: ATA bus error Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode January 17th, 2011 #1 davidhoenig View Profile View Forum Posts Private Message 5 Cups of Ubuntu Join Date May 2008 Beans 18 ATA bus error Every once in a while it feels like accesses to my boot hard disk (~1yr old 32GB SSD) get reallllly slow. I'm doing some debug and trying to figure out if I might have a hardware problem/bad disk. Here's what I see: During boot, dmesg shows these messages, at three separate times: [ 4.164797] ata7.00: exception Emask 0x10 SAct 0x1 SErr 0x780100 action 0x6 [ 4.164800] ata7.00: irq_stat 0x08000000 [ 4.164802] ata7: SError: { UnrecovData 10B8B Dispar BadCRC Handshk } [ 4.164804] ata7.00: failed command: READ FPDMA QUEUED [ 4.164807] ata7.00: cmd 60/08:00:10:09:00/00:00:00:00:00/40 tag 0 ncq 4096 in [ 4.164808] res 40/00:04:10:09:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) [ 4.164809] ata7.00: status: { DRDY } [ 4.164812] ata7: hard resetting link Neither 'fsck' nor smartmontools report any problems. Can anyone tell me if the above messages