10-07-2002
mount point lost
hi ,
I was applying patches after that when i reboot i get these message. I did not do anything other thatn this. Now i am unable to start my oracle . Tell me how to solve this
These are the error messages
forceload of /drv/rdriver failed
/drv/rdmexus failed
drvconfig - driver failed to attach : rdriver
mount pt - /dev/dsk/c4t5s0s6 or /u01
unable to repair one or more fs
Run fsck manually
/dev/rsdk/c4t5d0s6 - no such file or directory
regards
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
A disk was sliced into 6 slices with m01 being the mount point for one of the slices. This mount point was deleted with rmdir (ie. rmdir m01).
What is the easiest way to recover this mount point? (1 Reply)
Discussion started by: here2learn
1 Replies
2. UNIX for Dummies Questions & Answers
hi people,
I'm trying to create a mount point, but am having no sucess at all, with the following:
mount -F ufs /dev/dsk/diskname /newdirectory
but i keep getting - mount-point /newdirectory doesn't exist.
What am i doing wrong/missing?
Thanks
Rc (1 Reply)
Discussion started by: colesy
1 Replies
3. UNIX for Dummies Questions & Answers
hi
can i know what is the command to create auto mount point in my unix server? is there any directory which i have to go? (1 Reply)
Discussion started by: legato
1 Replies
4. UNIX for Dummies Questions & Answers
Hi All
I Know it is a really basic and stupid question perhaps...But I am going bonkers..
I have following valid paths in my unix system:
1. /opt/cdedev/informatica/InfSrv/app/bin
2. /vikas/cdedev/app
Both refer to the same physical location. So if I created one file 'test' in first... (3 Replies)
Discussion started by: Vikas Sood
3 Replies
5. UNIX for Advanced & Expert Users
Hello all,
I'm sharing 1 volume from a Sun Storage array (6130), out to 2 servers. Created a slice on one server and mounted a filesystem. On the other server the disk already sees the created slice from the other server (shared throught the storage array, so mounted this filesystem as well.
... (1 Reply)
Discussion started by: Sunguy222
1 Replies
6. UNIX for Advanced & Expert Users
is there any command to know the list of mount points in a server.i need only the mount point lists.i tried using df but it was not helpful.i am using Solaris (1 Reply)
Discussion started by: dr46014
1 Replies
7. Solaris
Dear Gurus,
Could it be possible to have the output of df -k sorted? The df -k output messed up after recent power trip.
Also, is there any folders that I should look into to reduce the root size (other than /var/adm and /var/crash) after server crash?
Many thanks in advance.
... (2 Replies)
Discussion started by: honmin
2 Replies
8. AIX
Deart All,
can any one help to do this,
i need to change mount point in AIX 6
/opt/OM should be /usr/lpp/OM, how do i do....
Please help me Urgent issue (2 Replies)
Discussion started by: gulamibrahim
2 Replies
9. Shell Programming and Scripting
Hi Guys,
I have Solaris 9 and RHEL 5 boxes I implemented script to send me an email when my mount point is > 90.
Now the ouput id like these:
/dev/dsk/emcpower20a 1589461168 1509087840 64478720 96% /data1
/dev/dsk/emcpower21a 474982909 451894234 18338846 97% /data2... (2 Replies)
Discussion started by: Phuti
2 Replies
10. UNIX for Beginners Questions & Answers
How to create a new mount point with 600GB and add 350 GBexisting mount point
Best if there step that i can follow or execute before i mount or add diskspace IN AIX
Thanks (2 Replies)
Discussion started by: Thilagarajan
2 Replies
usoc(7D) Devices usoc(7D)
NAME
usoc - universal serial optical controller for Fibre Channel arbitrated loop (SOC+) device driver
DESCRIPTION
The Fibre Channel adapter is an SBus card that implements two full duplex Fibre Channel interfaces. Each interface can connect to a Fibre
Channel arbitrated loop (FC-AL). The usoc device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.
FILES
/kernel/drv/usoc
32-bit ELF kernel module
/kernel/drv/sparcv9/usoc
64-bit ELF kernel module
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
|Interface stability |Unknown |
+-----------------------------+-----------------------------+
|Availability |SUNWusoc |
+-----------------------------+-----------------------------+
SEE ALSO
fctl(7D), sbus(4), fcp(7D), fp(7D), ssd(7D)
Writing Device Drivers
Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994
Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998
Fabric Channel Loop Attachment (FC-FLA), NCITS TR-20:1998
DIAGNOSTICS
The following messages are logged and may also appear on the system console. On the console these messages are preceded by:
usoc%d:
where
usoc%d:
is the per-port instance number of the usoc controller.
Fibre Channel is ONLINE
The Fibre Channel loop is now online.
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: alloc soft state.
Driver did not attach, devices will be inaccessible.
attach failed: bad soft state.
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 20 Jul 1999 usoc(7D)