11-08-2005
M p unknown unknown /dev/dsk/c1t1d0s4 << bad disk
M p unknown unknown /dev/dsk/c1t3d0s4 << bad disk
Note in your metadb - looks like someone added to the metadb but never rebooted - that's usually why you get the unknown in the status although it's possible you are also getting it because the disks are bad. The good thing is that there are so many copies of the metadb - so you can replace the bad disks without no worry about losing anything.
As far as the bad disk, get the replacement disk drives and you can use the metareplace command. Or you can use metadetach and metaclear to remove them from the metastat and replace the drives, format, and readd them. You can hot swap the drives so you should not need any down time.
Also, insure that the boot device is c1t0d0s0 and not c1t1d0s0. You don't want to hot swap or remove the drive you are booted off of (inital boot will be off one drive and then the mirrors come into play). Just check the output of eeprom and look for boot-device - hopefully it isn't simply "disk:a" but gives you the output that you would be able to tell which drive it really is. If not, then you can play it safe and reboot into single user to do the drive replacements. More info can be found
in this thread
10 More Discussions You Might Find Interesting
1. Solaris
Hi Guys,
Need to add 2 disks into a JBOD array (3310).
Does anyone see anything wrong with my Procedure / Doco below?
1> Logon to system, check system logs for abnormal entries.
2> Make backups of related system files:
A>cp -p /etc/system /etc/system.backup.081505
B>cp -p /etc/vfstab... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
2. Solaris
hi expert,
sorry i'm new in solaris system, need more advice and help :)
i'm confusing with mirroring disk at my sparc v890 solaris 8, i have 6 harddisk which the structure shown below :
format :
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
... (4 Replies)
Discussion started by: bucci
4 Replies
3. Solaris
Hi
I have a Sunfire X4100 box with a 4 disk Chassis (although I only have 2 disks in it). I have been asked to add two more disks into the chassis so that I can mirror the original two using SVM .....Ive read through a couple of SVM docs but am finding it a little confusing, and if any of you... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
4. Solaris
I am having an issue with setting up disk mirroring for Solaris 10 on an x86 server. My main problem is that the volumes and slices have already been setup and our proprietary software has already been installed and configured. The entire drive has been allocated in this configuration and the... (2 Replies)
Discussion started by: chuck43
2 Replies
5. Solaris
Has anyone managed to set up disk mirroring in Solaris 10 yet? If so can you point me in the direction of some useful documentation please.
Cheers (25 Replies)
Discussion started by: korfnz
25 Replies
6. Solaris
Hi Friends,
I am having Sun Solaris 5.8 OS installed having 2 different size hard disk, sizes are c0t0d0s0(160 GB) and c0t2d0s0 (40GB). I have installed Sun Solaris 5.8 OS in c0t0d0s0 (160GB) harddisk.
I have configured all the parameters required for disk mirroring. But when executing... (4 Replies)
Discussion started by: Vijayakumarpc
4 Replies
7. Solaris
Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment.
Let me know if you need any deatils on this.
Thanks,
Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies
8. Solaris
Hi Guys,
I have an issue with my Hotspares/Metastat on an x4270m2.
I have no hotspares available, when i printed out my metastat i got
d21: Concat/Stripe
Size: 33559785 blocks (16 GB)
Stripe 0:
Device Start Block Dbase Reloc
... (0 Replies)
Discussion started by: A-Train
0 Replies
9. Solaris
I would like to perform root disk mirroring task. Can someone please help me out on this.
Thanks !!
Regards,
Rama (2 Replies)
Discussion started by: ramagore85
2 Replies
10. Solaris
I have 2 disks in my system.I recently added a zpool to the disk, but today I changed my mind and deleted the zpool ,
zpool destroy -f extra
The zpool is now deleted and I want to partition the disk, so I delete the only partition on the disk.
Now when I run format again,
format... (13 Replies)
Discussion started by: cbtshare
13 Replies
LEARN ABOUT REDHAT
unknown
unknown(n) Tcl Built-In Commands unknown(n)
__________________________________________________________________________________________________________________________________________________
NAME
unknown - Handle attempts to use non-existent commands
SYNOPSIS
unknown cmdName ?arg arg ...?
_________________________________________________________________
DESCRIPTION
This command is invoked by the Tcl interpreter whenever a script tries to invoke a command that doesn't exist. The implementation of
unknown isn't part of the Tcl core; instead, it is a library procedure defined by default when Tcl starts up. You can override the
default unknown to change its functionality.
If the Tcl interpreter encounters a command name for which there is not a defined command, then Tcl checks for the existence of a command
named unknown. If there is no such command, then the interpreter returns an error. If the unknown command exists, then it is invoked with
arguments consisting of the fully-substituted name and arguments for the original non-existent command. The unknown command typically does
things like searching through library directories for a command procedure with the name cmdName, or expanding abbreviated command names to
full-length, or automatically executing unknown commands as sub-processes. In some cases (such as expanding abbreviations) unknown will
change the original command slightly and then (re-)execute it. The result of the unknown command is used as the result for the original
non-existent command.
The default implementation of unknown behaves as follows. It first calls the auto_load library procedure to load the command. If this
succeeds, then it executes the original command with its original arguments. If the auto-load fails then unknown calls auto_execok to see
if there is an executable file by the name cmd. If so, it invokes the Tcl exec command with cmd and all the args as arguments. If cmd
can't be auto-executed, unknown checks to see if the command was invoked at top-level and outside of any script. If so, then unknown takes
two additional steps. First, it sees if cmd has one of the following three forms: !!, !event, or ^old^new?^?. If so, then unknown carries
out history substitution in the same way that csh would for these constructs. Finally, unknown checks to see if cmd is a unique abbrevia-
tion for an existing Tcl command. If so, it expands the command name and executes the command with the original arguments. If none of the
above efforts has been able to execute the command, unknown generates an error return. If the global variable auto_noload is defined, then
the auto-load step is skipped. If the global variable auto_noexec is defined then the auto-exec step is skipped. Under normal circum-
stances the return value from unknown is the return value from the command that was eventually executed.
SEE ALSO
info(n), proc(n)
KEYWORDS
error, non-existent command
Tcl unknown(n)