Date: Wed, 30 Sep 2009 10:37:30 +0100 From: Robin Becker <robin@reportlab.com> To: freebsd-questions@freebsd.org Cc: Adam Vande More <amvandemore@gmail.com> Subject: Re: fix remote degraded gmirror Message-ID: <4AC326DA.1070005@chamonix.reportlab.co.uk> In-Reply-To: <6201873e0909281056m1660351arc38c5faa975fef02@mail.gmail.com> References: <4AC07E69.30800@chamonix.reportlab.co.uk> <6201873e0909280710n2a5fc7beo99706e1b87080f73@mail.gmail.com> <4AC0D9CF.6000309@chamonix.reportlab.co.uk> <6201873e0909281056m1660351arc38c5faa975fef02@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
......... > > a simple > > dd if=/dev/zero of=/dev/adX bs=1M count=1 > > would fix that if nothing else > > if there's was no existing label, there is nothing to do except gmirror man > instructions. Gmirror is block level mirroring which why no other steps are > needed. > well now I really need advice, the data centre guy successfully inserted another disk in the right place and it appears to be the same model. However, smartctl -a /dev/ad4 seems to show a number of errors and many of the indicators are prefail or old_age. In addition the disk doesn't have exactly the same length so when I tried to insert gmirror complains that it is too small. What are my options? -- Robin Becker
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AC326DA.1070005>