Yesterday I did a backup of the sensible stuff of the pool and decided
to just break stuff on purpose ;)
I writed with dd over the sector marked as faulty by smartctl and
runned a smartctl short test. I repeated the process several times
until smartctl gave no errors at all on ada3.
After that i
Jeremy Chadwick wrote:
>
> CRC errors ...
>
>I have no real advice for tracking this kind of problem down. The most
>common response is "replace cables", which isn't necessarily the root
>cause. I have no advice or tips on how to track down interference
>issues, or how to truly examine a disk PCB
On Wed, Feb 15, 2012 at 07:17:57PM +0100, Victor Balada Diaz wrote:
> On Tue, Feb 14, 2012 at 06:16:01AM -0800, Jeremy Chadwick wrote:
> > Thanks. Both your drives look overall fine, sort-of. I'll outline my
> > concern points, and ask for some more info:
> >
> > * ada0 has 28 CRC errors, while
On Tue, Feb 14, 2012 at 06:16:01AM -0800, Jeremy Chadwick wrote:
> Thanks. Both your drives look overall fine, sort-of. I'll outline my
> concern points, and ask for some more info:
>
> * ada0 has 28 CRC errors, while ada1 has 2. These drives have been in
> use for 4688 hours and 4583 hours (re
On Tue, Feb 14, 2012 at 04:42:47PM -0700, Scott Long wrote:
> On Feb 14, 2012, at 4:34 PM, Victor Balada Diaz wrote:
> > On Tue, Feb 14, 2012 at 03:09:58PM -0800, Jeremy Chadwick wrote:
> >> I took a stab at this, but I don't feel confident this is the proper
> >> solution/method. I worry there's
On Wed, Feb 15, 2012 at 10:52 AM, Jeremy Chadwick
wrote:
> Sorry, I missed the in-line part of your post at the top where you said:
>
>> > Interesting. I have 9 SAMSUNG HD154UI 1AG01118 in my raidz setup,
>> > haven't had a problem with any of them yet (touch wood).
>
> So that would be you using
schrieb Jeremy Chadwick am 15.02.2012 11:42 (localtime):
> On Wed, Feb 15, 2012 at 10:19:37AM +, Tom Evans wrote:
>> On Tue, Feb 14, 2012 at 7:52 PM, Jeremy Chadwick
>> wrote:
>>> On Tue, Feb 14, 2012 at 08:31:23PM +0100, Oscar Prieto wrote:
I used to had tons of ahci errors in my 4 disk
On Wed, Feb 15, 2012 at 02:42:05AM -0800, Jeremy Chadwick wrote:
> On Wed, Feb 15, 2012 at 10:19:37AM +, Tom Evans wrote:
> > On Tue, Feb 14, 2012 at 7:52 PM, Jeremy Chadwick
> > wrote:
> > > On Tue, Feb 14, 2012 at 08:31:23PM +0100, Oscar Prieto wrote:
> > >> I used to had tons of ahci erro
On Wed, Feb 15, 2012 at 10:19:37AM +, Tom Evans wrote:
> On Tue, Feb 14, 2012 at 7:52 PM, Jeremy Chadwick
> wrote:
> > On Tue, Feb 14, 2012 at 08:31:23PM +0100, Oscar Prieto wrote:
> >> I used to had tons of ahci errors in my 4 disk raidz1 worth of
> >> HD154UIs when the rig was built a year a
On Tue, Feb 14, 2012 at 7:52 PM, Jeremy Chadwick
wrote:
> On Tue, Feb 14, 2012 at 08:31:23PM +0100, Oscar Prieto wrote:
>> I used to had tons of ahci errors in my 4 disk raidz1 worth of
>> HD154UIs when the rig was built a year ago or so (with 8.0 Release),
>> but they dissapeared after tuning ZFS
[cc list somewhat trimmed]
on 15/02/2012 10:29 Victor Balada Diaz said the following:
> Indeed you're right. It's a hack.
Sorry for intruding and under-quoting... perhaps the following commit could be a
model solution for your problem here?
http://svnweb.freebsd.org/base?view=revision&revision=2
On Tue, Feb 14, 2012 at 04:10:20PM -0800, Jeremy Chadwick wrote:
> I'm too tired to quite understand (in full) what's wrong with my patch,
> but I think you're referring to situations where someone would have
> kern.cam.ada.X.quirks set in loader.conf?
>
> If so, I believe that same situation woul
On Feb 14, 2012, at 4:34 PM, Victor Balada Diaz wrote:
> On Tue, Feb 14, 2012 at 03:09:58PM -0800, Jeremy Chadwick wrote:
>> On Tue, Feb 14, 2012 at 11:15:27PM +0100, Victor Balada Diaz wrote:
>>> On Tue, Feb 14, 2012 at 06:17:19PM +0100, Harald Schmalzbauer wrote:
schrieb Jeremy Chadwick am
On Wed, Feb 15, 2012 at 12:34:20AM +0100, Victor Balada Diaz wrote:
> On Tue, Feb 14, 2012 at 03:09:58PM -0800, Jeremy Chadwick wrote:
> > On Tue, Feb 14, 2012 at 11:15:27PM +0100, Victor Balada Diaz wrote:
> > > On Tue, Feb 14, 2012 at 06:17:19PM +0100, Harald Schmalzbauer wrote:
> > > > schrieb
On Tue, Feb 14, 2012 at 03:09:58PM -0800, Jeremy Chadwick wrote:
> On Tue, Feb 14, 2012 at 11:15:27PM +0100, Victor Balada Diaz wrote:
> > On Tue, Feb 14, 2012 at 06:17:19PM +0100, Harald Schmalzbauer wrote:
> > > schrieb Jeremy Chadwick am 14.02.2012 17:50 (localtime):
> > > > On Tue, Feb 14, 201
On Tue, Feb 14, 2012 at 11:15:27PM +0100, Victor Balada Diaz wrote:
> On Tue, Feb 14, 2012 at 06:17:19PM +0100, Harald Schmalzbauer wrote:
> > schrieb Jeremy Chadwick am 14.02.2012 17:50 (localtime):
> > > On Tue, Feb 14, 2012 at 04:55:10PM +0100, Claudius Herder wrote:
> > >> Hello,
> > >>
> > >>
Thank you again Jeremy, sure it helps!
On Tue, Feb 14, 2012 at 9:31 PM, Jeremy Chadwick
wrote:
> On Tue, Feb 14, 2012 at 09:19:02PM +0100, Oscar Prieto wrote:
>> Thank you Jeremy, i'm already checking your links.
>>
>> When i installed smartd i configured a daily short test and a weekly
>> long o
On Tue, Feb 14, 2012 at 06:17:19PM +0100, Harald Schmalzbauer wrote:
> schrieb Jeremy Chadwick am 14.02.2012 17:50 (localtime):
> > On Tue, Feb 14, 2012 at 04:55:10PM +0100, Claudius Herder wrote:
> >> Hello,
> >>
> >> I have got a quite similar problem with AHCI on FreeBSD 8.2 and it still
> >> p
On Tue, Feb 14, 2012 at 09:19:02PM +0100, Oscar Prieto wrote:
> Thank you Jeremy, i'm already checking your links.
>
> When i installed smartd i configured a daily short test and a weekly
> long one for all the drives while the machine remains mostly unused,
> never thought it could be a problem r
Thank you Jeremy, i'm already checking your links.
When i installed smartd i configured a daily short test and a weekly
long one for all the drives while the machine remains mostly unused,
never thought it could be a problem reading the documentation and info
around.
# /usr/local/etc/smartd.conf
On Tue, Feb 14, 2012 at 08:31:23PM +0100, Oscar Prieto wrote:
> I used to had tons of ahci errors in my 4 disk raidz1 worth of
> HD154UIs when the rig was built a year ago or so (with 8.0 Release),
> but they dissapeared after tuning ZFS.
>
> Sadly i also got a new timeout days ago followed with s
Am Tue, 14 Feb 2012 20:24:32 +0100
schrieb Harald Schmalzbauer :
> I guess it's always the firmware of the EcoGreen models which cause
> these problems. Your drive isn't EG...
> I don't remember exactly the different model numbers, but I'm sure
> they were all EcoGreen. The lower power consumption
schrieb Martin Sugioarto am 14.02.2012 19:23 (localtime):
> Am Tue, 14 Feb 2012 18:17:19 +0100
> schrieb Harald Schmalzbauer :
>
>>> I find it interesting that, at least so far, the only people
>>> reporting problems of this type with the ahci.ko driver are people
>>> using Samsung disks. The onl
Am Tue, 14 Feb 2012 18:17:19 +0100
schrieb Harald Schmalzbauer :
> > I find it interesting that, at least so far, the only people
> > reporting problems of this type with the ahci.ko driver are people
> > using Samsung disks. The only difference is that your models are
> > F1s while the OPs are F
schrieb Jeremy Chadwick am 14.02.2012 17:50 (localtime):
> On Tue, Feb 14, 2012 at 04:55:10PM +0100, Claudius Herder wrote:
>> Hello,
>>
>> I have got a quite similar problem with AHCI on FreeBSD 8.2 and it still
>> persists on FreeBSD 9.0 release.
>>
>> Switching from ahci to ataahci resolved the
On Tue, Feb 14, 2012 at 04:55:10PM +0100, Claudius Herder wrote:
>
> Hello,
>
> I have got a quite similar problem with AHCI on FreeBSD 8.2 and it still
> persists on FreeBSD 9.0 release.
>
> Switching from ahci to ataahci resolved the problem for me too.
>
> I'm using gmirror for swap, system
Hello,
I have got a quite similar problem with AHCI on FreeBSD 8.2 and it still
persists on FreeBSD 9.0 release.
Switching from ahci to ataahci resolved the problem for me too.
I'm using gmirror for swap, system is on a zpool and the problem first
occurred during a zpool scrub, but it is easily
On Tue, Feb 14, 2012 at 06:16:01AM -0800, Jeremy Chadwick wrote:
[..]
>
> Thanks. Both your drives look overall fine, sort-of. I'll outline my
> concern points, and ask for some more info:
>
> * ada0 has 28 CRC errors, while ada1 has 2. These drives have been in
> use for 4688 hours and 4583
On Tue, Feb 14, 2012 at 02:54:35PM +0100, Victor Balada Diaz wrote:
> On Tue, Feb 14, 2012 at 02:05:13AM -0800, Jeremy Chadwick wrote:
> > On Tue, Feb 14, 2012 at 10:19:09AM +0100, Victor Balada Diaz wrote:
> > > We're having some troubles with AHCI under FreeBSD 8.2 and 8-STABLE. The
> > > error
On Tue, Feb 14, 2012 at 02:05:13AM -0800, Jeremy Chadwick wrote:
> On Tue, Feb 14, 2012 at 10:19:09AM +0100, Victor Balada Diaz wrote:
> > We're having some troubles with AHCI under FreeBSD 8.2 and 8-STABLE. The
> > error is:
> >
> > ahcich0: Timeout on slot 8
> > ahcich0: is cs 0100
On Tue, Feb 14, 2012 at 10:19:09AM +0100, Victor Balada Diaz wrote:
> We're having some troubles with AHCI under FreeBSD 8.2 and 8-STABLE. The
> error is:
>
> ahcich0: Timeout on slot 8
> ahcich0: is cs 0100 ss rs 0100 tfd c0 serr
> ahcich0: AHCI reset...
> ahci
On 02/14/12 11:19, Victor Balada Diaz wrote:
We're having some troubles with AHCI under FreeBSD 8.2 and 8-STABLE. The error
is:
ahcich0: Timeout on slot 8
ahcich0: is cs 0100 ss rs 0100 tfd c0 serr
ahcich0: AHCI reset...
ahcich0: SATA connect time=0ms status=0
32 matches
Mail list logo
