On Thu, Jan 28, 2010 at 10:01:17AM -0500, Toby Bluhm wrote: > Stephen Harris wrote: > > ata7.01: exception Emask 0x0 SAct 0x0 SErr 0x0 a ction 0x0 > > ata7.01: irq_stat 0x00060002, device error via D 2H FIS > > ata7.01: cmd 25/00:08:47:1c:92/00:00:6c:00:00/e0 tag 0 dma 4096 in > > res 51/40:00:4e:1c:92/00:00:6c:00:00/00 Emask 0x9 (media error) > > How do I tell what disk this is complaining about? Is there a way > > to determine what ata7.01 maps to in terms of /dev/sd# values? > Try looking in /dev/disk/ Hmm... by-label and by-uuid clearly isn't useful here since that's based on filesystem data ;-) by-id doesn't look too helpful; it'd be good for determining model/serial number mapping to disk, but I don't have that info. Potentially useful information in other cases, but not here :-( by-path, unfortunately, returns the scsi controller data at a hardware address, not the ata#.# number eg pci-0000:00:1d.7-usb-0:3:1.0-scsi-0:0:0:0 pci-0000:00:1f.2-scsi-0:0:0:0 pci-0000:00:1f.2-scsi-1:0:0:0 pci-0000:00:1f.2-scsi-2:0:0:0 pci-0000:02:00.0-scsi-0:0:0:0 pci-0000:02:00.0-scsi-0:1:0:0 pci-0000:02:00.0-scsi-0:2:0:0 pci-0000:02:00.0-scsi-0:3:0:0 pci-0000:02:00.0-scsi-1:0:0:0 (internal disk, internal DVD writer, internal DVD-ROM, 5 external disks, 1 USB disk) That's really useful for mapping position in the array to sd number, though! Thanks for the idea, though! -- rgds Stephen