lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 30 Aug 2012 18:14:46 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...i.de>
To:	Andy Lutomirski <luto@...capital.net>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-ide@...r.kernel.org, Bjoern Franke <bjo@...d-west.org>,
	Borislav Petkov <bp@...en8.de>,
	Tim Nufire <linux_ide_tim@...nk.com>
Subject: Re: Which disk is ata4?

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ