Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Jun 2013 08:16:48 -0700
From:      Charles Swiger <>
To:        =?utf-8?Q?Nikola_Pavlovi=C4=87?= <>
Subject:   Re: Troubleshooting a gmirror disk marked broken
Message-ID:  <>
In-Reply-To: <20130627023837.GA7685@sputnjik.localdomain>
References:  <20130627023837.GA7685@sputnjik.localdomain>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

On Jun 26, 2013, at 7:38 PM, Nikola Pavlovi=C4=87 <> =
[ ... ]
> At the moment I'm attaching smartctl -a results for both disks (ad4 =
> marked broken).  As I'm completely useless in deciphering smartctl
> results (apart from being thought by experience to pretty much
> ignore(tm) the 'Pre-fail' statuses), I'd appreciate assessment from =
> knowledgeable people.

As Adam said, your drives haven't failed, but they are on the way out.
Pay close attention to Reallocated_Sector_Ct, especially if it starts
jumping upwards.

You might also want to check the thermals; the Seagate is running at =
which is significantly hotter than it ought to be, except for maybe a =
I'd much rather see a drive running below 40C....

If you haven't rebuilt the mirror already, running a full disk read scan
against both drives (ie, via "dd if=3D/dev/ad4 of=3D/dev/null bs=3D1m" =
or similar)
might be prudent.  That will help identify/migrate any sectors which are
failing but still recoverable via ECC to the spare sectors.


Want to link to this message? Use this URL: <>