11-08-2005
Quote:
Originally Posted by RTM
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
The boot disk looks like it refers to the c1t0d0 disk according to eeprom. It doesn't indicate the slice.
I think that error occured because of an incorrect powerdown... But I'm not sure because I just got a hold of this box. As I said the drive light indicators on the outside of the box aren't indicating any faults. On the negative side, format does not list c1t3d0, but it does list c1t1d0 as well as all other drives.
Is there any way to tell if the disk is definetely bad? The box was recently moved, so I am concerned the drives may have been rattled around a bit, maybe even come unseated. I was thinking of powering down, reseating all the drives, then booting and running touch /reconfigure. If the drive was previously detected in the system would I even need to do that for it to come back online?
Thanks!
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 LINUX
unknown
UNKNOWN(1) General Commands Manual UNKNOWN(1)
NAME
unknown - identify possible genotypes for unknowns
SYNOPSIS
A program to rapidly identify which genotypes are possible for individuals typed as unknowns in the input pedigree.
unknown [ -cl ]
DESCRIPTION
unknown infers possible genotypes and mating combinations for parents with unknown genotypes for ilink(1), mlink(1) and linkmap(1).
OPTIONS
-c Use conditional allele frequencies.
-l Choose a good set of loop breakers automatically.
RETURN VALUE
0 Successful completion
ERRORS
10 File not found
255 Failure
EXAMPLES
Normally, unknown(1) is run immediately prior to its sister programs, ilink(1), mlink(1) and linkmap(1), like this:
unknown
mlink
FILES
unknown(1) reads the two files pedfile.dat and datafile.dat as its own input and produces various temporary files that are used as input to
the next program. These temporary files are ipedfile.dat, upedfile.dat, speedfile.dat and newspeedfile.dat.
NOTES
unknown(1) is part of the FASTLINK package, which is a re-implementation of the LINKAGE suite of computer tools that help investigate
genetic linkage as first proposed G.M. Lathrop, J.M. Lalouel, C. Julier, and J. Ott.
AUTHORS
Dylan Cooper, Alejandro Schaffer, and Tony Schurtz based on work originally by Jurg Ott, Ph.D, et. al.
This manual page was written by Elizabeth Barham <lizzy@soggytrousers.net> for the Debian GNU/Linux system (but may be used by others).
WORD-WIDE-WEB
http://www.ncbi.nlm.nih.gov/CBBResearch/Schaffer/fastlink.html
SEE ALSO
ilink(1), linkmap(1), lodscore(1), mlink(1).
April 15, 2003 UNKNOWN(1)