10-09-2011
10 More Discussions You Might Find Interesting
1. Solaris
How do I get the PCI ID for my Realtek adapter?
It's a Solaris x86 installation. (5 Replies)
Discussion started by: kuultak
5 Replies
2. Solaris
Has anyone ever relocated an HBA card after already having it configured in another PCI slot? I've found that the HBA instance #'s start incrementing past the previous. It results in me having to have my instance numbers in /kernel/drv/qla2300.conf be 4,5,6,7 instead of 0,1,2,3. Cleanup with... (5 Replies)
Discussion started by: kduffin
5 Replies
3. AIX
I have 1 PCI-X Dual Channel Ultra320 SCSI Adapter card for my p570 server. I would like to split the 2 channels for the usage of 2 tape drives in different LPARs. Is that possible?
For example, I have 2 LPARs running in p570 server, LPAR-A configured the Ultra320 card as pci7 in slot... (11 Replies)
Discussion started by: kwliew999
11 Replies
4. SCO
I'm floundering here trying to locate a PCI-E 1x HBA that will support an external tape drive in SCO Openserver 6. I was unable to find anything that would work in the compatible hardware list and a call to Adaptec confirmed that PCI-X would've been a better option for the risers in the Dell 2950... (1 Reply)
Discussion started by: s_mal
1 Replies
5. AIX
Hello,
I have a scsi pci x raid controller card on which I had created a disk array of 3 disks
when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk )
suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies
6. SCO
OK group, it's been 12 years since I worked with SCO. I need some direction here:
SCO Openserver 5.07
I have a server with a bad motherboard. I have moved the SCSI adapter and hard drive to another computer. This new server has different hardware so I must install the chipset drivers for... (1 Reply)
Discussion started by: jscholz
1 Replies
7. Hardware
Internally speaking, for your motherboard bus. Would it be possible for a usb standard to be used in place of the PCI or PCIe bus that is now nearly standard on all PC's? If not, why wouldn't this work? (8 Replies)
Discussion started by: Lost in Cyberia
8 Replies
8. Red Hat
I am trying to cause a callback in the Linux nvme driver by using AER injection. I've modified the AER source code to directly inject errors through module loading rather than from userland program.
I've verified that I got the correct bus, dev, and fn and that the error injection went... (0 Replies)
Discussion started by: Decrypto
0 Replies
9. HP-UX
I am trying to reload a RP4440 with 2x300gb disks and dual Port Network card, with HPUX 11.11 Sept 2003. When the os boots and and gets to the main menu to install HPUX or run recovery, it cannot find the disks or NIC.
At the OS prompt (after loading files), ioscan shows the Class ba, and shows... (0 Replies)
Discussion started by: mrmurdock
0 Replies
10. Solaris
Hi,
I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error:
WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1):
SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 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