From owner-freebsd-questions@FreeBSD.ORG Sun Mar 16 21:29:44 2014 Return-Path: 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 4749BFF for ; Sun, 16 Mar 2014 21:29:44 +0000 (UTC) Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1F5C2762 for ; Sun, 16 Mar 2014 21:29:44 +0000 (UTC) Received: by mail-pa0-f46.google.com with SMTP id kp14so4902068pab.33 for ; Sun, 16 Mar 2014 14:29:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=q2pheRaMai52lsXQZwMg3952UQl2ERSVJdWmWOQKbFA=; b=GvK0Cea8is64MPlOYh8ClpNhiZy22/Hk3EhK1IEXQIGbTmZg+al2rQrPkBWpHUxPnl 8FAj0JHvYoI7vHmOyX5kHueu4LMbFoeAm9wwzr+n0tWxW/aIpr6G7ZOaYc2+fJfHHv3X njO/hMVhzxkzh6q/RUL/jMk4YdTapK5v5IQViUTv6y1sAHTXmCgEWO2TXPVi/qnKH+T0 M3aLVA7rhAza/hPs3jlu5lWK4RfMXec/Z49zq5g7tQ4OBYzTohI9rBEEZ2dFnUrDiXT9 6+Rtwt4r0QMsFkq7JX+pERGFe+3ZmDlwXT6jjS5xS7NZKUIyDzpavlrH4eNjklBw03K4 yEWg== MIME-Version: 1.0 X-Received: by 10.66.20.10 with SMTP id j10mr22501296pae.11.1395005383787; Sun, 16 Mar 2014 14:29:43 -0700 (PDT) Received: by 10.68.157.73 with HTTP; Sun, 16 Mar 2014 14:29:43 -0700 (PDT) In-Reply-To: <5325E71D.30800@bluerosetech.com> References: <20140316130936.3f2d18e0@X220.alogt.com> <20140316134309.2edc258a@X220.alogt.com> <5325E71D.30800@bluerosetech.com> Date: Sun, 16 Mar 2014 16:29:43 -0500 Message-ID: Subject: Re: Another case of the vanishing disk From: cruxpot To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Mar 2014 21:29:44 -0000 Hi all, I am leaning towards the Green hard drive problem myself. I do not have all the drives on one rail. I have them separated on the two rails that have the SATA 15-pin connectors, two hard drives on each. The CD-ROM is connected to a Molex connector on a separate rail. I think the power is more than sufficient and like I said, I did move the system to plug it into a surge protector and it's not on the UPS at the moment even though I would like it on the UPS (which is not active PFC but I have seen no other problems). I looked at the firmware for this drive and all of them have the latest CC32 revision so that is not the issue. I am thinking I need something in FreeBSD to keep the drives awake, the way you can do it in Windows Power Settings or using nosleep programs. I will look at the sysutils/ataidle port and see if that can do it. I do not see any official Seagate utilities for modifying the firmware settings of the Barracuda Green drives but if I am mistaken, please let me know. I guess I did shoot myself in the foot on buying these drives, but they were $75/each at Best Buy on a sale about two years ago and I thought it was too good to pass up. I will report back to the list about my progress since the issue may be somewhat common with these cheaper drives in NAS systems. Thanks. On Sun, Mar 16, 2014 at 1:02 PM, Darren Pilgrim wrote: > On 3/15/2014 11:04 PM, 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? > > > How are the drives connected to the power supply? Are they all on the same > rails or are they spread across mutliple sets of rails? > > Be aware that you may have shot yourself in the foot buying "green" drives. > Drives not designed for use in NAS/RAID usually have firmware that expects > the machine to sleep the disks and be tolerant of delayed responses. The > drives get to be cheaper because the controller has more "offline" time to > fix errors due to higher tolerance parts. In some cases (like certain WD > disks), the drives eventually start dropping off the port because they're > going into an offline error recovery mode and take too long to respond. On > a regular desktop, the OS knows to wait because the drive was signalled into > a sleep mode. That doesn't happen in a server and you really don't want it > to happen in a server. > > I'm betting that even if you had each drive on its own +3.3v, +5v and +12v > rails, a line-interactive UPS and a server-grade power supply, you'll still > have dropouts. >