9 More Discussions You Might Find Interesting
1. AIX
Hi all,
I am not sure whether anyone of you using XIV to copy vg from one host to another. After I managed to copy all the respective vg over to destination vg, and map all vg to destination and when come to varyonvg, I got the following error
0516-510 varyonvg: Physical volume not found for... (2 Replies)
Discussion started by: ckwan
2 Replies
2. Red Hat
Hi Masters,
How to find out the failed disk in redhat linux (OR)
How to decalare whether our hard disk goes bad ?
My option is:
dmesg | grep "failed"
check in /var/log/messages with the kernel error.
Please corrrect me if im wrong.
And also i heard "smartctl" command. But it's... (2 Replies)
Discussion started by: abhay1983
2 Replies
3. AIX
Hello,
On Aix 5.3, during importvg, the varyonvg fails:
importvg -y vgtest hdisk20
0516-013 varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
When i use manually the command varyonvg -u -b -t vgtest to force, the vg can... (3 Replies)
Discussion started by: dantares
3 Replies
4. Solaris
Dear all
Please can any one explain me how to replace failed disk in Solaris 10.
Please tell me the step by step procedure. (9 Replies)
Discussion started by: suneelieg
9 Replies
5. Windows & DOS: Issues & Discussions
Hi
The Autosys job that call DOS batch file which in turn calls java and this java program has successful completion though there are series of exception occurred in the data it handles and want the job to be set to Fail in its autosys, how could it be done?
a.bat
{
java sample.class
... (1 Reply)
Discussion started by: muthupus
1 Replies
6. Solaris
Hi All,
Seems to be one of the disk has failed on my Solaris server.
How do i confirm that disk has really failed or not?
Here are alert details.
-------
iostat -En out/put
c1t3d0 Soft Errors: 1884 Hard Errors: 153 Transport Errors: 54
Vendor: FUJITSU Product:... (3 Replies)
Discussion started by: Naresh Kommina
3 Replies
7. AIX
Good evening,
Thanks a lot for your help, we appreciate it a bunch. Heres basically a summary of what we have (sorry Im adding some extra history as well):
We have 2 Ibm Servers (Hag and Aki) that are running AIX Version 5. Each connect to a SAN device via 2 separate fiber paths. Hag seems to... (9 Replies)
Discussion started by: aix-olympics
9 Replies
8. UNIX for Advanced & Expert Users
Hello all,
Strange problem on p5 520 server. I've created two volume groups, filesystems, etc.. Everything working fine, without any problem. After some tests with a DS4300 unit I wanted to remove the volume groups, change the DS4300 configuration, and re-create a new volumegroup. However, I'm... (0 Replies)
Discussion started by: EricBE
0 Replies
9. UNIX for Advanced & Expert Users
My WS boot disk has failed so when i want to boot system (by OK boot -s or Ok boot disk0 ) i get these mesgs:
disk read error
boot :can not find misc/sparc9v/krtld
boot:error loading interperetor (misc/sparc9v/krtld)
Elf64 read error.
boot failed.
although it's probed ,finally i try... (1 Reply)
Discussion started by: nikk
1 Replies
sf(7D) Devices sf(7D)
NAME
sf - SOC+ FC-AL FCP Driver
SYNOPSIS
sf@port,0
DESCRIPTION
The sf driver is a SCSA compliant nexus driver which supports the Fibre Channel Protocol for SCSI on Private Fibre Channel Arbitrated
loops. An SBus card called the SOC+ card (see socal(7D)) connects the Fibre Channel loop to the host system.
The sf driver interfaces with the SOC+ device driver, socal(7D), the SCSI disk target driver, ssd(7D), and the SCSI-3 Enclosure Services
driver, ses(7D). It only supports SCSI devices of type disk and ses.
The sf driver supports the standard functions provided by the SCSA interface. The driver supports auto request sense and tagged queueing
by default.
The driver requires that all devices have unique hard addresses defined by switch settings in hardware. Devices with conflicting hard
addresses will not be accessible.
FILES
/platform/architecture/kernel/drv/sf ELF kernel module
/platform/architecture/kernel/drv/sf.consf driver configuration file
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
SEE ALSO
luxadm(1M), prtconf(1M), driver.conf(4), socal(7D), ssd(7D)
Writing Device Drivers
ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)
ANSI X3.269-1996, Fibre Channel Protocol for SCSI (FCP)
ANSI X3.270-1996, SCSI-3 Architecture Model (SAM)
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA)
DIAGNOSTICS
In addition to being logged, the messages below may display on the system console.
The first set of messages indicate that the attachment was unsuccessful, and will only display while the sf driver is initially attempting
to attach. Each message is preceded by sf%d , where %d is the instance number of the sf device.
Failed to alloc soft state
Driver was unable to allocate space for the internal state structure. Driver did not attach to device, SCSI devices will be inaccessi-
ble.
Bad soft state
Driver requested an invalid internal state structure. Driver did not attach to device, SCSI devices will be inaccessible.
Failed to obtain transport handle
Driver was unable to obtain a transport handle to communicate with the socal driver. Driver did not attach to device, SCSI devices will
be inaccessible
Failed to allocate command/response pool
Driver was unable to allocate space for commands and responses. Driver did not attach to device, SCSI devices will be inaccessible.
Failed to allocate kmem cache
Driver was unable to allocate space for the packet cache. Driver did not attach to device, SCSI devices will be inaccessible.
Failed to allocate dma handle for
Driver was unable to allocate a dma handle for the loop map. Driver did not attach to device, SCSI devices will be inaccessible.
Failed to allocate lilp map
Driver was unable to allocate space for the loop map. Driver did not attach to device, SCSI devices will be inaccessible.
Failed to bind dma handle for
Driver was unable to bind a dma handle for the loop map. Driver did not attach to device, SCSI devices will be inaccessible.
Failed to attach
Driver was unable to attach for some reason that may be printed. Driver did not attach to device, SCSI devices will be inaccessible.
The next set of messages may display at any time. The full device pathname, followed by the shorter form described above, will precede
the message.
Invalid lilp map
The driver did not obtain a valid lilp map from the socal driver. SCSI device will be inaccessible.
Target t, AL-PA x and hard
The device with a switch setting t has an AL-PA x which does not match its hard address y. The device will not be accessible.
Duplicate switch settings
The driver detected devices with the same switch setting. All such devices will be inaccessible.
WWN changed on target t
The World Wide Name (WWN) has changed on the device with switch setting t.
Target t, unknown device type
The driver does not know the device type reported by the device with switch setting t.
SunOS 5.10 27 Mar 1997 sf(7D)