Re: SMART support for SATA drives in SAS enclosures
Douglas Gilbert wrote: For recent versions of smartmontools version 5.37 and MPT Fusion SAS HBAs this should work if /dev/sdc is a SATA disk. Your HBA may need a firmware upgrade. You might fetch sg3_utils version 1.24 and try: sg_sat_identify /dev/sdc That needs to work before smartctl has a hope. Indeed, a firmware update made sg_sat_identify and the smartmontools work as advertised. Thanks, Pim - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: SMART support for SATA drives in SAS enclosures
Doug, /dev/sdc is indeed a physical SATA disk. sg_sat_identify says: ATA PASS-THROUGH (16) not supported I'll look into a firmware update. Thanks, Pim Douglas Gilbert wrote: Pim Zandbergen wrote: Is SMART support available for SATA drives in SAS enclosures? I'm testing this setup LSI Logic SAS3800X PCI-X SAS controller (mptsas driver) Promise V-Trak J300S SAS/SATA enclosure/expander 12x Seagate ST3500630NS Linux kernel 2.6.21.1 x86_64 smartmontools-5.37-1.1.fc6 from Fedora Core 6 smartctl -i -d sat /dev/sdc gives me Smartctl: Device Read Identity Failed I presume /dev/sdc is an actual disk rather than a RAID device made up of several disks. The SAT standard (and smartmontools) don't have a general way of addressing individual disks behind RAID infrastructure. For recent versions of smartmontools version 5.37 and MPT Fusion SAS HBAs this should work if /dev/sdc is a SATA disk. Your HBA may need a firmware upgrade. You might fetch sg3_utils version 1.24 and try: sg_sat_identify /dev/sdc That needs to work before smartctl has a hope. Same with -d ata. If I treat the disk as SCSI (-d scsi), the command will not fail, but wil only retrieve the serial number. With MPT Fusion SAS hardware (that I have seen) the SAT layer is in the HBA firmware. Only later versions of the firmware support the SCSI ATA PASS-THROUGH command. Doug Gilbert - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
SMART support for SATA drives in SAS enclosures
Is SMART support available for SATA drives in SAS enclosures? I'm testing this setup LSI Logic SAS3800X PCI-X SAS controller (mptsas driver) Promise V-Trak J300S SAS/SATA enclosure/expander 12x Seagate ST3500630NS Linux kernel 2.6.21.1 x86_64 smartmontools-5.37-1.1.fc6 from Fedora Core 6 smartctl -i -d sat /dev/sdc gives me Smartctl: Device Read Identity Failed Same with -d ata. If I treat the disk as SCSI (-d scsi), the command will not fail, but wil only retrieve the serial number. Thanks, Pim - To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH] aic94xx: add PCI ID 9005:0416
I just received the retail version of an Adaptec 58300 PCI-X SAS adapter
with PCI ID 9005:0416.
Here's the lspci -vvn output:
03:08.0 Class 0107: 9005:0416 (rev 09)
Subsystem: 9005:0416
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=slow TAbort- TAbort-
MAbort- SERR- PERR-
Latency: 32 (32000ns min, 26750ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fe70 (64-bit, non-prefetchable) [size=256K]
Region 2: Memory at fe50 (64-bit, prefetchable) [size=128K]
Region 4: I/O ports at bc00 [size=256]
Expansion ROM at fe60 [disabled] [size=512K]
Capabilities: [40] PCI-X non-bridge device.
Command: DPERE- ERO- RBC=3 OST=4
Status: Bus=255 Dev=31 Func=0 64bit+ 133MHz+ SCD- USC-,
DC=simple, DMMRBC=3, DMOST=4, DMCRS=4, RSCEM-
Capabilities: [58] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [e0] Message Signalled Interrupts: 64bit+ Queue=0/2
Enable-
Address: Data:
The aic94xx driver in kernel 2.6.21.1 does not recognize the card.
With following patch it does:
--- linux-2.6.21.1.orig/drivers/scsi/aic94xx/aic94xx_hwi.h 2007-05-10
18:29:38.0 +0200
+++ linux-2.6.21.1/drivers/scsi/aic94xx/aic94xx_hwi.h 2007-05-03
22:42:35.0 +0200
@@ -45,6 +45,7 @@
*/
#define PCI_DEVICE_ID_ADAPTEC2_RAZOR10 0x410
#define PCI_DEVICE_ID_ADAPTEC2_RAZOR12 0x412
+#define PCI_DEVICE_ID_ADAPTEC2_RAZOR16 0x416
#define PCI_DEVICE_ID_ADAPTEC2_RAZOR1E 0x41E
#define PCI_DEVICE_ID_ADAPTEC2_RAZOR1F 0x41F
#define PCI_DEVICE_ID_ADAPTEC2_RAZOR30 0x430
--- linux-2.6.21.1.orig/drivers/scsi/aic94xx/aic94xx_init.c 2007-05-10
18:30:14.0 +0200
+++ linux-2.6.21.1/drivers/scsi/aic94xx/aic94xx_init.c 2007-05-03
22:43:29.0 +0200
@@ -837,6 +837,8 @@
0, 0, 1},
{PCI_DEVICE(PCI_VENDOR_ID_ADAPTEC2, PCI_DEVICE_ID_ADAPTEC2_RAZOR12),
0, 0, 1},
+ {PCI_DEVICE(PCI_VENDOR_ID_ADAPTEC2, PCI_DEVICE_ID_ADAPTEC2_RAZOR16),
+0, 0, 1},
{PCI_DEVICE(PCI_VENDOR_ID_ADAPTEC2, PCI_DEVICE_ID_ADAPTEC2_RAZOR1E),
0, 0, 1},
{PCI_DEVICE(PCI_VENDOR_ID_ADAPTEC2, PCI_DEVICE_ID_ADAPTEC2_RAZOR1F),
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
