insufficient metadevice database replicas ERROR

Thread Tools Search this Thread
Operating Systems Solaris insufficient metadevice database replicas ERROR
# 1  
Old 11-11-2005
insufficient metadevice database replicas ERROR

First I would like to thank this forum for assisting me in setting up my 1st sunbox.
Could not have done it if it had not been for you guys and google Smilie

I have mirrored my box and have SUCCESSFULLY tested booting from the rootdisk and rootmirror successfully.
I am now looking at configuring the system to automatically boot the rootmirror when the rootdisk is not available/offline.

I initially received "md : d10 unavailable" messages, which I believe needed "nologging"
to be associated w/the root device in my /etc/vfstab file.

unfortunately, I am now receiving "insufficient metadevice" messages:

Insufficient metadevice database replicas located.

Use metadb to delete databases which are broken.
Ignore any "Read-only file system" error messages.
Reboot the system when finished to reload the metadevice database.
After reboot, repair any broken database replicas which were deleted.

Type control-d to proceed with normal startup

Is there a way to configure the box to automatically boot off the alternate?
Or do I have to DELETE the primary from the metadb before being able to bring the system backONLINE after a failed drive?


my eeprom contains the following:

test-args: data not available.
oem-logo: data not available.
oem-banner: data not available.
diag-file: data not available.
diag-device=rootdisk rootmirror
boot-file: data not available.
boot-device=rootdisk rootmirror
nvramrc=devalias rootdisk /pci@1f,700000/scsi@2/disk@0,0
devalias rootmirror /pci@1f,700000/scsi@2/disk@1,0
security-password: data not available.
diag-trigger=error-reset power-on-reset

my metadb contians the following:
# metadb -i
flags first blk block count
a p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a m p luo 16 8192 /dev/dsk/c1t1d0s7
a p luo 8208 8192 /dev/dsk/c1t1d0s7

when I created my DiskSuite database replicas I used the following command:
metadb -a -f -c2 /dev/dsk/c1t0d0s7 /dev/dsk/c1t1d0s7

my Drive slices are setup as follows:

# df -h | grep dsk
/dev/md/dsk/d30 14G 4.6G 9.6G 33% /
/dev/md/dsk/d31 5.8G 539M 5.2G 10% /var
/dev/md/dsk/d34 4.8G 4.9M 4.8G 1% /tmp
/dev/md/dsk/d32 14G 15M 14G 1% /apps
/dev/md/dsk/d35 15G 16M 15G 1% /dbaexports
/dev/md/dsk/d33 6.3G 8.0M 6.2G 1% /home
# swap -l
swapfile dev swaplo blocks free
/dev/md/dsk/d36 85,36 16 10247216 10247216
# 2  
Old 11-11-2005
At least three state database replicas should be created. The system will stay running with exactly half or more state database replicas available at any one time. The system will panic when less than half the state database replicas are available. The system will not reboot without one more than half the total state database replicas. Instead, it will go into single-user mode for administrative tasks.
Note the two last lines.

See DiskSuite User's Guide

If you only have two drives, it won't matter how many state database replicas you have - if you lose one drive, you won't have "one more than half the total state database replicas"
# 3  
Old 11-11-2005
thank you sir...
two drives = no automated solution in drive failure
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Xargs error: insufficient space for argument

I'm trying to crudely hack my way through some data processing. I have file.txt with around 17,000 lines like this: ACYPI002690-PA.aa.afa.afa.trim_phyml_tree_fullnames_fullhomolog.txt 3 72 71 ACYPI002690-PA.aa.afa.afa.trim_phyml_tree_fullnames_fullhomolog.txt 97 111 71... (1 Reply)
Discussion started by: pathunkathunk
1 Replies

2. UNIX for Advanced & Expert Users

sendmail error - 452 4.3.1 Insufficient system resources

Hi All, I am using svnnotify (which is available on net) script to send svn commit notification. Everything was working fine up to yesterday but from yesterday i started seeing error. 29CD01FCE44 7228 Thu Apr 5 11:11:51 (host said: 452... (6 Replies)
Discussion started by: vishal_vsh1
6 Replies

3. Solaris

zfs raidz2 - insufficient replicas

I lost my system volume in a power outage, but fortunately I had a dual boot and I could boot into an older opensolaris version and my raidz2 7 drive pool was still fine. I even scrubbed it, no errors. However, the older os has some smb problems so I wanted to upgrade to opensolaris11. I... (3 Replies)
Discussion started by: skk
3 Replies

4. Programming

Fortran runtime error: Insufficient data descriptors in format after reversion

Hello, I have some Fortran code that is providing the following error: At line 1165 of lapc_shells_2.f Fortran runtime error: Insufficient data descriptors in format after reversion Here are the lines just above and including 1165: WRITE (*,"('ATTEMPTING TO READ PLATE... (1 Reply)
Discussion started by: jm4smtddd
1 Replies

5. Solaris

Solaris Volume Manger - Database Replicas Question - Benefits of Increasing Default Size?

Hey all! I was hoping someone knew anything about this one... I know with Solaris Volume Manager the default Database Replica size is 8192 blocks (4MB approximately) Now I know you can increase this amount but is there any point? The reason I am asking this is that I've setup mirroring on... (2 Replies)
Discussion started by: Keepcase
2 Replies

6. Solaris

metadevices: how to test metadb (how to corrupt replicas/understanding replicas)

Hi all, I recently started exploring Solaris 10. I am testing metadevices now. I have been reading about the state databases here: 6.State Database (Overview) (Solaris Volume Manager Administration Guide) - Sun Microsystems So I created 3 metadbs on 2 slices (6 in total; c1t1d0s3... (3 Replies)
Discussion started by: deadeyes
3 Replies

7. Solaris

metadevice submirrors 0 and 1 not consistent

At a new job, I've inherited a handful of Solaris 10 SunFire V240 servers. I noticed that the metadevices are not consistent, in a way that I've not seen before.... internal mirrored disks: metadevice d60 has c1t0d0s6 as submirror 0 (d61) and c1t1d0s6 as submirror 1 (d62) metadevice... (1 Reply)
Discussion started by: Max Power
1 Replies

8. Solaris

metadevice problem

hi all i am very new to solaris...i am trying configure raid 0 in my ultrascsi box which is having 6 sun36GB hard disks. I have created 4 state database replicas in the following slices /dev/dsk/c1t1d0s7 /dev/dsk/c1t2d0s7 /dev/dsk/c1t3d0s7 and /dev/dsk/c1t4d0s7. i could not use any other... (7 Replies)
Discussion started by: kingston
7 Replies

9. Solaris

Problem with DiskSuite replicas

Good morning, I have Solstice disk suite installed on my server. One disk broke so I sostitute it. A replica was present on this disk. I had delete and then recreate it with commands metadb -d and metadb -a. Now when I inquire for the status of replicas I see this: stp11# metadb -i ... (2 Replies)
Discussion started by: bonovox
2 Replies

10. UNIX for Advanced & Expert Users

SDS and replicas

Hello, We are using Solstice Disk Suite on Solaris 2.7. We want to add two striped volume with six disks. On each disk, we take a slice and we create the stripe. That I want to know : Is it necessary to add two replicas on the same slice on the new disks, as made before on the others... (1 Reply)
Discussion started by: christophe
1 Replies
Login or Register to Ask a Question

Featured Tech Videos