From owner-freebsd-questions@FreeBSD.ORG  Sun Mar 16 14:33:15 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E16587CD
 for <freebsd-questions@freebsd.org>; Sun, 16 Mar 2014 14:33:15 +0000 (UTC)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8C837E9D
 for <freebsd-questions@freebsd.org>; Sun, 16 Mar 2014 14:33:15 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.14.8/8.14.8) with ESMTP id s2GEXD6v021769
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Sun, 16 Mar 2014 08:33:14 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.14.8/8.14.8/Submit) with ESMTP id s2GEXDZh021766;
 Sun, 16 Mar 2014 08:33:13 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Date: Sun, 16 Mar 2014 08:33:13 -0600 (MDT)
From: Warren Block <wblock@wonkity.com>
To: cruxpot <cruxpot@gmail.com>
Subject: Re: Another case of the vanishing disk
In-Reply-To: <CAPYfQ9ztmzYWSRoNLJk2Z-mTAdDti48ZOJrKT0LEEpuWf5SqHg@mail.gmail.com>
Message-ID: <alpine.BSF.2.00.1403160828130.21326@wonkity.com>
References: <CAPYfQ9z-YUzKDAh3=V3_m1wmDtds4NzcewTq0wLUD9LWt3VaGA@mail.gmail.com>
 <20140316130936.3f2d18e0@X220.alogt.com>
 <CAPYfQ9ycxEr+-qPBC6qY6tvLrTMqT3guU+8q+bK2_RAj=WH1tw@mail.gmail.com>
 <20140316134309.2edc258a@X220.alogt.com>
 <CAPYfQ9ztmzYWSRoNLJk2Z-mTAdDti48ZOJrKT0LEEpuWf5SqHg@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (wonkity.com [127.0.0.1]); Sun, 16 Mar 2014 08:33:14 -0600 (MDT)
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Mar 2014 14:33:15 -0000

On Sun, 16 Mar 2014, cruxpot wrote:

> Back in December, it was the power supply. That was a cheap Rosewill
> 300W PSU. The new is a Corsair CX500 (500W). The system basically just
> has an old SCSI card and 4 Green Barracuda 2TB disks and a low end
> pci-e video card and pci-e gigabit NIC. How can the PSU be the problem
> since I replaced it and it's more than adequate?

As before, this does not sound like a power supply problem to me.

"Green" drive power management is sometimes a problem.  Idle drives spin 
down to save power, then don't report ready quickly and the system sees 
them as down.  If the drives allow it, disable power management.  The 
sysutils/ataidle port can do that.  However, some drives ignore the 
settings.  Another possibility is to set a longer delay before 
spin-down.  Seagate might have utility software that can modify the 
settings on the drives.