07-15-2009
Quote:
Originally Posted by
Sapfeer
Sorry for delays, I didn't receive notification about your answer. Try fsck on c0d1
No problem,
Quote:
-bash-3.00# fsck /dev/rdsk/c0d1
fsck: could not stat /dev/rdsk/c0d1: No such file or directory
Quote:
fsck /dev/rdsk/c0d1s2
** /dev/rdsk/c0d1s2
BAD SUPERBLOCK AT BLOCK 16: MAGIC NUMBER WRONG
LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS? ^C
Quote:
-bash-3.00# fsck -y /dev/rdsk/c0d1s2
** /dev/rdsk/c0d1s2
BAD SUPERBLOCK AT BLOCK 16: MAGIC NUMBER WRONG
LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS? yes
LOOK FOR ALTERNATE SUPERBLOCKS WITH NEWFS? yes
SEARCH FOR ALTERNATE SUPERBLOCKS FAILED.
USE GENERIC SUPERBLOCK FROM MKFS? yes
CALCULATED GENERIC SUPERBLOCK WITH MKFS
If filesystem was created with manually-specified geometry, using
auto-discovered superblock may result in irrecoverable damage to
filesystem and user data.
CANCEL FILESYSTEM CHECK? yes
Please verify that the indicated block contains a proper
superblock for the filesystem (see fsdb(1M)).
FSCK was running in YES mode. If you wish to run in that mode using
the alternate superblock, run `fsck -y -o b=1213632 /dev/rdsk/c0d1s2'.
/var/adm/messages
Quote:
Cluster.devices.did: [ID 230304 daemon.notice] cldev: (C507896) Inquiry on device "/dev/rdsk/c0d1s2" failed
Any idea? Thanks!!
Last edited by upengan78; 07-15-2009 at 01:16 PM..
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
On solaris 10, t5120,
I don't understand what are the last 2 file systems
so last 2 file systems what are they, why are they getting shown and also confused why the swap is shown so many times and different size when I set it to 16 G at the time of installing solaris 10. ( rest... (3 Replies)
Discussion started by: upengan78
3 Replies
2. Solaris
hi All,
We tried to establish a connection from OpenSSH3.8.1 running on Windows Box to SunSSH-1.1 running on Solaris 10. Please see the debug statements.
C:\Documents and Settings\sadmin\.ssh>ssh sadmin@10.4.3.8 -v -v -v
OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004
debug1: Reading... (2 Replies)
Discussion started by: venusunil
2 Replies
3. Virtualization and Cloud Computing
I'm trying to configure sun cluster 3.2 on vmware server 2.0 on windows xp host with solaris 10x86 guests VM3 and VM4 and i 'm running scinstall from VM4 .. it fails with following error
Initializing cluster name to "laptop" ... done
Initializing authentication options ... done
Initializing... (0 Replies)
Discussion started by: fugitive
0 Replies
4. Solaris
In my 2 node cluster (sun cluster3.2) running on x86 VMs. One of my nodes VM1 does not have the global devices populated due to which i cannot failover my file system to node VM1 , what could be the reason for this and how can i rectify it ?
VM1:/>cd /dev/global
-bash: cd: /dev/global: No... (1 Reply)
Discussion started by: fugitive
1 Replies
5. Solaris
I want to configure Sun Cluster3.2 with Oracle10g ... i created 4 resources namely , logical host, sotrage, oracle -server & Listener .. all work fine butoracle resource does not come up .. though i can bring up the oracle outside sun cluster.
node1:/>clrg online ora-rg
clrg: (C450598) On... (1 Reply)
Discussion started by: fugitive
1 Replies
6. Solaris
Failed to recover lost root password for Solaris SunSparc
(On Sun Ultra10 - SPARC CPU Hardware, not x86 Intel CPU nor x64 AMD CPU)
This Sun Ultra10 workstation comes with an old 6-in wafer probing station purchased from a Surplus equipment vendor.
Computer: Sun Ultra 5/10 UPA/PCI... (21 Replies)
Discussion started by: fromtexas0
21 Replies
7. Solaris
Can someone point me to a procedure detailing the replacement of a failed battery in a SUN 6540 controller.
Or describe the procedure.
Thanks (1 Reply)
Discussion started by: USFE
1 Replies
8. Solaris
Hi folks,
I was patching Sun server (SunOS suns121 5.10 Generic_144488-17 sun4v sparc SUNW,Sun-Fire-T200) with the lateset bundle. It was completed with no errors. Server was restarted with shutdown command
(/usr/sbin/shutdown -y -i6 -g0) after patching was complete. However, after that,... (3 Replies)
Discussion started by: zulu1
3 Replies
9. Solaris
Hi Guys,
I have recently started reciving below Error message
Failed HTTPS transfer to https://supportfiles.sun.com/curl
whenever I run
/usr/local/bin/sudo /opt/SUNWexplo/bin/explorer -P -q -v
from all Servers.
Looks like the SSL certificate as Expired.
Whenever I type... (4 Replies)
Discussion started by: manalisharmabe
4 Replies
10. Solaris
Hi
I am new to this forum & oracle DBA also, I would like to know that can we add Oracle ASM in failover mode in sun cluster 3.3 or 4.0 means that if suppose oracle is running along with ASM on node1 & this node went down due to hardware issue then both oracle along with ASM must move to... (1 Reply)
Discussion started by: hb00
1 Replies
LEARN ABOUT OSX
volrmmount
volrmmount(1) User Commands volrmmount(1)
NAME
volrmmount - call rmmount to mount or unmount media
SYNOPSIS
volrmmount [-i | -e] [name | nickname]
volrmmount [-d]
DESCRIPTION
The volrmmount utility calls rmmount(1M) to, in effect, simulate an insertion (-i) or an ejection (-e). Simulating an insertion often
means that rmmount will mount the media. Conversely, simulating an ejection often means that rmmount will unmount the media. However,
these actions can vary depending on the rmmount configuration and media type (see rmmount.conf(4)).
For example, if you use the default /etc/rmmount.conf and insert a music CD, it will not be mounted. However, you can configure rmmount so
that it calls workman whenever a music CD is inserted.
This command allows you to override Volume Management's usual handling of media (see EXAMPLES below).
OPTIONS
The following options are supported:
-i Simulates an insertion of the specified media by calling rmmount.
-e Simulates an ejection of the specified media by calling rmmount.
-d Displays the name of the default device for volrmmount to handle. This device is used if no name or nickname is supplied.
OPERANDS
The following operands are supported:
name The name that Volume Management recognizes as the device's name. See volfs(7FS).
nickname A shortened version of the device's name. Following is the list of recognized nicknames:
+-----------------------------+-----------------------------+
| Nickname | Path |
+-----------------------------+-----------------------------+
|fd |/dev/rdiskette |
+-----------------------------+-----------------------------+
|fd0 |/dev/rdiskette |
+-----------------------------+-----------------------------+
|fd1 |/dev/rdiskette1 |
+-----------------------------+-----------------------------+
|diskette |/dev/rdiskette |
+-----------------------------+-----------------------------+
|diskette0 |/dev/rdiskette0 |
+-----------------------------+-----------------------------+
|diskette1 |/dev/rdiskette1 |
+-----------------------------+-----------------------------+
|rdiskette |/dev/rdiskette |
+-----------------------------+-----------------------------+
|rdiskette0 |/dev/rdiskette0 |
+-----------------------------+-----------------------------+
|rdiskette1 |/dev/rdiskette1 |
+-----------------------------+-----------------------------+
|floppy |/dev/rdiskette |
+-----------------------------+-----------------------------+
|floppy0 |/dev/rdiskette0 |
+-----------------------------+-----------------------------+
|floppy1 |/dev/rdiskette1 |
+-----------------------------+-----------------------------+
|cdrom0 |/vol/dev/rdsk/cXtYdZ/label |
+-----------------------------+-----------------------------+
|zip0 |/vol/dev/rdsk/cXtYdZ/label |
+-----------------------------+-----------------------------+
|jaz0 |/vol/dev/rdsk/cXtYdZ/label |
+-----------------------------+-----------------------------+
|rmdisk0 |/vol/dev/rdsk/cXtYdZ/label |
+-----------------------------+-----------------------------+
EXAMPLES
Example 1: Using the volrmmount command
When Volume Management finds a floppy that contains a filesystem, it calls rmmount to mount it. If you wish to run tar(1) or cpio(1) on
that floppy, it must first be unmounted. To unmount the floppy use:
example% volrmmount -e floppy0
After volrmmount unmounts the floppy, if you wish to re-mount it (rather than ejecting it and reinserting it) use:
example% volrmmount -i floppy0
Notice that if you are using a named floppy, you can use its name in place of floppy0.
FILES
/dev/volctl Volume Management control port
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWvolu |
+-----------------------------+-----------------------------+
SEE ALSO
cpio(1), eject(1), tar(1), rmmount(1M), vold(1M), rmmount.conf(4), attributes(5), volfs(7FS)
NOTES
Volume Management (vold) must be running to use this command.
SunOS 5.10 30 Aug 2000 volrmmount(1)