Date: Wed, 30 Sep 2009 15:07:00 +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: <4AC36604.1050606@chamonix.reportlab.co.uk> In-Reply-To: <6201873e0909300555x3721c3ccq45c604bd28c1f8c@mail.gmail.com> 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> <6201873e0909300555x3721c3ccq45c604bd28c1f8c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Adam Vande More wrote: ......... >> > > 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. > > yes this is a fairly old WD original was Device Model: WDC WD1600JS-22MHB0 Firmware Version: 02.01C03 User Capacity: 160,041,885,696 bytes they replaced with Device Model: WDC WD1600JS-75NCB2 Firmware Version: 10.02E03 User Capacity: 160,000,000,000 bytes which looks quite strange as it looks like something got lopped off somehow. I didn't think bad blocking/sectoring was done any more. Anyhow they've removed this disk and are considering options (at least I hope they are). -- Robin Becker
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AC36604.1050606>