ata8 = ??
Hi all,
Spent some time searching for this. I figured there must be an easy way to work this out. I have mentions of ata1 and ata8 in my messages log, like "ata8: hard resetting link" How does one map ata8 to a real disk? I can not find anything in /dev/disk, not fdisk or lshw. The only way I found was grepping through dmesg and you get a serial which you can then use lshw to find out. But is this the only way? Thanks for any info. |
I had a similar problem with a squizillion ata4 error messages along the same lines. The trouble was that I had 6 identical disks in the system, so model numbers were useless.
When the disk eventually "died" (and I use that term loosely, because it didn't actually die - the SATA cable was dodgy), the activity light was permanently on for that disk - which turned out to be /dev/sdb. Amusingly, with a different kernel version (or maybe it was a distro update, I forget specifically) the disks were /dev/sdb-/dev/sdg instead of /dev/sda-/dev/sdf. <shrugs> I only just found the use of using dmesg and smartctl to correlate the data myself. Wish I knew some logic behind the ataX numbering... |
Frustrating indeed.
I was hoping for a symlink mapping like what is found in /dev/disk. |
I have since worked this out.
It turns out that these devices are Device Mapper (DM) devices. To work them out you need to run Code:
lvdisplay Code:
Block Device Code:
253:3 Code:
ata3 |
All times are GMT -5. The time now is 07:18 PM. |