Date: Mon, 04 Jun 2012 12:20:13 +0100 From: Kaya Saman <kayasaman@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Strange case of vanishing disk Message-ID: <4FCC99ED.3030409@gmail.com> In-Reply-To: <20120603224223.123bc4fa@vixen42.vulpes.vvelox.net> References: <4FCC0A31.3000902@gmail.com> <20120603224223.123bc4fa@vixen42.vulpes.vvelox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/04/2012 04:42 AM, Zane C. B-H. wrote: > On Mon, 04 Jun 2012 02:06:57 +0100 > Kaya Saman<kayasaman@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FCC99ED.3030409>