On Thu, Aug 30, 2012 at 1:49 AM, Bjoern Franke <b...@nord-west.org> wrote: > Am Mittwoch, den 29.08.2012, 21:38 -0700 schrieb Andy Lutomirski: >> One of my disks went out to lunch for a while. Logs below. > > dmesg | grep ata4 > > for instance with ata1: > [root@ostrea][/]# dmesg | grep ata1 > ata1.00: ATA-7: SAMSUNG MP0402H, UC200-16, max UDMA/100
I tried that, too. $ dmesg |grep ST3000DM001-9YN166 [ 1.064910] ata5.00: ATA-8: ST3000DM001-9YN166, CC4B, max UDMA/133 [ 1.064926] ata3.00: ATA-8: ST3000DM001-9YN166, CC4B, max UDMA/133 [ 1.064986] ata2.00: ATA-8: ST3000DM001-9YN166, CC4B, max UDMA/133 [ 1.065012] ata4.00: ATA-8: ST3000DM001-9YN166, CC4B, max UDMA/133 [ 1.235753] ata7.00: ATA-8: ST3000DM001-9YN166, CC4B, max UDMA/133 [ 1.727000] ata8.00: ATA-8: ST3000DM001-9YN166, CC4B, max UDMA/133 This is unhelpful. Also, the dmesg lines are nicely interleaved, making it rather hard to line up ataN lines with sdX lines. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/