Re: SCSI opcode 0x80 and 3ware Escalade 7000 ATA RAID

2005-04-16 Thread Jurgen Kramer
On Fri, 2005-04-15 at 18:26 -0400, Kyle Moffett wrote: > I've been getting the following message in syslog on a couple of my > servers > recently: > > > Apr 15 16:41:18 king kernel: scsi: unknown opcode 0x80 I now am seeing the same error messages on my 3ware 9000 controller running kernel

Re: SCSI opcode 0x80 and 3ware Escalade 7000 ATA RAID

2005-04-16 Thread Jurgen Kramer
On Fri, 2005-04-15 at 18:26 -0400, Kyle Moffett wrote: I've been getting the following message in syslog on a couple of my servers recently: Apr 15 16:41:18 king kernel: scsi: unknown opcode 0x80 I now am seeing the same error messages on my 3ware 9000 controller running kernel 2.6.11

Re: SCSI opcode 0x80 and 3ware Escalade 7000 ATA RAID

2005-04-15 Thread Kyle Moffett
On Apr 15, 2005, at 18:50, adam radford wrote: Make sure you are are using the 3ware character ioctl interface at /dev/twe0 (dynamic major, controller number minor) for your smartmontools, not /dev/sda. Hmm, I don't have any /dev/twe* here. I _do_ have hotplug, udev, etc, installed, and this is a

Re: SCSI opcode 0x80 and 3ware Escalade 7000 ATA RAID

2005-04-15 Thread adam radford
Make sure you are are using the 3ware character ioctl interface at /dev/twe0 (dynamic major, controller number minor) for your smartmontools, not /dev/sda. i.e. smartctl -a -d 3ware,X /dev/tweY where X = port # of the drive whose information you want, Y=controller #. The old interface from

SCSI opcode 0x80 and 3ware Escalade 7000 ATA RAID

2005-04-15 Thread Kyle Moffett
I've been getting the following message in syslog on a couple of my servers recently: Apr 15 16:41:18 king kernel: scsi: unknown opcode 0x80 I've tracked it down to the SCSI opcode verification patch that went in a while back. I also determined that the trigger was our smartd/smartctl runs,

SCSI opcode 0x80 and 3ware Escalade 7000 ATA RAID

2005-04-15 Thread Kyle Moffett
I've been getting the following message in syslog on a couple of my servers recently: Apr 15 16:41:18 king kernel: scsi: unknown opcode 0x80 I've tracked it down to the SCSI opcode verification patch that went in a while back. I also determined that the trigger was our smartd/smartctl runs,

Re: SCSI opcode 0x80 and 3ware Escalade 7000 ATA RAID

2005-04-15 Thread adam radford
Make sure you are are using the 3ware character ioctl interface at /dev/twe0 (dynamic major, controller number minor) for your smartmontools, not /dev/sda. i.e. smartctl -a -d 3ware,X /dev/tweY where X = port # of the drive whose information you want, Y=controller #. The old interface from

Re: SCSI opcode 0x80 and 3ware Escalade 7000 ATA RAID

2005-04-15 Thread Kyle Moffett
On Apr 15, 2005, at 18:50, adam radford wrote: Make sure you are are using the 3ware character ioctl interface at /dev/twe0 (dynamic major, controller number minor) for your smartmontools, not /dev/sda. Hmm, I don't have any /dev/twe* here. I _do_ have hotplug, udev, etc, installed, and this is a