Solved [Solved] LSI 9211-4i multiple errors

Melchior

Melchior

Hi everybody,

I have a Intel SR1530SH with a LSI 9211-4i.
I use FreeBSD 10.0-p8

In the dmesg, I have this errors:

Code: 
Sep 14 21:23:16 turing kernel: mps0: <LSI SAS2004> port 0x2000-0x20ff mem 0xe1a40000-0xe1a43fff,0xe1a00000-0xe1a3ffff irq 16 at device 0.0 on pci1
Sep 14 21:23:16 turing kernel: mps0: Firmware: 19.00.00.00, Driver: 16.00.00.00-fbsd
Sep 14 21:23:16 turing kernel: mps0: IOCCapabilities: 185c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,IR>
[...]
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:0): INQUIRY. CDB: 12 00 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:0): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:0): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:0): INQUIRY. CDB: 12 00 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:0): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:0): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:0): INQUIRY. CDB: 12 00 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:0): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:0): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:0): INQUIRY. CDB: 12 00 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:0): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:0): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:1): INQUIRY. CDB: 12 20 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:1): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:1): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:1): INQUIRY. CDB: 12 20 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:1): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:1): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:2:1): INQUIRY. CDB: 12 20 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:2:1): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:2:1): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:1): INQUIRY. CDB: 12 20 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:1): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:1): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:2): INQUIRY. CDB: 12 40 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:2): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:2): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:2): INQUIRY. CDB: 12 40 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:2): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:2): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:2): INQUIRY. CDB: 12 40 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:2): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:2): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:2): INQUIRY. CDB: 12 40 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:2): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:2): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:3): INQUIRY. CDB: 12 60 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:3): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:3): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:3): INQUIRY. CDB: 12 60 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:3): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:3): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:2:3): INQUIRY. CDB: 12 60 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:2:3): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:2:3): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:3): INQUIRY. CDB: 12 60 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:3): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:3): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:4): INQUIRY. CDB: 12 80 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:4): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:4): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:4): INQUIRY. CDB: 12 80 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:4): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:4): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:4): INQUIRY. CDB: 12 80 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:4): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:4): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:4): INQUIRY. CDB: 12 80 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:4): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:4): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:5): INQUIRY. CDB: 12 a0 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:5): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:5): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:5): INQUIRY. CDB: 12 a0 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:5): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:5): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:2:5): INQUIRY. CDB: 12 a0 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:2:5): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:2:5): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:5): INQUIRY. CDB: 12 a0 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:5): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:5): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:6): INQUIRY. CDB: 12 c0 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:6): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:6): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:6): INQUIRY. CDB: 12 c0 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:6): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:6): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:6): INQUIRY. CDB: 12 c0 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:6): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:2:6): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:6): INQUIRY. CDB: 12 c0 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:6): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:3:6): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:7): INQUIRY. CDB: 12 e0 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:7): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe3:mps0:0:2:7): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:7): INQUIRY. CDB: 12 e0 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:7): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:7): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:2:7): INQUIRY. CDB: 12 e0 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:2:7): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe1:mps0:0:2:7): Error 22, Unretryable error
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:7): INQUIRY. CDB: 12 e0 00 00 24 00 
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:7): CAM status: Invalid Target ID
Sep 14 21:23:16 turing kernel: (probe0:mps0:0:3:7): Error 22, Unretryable error
And this:

Code: 
Sep 14 21:23:16 turing kernel: da0 at mps0 bus 0 scbus0 target 0 lun 0
Sep 14 21:23:16 turing kernel: da0: <LSI Logical Volume 3000> Fixed Direct Access SCSI-6 device 
Sep 14 21:23:16 turing kernel: da0: Serial Number   400808689134493729
Sep 14 21:23:16 turing kernel: da0: 150.000MB/s transfers
Sep 14 21:23:16 turing kernel: da0: Command Queueing enabled
Sep 14 21:23:16 turing kernel: da0: 1906394MB (3904294912 512 byte sectors: 255H 63S/T 243031C)
The LSI card 9211-4i lets have SATA-II (300MB/s), but as shown above, it uses the SATA-I (150MB/s) ... The problem would come about the driver?
PS: The two hard drives are WD RE4 GP @ 2TB!


EDIT:

For the first error block, I installed the latest version of the driver by following this procedure and this is the result:

Code: 
Sep 15 00:05:28 turing kernel: mpslsi0: <LSI SAS2004> port 0x2000-0x20ff mem 0xe1a40000-0xe1a43fff,0xe1a00000-0xe1a3ffff irq 16 at device 0.0 on pci1
Sep 15 00:05:28 turing kernel: mpslsi0: Firmware: 19.00.00.00, Driver: 19.00.00.00
Sep 15 00:05:28 turing kernel: mpslsi0: IOCCapabilities: 185c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,IR>
[...]
Sep 15 00:05:28 turing kernel: da0 at mpslsi0 bus 0 scbus0 target 0 lun 0
Sep 15 00:05:28 turing kernel: da0: <LSI Logical Volume 3000> Fixed Direct Access SCSI-6 device 
Sep 15 00:05:28 turing kernel: da0: Serial Number   400808689134493729
Sep 15 00:05:28 turing kernel: da0: 150.000MB/s transfers
Sep 15 00:05:28 turing kernel: da0: Command Queueing enabled
Sep 15 00:05:28 turing kernel: da0: 1906394MB (3904294912 512 byte sectors: 255H 63S/T 243031C)
I have no error message: (probe3:mps0:0:2:5): CAM status: Invalid Target ID :beergrin
But the transfer rate is still stuck in SATA-I (150MB/s) :(

Do you have an idea?

Thank you in advance for your lights!


Best regards, Melchior
 
Re: LSI 9211-4i multiple errors

Melchior said:
But the transfer rate is still stuck in SATA-I (150MB/s) :(
Click to expand...

The Western Digital RE4, 2 TB (WD2002FYPS) has a max read/write throughput of 110 MB/s.
 
Re: LSI 9211-4i multiple errors

User23 said:
Melchior said:
But the transfer rate is still stuck in SATA-I (150MB/s) :(
Click to expand...

The Western Digital RE4, 2 TB (WD2002FYPS) has a max read/write throughput of 110 MB/s.
Click to expand...
http://www.wdc.com/wdproducts/library/a ... 771113.pdf

When I see something written I like it when it's the same thing on my system!

Although the rate of writing/reading is 110MB/s system see why discs SATA I instead of the SATA II?

When I buy a BMW ///M5, I like everything to be as a ///M5 ;)


Best regards, Melchior
 
Re: LSI 9211-4i multiple errors

Is it jumpered to use a slower speed? The manual says a jumper on pins 5-6 sets it to the slower communication speed. Although, as @User23 says, that's still faster than the drive can transfer data from the disk.
 
Last edited by a moderator:
Re: LSI 9211-4i multiple errors

wblock@ said:
Is it jumpered to use a slower speed? The manual says a jumper on pins 5-6 sets it to the slower communication speed. Although, as @User23 says, that's still faster than the drive can transfer data from the disk.
Click to expand...
Many of our drivers simply make up a speed and report it. Years ago I submitted patches for this for a number of controllers, but they pre-date the CAM and AHCI changes and appear to have been dropped. In the case of the OP, the issue is here, in mpt_sas.c:

Code: 
                strncpy(cpi->sim_vid, "FreeBSD", SIM_IDLEN);
                strncpy(cpi->hba_vid, "LSILogic", HBA_IDLEN);
                strncpy(cpi->dev_name, cam_sim_name(sim), DEV_IDLEN);
                cpi->unit_number = cam_sim_unit(sim);
                cpi->bus_id = cam_sim_bus(sim);
                cpi->base_transfer_speed = 150000;                                      <--- hard-coded value
                cpi->transport = XPORT_SAS;
                cpi->transport_version = 0;
                cpi->protocol = PROTO_SCSI;
                cpi->protocol_version = SCSI_REV_SPC;

If the drive in question is really a SAS drive and not a SATA one, you can get the actual speed with smartctl -x:

Code: 
Protocol Specific port log page for SAS SSP
relative target port id = 1
  generation code = 0
  number of phys = 1
  phy identifier = 0
    attached device type: SAS or SATA device
    attached reason: unknown
    reason: unknown
    negotiated logical link rate: phy enabled; 6 Gbps                                   <--- actual transfer rate
    attached initiator port: ssp=1 stp=1 smp=1
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5000c5003b5524dd
    attached SAS address = 0x5842b2b065161905
    attached phy identifier = 7
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization = 0
    Phy reset problem = 0
    Phy event descriptors:
     Invalid word count: 0
     Running disparity error count: 0
     Loss of dword synchronization count: 0
     Phy reset problem count: 0

This is by no means limited to the mps(4) driver. mfi(4) and twa(4) definitely have the same problem, and likely others as well.
 
Last edited by a moderator:
Re: LSI 9211-4i multiple errors

My problem is solved, not completely but almost!

I destroyed my RAID array. I start with my CD and I install FreeBSD!

Nice job my dear! :f

I run dmesg and ... TADAAA :beergrin

Code: 
da0 at mps0 bus 0 scbus0 target 0 lun 0
da0: <ATA WDC WD2002FYPS-0 1G01> Fixed Direct Access SCSI-6 device
da0: Serial Number      WD-WCAVY6489470
da0: 300.000MB/s transfers
da0: Command Queueing enabled
da0: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C)
da1 at mps0 bus 0 scbus0 target 1 lun 0
da1: <ATA WDC WD2002FYPS-0 1G01> Fixed Direct Access SCSI-6 device
da1: Serial Number      WD-WCAVY6554855
da1: 300.000MB/s transfers
da1: Command Queueing enabled
da1: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C)
The problem is with the RAID card, even if it is flashed, installed with the correct drivers, the RAID card shows that it's SATA I when I created a RAID 1 or 0...

Now, I use the LSI's IT firmware and i create a RAID 1 with ZFS!

By doing this I also noticed that I no longer had my freezes on the screen!


Best regards, Melchior
 
You must log in or register to reply here.
Back
Top