7 More Discussions You Might Find Interesting
1. SCO
I was asked to get a Dell PowerEdge 2600 server, out of warranty, running SCO 3.2v5.06 to perform a full backup. I spent hours researching and preparing a strategy only to fail on-site.
The only device names in /dev for a tape drive were
/dev/xStp0
/dev/xcdt0
/dev/xct0
... (6 Replies)
Discussion started by: ezlarry
6 Replies
2. Programming
Hi,
I have a C++ program to access /dev/mem and retrieve details like Vendor, Manufacturer details of the motherboard. This works fine on all the machines except for on Dell Poweredge 2850,1950... machines.
I receive a 'EFAULT' when I try to access /dev/mem on these servers.
I suspect some... (1 Reply)
Discussion started by: ragisreekanth
1 Replies
3. UNIX for Dummies Questions & Answers
I have 2 Dell Poweredge 1950 servers running . I have been having intermittent performance issues with the NIC cards on one of them. The two servers are identical and are running the same operating system. The server that has the issue is on the DMZ on a a static IP and is hosting a website. ... (0 Replies)
Discussion started by: skotapal
0 Replies
4. Filesystems, Disks and Memory
Does anybody no how to get around the fact that the Red Hat installation does not see the SCSI hard drives. It lets you manually pick the proper device, but still fails saying no drive detected (or something to that effect). I was going to install windows 2003 Server and use VMware...but again,... (1 Reply)
Discussion started by: Fatflea
1 Replies
5. Solaris
hi, i am trying to install solaris 10 (on 4 cd's downloaded from the sun website) on my dell poweredge 2800 server. 2 xeon processors, 2GB of RAM and 2 NICS, 73 GB SCSI (maxtor ultra320, 3.5 series), i can give more details on request...
the installation crashes when trying to detect the NICS... (0 Replies)
Discussion started by: xinugeek
0 Replies
6. Linux Benchmarks
CPU/Speed: Dual PIII 533
Ram: 256Mb PC133
Motherboard: Unknown, Intel Chipset
Cache: 256k on board
Controller: PARC Raid 2/Si, AIC-7880U
Disk: 30Gb RAID 5
Load: 1 user. Clean boot, init 5 but X-Windows not loaded.
Kernel: See Benchmarks.
pgms: gcc 3.2.3
... (2 Replies)
Discussion started by: Garp
2 Replies
7. Linux Benchmarks
Notes:
System Configuration: Dell Computer Corporation PowerEdge 4600 (4 X Intel(R) XEON(TM) CPU 2.00GHz
1988.782 MHz) hyperthreaded
System clock frequency: 99.0827 MHz
Memory size (approximate): 2559 Megabytes
========================= CPUs ========================
CPU # CPU... (0 Replies)
Discussion started by: tnorth
0 Replies
AMR(4) BSD Kernel Interfaces Manual AMR(4)
NAME
amr -- MegaRAID SCSI/ATA/SATA RAID driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device pci
device scbus
device amr
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
amr_load="YES"
DESCRIPTION
The amr driver provides support for LSI Logic MegaRAID SCSI, ATA and SATA RAID controllers and legacy American Megatrends MegaRAID SCSI RAID
controllers, including models relabeled and sold by Dell and Hewlett-Packard.
LSI MegaRAID SAS controllers are supported by mfi(4) and will not work with this driver.
HARDWARE
Controllers supported by the amr driver include:
o MegaRAID SATA 150-4
o MegaRAID SATA 150-6
o MegaRAID SATA 300-4X
o MegaRAID SATA 300-8X
o MegaRAID SCSI 320-1E
o MegaRAID SCSI 320-2E
o MegaRAID SCSI 320-4E
o MegaRAID SCSI 320-0X
o MegaRAID SCSI 320-2X
o MegaRAID SCSI 320-4X
o MegaRAID SCSI 320-0
o MegaRAID SCSI 320-1
o MegaRAID SCSI 320-2
o MegaRAID SCSI 320-4
o MegaRAID Series 418
o MegaRAID i4 133 RAID
o MegaRAID Elite 1500 (Series 467)
o MegaRAID Elite 1600 (Series 493)
o MegaRAID Elite 1650 (Series 4xx)
o MegaRAID Enterprise 1200 (Series 428)
o MegaRAID Enterprise 1300 (Series 434)
o MegaRAID Enterprise 1400 (Series 438)
o MegaRAID Enterprise 1500 (Series 467)
o MegaRAID Enterprise 1600 (Series 471)
o MegaRAID Express 100 (Series 466WS)
o MegaRAID Express 200 (Series 466)
o MegaRAID Express 300 (Series 490)
o MegaRAID Express 500 (Series 475)
o Dell PERC
o Dell PERC 2/SC
o Dell PERC 2/DC
o Dell PERC 3/DCL
o Dell PERC 3/QC
o Dell PERC 4/DC
o Dell PERC 4/IM
o Dell PERC 4/SC
o Dell PERC 4/Di
o Dell PERC 4e/DC
o Dell PERC 4e/Di
o Dell PERC 4e/Si
o Dell PERC 4ei
o HP NetRAID-1/Si
o HP NetRAID-3/Si (D4943A)
o HP Embedded NetRAID
o Intel RAID Controller SRCS16
o Intel RAID Controller SRCU42X
DIAGNOSTICS
Driver initialisation/shutdown phase
amr%d: memory window not available
amr%d: I/O window not available
The PCI BIOS did not allocate resources necessary for the correct operation of the controller. The driver cannot attach to this controller.
amr%d: busmaster bit not set, enabling
The PCI BIOS did not enable busmaster DMA, which is required for the correct operation of the controller. The driver has enabled this bit
and initialisation will proceed.
amr%d: can't allocate register window
amr%d: can't allocate interrupt
amr%d: can't set up interrupt
amr%d: can't allocate parent DMA tag
amr%d: can't allocate buffer DMA tag
amr%d: can't allocate scatter/gather DMA tag
amr%d: can't allocate s/g table
amr%d: can't allocate mailbox tag
amr%d: can't allocate mailbox memory
A resource allocation error occurred while initialising the driver; initialisation has failed and the driver will not attach to this con-
troller.
amr%d: can't obtain configuration data from controller
amr%d: can't obtain product data from controller
The driver was unable to obtain vital configuration data from the controller. Initialisation has failed and the driver will not attach to
this controller.
amr%d: can't establish configuration hook
amr%d: can't scan controller for drives
The scan for logical drives managed by the controller failed. No drives will be attached.
amr%d: device_add_child failed
amr%d: bus_generic_attach returned %d
Creation of the logical drive instances failed; attachment of one or more logical drives may have been aborted.
amr%d: flushing cache...
The controller cache is being flushed prior to shutdown or detach.
Operational diagnostics
amr%d: I/O beyond end of unit (%u,%d > %u)
A partitioning error or disk corruption has caused an I/O request beyond the end of the logical drive. This may also occur if FlexRAID Vir-
tual Sizing is enabled and an I/O operation is attempted on a portion of the virtual drive beyond the actual capacity available.
amr%d: polled command timeout
An initialisation command timed out. The initialisation process may fail as a result.
amr%d: bad slot %d completed
The controller reported completion of a command that the driver did not issue. This may result in data corruption, and suggests a hardware
or firmware problem with the system or controller.
amr%d: I/O error - %x
An I/O error has occurred.
SEE ALSO
cd(4), da(4), mfi(4), sa(4), scsi(4)
AUTHORS
The amr driver was written by Mike Smith <msmith@FreeBSD.org>.
This manual page was written by Mike Smith <msmith@FreeBSD.org> and Jeroen Ruigrok van der Werven <asmodai@FreeBSD.org>.
BSD March 29, 2006 BSD