On Thursday 2012-08-30 06:38, Andy Lutomirski wrote:
>One of my disks went out to lunch for a while. Logs below.
>
>[784786.047673] ata4.00: exception Emask 0x10 SAct 0x7800 SErr 0x0
>action 0x6 frozen
>
>Which one is it? The only useful thing in /sys/class/ata_port/ata4 is
>the device symlink, which points at
>/sys/devices/pci0000:00/0000:00:1f.2/ata4.
For example, ata2 here:
$ cd /sys/devices
$ find . -name ata2
./pci0000:00/0000:00:1f.2/ata2
./pci0000:00/0000:00:1f.2/ata2/ata_port/ata2
$ cd ./pci0000:00/0000:00:1f.2/ata2
$ ls -dl host*/targ*
drwxr-xr-x 4 root root 0 Aug 30 18:09 host1/target1:0:0
$ lsscsi
[0:0:0:0] disk ATA ST3000DM001-9YN1 CC4C /dev/sda
[1:0:0:0] disk ATA ST3000DM001-9YN1 CC4C /dev/sdb
# sdparm -i /dev/sdb
/dev/sdb: ATA ST3000DM001-9YN1 CC4C
Device identification VPD page:
Addressed logical unit:
designator type: vendor specific [0x0], code set: ASCII
vendor specific: Z1F0KR3H
designator type: T10 vendor identification, code set: ASCII
vendor id: ATA
vendor specific: ST3000DM001-9YN166
Z1F0KR3H
designator type: NAA, code set: Binary
0x5000c500408f772f
This tells me everything to replace a disk.
1. sdparm -C stop /dev/sdb
2. Removing Z1F0KR3H from the chassis.
3. Put new disk in..
(4. Profit.)
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
