Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 29 Jun 2013 00:36:59 +0200
From:      Nikola =?utf-8?B?UGF2bG92acSH?= <nzp@riseup.net>
To:        Charles Swiger <cswiger@mac.com>
Cc:        Adam Vande More <amvandemore@gmail.com>, FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: Troubleshooting a gmirror disk marked broken
Message-ID:  <20130628223659.GB15414@sputnjik.localdomain>
In-Reply-To: <0469490B-A577-40DA-9A04-910150330E16@mac.com>
References:  <20130627023837.GA7685@sputnjik.localdomain> <36C962B9-ABC4-45E3-AC94-46D6CEE960E1@mac.com> <CA+tpaK0rT83sMcaQTsg3m31Gr2RrnZBTbDgr-sZyWAS_6fzS5w@mail.gmail.com> <0469490B-A577-40DA-9A04-910150330E16@mac.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, Jun 27, 2013 at 10:06:45AM -0700, Charles Swiger wrote:
> Hi--
> 
> On Jun 27, 2013, at 9:58 AM, Adam Vande More <amvandemore@gmail.com> wrote:
> > On Thu, Jun 27, 2013 at 10:16 AM, Charles Swiger <cswiger@mac.com> wrote:
> >> If you haven't rebuilt the mirror already, running a full disk read scan
> >> against both drives (ie, via "dd if=/dev/ad4 of=/dev/null bs=1m" or similar)
> >> might be prudent.  That will help identify/migrate any sectors which are
> >> failing but still recoverable via ECC to the spare sectors.
> > 
> > I was going to say something like that too but AFAIK sectors aren't remapped on failed reads, has to be written to(dd if=/dev/zero of=/dev/ad4 bs=1m).  If it were me, I make sure I had fully tested complete backups before I broke the mirror and did that.
> 
> 
> If the drive reads a sector with ECC-correctable errors, it's supposed to try to re-write that sector in order to fix up the ECC data.  If that write fails, it remaps.
> 
> Of course, your suggestion of blanking the entire drive and restoring from the mirror or a backup would be best, or perhaps "better short of replacing the drive".
> 

OK, thank you both for suggestions.  It rebuilt fine, and it's working
fine.  If it starts giving me trouble again I'll try your suggestions,
or, ultimately, ask to get the disk replaced (although I don't expect a
much better replacement, it's one of those cheap rental servers, you get
what you pay :))

I'm still a bit reluctant to run the ports tree update again, but I'll
ask on -ports@ for further assistance with that.



-- 
Writing free verse is like playing tennis with the net down.




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20130628223659.GB15414>