10 More Discussions You Might Find Interesting
1. SCO
I need to be able to make a backup image of an OLD UNIX server HD where I can restore the complete HD from scratch if (when) the HD fails. This server runs the accounting system for a company.
I can and have backed the data up via local FTP, but O/S and Apps are so old that I am not sure I could... (21 Replies)
Discussion started by: chrishouse
21 Replies
2. Debian
I am installing a Debian Server on a:
HP Proliant DL380 G4
Dual CPU's 3.20 ghz / 800 mhz / 1MB L2
5120 MB RAM
6 hard disks on HP Smart Array 6i controller (36.4 GB Ultra320 SCSI HD each)
I will be using this server to capture VHS video, encode, compress, cut, edit, make DVD's, rip... (0 Replies)
Discussion started by: Marcus Aurelius
0 Replies
3. 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
4. Linux
I just built a home computer with 3TB hard drives I wanted to set up in a RAID 5 and load Ubuntu server onto it.
The first thing I did was set up the drives in a RAID 5 using just the motherboard chipset software to do it, so a 'hardware' RAID basically.
I installed Windows first to see if... (2 Replies)
Discussion started by: lorewap3
2 Replies
5. Hardware
Hi guys.
if we want to use SSD drives on a database server, can we use RAID 0 configuration because of their reliability? (3 Replies)
Discussion started by: majid.merkava
3 Replies
6. Hardware
Hi All
I have a Sun T2000 server. Couple of years ago I had configured and mirrored the boot drive with an other drive using hardware RAID 1 using raidctl command.
Following is the hardware RAID output.
root@oracledatabaseserver / $ raidctl
RAID Volume RAID RAID Disk... (0 Replies)
Discussion started by: Tirmazi
0 Replies
7. UNIX for Dummies Questions & Answers
I need to put together a RAID1 file server for use by Windoze systems. I've built zillions of windows systems from components. I was a HPUX SE for a long time at HP, but have been out of the game for years.
I've got an old workhorse mobo FIC PA-2013 with a 450 MHz K6 III+ I could use, but I'd... (2 Replies)
Discussion started by: pcmacd
2 Replies
8. Red Hat
I am planning on building a fedora box with raid controller (database server).
Is anybody done that ? also what kind of software do you need to backup and recover data. (1 Reply)
Discussion started by: amir07
1 Replies
9. Filesystems, Disks and Memory
Hi,
I have a server that I am adding a RAID that we purchased to. The server works fine. It is running Fedora 7 and is a Dell Precision 690.
When the RAID is attached, it boots up and says the following:
Controller Bus #00, Device#1F, Function#02: 00 Ports
No device found
AHCI BIOS not... (0 Replies)
Discussion started by: user23
0 Replies
10. Filesystems, Disks and Memory
Help, if possible.
In SCO Open Server with installation of two-channel RAID controller the following happens: on the channel 0 disk array is seen by an operational system, and on the channel 1 array is not seen (simultaneously). That is the operational system can not simultaneously use more than... (1 Reply)
Discussion started by: pko60
1 Replies
TWE(4) BSD Kernel Interfaces Manual TWE(4)
NAME
twe -- 3ware 5000/6000/7000/8000 series PATA/SATA RAID adapter driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device pci
device twe
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
twe_load="YES"
DESCRIPTION
The twe driver provides support for AMCC's 3ware 5000/6000/7000/8000 series PATA/SATA RAID adapters. These adapters were formerly known as
``3ware Escalade''.
These devices support 2, 4, 8, or 12 ATA disk drives and provide RAID0 (striping) and RAID1 (mirroring) functionality.
HARDWARE
The twe driver supports the following PATA/SATA RAID controllers:
o AMCC's 3ware 5000 series
o AMCC's 3ware 6000 series
o AMCC's 3ware 7000-2
o AMCC's 3ware 7006-2
o AMCC's 3ware 7500-4LP
o AMCC's 3ware 7500-8
o AMCC's 3ware 7500-12
o AMCC's 3ware 7506-4LP
o AMCC's 3ware 7506-8
o AMCC's 3ware 7506-12
o AMCC's 3ware 8006-2LP
o AMCC's 3ware 8500-4LP
o AMCC's 3ware 8500-8
o AMCC's 3ware 8500-12
o AMCC's 3ware 8506-4LP
o AMCC's 3ware 8506-8
o AMCC's 3ware 8506-8MI
o AMCC's 3ware 8506-12
o AMCC's 3ware 8506-12MI
DIAGNOSTICS
Controller initialisation phase
twe%d: microcontroller not ready
The controller's onboard CPU is not reporting that it is ready; this may be due to either a board or system failure. Initialisation has
failed.
twe%d: no attention interrupt
twe%d: can't drain AEN queue
twe%d: reset not reported
twe%d: controller errors detected
twe%d: can't drain response queue
twe%d: reset %d failed, trying again
The controller is not responding correctly to the driver's attempts to reset and initialise it. This process is retried several times.
twe%d: can't initialise controller, giving up
Several attempts to reset and initialise the controller have failed; initialisation has failed and the driver will not attach to this con-
troller.
Driver initialisation/shutdown phase
twe%d: register window not available
twe%d: can't allocate register window
twe%d: can't allocate parent DMA tag
twe%d: can't allocate interrupt
twe%d: can't set up interrupt
twe%d: can't establish configuration hook
A resource allocation error occurred while initialising the driver; initialisation has failed and the driver will not attach to this con-
troller.
twe%d: can't detect attached units
Fetching the list of attached units failed; initialisation has failed.
twe%d: error fetching capacity for unit %d
twe%d: error fetching state for unit %d
twe%d: error fetching descriptor size for unit %d
twe%d: error fetching descriptor for unit %d
twe%d: device_add_child failed
twe%d: bus_generic_attach returned %d
Creation of the disk devices failed, either due to communication problems with the adapter or due to resource shortage; attachment of one or
more units may have been aborted.
Operational phase
twe%d: command completed - %s
A command was reported completed with a warning by the controller. The warning may be one of:
redundant/inconsequential request ignored
failed to write zeroes to LBA 0
failed to profile TwinStor zones
twe%d: command failed - %s
A command was reported as failed by the controller. The failure message may be one of:
aborted due to system command or reconfiguration
aborted
access error
access violation
device failure
controller error
timed out
invalid unit number
unit not available
undefined opcode
request incompatible with unit
invalid request
firmware error, reset requested
The command will be returned to the operating system after a fatal error.
twe%d: command failed submission - controller wedged
A command could not be delivered to the controller because the controller is unresponsive.
twe%d: AEN: <%s>
The controller has reported a change in status using an AEN (Asynchronous Event Notification). The following AENs may be reported:
queue empty
soft reset
degraded mirror
controller error
rebuild fail
rebuild done
incomplete unit
initialisation done
unclean shutdown detected
drive timeout
drive error
rebuild started
aen queue full
AENs are also queued internally for use by management tools.
twe%d: error polling for signalled AENs
The controller has reported that one or more status messages are ready for the driver, but attempting to fetch one of these has returned an
error.
twe%d: AEN queue overflow, lost AEN <%s>
A status message was retrieved from the controller, but there is no more room to queue it in the driver. The message is lost (but will be
printed to the console).
twe%d: missing expected status bits %s
twe%d: unexpected status bits %s
A check of the controller's status bits indicates an unexpected condition.
twe%d: host interrupt
The controller has signalled a host interrupt. This serves an unknown purpose and is ignored.
twe%d: command interrupt
The controller has signalled a command interrupt. This is not used, and will be disabled.
twe%d: controller reset in progress...
The controller is being reset by the driver. Typically this is done when the driver has determined that the controller is in an unrecover-
able state.
twe%d: can't reset controller, giving up
The driver has given up on resetting the controller. No further I/O will be handled.
controller reset done, %d commands restarted
The controller was successfully reset, and outstanding commands were restarted.
AUTHORS
The twe driver and manual page were written by Michael Smith <msmith@FreeBSD.org>.
Extensive work done on the driver by Vinod Kashyap <vkashyap@FreeBSD.org> and Paul Saab <ps@FreeBSD.org>.
BUGS
The controller cannot handle I/O transfers that are not aligned to a 512-byte boundary. In order to support raw device access from user-
space, the driver will perform alignment fixup on non-aligned data. This process is inefficient, and thus in order to obtain best perfor-
mance user-space applications accessing the device should do so with aligned buffers.
BSD
August 15, 2004 BSD
