From owner-freebsd-questions@FreeBSD.ORG Mon Jun 4 11:20:59 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 018A6106566B for ; Mon, 4 Jun 2012 11:20:59 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7537A8FC0A for ; Mon, 4 Jun 2012 11:20:58 +0000 (UTC) Received: by bkvi18 with SMTP id i18so4520605bkv.13 for ; Mon, 04 Jun 2012 04:20:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/c+eNAhUq4LU4MjIT0ksAnlujltiJwh5LWxIY5SxmU8=; b=n6qpgsOxExd+anXWODLnUupAJv8BGA9texc3ivPn+bKcI6LAkQSUEttGNtvMTgO7c6 nS7SRmI/vGpSiTRRZLUMCFifl9wruRH75IJ+eg/tosXOVRWmDvXyw4wJz/IygQKe8Our 4Z0Gt7/6GCnTdWN9x//b0gnGAH5mX9Z1HjnSTf3DUpeQX/yFmVW/anhneGUMCwlO58gI 3Nbd/Jzzl/+efiYg36NlZM4g/BKNgsno4OSXcpQ3fvwPlI3D7TJQDA5OJXd1nXGcJKsl LprOjt6B/Df6fLtTArEdT+U9grXT4P3HQu7Rz1itJBixhWF7ytoZyFabLxXwcBat5hFW HDig== Received: by 10.205.134.6 with SMTP id ia6mr6583447bkc.51.1338808857384; Mon, 04 Jun 2012 04:20:57 -0700 (PDT) Received: from X220.optiplex-networks.com (81-178-2-118.dsl.pipex.com. [81.178.2.118]) by mx.google.com with ESMTPS id o4sm9965529bkv.15.2012.06.04.04.20.54 (version=SSLv3 cipher=OTHER); Mon, 04 Jun 2012 04:20:55 -0700 (PDT) Message-ID: <4FCC99ED.3030409@gmail.com> Date: Mon, 04 Jun 2012 12:20:13 +0100 From: Kaya Saman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4FCC0A31.3000902@gmail.com> <20120603224223.123bc4fa@vixen42.vulpes.vvelox.net> In-Reply-To: <20120603224223.123bc4fa@vixen42.vulpes.vvelox.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Strange case of vanishing disk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 11:20:59 -0000 On 06/04/2012 04:42 AM, Zane C. B-H. wrote: > On Mon, 04 Jun 2012 02:06:57 +0100 > Kaya Saman wrote: > >> Hi, >> >> this is a very strange issue but I guess will either be related to >> 2 things, PSU not being powerful enough or disk controller simply >> being crap. >> >> >> Here's what's going on. I have a little Chenbro 4 disk mini-ITX NAS >> server with 2x 2TB disks and 2x4TB disks as storage - all spread >> out over 2 ZFS storage pools. Additionally I am running the root >> file system on a 40GB SSD. >> >> The strange thing with this is that I recently installed the 4TB >> disks and they're brand new. >> >> >> One disk connected to the system board works fine and shows up as >> online and on one of the channels using atacontrol list. >> >> >> The other disk is connected to a Startech.com Jmicron based 2x SATA >> RAID controller card. >> >> >> The disk connected to the controller card is having issues. At >> first the drive wouldn't be seen by the system then after a while >> all of a sudden it was there. No reboots, no io scans nothing it >> just appeared. >> >> After blasting it with IO for a few days the disk has now vanished >> again..... >> >> I had this error in dmesg for a while: >> >> ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=113337535 >> >> I have tried to use pciconf -lbvv to show the connected interfaces >> and the JMICRON comes up fine: >> >> >> atapci0@pci0:2:0:0: class=0x010400 card=0x2366197b >> chip=0x2366197b rev=0x02 hdr=0x00 >> vendor = 'JMicron Technology Corp.' >> device = 'JMicron JMB366 AHCI/IDE Controller (JMB36X)' >> class = mass storage >> subclass = RAID >> bar [10] = type I/O Port, range 32, base 0xd040, size 8, >> enabled bar [14] = type I/O Port, range 32, base 0xd030, size 4, >> enabled bar [18] = type I/O Port, range 32, base 0xd020, size 8, >> enabled bar [1c] = type I/O Port, range 32, base 0xd010, size 4, >> enabled bar [20] = type I/O Port, range 32, base 0xd000, size 16, >> enabled bar [24] = type Memory, range 32, base 0xd0510000, size >> 8192, enabled >> >> >> So why isn't the disk? >> >> I reckon as stated at the beginning that either the 180Watt PSU >> inside the system isn't enough or the controller is just really >> poor?? >> >> >> Could anyone suggest anything to look into, I'm sure I've covered >> all the bases but just incase there is something else I can do with >> this one?? > Greetings, > > It looks like you are using the default ATA drive with that. I would > suggest trying the AHCI driver and see if that works better. > > kldload ahci > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" I've just tried this and lost my whole system..... My boot disk is not labeled to work with ahci as it just has standard formatting on there. Need to remove the ahci_load="YES" from /boot/loader.conf file now. Regards, Kaya