04-11-2015
Do you know the PCI id of the LSI 2308? If it's 1000:006e, I don't see it in /etc/driver_aliases on my Solaris 11.2 box.
Even if it's not there, I'd think there's a good chance it'll work if you manually add it to driver_aliases or run add_drv. Just about every LSI HBA just uses the "mpt" driver anyway - FC, SAS, SCSI. And they can all be manipulated with the "lsiutil" utility.
This User Gave Thanks to achenle For This Post:
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does anyone had perfomed a tuning with SAS on Solaris???
Performance is not so good and I found out that Share Memory an Semaphores are the same that initial instalation, I havent found info at internet
Please help (1 Reply)
Discussion started by: alex blanco
1 Replies
2. Solaris
Hi, I have a solaris box with an LSI SAS HBA and a16 bay SAS JBOD. I can only see 15 of the 16 drives, ID 7 is not seen. Do I have to edit the st.conf file to get things to work properly?
Thanks (0 Replies)
Discussion started by: montanye
0 Replies
3. Solaris
Hi all
i would like to ask some suggests about my next job!
I have to install a new Sun Netra T5220, with an additional internal StorageTek SAS HBA Raid.
The problem come in if every disk is now controlled by the HBA, how can I install the OS?
No disk is being detected by the OS.
SAS card... (2 Replies)
Discussion started by: kakabobo
2 Replies
4. Solaris
i was given a task which needs to perform a raid 1 on the boot disk, and 4 other disks on raid 10.
Is there any other alternative in installing solaris 10 other than through network installation?will be using solaris update 6.
while reading through the user guide i got pretty confuse.
... (1 Reply)
Discussion started by: monstar1407
1 Replies
5. Linux
supermicro(dual core) server getting rebooted after "decompressing the kernel;booting the kernel" message comes.
I tried giving acpi=off to the kernel command line but same problem.It shows everything ok and no problem with memory and processors and power supplies.Wt could be the reason?
It has... (1 Reply)
Discussion started by: pankajd
1 Replies
6. SCO
Hi folks,
I had problems trying to install SCO OpenServer 6 on a PC with no floppy drive and a SATA CD drive.
Eventually after advice received on this forum last week, I adopted a different approach by fitting the LSI HBA RAID adapter and associated disks into an older PC that does have CD and... (4 Replies)
Discussion started by: millosman
4 Replies
7. Solaris
Got a T2000 which has got the 2.5" SAS drives. Want to be able, if I can, to connect to USB caddy and connect to a V440.
Anyone ever tried this? To be honest, having problems even finding a SAS-USB caddy. (0 Replies)
Discussion started by: psychocandy
0 Replies
8. Linux
I bought for backup this controller
LSI LSI9212-4i4e 6G SAS
I will buy a quantum reader like this
Quantum TC-L62BN-EM 2500GB LTO
Two simple question
a)I read..2500GB,this mean i cannot use tape lto6 over 3tb?
b)Wich external cable?A sata external cable is good?
Thanks (0 Replies)
Discussion started by: Linusolaradm1
0 Replies
MFI(4) BSD Kernel Interfaces Manual MFI(4)
NAME
mfi -- LSI MegaRAID SAS driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device pci
device mfi
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
mfi_load="YES"
DESCRIPTION
This driver is for LSI's next generation PCI Express SAS RAID controllers. Access to RAID arrays (logical disks) from this driver is pro-
vided via /dev/mfid? device nodes. A simple management interface is also provided on a per-controller basis via the /dev/mfi? device node.
The mfi name is derived from the phrase "MegaRAID Firmware Interface", which is substantially different than the old "MegaRAID" interface and
thus requires a new driver. Older SCSI and SATA MegaRAID cards are supported by amr(4) and will not work with this driver.
Two sysctls are provided to tune the mfi driver's behavior when a request is made to remove a mounted volume. By default the driver will
disallow any requests to remove a mounted volume. If the sysctl dev.mfi.%d.delete_busy_volumes is set to 1, then the driver will allow
mounted volumes to be removed.
HARDWARE
The mfi driver supports the following hardware:
o LSI MegaRAID SAS 1078
o LSI MegaRAID SAS 8408E
o LSI MegaRAID SAS 8480E
o LSI MegaRAID SAS 9260
o Dell PERC5
o Dell PERC6
o IBM ServeRAID M5015 SAS/SATA
o IBM ServeRAID-MR10i
o Intel RAID Controller SROMBSAS18E
FILES
/dev/mfid? array/logical disk interface
/dev/mfi? management interface
DIAGNOSTICS
mfid%d: Unable to delete busy device An attempt was made to remove a mounted volume.
SEE ALSO
amr(4), pci(4), mfiutil(8)
HISTORY
The mfi driver first appeared in FreeBSD 6.1.
AUTHORS
The mfi driver and this manual page were written by Scott Long <scottl@FreeBSD.org>.
BUGS
The driver does not support big-endian architectures at this time.
BSD
May 12, 2010 BSD