![如何将 kern.log 错误消息中的 ataX.0 标识符映射到实际的 /dev/sdY 设备?](https://linux22.com/image/2119/%E5%A6%82%E4%BD%95%E5%B0%86%20kern.log%20%E9%94%99%E8%AF%AF%E6%B6%88%E6%81%AF%E4%B8%AD%E7%9A%84%20ataX.0%20%E6%A0%87%E8%AF%86%E7%AC%A6%E6%98%A0%E5%B0%84%E5%88%B0%E5%AE%9E%E9%99%85%E7%9A%84%20%2Fdev%2FsdY%20%E8%AE%BE%E5%A4%87%EF%BC%9F.png)
考虑以下kern.log
片段:
ata4.00: failed command: WRITE FPDMA QUEUED
ata4.00: cmd 61/00:78:40:1e:6c/04:00:f0:00:00/40 tag 15 ncq 524288 out
res 41/04:00:00:00:00/04:00:00:00:00/00 Emask 0x1 (device error)
ata4.00: status: { DRDY ERR }
ata4.00: error: { ABRT }
ata4: hard resetting link
ata4: nv: skipping hardreset on occupied port
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: configured for UDMA/133
ata4: EH complete
如何确定内核在谈论时实际上指的是哪个硬盘驱动器ata4.00
?
如何找到对应的/dev/sdY
设备名称?
答案1
通过遍历树可以找到对应的/dev/sdY设备/sys
:
$ find /sys/devices | grep '/ata[0-9]\+/.*/block/s[^/]\+$' \
| sed 's@^.\+/\(ata[0-9]\+\)/.\+/block/\(.\+\)$@\1 => /dev/\2@'
通过更有效的/sys
遍历(参见lsata.sh):
$ echo /sys/class/ata_port/ata*/../../host*/target*/*/block/s* | tr ' ' '\n' \
| awk -F/ '{printf("%s => /dev/%s\n", $5, $NF)}'
2 磁盘系统的输出示例:
ata1 => /dev/sda
ata2 => /dev/sdb
然后,为了可靠地识别实际硬件,您需要将 /dev/sdY 映射到序列号,例如:
$ ls /dev/disk/by-id -l | grep 'ata.*sd[a-zA-Z]$'
LSSCI
该lssci
实用程序还可用于导出映射:
$ lsscsi | sed 's@^\[\([^:]\+\).\+\(/dev/.\+\)$@\1,\2@' \
| awk -F, '{ printf("ata%d => %s\n", $1+1, $2) }'
请注意,相关的 lsscsi 枚举从 0 开始,而 ata 枚举从 0 开始。
系统日志
如果没有其他办法,可以查看系统日志/日志来导出映射。
设备/dev/sdY
的创建顺序与 ataX 标识符的枚举顺序相同,同时kern.log
忽略非磁盘设备 (ATAPI) 和未连接的链路。
因此,以下命令显示映射:
$ grep '^May 28 2' /var/log/kern.log.0 | \
grep 'ata[0-9]\+.[0-9][0-9]: ATA-' | \
sed 's/^.*\] ata//' | \
sort -n | sed 's/:.*//' | \
awk ' { a="ata" $1; printf("%10s is /dev/sd%c\n", a, 96+NR); }'
ata1.00 is /dev/sda
ata3.00 is /dev/sdb
ata5.00 is /dev/sdc
ata7.00 is /dev/sdd
ata8.00 is /dev/sde
ata10.00 is /dev/sdf
(请注意,不会显示 ata4,因为以上日志消息来自另一个系统。)
我正在使用/var/log/kern.log.0
而不是/var/log/kern.log
因为启动消息已经轮换了。我 grep 是May 28 2
因为这是最后一次启动时间,我想忽略以前的消息。
要验证映射,您可以通过查看以下输出进行一些检查:
$ grep '^May 28 2' /var/log/kern.log.0 | \
grep 'ata[0-9]\+.[0-9][0-9]: ATA-'
May 28 20:43:26 hn kernel: [ 1.260488] ata1.00: ATA-7: SAMSUNG SV0802N, max UDMA/100
May 28 20:43:26 hn kernel: [ 1.676400] ata5.00: ATA-5: ST380021A, 3.19, max UDMA/10
[..]
您可以将此输出与hdparm
输出进行比较,例如:
$ hdparm -i /dev/sda
/dev/sda:
Model=SAMSUNG SV0802N [..]
(使用内核2.6.32-31)
答案2
这是我的版本,是在上面修改的。由于我不知道系统启动的确切日期(为了测试它是 27 天前),并且我不知道哪个 kern.log 包含我需要的数据(有些可能gzipped
在我的系统上),所以我使用uptime
并date
计算大致的系统启动日期(无论如何,到当天),然后用于zgrep
搜索所有可用的 kern.log 文件。
我还稍微修改了第二条grep
语句,因为它现在还将显示 ATAPI CD/DVD 驱动器以及 ATA-* 驱动器。
它仍然可以使用细化(即,如果系统正常运行时间超过一年),但目前应该可以正常工作。
#!/bin/bash
uptime=$(uptime | awk -F' ' '{ print $3" "$4 }' | sed s/,//)
date=$(date -d "$uptime ago" | awk '{print $2" "$3 }')
zgrep "$date" /var/log/kern.log* | \
grep 'ata[0-9]\+.[0-9][0-9]: ATA' | \
sed 's/^.*\] ata//' | \
sort -n | sed 's/:.*//' | \
awk ' { a="ata" $1; printf("%10s is /dev/sd%c\n", a, 96+NR); }'
答案3
刚刚遇到了同样的问题,并找到了另一种可能会喜欢的解决方案。
lsscsi 工具列出 SCSI 设备(或主机)及其属性。
使用 lsscsi 可以获取 ata 名称和设备名称。
看起来像这样:
$ lsscsi --long
[0:0:1:0] cd/dvd MATSHITA DVD-ROM UJDA780 1.50 /dev/sr0
state=running queue_depth=1 scsi_level=6 type=5 device_blocked=0 timeout=30
[2:0:0:0] disk ATA WDC WD3000FYYZ-0 01.0 /dev/sda
state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30
[3:0:0:0] disk ATA WDC WD1002FBYS-0 03.0 /dev/sdb
state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30
[4:0:0:0] disk ATA WDC WD1002FBYS-0 03.0 /dev/sdc
state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30
[5:0:0:0] disk ATA WDC WD1002FBYS-0 03.0 /dev/sdd
state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30
[6:0:0:0] disk ATA WDC WD3000FYYZ-0 01.0 /dev/sde
state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30
[7:0:0:0] disk ATA WDC WD1002FBYS-0 03.0 /dev/sdf
state=running queue_depth=1 scsi_level=6 type=0 device_blocked=0 timeout=30
在 Ubuntu 上,可以简单地安装 lsscsi
$ sudo apt-get install lsscsi
答案4
上述答案都不适合我,而且由于 SCSI 总线编号和 ATA 编号之间的差异,lsscsi 方法实际上产生了错误的答案。在 21 个磁盘的系统上,我收到了许多有关 ATA18 问题(HSM 违规)的系统日志报告。哪个磁盘导致了这些错误?有些是 USB 驱动器,这让事情变得更加混乱。我需要统计每个 SCSI 驱动器如何连接到系统,我编写了下面的脚本,生成所有 SCSI 磁盘 (/dev/s[dr]?) 的表格列表,无论是 ATA 还是 USB。
然后,在完全考虑所有磁盘驱动器的情况下,我惊讶地发现我的 ATA 错误与任何我的磁盘驱动器。我一直在问错误的问题,我认为其他人很容易陷入同样的陷阱,这就是我在这里提到的原因。然后,我使用了第二种方法来识别生成 HSM 违规消息的硬件,下面的脚本中出现的文档也详细介绍了这一点。
#!/bin/bash
## This script lists the ata and usb bus numbers, as well as the
## overall "host" numbers, of each scsi disk. The same information
## appears formatted four ways, redundantly, for ease of lookup by (1)
## device lettername, (2) ata bus, (3) usb bus, or (4) overall "host"
## number.
#######################################################
## Q: What if you're looking for an ATA bus number, e.g. ata18, that
## isn't listed by this script?
## (1) Well, it's probably not a SCSI disk, at least not one that's
## operating.
## (2) Somewhere in /sys you can find a mapping from the ATA bus
## number to some overall host number, such as host17. For example,
## if you're looking for ata18, you can use a find command...
## find /sys -type l -exec bash -c 'link=`readlink "$0"`; if [[ "$link" =~ /ata18/ ]] ; then echo $link ; fi' {} \;
## ...which, after some delay, might yield output something like this:
## ../../devices/pci0000:00/0000:00:02.0/0000:02:00.0/ata18/ata_port/ata18
## ../../devices/pci0000:00/0000:00:02.0/0000:02:00.0/ata18/host17/target17:0:0/17:0:0:0/scsi_generic/sg5
## ../../devices/pci0000:00/0000:00:02.0/0000:02:00.0/ata18/link18/dev18.0/ata_device/dev18.0
## ../../devices/pci0000:00/0000:00:02.0/0000:02:00.0/ata18/host17/scsi_host/host17
## ../../devices/pci0000:00/0000:00:02.0/0000:02:00.0/ata18/link18/ata_link/link18
## ../../devices/pci0000:00/0000:00:02.0/0000:02:00.0/ata18/host17/target17:0:0/17:0:0:0/bsg/17:0:0:0
## ../../devices/pci0000:00/0000:00:02.0/0000:02:00.0/ata18/host17/target17:0:0/17:0:0:0/scsi_device/17:0:0:0
## ../../devices/pci0000:00/0000:00:02.0/0000:02:00.0/ata18/host17/target17:0:0/17:0:0:0/scsi_generic/sg5
## ../../devices/pci0000:00/0000:00:02.0/0000:02:00.0/ata18/host17/target17:0:0/17:0:0:0/bsg/17:0:0:0
## ../../../devices/pci0000:00/0000:00:02.0/0000:02:00.0/ata18/host17/target17:0:0/17:0:0:0
## ../../../devices/pci0000:00/0000:00:02.0/0000:02:00.0/ata18/host17
## ../../../devices/pci0000:00/0000:00:02.0/0000:02:00.0/ata18/host17/target17:0:0
## Then you might notice the "/host17/" or "scsi_device/17:0:0:0"
## in the above output lines, and look in the output of...
## lshw
## .. for "scsi17" or "17:0" or such, and discover, somewhere in it ...
## ...
## *-scsi:5
## physical id: 8
## logical name: scsi17
## capabilities: emulated
## *-processor UNCLAIMED
## description: SCSI Processor
## product: 91xx Config
## vendor: Marvell
## physical id: 0.0.0
## bus info: scsi@17:0.0.0
## version: 1.01
## capabilities: removable
## configuration: ansiversion=5
## ...
## ...thus learning that ata18 corresponds to an unclaimed device (but
## not actually a disk). Q.E.D.
## P.S. the lsscsi command yields the following, which might lead
## one to think that the problem was being caused by a CD-ROM drive
## (SCSI18:0) rather than emanating from the Marvell (SCSI17:0):
## [17:0:0:0] process Marvell 91xx Config 1.01 -
## [18:0:0:0] cd/dvd HL-DT-ST DVDRAM GH22NS90 HN00 /dev/sr0
## ... but ATA != SCSI, and 17 != 18. The CD/DVD drive was ATA19,
## actually. You can still use lsscsi, but
## bear in mind that what you're seeing in the left column
## is *not* ATA numbers but rather SCSI bus numbers, and the two
## are not to be confused.
#######################################################
blockDevsDir=/sys/dev/block
declare -A scsiDevLetters
declare -A hostNumbers
declare -A ataNumbers
declare -A usbNumbers
scsiDevLetterRE='/s(d[a-z]|r[0-9])$'
hostNumberRE='/host([0-9]+)/'
ataNumberRE='/ata([0-9]+)/'
usbNumberRE='/usb([0-9]+)/'
cd "$blockDevsDir"
for busid in `ls -1` ; do
linkval=`readlink "$busid" `
if [[ "$linkval" =~ $scsiDevLetterRE ]] ; then
scsiDevLetter="${BASH_REMATCH[1]}"
if [[ "$linkval" =~ $hostNumberRE ]] ; then
hostNumber="${BASH_REMATCH[1]}"
if [[ "$linkval" =~ $ataNumberRE ]] ; then
ataNumber="${BASH_REMATCH[1]}"
scsiDevLetters[$scsiDevLetter]=`printf 'ata%-2.2s host%-2.2s' "${ataNumber}" "${hostNumber}"`
hostNumbers[${hostNumber}]=`printf '/dev/sd%s ata%-2.2s' "${scsiDevLetter}" "${ataNumber}"`
ataNumbers[${ataNumber}]=`printf '/dev/sd%s host%-2.2s' "${scsiDevLetter}" "${hostNumber}"`
elif [[ "$linkval" =~ $usbNumberRE ]] ; then
usbNumber="${BASH_REMATCH[1]}"
scsiDevLetters[$scsiDevLetter]=`printf 'usb%-2.2s host%-2.2s' "${usbNumber}" "${hostNumber}"`
hostNumbers[${hostNumber}]=`printf '/dev/sd%s usb%-2.2s' "${scsiDevLetter}" "${usbNumber}"`
existingUsbValue="${usbNumbers[${usbNumber}]}"
addedUsbValue=`printf '/dev/sd%s host%-2.2s' "${scsiDevLetter}" "${hostNumber}"`
if [ -n "$existingUsbValue" ] ; then
usbNumbers[${usbNumber}]="$existingUsbValue | $addedUsbValue"
else
usbNumbers[${usbNumber}]="$addedUsbValue"
fi
else
echo "Neither ata nor usb: /dev/sd${scsiDevLetter} (host${hostNumber}) !"
fi
else
echo "No host number for /dev/sd${scsiDevLetter}"
fi
fi
done
echo '/dev/sd?'
echo '--------'
for scsiDevLetter in `echo "${!scsiDevLetters[*]}" | tr ' ' '\n' | sort` ; do
echo "/dev/sd${scsiDevLetter} ${scsiDevLetters[$scsiDevLetter]}"
done
echo
echo 'ataNN'
echo '-----'
for ataNumber in `echo "${!ataNumbers[*]}" | tr ' ' '\n' | sort -n` ; do
printf 'ata%-2.2s %s\n' "$ataNumber" "${ataNumbers[$ataNumber]}"
done
echo
echo 'usbNN'
echo '-----'
for usbNumber in `echo "${!usbNumbers[*]}" | tr ' ' '\n' | sort -n` ; do
printf 'usb%-2.2s %s\n' "$usbNumber" "${usbNumbers[$usbNumber]}"
done
echo
echo 'hostNN'
echo '------'
for hostNumber in `echo "${!hostNumbers[*]}" | tr ' ' '\n' | sort -n` ; do
printf 'host%-2.2s %s\n' "$hostNumber" "${hostNumbers[$hostNumber]}"
done