Ok do you know if the new disk has been detected ? Please issue this command:
devfsadm -nv Note: Be carefull with this command, issue it with the "-n" command, else it would load new devices and drivers and i don't want to modify anything on your server/pc. Thanks. On Mon, Sep 21, 2009 at 10:13 AM, Martijn de Munnik <[email protected]> wrote: > > On Mon, 2009-09-21 at 10:01 -0300, Walter Lamagna wrote: >> Have you the correct amount of metadb ? Please reply with the state >> of the meta databases (metadb -i). > > flags first blk block count > a m p luo 16 8192 /dev/dsk/c0d0s1 > a p luo 8208 8192 /dev/dsk/c0d0s1 > a p luo 16 8192 /dev/dsk/c0d0s6 > a p luo 8208 8192 /dev/dsk/c0d0s6 > a p luo 16 8192 /dev/dsk/c1d0s1 > a p luo 8208 8192 /dev/dsk/c1d0s1 > a p luo 16 8192 /dev/dsk/c1d0s6 > a p luo 8208 8192 /dev/dsk/c1d0s6 > a u 16 > 8192 /dev/dsk/c2t0d0s1 > a u 8208 > 8192 /dev/dsk/c2t0d0s1 > a u 16 > 8192 /dev/dsk/c2t0d0s6 > a u 8208 > 8192 /dev/dsk/c2t0d0s6 > r - replica does not have device relocation information > o - replica active prior to last mddb configuration change > u - replica is up to date > l - locator for this replica was read successfully > c - replica's location was in /etc/lvm/mddb.cf > p - replica's location was patched in kernel > m - replica is master, this is replica selected as input > W - replica has device write errors > a - replica is active, commits are occurring to this replica > M - replica had problem with master blocks > D - replica had problem with data blocks > F - replica had format problems > S - replica is too small to hold current data base > R - replica had device read errors > >> >> May be the minimum majority algorithm is failing and there are not >> (half + 1) replicas available, causing the metadb to be declared >> invalid. > > I have these lines in /etc/system > > * Begin MDD root info (do not edit) > rootdev:/pseudo/m...@0:0,0,blk > * End MDD root info (do not edit) > set md:mirrored_root_flag=1 > set md_mirror:md_resync_bufsz=2048 > > > c0d0 and c1d0 are the internal scsi disks, c2t0d0 is the 3rd (temporary > usb) disk. > >> >> Thanks. >> >> On Mon, Sep 21, 2009 at 9:47 AM, Martijn de Munnik <[email protected]> >> wrote: >> > Hi list, >> > >> > I've posted a question on the Sun forums but it is unanswered. >> > >> > http://forums.sun.com/thread.jspa?threadID=5407876 >> > >> > In short: I have a mirror of two disk which both have hardware errors. >> > The errors are on different sectors on each disk so the mirror should >> > still work. I tried to replace the disk in the mirror without dataloss >> > by adding a third disk to the mirror. But the third disk won't sync... >> > >> > Any ideas? >> > >> > -- >> > >> > Martijn >> > >> > _______________________________________________ >> > Solaris-Users mailing list >> > [email protected] >> > http://www.filibeto.org/mailman/listinfo/solaris-users >> > >> >> >> > > Met vriendelijke groet, > > Martijn de Munnik > > -- > YoungGuns > Kasteleinenkampweg 7b > 5222 AX 's-Hertogenbosch > T. 073 623 56 40 > F. 073 623 56 39 > www.youngguns.nl > KvK 18076568 > > _______________________________________________ > Solaris-Users mailing list > [email protected] > http://www.filibeto.org/mailman/listinfo/solaris-users > -- Walter Lamagna, Eng, SCSA. serverlinux.blogspot.com www.magnacounter.com _______________________________________________ Solaris-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/solaris-users
