Re: disk problems: which ATA?
On Sun, 2011-07-03 at 19:19 +0000, Camaleón wrote:
> On Sun, 03 Jul 2011 11:25:18 -0700, Ross Boylan wrote:
> > How can I tell which ata device is which hard drive? It's come up
> > several times for me, most recently with ata2.00: exception Emask 0x0
> > SAct 0x0 SErr 0x0 action 0x6 frozen
> You can:
> - Run "smartctl -i /dev/sdb | grep -i model"
Except the drive isn't responding to smartctl (see original message).
I tried adding -T permissive, but all that gets me is
Short INQUIRY response, skip product id
(curiously, no error about command failed).
> - Then "dmesg | grep -i ata2"
> - To finally compare by hdd model :-)
That works for my current machine. But on another machine I want to
figure out which drive an error message goes with, and there are 2
identical drivers. I suppose that even if I new which sd device the ata
went with, I still wouldn't be sure which physical drive that was...
> As per the error itself, you can use the manufacturer hard disk
> diagnostic tools which uses to run from a LiveCD and will provide
> accurate results about your hdd health and status.
> OTOH, I've also seen that kind of error coming from bad sata cable or bad
> sit connection to motherboard/disk. You may also check this.
I think I already tried reseating, but I suppose it's worth trying
again. I'm concerned if I power down I may not be able to get back up,
since the failing hard disk is actually part of an LVM volume group. I
am also unable to get information on that VG right now.
Most of the logical vomes in the group are backed by other hard drives,
but I'm not quite sure what will happen if the disk is toast. At the
moment, I have access to most of the LVs, even though I can't get info
on the PV that contains them (!).
P.S. For the record, kernel logs need to be read carefully to figure out
which drive is ata2. Mine had
Jun 22 09:24:10 corn kernel: [ 7.767461] hdf: 26563824 sectors (13600 MB) w/256KiB Cache, CHS=26353/16/63
Jun 22 09:24:10 corn kernel: [ 7.798391] hdf: cache flushes not supported
Jun 22 09:24:10 corn kernel: [ 7.829859] usb 1-4: New USB device found, idVendor=04b8, idProduct=011e
Jun 22 09:24:10 corn kernel: [ 7.829859] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 22 09:24:10 corn kernel: [ 7.829859] usb 1-4: Product: EPSON Scanner
Jun 22 09:24:10 corn kernel: [ 7.829859] usb 1-4: Manufacturer: EPSON
Jun 22 09:24:10 corn kernel: [ 7.967458] hdf:<6>ata2.00: ATA-8: ST31000340AS, SD15, max UDMA/133
Jun 22 09:24:10 corn kernel: [ 8.135686] hdf1 hdf2 hdf3
Jun 22 09:24:10 corn kernel: [ 8.129867] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Jun 22 09:24:10 corn kernel: [ 8.241613] ata2.00: configured for UDMA/133
Jun 22 09:24:10 corn kernel: [ 8.129867] scsi 0:0:0:0: Direct-Access ATA WDC WD2500JS-00M 02.0 PQ: 0 ANSI: 5
Jun 22 09:24:10 corn kernel: [ 8.290133] scsi 1:0:0:0: Direct-Access ATA ST31000340AS SD15 PQ: 0 ANSI: 5
The key point is that although the message about ata2.00 (at 7.967458)
appears in the middle of the hdf information, the 2 have no relation.
It seems the <6> indicates an asyncronous message dumped before the end
of the line. Later comes
Jun 22 09:24:10 corn kernel: [ 9.520209] sd 1:0:0:0: [sdb] 1953525168 512-byte hardware sectors (1000205 MB)
so the sector count indicates this matches ata2.00, which is the Seagate ST31000340AS at scsi 1:0:0:0.
I guess the first ata line (after the <6>) gives the model.