Date: Wed, 30 Sep 2009 07:55:45 -0500 From: Adam Vande More <amvandemore@gmail.com> To: Robin Becker <robin@reportlab.com> Cc: freebsd-questions@freebsd.org Subject: Re: fix remote degraded gmirror Message-ID: <6201873e0909300555x3721c3ccq45c604bd28c1f8c@mail.gmail.com> In-Reply-To: <4AC326DA.1070005@chamonix.reportlab.co.uk> References: <4AC07E69.30800@chamonix.reportlab.co.uk> <6201873e0909280710n2a5fc7beo99706e1b87080f73@mail.gmail.com> <4AC0D9CF.6000309@chamonix.reportlab.co.uk> <6201873e0909281056m1660351arc38c5faa975fef02@mail.gmail.com> <4AC326DA.1070005@chamonix.reportlab.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 30, 2009 at 4:37 AM, Robin Becker <robin@reportlab.com> wrote: > ......... > >> >> 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 > This has been answered already but you should be aware that when using gmirror, your back disk should either be the same model or bigger as hard drive capacities differ between manufacturers. As in Seagate 250GB ~= WD 250GB. So this is not an uncommon problem. -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6201873e0909300555x3721c3ccq45c604bd28c1f8c>