Errors from ata6:00 -- How to find corresponding device?

[Chris Tyler]

I'm getting tons of messages in /var/log/messages about 'ata6' or
'ata6:00':

Nov  7 11:16:21 concord3 kernel: ata6.00: exception Emask 0x0 SAct 0x0
SErr 0x0 action 0x6 frozen
Nov  7 11:16:21 concord3 kernel: ata6.00: cmd
a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Nov  7 11:16:21 concord3 kernel:         cdb 00 00 00 00 00 00 00 00  00
00 00 00 00 00 00 00
Nov  7 11:16:21 concord3 kernel:         res
40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Nov  7 11:16:21 concord3 kernel: ata6.00: status: { DRDY }
Nov  7 11:16:21 concord3 kernel: ata6: soft resetting link
Nov  7 11:16:21 concord3 kernel: ata6.00: configured for PIO0
Nov  7 11:16:21 concord3 kernel: ata6: EH complete

The problem is that I can't figure out which device this corresponds to.
The possibilities are /dev/sd[a-c] (3 sata 500G drives) or /dev/sr0
(sata dvd writer).

What does the 6 or 6:00 correspond to? It doesn't appear to be a major
or minor device number, or correspond to any entries in /sys that I can
find. If the 6 is not the device (but rather the driver version or
something), is there any part of these messages that indicate which
device is associated with the error?

Any pointers appreciated!--

-Chris

--
fedora-list mailing list
fedora-list@...
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Andy Campbell-2]

> What does the 6 or 6:00 correspond to? It doesn't appear to be a major
> or minor device number, or correspond to any entries in /sys that I can
> find. If the 6 is not the device (but rather the driver version or
> something), is there any part of these messages that indicate which
> device is associated with the error?

According to the libata wiki ...

http://ata.wiki.kernel.org/index.php/Libata_error_messages

It should be the drive plugged into port 6 of your motherboard.


--
fedora-list mailing list
fedora-list@...
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Roberto Ragusa]

Chris Tyler wrote:
> What does the 6 or 6:00 correspond to? It doesn't appear to be a major
> or minor device number, or correspond to any entries in /sys that I can
> find. If the 6 is not the device (but rather the driver version or
> something), is there any part of these messages that indicate which
> device is associated with the error?

Maybe you can find useful hints in /var/log/dmesg (or /var/log/messages).

--
   Roberto Ragusa    mail at robertoragusa.it

--
fedora-list mailing list
fedora-list@...
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Chris Tyler]

On Sun, 2009-11-08 at 09:17 +0000, Andy Campbell wrote:

> > What does the 6 or 6:00 correspond to? It doesn't appear to be a major
> > or minor device number, or correspond to any entries in /sys that I can
> > find. If the 6 is not the device (but rather the driver version or
> > something), is there any part of these messages that indicate which
> > device is associated with the error?
>
> According to the libata wiki ...
>
> http://ata.wiki.kernel.org/index.php/Libata_error_messages
>
> It should be the drive plugged into port 6 of your motherboard.

Thank you! That's a great link; I had googled all over for that info but
somehow didn't find it.

I still wonder, though, how to convert "port 6" to a Linux device name
-- surely the kernel knows the mapping somewhere, how do I get at that
info?

-Chris

--
fedora-list mailing list
fedora-list@...
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[John Wendel]

On 11/08/2009 06:20 AM, Chris Tyler wrote:

> On Sun, 2009-11-08 at 09:17 +0000, Andy Campbell wrote:
>>> What does the 6 or 6:00 correspond to? It doesn't appear to be a major
>>> or minor device number, or correspond to any entries in /sys that I can
>>> find. If the 6 is not the device (but rather the driver version or
>>> something), is there any part of these messages that indicate which
>>> device is associated with the error?
>>
>> According to the libata wiki ...
>>
>> http://ata.wiki.kernel.org/index.php/Libata_error_messages
>>
>> It should be the drive plugged into port 6 of your motherboard.
>
> Thank you! That's a great link; I had googled all over for that info but
> somehow didn't find it.
>
> I still wonder, though, how to convert "port 6" to a Linux device name
> -- surely the kernel knows the mapping somewhere, how do I get at that
> info?
>
> -Chris
>

Take a look at "/sys".  "ls /sys/block" will show you all the block
devices in your system and the device controller they are attached to.

lrwxrwxrwx 1 root root 0 2009-11-08 09:57 sda ->
../devices/pci0000:00/0000:00:1f.2/host2/target2:0:0/2:0:0:0/block/sda

Now, "ls /sys/block/sda" will show something like this:

alignment_offset  capability  device     holders  queue  removable  sda1
  slaves  subsystem
bdi               dev         ext_range  power    range  ro         size
  stat    uevent

Some of these are "pseudo" files that you can cat, others are
directories the you can examine. The info you want is here.

Sorry I don't know the exact answer, but I'll bet that you find it by
poking around in /sys.

Regards,

John


--
fedora-list mailing list
fedora-list@...
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Marc Wilson]

On Sun, Nov 8, 2009 at 10:25 AM, john wendel <jwendel10@...> wrote:

> Sorry I don't know the exact answer, but I'll bet that you find it by poking
> around in /sys.


I'll bet that he'd find it by actually bothering to read his dmesg
like he was told to, since all the devices the kernel found and the
interfaces that they're connected to are enumerated there.  Wow, the
devices are even there by NAME!

dell $ dmesg | grep ata..0
ata1.00: ATA-7: WDC WD5000AAKS-00TMA0, 12.01C01, max UDMA/133
ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2.00: ATAPI: TSSTcorp DVD+/-RW TS-H653A, D500, max UDMA/33
ata2.00: applying bridge limits
ata2.00: configured for UDMA/33
ata5.00: ATA-8: WDC WD5000AAKS-65A7B0, 01.03B01, max UDMA/133
ata5.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata5.00: configured for UDMA/133
ata6.00: ATAPI: TSSTcorpCD/DVDW SH-S183L, SB03, max UDMA/33, ATAPI AN
ata6.00: applying bridge limits
ata6.00: configured for UDMA/33

But that's just me.

--
Marc Wilson
msw@...

--
fedora-list mailing list
fedora-list@...
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines