From: Marcelo Ricardo Leitner marcelo.leitner@gmail.com On Tue, May 01, 2018 at 03:28:29PM -0400, m.roth@5-cent.us wrote:
My manager's workstation is C 7.4, and it started screaming yesterday about issues with ata5.
Except that he has one internal and one external drive, and a DVD. Anyone have clues as to what could be causing this, or where to start looking?
ata'5' is about the port it is connected and not related to the count of devices in there.
You should be able to match it with: ls -l /sys/class/block | grep ata5 There sould be a symlink like: lrwxrwxrwx. 1 root root 0 abr 29 19:23 sda -> ../../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
Or by going through boot dmesg.
Good thought... but no joy. I see links with sda, sda1, sdb, sdb1 and sdb2, and four for dm-[0-3], and nothing else. Looking in that symlink, I see ll /sys/devices/pci0000:00/0000:00:1f.2/ata5/ total 0 drwxr-xr-x. 6 root root 0 May 2 10:12 ./ drwxr-xr-x. 10 root root 0 May 2 10:11 ../ drwxr-xr-x. 3 root root 0 May 2 10:14 ata_port/ drwxr-xr-x. 4 root root 0 May 2 10:14 host4/ drwxr-xr-x. 5 root root 0 May 2 10:14 link5/ drwxr-xr-x. 2 root root 0 May 2 10:14 power/ -rw-r--r--. 1 root root 4096 May 2 10:14 uevent $ ll /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/ total 0 drwxr-xr-x. 4 root root 0 May 2 10:14 ./ drwxr-xr-x. 6 root root 0 May 2 10:12 ../ drwxr-xr-x. 2 root root 0 May 2 10:15 power/ drwxr-xr-x. 3 root root 0 May 2 10:15 scsi_host/ lrwxrwxrwx. 1 root root 0 May 1 17:59 subsystem -> ../../../../../bus/scsi/ -rw-r--r--. 1 root root 4096 May 2 10:15 uevent
Finally, I did ll /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/scsi_host/host4/ total 0 drwxr-xr-x. 3 root root 0 May 2 10:15 ./ drwxr-xr-x. 3 root root 0 May 2 10:15 ../ -rw-r--r--. 1 root root 4096 May 2 10:15 active_mode -r--r--r--. 1 root root 4096 May 2 10:15 ahci_host_cap2 -r--r--r--. 1 root root 4096 May 2 10:15 ahci_host_caps -r--r--r--. 1 root root 4096 May 2 10:15 ahci_host_version -r--r--r--. 1 root root 4096 May 2 10:15 ahci_port_cmd -r--r--r--. 1 root root 4096 May 2 10:15 can_queue -r--r--r--. 1 root root 4096 May 2 10:15 cmd_per_lun lrwxrwxrwx. 1 root root 0 May 2 10:15 device -> ../../../host4/ -rw-r--r--. 1 root root 4096 May 2 10:15 eh_deadline -rw-r--r--. 1 root root 4096 May 2 10:15 em_buffer -rw-r--r--. 1 root root 4096 May 2 10:15 em_message -r--r--r--. 1 root root 4096 May 2 10:15 em_message_supported -r--r--r--. 1 root root 4096 May 2 10:15 em_message_type -r--r--r--. 1 root root 4096 May 2 10:15 host_busy --w-------. 1 root root 4096 May 2 10:15 host_reset -rw-r--r--. 1 root root 4096 May 1 18:00 link_power_management_policy drwxr-xr-x. 2 root root 0 May 2 10:15 power/ -r--r--r--. 1 root root 4096 May 2 10:15 proc_name -r--r--r--. 1 root root 4096 May 2 10:15 prot_capabilities -r--r--r--. 1 root root 4096 May 2 10:15 prot_guard_type --w-------. 1 root root 4096 May 2 10:15 scan -r--r--r--. 1 root root 4096 May 2 10:15 sg_prot_tablesize -r--r--r--. 1 root root 4096 May 2 10:15 sg_tablesize -rw-r--r--. 1 root root 4096 May 2 10:15 state lrwxrwxrwx. 1 root root 0 May 1 18:00 subsystem -> ../../../../../../../class/scsi_host/ -rw-r--r--. 1 root root 4096 May 2 10:15 supported_mode -rw-r--r--. 1 root root 4096 May 2 10:15 uevent -r--r--r--. 1 root root 4096 May 2 10:15 unchecked_isa_dma -r--r--r--. 1 root root 4096 May 2 10:15 unique_id -r--r--r--. 1 root root 4096 May 2 10:15 use_blk_mq
And nothing else. Note that the it's running 3.10.0-862.el7.x86_64.
Seems to have given up, for at least now, but could start flooding the logs again....
mark