07-07-2009
sometimes the backup problem may be coz of the device driver. If proper device driver is not installed then it might cause the problem I have faced it many times.
please check Driver and firmware that might help.
10 More Discussions You Might Find Interesting
1. AIX
Hello all,
Anyboby knows what is the reason by which the ouput of the command mt -f /dev/rmt0.1 status on AIX does not show the same information that in the rest of platforms UNIX (Solaris, HP-UX, ...)?
Then, what command of AIX is similar to mt- f /dev/rmt0.1 status of Solaris? We need it to... (0 Replies)
Discussion started by: smoraprosol
0 Replies
2. Solaris
Hi, Anyone can help
My solaris 8 system has the following
/dev/null , /dev/tty and /dev/console
All permission are lrwxrwxrwx
Can this be change to a non-world write ??
any impact ?? (12 Replies)
Discussion started by: civic2005
12 Replies
3. AIX
I am trying to find a way to do the following on an AIX 4.2 with Korn:
tar cvfpdl - . | compress > /dev/rmt0
The /dev/rmt0 is the device we use when we tar directly to it.
I want to compress a folder's content to tape. Our current TAR does not have compression at all. We only have... (5 Replies)
Discussion started by: Browser_ice
5 Replies
4. AIX
I only about the principle of filesystems from the very basics on Linux and Windows. But I want to know if it is possible on an AIX 4.2 to create one NFS on a server which is pointing to a tape drive (/dev/rmt0) of another server ?
This is because we several backups to do on a 5 servers that... (5 Replies)
Discussion started by: Browser_ice
5 Replies
5. UNIX for Dummies Questions & Answers
Hi folks,
Here i have written a shell script to calculate a maximum number from 10 numbers entered on command line.
max=0
echo Enter 10 numbers , one at a time
for i in 1 2 3 4 5 6 7 8 9 10
do
read n
max=`expr $max + $n`
if --- At this last step there is some problem, it gives error... (5 Replies)
Discussion started by: rits
5 Replies
6. AIX
rmt0 allows get increased .. !
I have faced this issue in my AIX server, rmt0 allows get increased and it's filled /root till 100%
There is no tape in tape drive why it's increased?
Pls advice.. (1 Reply)
Discussion started by: Mr.AIX
1 Replies
7. Homework & Coursework Questions
Creating a large number of rules such as 100000, iptables will produce errors after 42000 rules "iptables: Unknown error 18446744073709551615".
But another machine where i have debian virtual machine I can easily run the sciprt of 100000 of rules
I am waiting for your reply
4.... (1 Reply)
Discussion started by: tahirfattani
1 Replies
8. AIX
Dear all
First of all, my English not so good.
We have p52a (production server) and p52a (test server). Tape drives are VXA2.
When both servers were AIX 5.3, mksysb on production server and restoring to test server was OK.
The production server was AIX 5.3 and recently upgraded to... (3 Replies)
Discussion started by: fifa15pc
3 Replies
9. Shell Programming and Scripting
Objective: To recreate the partitioning setup of /dev/sda on /dev/sdc
How would I parse the below information and initialize variables
(an array?) that can be used to build sgdisk commands in a script, regardless of the number of partitions?
Something along the lines of:
sgdisk -n... (12 Replies)
Discussion started by: RogerBaran
12 Replies
10. AIX
The company I work for has various AIX servers that I've recently migrated to AIX 7.1 (from 6.1). Some are powerHA clusters some are not. Likewise, the systems engineer that I replaced had net-snmp installed on said clustered systems. Long story short I am re-invoking AIX's native SNMP (v3) for... (1 Reply)
Discussion started by: davix
1 Replies
socal(7D) Devices socal(7D)
NAME
socal - Serial Optical Controller for Fibre Channel Arbitrated Loop (SOC+) device driver
SYNOPSIS
socal@sbus-slot,0
DESCRIPTION
The Fibre Channel Host Bus Adapter is an SBus card which implements two full duplex Fibre Channel interfaces. Each Fibre Channel interface
can connect to a Fibre Channel Arbitrated Loop (FC-AL).
The socal device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.
FILES
/kernel/drv/socal ELF Kernel Module
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
SEE ALSO
sbus(4), sf(7D), ssd(7D)
Writing Device Drivers
ANSI X3.230-1994, Fibre Channel Physical and Signalling Interface (FC-PH)
ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA)
DIAGNOSTICS
The messages described below may appear on system console in addition to being logged.
On the console, these messages are preceded by:
socal%d: port %a
where %d is the instance number of the socal controller and %a is the port on the host adapter.
Fibre Channel Loop is ONLINE
The Fibre Channel loop is now online.
Fibre Channel Loop is OFFLINE
The Fibre Channel loop is now offline.
attach failed: device in slave-only slot.
Move soc+ card to another slot.
attach failed: bad soft state.
Driver did not attach, devices will be inaccessible.
attach failed: unable to alloc xport struct.
Driver did not attach, devices will be inaccessible.
attach failed: unable to map eeprom
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map XRAM
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map registers
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access status register
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to install interrupt handler
Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access host adapter XRAM
Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to write host adapter XRAM
Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: read/write mismatch in XRAM
Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
SunOS 5.10 9 May 1997 socal(7D)