Supermicro AOC-USAS-L8i UIO 8 port sas/sata card

[FatBoyNotSoSlim]

Guys, does this only affect a raid 6 (i've seen this mentioned specifically a lot) array, or any array with drives from the card? As my USAS-L8i arrived this morning, yet to unpack it, and I'm running Ubuntu 9.04 right now...

After a failed attempt to use a perc5, not being able to use the L8i is not desireable. I just want to add more drives to my existing mdadm array.

[Dragon_191]

The driver was one of the things I updated when I was having problems:

storage:~ # cat /proc/mpt/version
mptlinux-4.00.43.00suse
Fusion MPT base driver
Fusion MPT SAS host driver
Fusion MPT ioctl driver

[davros123]

Metal, yes, please do recompile and let us know how you go.

Is there adummies guide on how to recompile this for ubuntu 9.10?h

[FatBoyNotSoSlim]

Originally Posted by Dragon_191

The driver was one of the things I updated when I was having problems:

Did it fix your problems? Or was it just one of the things done at random that helped you out?

[Dragon_191]

Originally Posted by FatBoyNotSoSlim

Did it fix your problems? Or was it just one of the things done at random that helped you out?

yeah, not sure exactly what fixed my problem, but definitely think the newer driver helped.

[Rampage101]

Where can one fine the updated source driver? My l33t Google skills have failed me.

[FatBoyNotSoSlim]

Originally Posted by Rampage101

Where can one fine the updated source driver? My l33t Google skills have failed me.

From that blog post that MetalPhreak posted a few posts ago: http://www.lsi.com/storage_home/prod...te=1&locale=EN which found me the correct chipset page: http://www.lsi.com/storage_home/prod...68e/index.html Since the L8i has a LSISAS 1068E SAS controller.

I'm not sure what chipset the card has though, since I just got it this morning myself.

NB, does the card need a firmware update? I cant remember if I was reading it about the L8i or the Perc5 card, but arent their different firmwares like LBA/IT/other acronym?

[Rampage101]

IT is one mode, there are 2 others. But updated firmware makes no difference, as I already had it.

[FatBoyNotSoSlim]

Originally Posted by Rampage101

IT is one mode, there are 2 others. But updated firmware makes no difference, as I already had it.

Ok. I found the correct link in the my previous, edited, post.

NB, I found what i was looking for: IT, IR and SR modes... Which I now have to google to see WTF they mean.

[Rampage101]

Found it, 150mb download for a 300kb source file inside

[MetalPhreak]

I can't get it to compile from source

http://pastebin.com/m196e84fc

I have no clue what's happening. If anyone could help I'd appreciate it

[Rampage101]

Think its the way your doing it. From the mptlinux.txt file:

------ Driver Build Instructions

The following examples show how to configure and build the LSI Logic
Fusion-MPT driver(s) as kernel modules. However, the MPT base and ScsiHost
drivers can alternatively be compiled into the Linux kernel instead of
being built as modules.

1.  From the /usr/src/linux directory, ensure a clean kernel source
    tree by executing the following command:
        # make mrproper

2.  From the /usr/src/linux directory, run the normal kernel
    configuration routine:
        # make oldconfig
      or:
        # make config
      or:
        # make menuconfig
      or:
        # make xconfig

3.  Look for the new top-level "Fusion-MPT device support" entry:
        Fusion-MPT device support  --->
      and select it to access the Fusion-MPT drivers submenu entries:
        <M> Fusion-MPT (base + ScsiHost) drivers
        <M>   Enhanced SCSI error reporting
        < >   Fusion-MPT misc device (ioctl) driver
        < >   Fusion-MPT LAN driver

      On the submenu, select the "Fusion-MPT (base + ScsiHost) drivers" line,
      and then enter "m" to configure for building this support as a module.
      (Alternatively, you can enter "y" to have this support built
      into the kernel.)

      NOTES:
       o  Enhanced SCSI error reporting and ioctl drivers are optional.
          LSI Logic recommends that they only be built as modules,
          due to kernel size considerations.
       o  DO NOT answer "y" for the Fusion-MPT LAN driver option! Support
          for this driver is currently restricted to module use only.

4.  For LAN support, make sure that "Fibre Channel driver support" is turned
    on in the "Network device support" section.

5.  Save the kernel config changes.  Follow any post config instructions,
    and do everything needed on your platform to rebuild the kernel.
    This typically includes:
        # make dep
      and:
        # make bzImage                  # varies on non-Intel platforms

6.  Rebuild the kernel modules:
        # make modules

7.  Optionally, (and potentially dangerous!), do everything needed
    on your platform to install a newly built kernel.
    (possibly temporarily, for sanity testing)

      Be careful with this step, and be sure you know what you're doing!
      It is easy to wipe out a good/stable kernel from this point forward
      in the procedure!

8.  (Re)Install newly compiled kernel modules:
        # make modules_install

      The output from the last step should look something like this:
        Installing modules under /lib/modules/2.2.14-5.0/block
        Installing modules under /lib/modules/2.2.14-5.0/net
        Installing modules under /lib/modules/2.2.14-5.0/ipv4
        Installing modules under /lib/modules/2.2.14-5.0/scsi
        Installing modules under /lib/modules/2.2.14-5.0/fs
        Installing modules under /lib/modules/2.2.14-5.0/fs
        Installing modules under /lib/modules/2.2.14-5.0/cdrom
        Installing modules under /lib/modules/2.2.14-5.0/video
        Installing modules under /lib/modules/2.2.14-5.0/net
        Installing modules under /lib/modules/2.2.14-5.0/misc

9.   Update your /boot sector with the new System.map and bzImage,
     re-create your ramdisk image (refer to your vendor literature), and
     update your boot manager--i.e., lilo.conf, grub.conf. If you are
     using lilo, you must run lilo -v prior to reboot.

10.  Shut down the system:
      Example:
        # shutdown -r now
      and then reboot with the newly built Linux kernel.

=== Loading the Drivers As Modules ===

Follow these steps to load the new driver binaries:

1.  Load the Fusion-MPT base driver.
        # insmod mptbase
        Fusion-MPT base driver 2.05.06
        Copyright (c) 1999-2002 LSI Logic Corporation
        mptbase: Initiating ioc0 bringup
        ioc0: FC919: Capabilities={Initiator,Target,LAN}
        mptbase: 1 MPT adapter found, 1 installed.

2.  Load the isense driver (optional but highly recommended),
    to enable enhanced SCSI error reporting.
        # insmod isense
        SCSI-3 Opcodes & ASC/ASCQ Strings 2.05.06
        mptbase: English readable SCSI-3 OPs & ASC/ASCQ strings enabled.

3.  Load the Fusion-MPT SCSI host driver.
        # insmod mptscsih
        Fusion-MPT SCSI Host driver 2.05.06

      Depending on which FC devices you have attached to your FC link,
      you should see something like the following on the console and
      in the system log:
        scsi0 : ioc0: LSIFC919, FwRev=1000h, Ports=1, MaxQ=256, IRQ=9
        scsi : 1 host.
          Vendor: SEAGATE   Model: ST39102FC         Rev: 0007
          Type:   Direct-Access                      ANSI SCSI revision: 02
        Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
          Vendor: SEAGATE   Model: ST19171FC         Rev: 0017
          Type:   Direct-Access                      ANSI SCSI revision: 02
        Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
        SCSI device sda: hdwr sector= 512 bytes. Sectors= 17783240 [8683 MB] [8.7 GB]
         sda: sda1
        SCSI device sdb: hdwr sector= 512 bytes. Sectors= 17783112 [8683 MB] [8.7 GB]
         sdb: sdb1

    All Fibre Channel target devices should be detected and mapped to Linux
    SCSI devices, /dev/sd{a,b,c,...} when the mptscsih module is loaded.

    All Linux commands pertaining to SCSI disk storage management
    (fdisk, mke2fs, mount, etc.) using the /dev/sdX[N] notation
    should now be functional.

    FCP (SCSI) Device Access Example:
        # fdisk /dev/sdb
        # mke2fs /dev/sdb1
        # mount /dev/sdb1 /mnt/s1

Update. Looks like mine is failing much the same.

  CC      drivers/message/fusion/mptbase.o
  CC      drivers/message/fusion/mptscsih.o
  CC      drivers/message/fusion/mptsas.o
drivers/message/fusion/mptsas.c: In function 'mptsas_smp_handler':
drivers/message/fusion/mptsas.c:2437: error: 'struct request' has no member named 'data_len'
drivers/message/fusion/mptsas.c:2438: error: 'struct request' has no member named 'data_len'
drivers/message/fusion/mptsas.c:2455: error: 'struct request' has no member named 'data_len'
drivers/message/fusion/mptsas.c:2485: error: 'struct request' has no member named 'data_len'
drivers/message/fusion/mptsas.c:2488: error: 'struct request' has no member named 'data_len'
drivers/message/fusion/mptsas.c:2501: error: 'struct request' has no member named 'data_len'
drivers/message/fusion/mptsas.c:2503: error: 'struct request' has no member named 'data_len'
drivers/message/fusion/mptsas.c:2534: error: 'struct request' has no member named 'data_len'
drivers/message/fusion/mptsas.c:2535: error: 'struct request' has no member named 'data_len'
drivers/message/fusion/mptsas.c:2544: error: 'struct request' has no member named 'data_len'
drivers/message/fusion/mptsas.c:2547: error: 'struct request' has no member named 'data_len'
make[3]: *** [drivers/message/fusion/mptsas.o] Error 1
make[2]: *** [drivers/message/fusion] Error 2
make[1]: *** [drivers/message] Error 2
make: *** [drivers] Error 2

[Rampage101]

https://bugzilla.redhat.com/show_bug.cgi?id=493093

Comment 3 seems to lead to the problem we are all having, in which 4 series driver fixes it if I am reading correctly.

[MetalPhreak]

Dragon 191: Are you running SuSE ?

I've given up trying to compile the drivers. ATM i've got the issue of a faulty drive. Brand new WD10EADS does some weird seek/clicking noise when it's not being accessed (even with no sata data cable). And now I'm getting errors like this: "raid5:md0: read error corrected (8 sectors at 3611744 on sdm)"

Hopefully I'll be able to get a straight swap when I take it back.

[Dragon_191]

Originally Posted by MetalPhreak

Dragon 191: Are you running SuSE ?

Yes, running SLES 11.