Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,581
Rep:
Intermittent ata2.00 error: What does it mean?
Excerpt from /var/log/messages:
Code:
...
<7>usb-storage: device scan complete
<6>rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
<6>rtc0: alarms up to one year, y3k
<6>ppdev: user-space parallel port driver
<6>Adding 3502160k swap on /dev/sdb2. Priority:-1 extents:1 across:3502160k
<6>EXT3 FS on sda7, internal journal
<6>device-mapper: uevent: version 1.0.3
<6>device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-devel@redhat.com
<3>ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
<3>ata2.00: BMDMA stat 0x64
<3>ata2.00: cmd c8/00:fc:4d:eb:f6/00:00:00:00:00/e0 tag 0 dma 129024 in
<4> res 51/84:00:4d:eb:f6/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
<3>ata2.00: status: { DRDY ERR }
<3>ata2.00: error: { ICRC ABRT }
<6>ata2: soft resetting link
<6>ata2.00: configured for UDMA/66
<6>ata2.01: configured for UDMA/33
<6>ata2: EH complete
<5>sd 1:0:0:0: [sdb] 20010816 512-byte hardware sectors (10246 MB)
<5>sd 1:0:0:0: [sdb] Write Protect is off
<7>sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
<5>sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<5>sd 1:0:0:0: [sdb] 20010816 512-byte hardware sectors (10246 MB)
<5>sd 1:0:0:0: [sdb] Write Protect is off
<7>sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
<5>sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<3>ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
<3>ata2.00: BMDMA stat 0x64
<3>ata2.00: cmd c8/00:b4:4d:ec:06/00:00:00:00:00/e1 tag 0 dma 92160 in
<4> res 51/84:00:4d:ec:06/00:00:00:00:00/e1 Emask 0x10 (ATA bus error)
<3>ata2.00: status: { DRDY ERR }
<3>ata2.00: error: { ICRC ABRT }
<6>ata2: soft resetting link
<6>ata2.00: configuDocumentsred for UDMA/66
<6>ata2.01: configured for UDMA/33
<6>ata2: EH complete
<5>sd 1:0:0:0: [sdb] 20010816 512-byte hardware sectors (10246 MB)
<5>sd 1:0:0:0: [sdb] Write Protect is off
<7>sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
<5>sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<5>sd 1:0:0:0: [sdb] 20010816 512-byte hardware sectors (10246 MB)
<5>sd 1:0:0:0: [sdb] Write Protect is off
<7>sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
<5>sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<3>ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
<3>ata2.00: BMDMA stat 0x64
<3>ata2.00: cmd c8/00:fc:4d:eb:22/00:00:00:00:00/e1 tag 0 dma 129024 in
<4> res 51/84:00:4d:eb:22/00:00:00:00:00/e1 Emask 0x10 (ATA bus error)
<3>ata2.00: status: { DRDY ERR }
<3>ata2.00: error: { ICRC ABRT }
<6>ata2: soft resetting link
<6>ata2.00: configured for UDMA/66
<6>ata2.01: configured for UDMA/33
<6>ata2: EH complete
<4>ata2.00: limiting speed to UDMA/44:PIO4
<3>ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
<3>ata2.00: BMDMA stat 0x64
<3>ata2.00: cmd c8/00:fc:4d:eb:22/00:00:00:00:00/e1 tag 0 dma 129024 in
<4> res 51/84:00:4d:eb:22/00:00:00:00:00/e1 Emask 0x10 (ATA bus error)
<3>ata2.00: status: { DRDY ERR }
<3>ata2.00: error: { ICRC ABRT }
<6>ata2: soft resetting link
<6>ata2.00: configured for UDMA/44
<6>ata2.01: configured for UDMA/33
<6>ata2: EH complete
<5>sd 1:0:0:0: [sdb] 20010816 512-byte hardware sectors (10246 MB)
<5>sd 1:0:0:0: [sdb] Write Protect is off
<7>sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
<5>sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<5>sd 1:0:0:0: [sdb] 20010816 512-byte hardware sectors (10246 MB)
<5>sd 1:0:0:0: [sdb] Write Protect is off
<7>sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
<5>sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<3>ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
<3>ata2.00: BMDMA stat 0x64
<3>ata2.00: cmd c8/00:10:39:51:17/00:00:00:00:00/e1 tag 0 dma 8192 in
<4> res 51/84:00:39:51:17/00:00:00:00:00/e1 Emask 0x10 (ATA bus error)
<3>ata2.00: status: { DRDY ERR }
<3>ata2.00: error: { ICRC ABRT }
<6>ata2: soft resetting link
<6>ata2.00: configured for UDMA/44
<6>ata2.01: configured for UDMA/33
<6>ata2: EH complete
<5>sd 1:0:0:0: [sdb] 20010816 512-byte hardware sectors (10246 MB)
<5>sd 1:0:0:0: [sdb] Write Protect is off
<7>sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
<5>sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<5>sd 1:0:0:0: [sdb] 20010816 512-byte hardware sectors (10246 MB)
<5>sd 1:0:0:0: [sdb] Write Protect is off
<7>sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
<5>sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<6>loop: module loaded
<6>kjournald starting. Commit interval 5 seconds
<6>EXT3 FS on sda1, internal journal
This happens not very frequently but I don't even know what the box is trying to tell me. What should I do? Is it at all something to worry about? I'd be grateful for any explanation...
Configuration of the box: 700 Mhz Athlon with sda 250 GB Maxtor sdc 10 GB Maxtor as swap sdd DVD burner.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,581
Original Poster
Rep:
Yes, sdb is the 10 GB Maxtor, I thought I had put it on hdc (ah, well...). It is only for /swap (and an old DOS partition). I'll run the tests over the weekend and come back with the results.
Sorry I didn't reply before, I was on vacation. But from the looks of it, there's nothing to worry about. It is a bit strange, but overall I doubt that it is failing or anything. It might be just a driver issue. What driver is it using anyway ? See or post output of '/sbin/lspci -vv'.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,581
Original Poster
Rep:
Quote:
Originally Posted by H_TeXMeX_H
Make sure the IDE cable is plugged in properly and is not damaged.
That is an issue or not . I mean, I set the plugs thoroughly since I had an other issue on the other IDE-channel (the cable is detected as a 40 lines cable though it has 80 lines, even when it was exchanged for a new part).
Quote:
Originally Posted by H_TeXMeX_H
The via drivers are not that good, it could be some type of driver issue. Maybe you could try a newer kernel.
Well the mobo is 10 years old...
It is the SuSE 11.0 kernel, that should usually work.
Quote:
Originally Posted by H_TeXMeX_H
Either way there is nothing in the SMART data to suggest that the drive is in danger of failing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
. 
. I mean, I set the plugs thoroughly since I had an other issue 
on the other IDE-channel (the cable is detected as a 40 lines cable though it has 80 lines, even when it was exchanged for a new part).
