Sponsored Content
Operating Systems Solaris replacing root disk SunFire 280R Post 302226367 by Smiling Dragon on Monday 18th of August 2008 08:26:25 PM
Old 08-18-2008
This should be pretty simple to sort out but I'm going to have to make a few assumptions as I don't know your metadevice naming standard, you've not posted your md.tab and without CODE tags round the metastat output it's very hard to read.
</grumble>

Righty, that out of the way, lets take a look at your current status and draw some inferences:
I think your current setup is thus:
Mirror devices:
d37
d35
d34
d33
d31
d30
Each mirror has two submirrors, d1x and d2x. Does that sound correct?
Your metadb is on slice 6, correct?
It also looks like the disk that died is c1t1d0, correct?

If all those assumptions are correct, (if not, stop here and clarify) then the normal course of action is to replace the failed disk, then run metareplace -e <mirror device> c1t1d0s<slice number> for each slice of the new disk.
Unfortunately you've already blown away most of your submirrors so we'll need to rebuild - don't worry, that's safe and easy and you won't lose any data Smilie Just a little more tedious.
As you've left d31 intact, fix that one by running:
Code:
metareplace -e d31 c1t1d0s1

While that rebuilds, we'll check the metadbs out.
Run
Code:
metadb

to list all the copies of the db. Anything with a W by it (probably everything on c1t1d0s6) is buggered. Provided you still have a few good copies of it, remove the faulty versions of the db. Count how many there are on that device, then run:
Code:
metadb -d c1t1d0s6

.
Then re-add them:
Code:
metadb -a -c <number of copies> c1t1d0s6

.
Now wait here until d31 has finished synching:
Code:
metastat | grep '%'

Wait until it stops showing you a % complete.
As you've already created all your submirror metadevices, the only thing left to do it attach them - One by one (yes really, anything else is _way_ slower). For each remaining mirror in the list, run:
Code:
metattach d3x d2x

I don't know what d38 d39 and d41 are for so I'm ignoring them for now Smilie
 

10 More Discussions You Might Find Interesting

1. Solaris

pls help urgently....for SUNfire 280R

hi, i hv received SUNfire 280R system ........for its initial configuration i want to connect to it through hyperterminal from the windows system..........i hv got one serial port to RJ-45 port converter with the system............can anybody tell me the normal console cable which is used to... (3 Replies)
Discussion started by: girish_shukla
3 Replies

2. Solaris

How to rebuild root disk - 280R

Hi!, We have a SUN Server 280R (2 *36GB) disks. The disk with the root filesystem needs to be replaced! Lots of H/W error messages! We have the new disk - but how do we go about re-building it! Is there any document or location where I can get detailed re-build instructions? Any help... (7 Replies)
Discussion started by: sdharmap
7 Replies

3. Solaris

how to do live upgrade from solaris8 to 9 for sunfire 280R?

hi!!!!!! how to upgrade sunfire 280R server from solaris8 to solaris9? pls help me. Thanks & Regards -Vishal (1 Reply)
Discussion started by: Vishal Shroff
1 Replies

4. Solaris

Sunfire 280R Can't Recognize Floppy Drive

Greetings all, I'm in a bit of a situation. I have this Sunfire 280R system that did not have a floppy drive in it, yet we needed one. We grabbed one from another Sun box we had laying around unused, and installed it. The system couldnt recognize it. Tried another floppy drive (non-sun) and... (4 Replies)
Discussion started by: snackiesmores
4 Replies

5. Solaris

Sunfire 280R disks ?

Hi there Does anybody know what the biggest capacity disk I can get into a Sunfire 280R I currently have two 73gb disks , but I need to get these up to the biggest available Any help would be greatly appreciated (4 Replies)
Discussion started by: hcclnoodles
4 Replies

6. Solaris

Sunfire 280R Solaris 5.9 booting

Hi, I have to question: 1) when O/S is booting, i see messages: /dev/rdsk/c1t0d0s5: is logging /dev/rdsk/c1t0d0s3: is logging /dev/rdsk/c1t0d0s7: is logging i partitioned these slices during installation of O/S 5.9. I can access to these mountpoint no problem. But... (3 Replies)
Discussion started by: lamoul
3 Replies

7. Solaris

Patch update on sunfire 280R sparc for solaris 5.9

Hi, i just finished installing solaris 5.9 and I'm looking for the tools to tell me if i should update the patches or how to make sure that the current patches are ok? thanks (2 Replies)
Discussion started by: lamoul
2 Replies

8. Solaris

Install SUN O/S 5.9 on Sparc Sunfire 280R

Hi, I' trying to install O/S 5.9 on Sparc system Sunfire 280R. I downloaded CD install and CD 2 from Sun Website but later i dowloaded CD 2 that i forgot for my installation. All CD are in ISO formats. I boot system at OK prompt then issue OK boot cdrom when it asks for CD 1, i removed... (7 Replies)
Discussion started by: lamoul
7 Replies

9. Hardware

Updating OBP on a Sun Sunfire 280R

Hi, I'm a newbie in the Unix world... :confused: I own a Sun Sunfire 280R computer with one 750Mhz CPU. I ordered two CPU of 900Mhz to replace it; however in the Service manual from Sun I read that to use 900Mhz CPU i will need to have a OBP of at least version 4.5.16. When I type .version in... (2 Replies)
Discussion started by: Monkey114
2 Replies

10. Hardware

SunFire 280R maintenance LED is on and no display

I got the system couple of days back from one of my friend. Last night I turned it on and I noticed that maintenance LED is on. At the same time I added an LCD monitor via VGA and nothing was showing on the screen. Though the system does not have any HDD So not sure if system will even show a BIOS... (3 Replies)
Discussion started by: pgirish007
3 Replies
mddb.cf(4)							   File Formats 							mddb.cf(4)

NAME
mddb.cf - metadevice state database replica locations SYNOPSIS
/etc/lvm/mddb.cf DESCRIPTION
The /etc/lvm/mddb.cf file is created when the metadb(1M) command is invoked. You should never directly edit this file. The file /etc/lvm/mddb.cf is used by the metainit(1M) command to find the locations of the metadevice state databases replicas. The metadb command creates the file and updates it each time it is run. Similar information is entered in the /kernel/drv/md.conf file. Each metadevice state database replica has a unique entry in the /etc/lvm/mddb.cf file. Each entry contains the driver and minor unit num- bers associated with the block physical device where a replica is stored. Each entry also contains the block number of the master block, which contains a list of all other blocks in the replica. Entries in the /etc/lvm/mddb.cf file are of the form: driver_name minor_t daddr_t checksum where driver_name and minor_t represent the device number of the physical device storing this replica. daddr_t is the disk block address. checksum is used to make certain the entry has not been corrupted. A pound sign (#) introduces a comment. EXAMPLES
Example 1: Sample File The following example shows a mddb.cf file. #metadevice database location file do not hand edit #driver minor_t daddr_t device id checksum sd 152 16 id1,sd@SSEAGATE_JDD288110MC9LH/a -2613 In the example above, the value for daddr_t indicates that the offset from the start of a given partition is 16 disk blocks from the start of that partition. FILES
/etc/lvm/mddb.cf /kernel/drv/md.conf SEE ALSO
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metarename(1M), metareplace(1M), metaroot(1M), metassist(1M), metaset(1M), metastat(1M), metasync(1M), metattach(1M), md.cf(4), md.tab(4), attributes(5), md(7D) Solaris Volume Manager Administration Guide SunOS 5.10 8 Aug 2003 mddb.cf(4)
All times are GMT -4. The time now is 07:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy