Re: ATA trouble again
On 11/16/11 13:13, Pegasus Mc Cleaft wrote: or do you know if the drives are using 4096 bytes Per sector? How do I find out without physical access to the box? The only way to be sure is to look at the datasheet for the drive. If the drives are SMART capable, you can always load Smart Monitoring Tools (/usr/ports/sysutils/smartmontools) and have it report the make and model of the drive. Just be careful, the report from the SMART data will more than likely show the drive as 512 Logical and Physical access (Even if they are not) So: the specs, smartctl and diskinfo all say sectors are 512 bytes. I tried disabling AHCI in the BIOS and, for now, this seems to work better. I'll keep you informed if troubles persist. bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ATA trouble again
Hello. This is a follow-up of a previous thread, which can be found here: http://lists.freebsd.org/pipermail/freebsd-questions/2011-July/232257.html I finally have two working WD Green drives: they have run severel times for more than a few days continuosly and I've run their full diags a few times over a span of some weeks, so I think I can be sure of that. Still I experience lot of troubles; however, trying different boxes, I found out that these depend heavily on the controller I use. A) A-Bit KV7 (featuring a VIA KT600) on 7.3 and 8.2/i386 With only one disk, I get some NID_NOT_FOUND errors, but I could almost say they can be ignored. With two disks, the NID_NOT_FOUND errors come frequently; rsync will work, but a diff will sooner or later fail. I tried Linux on this box: it frequently complains about errors and resets the ATA channels; this possibly will result in performance penalties, but it seems to work. Since then this box is dead, so I cannot do other tests. B) BioStar A785G3 with 8.1/i386: # pciconf -lv atapci0@pci0:0:17:0:class=0x010601 card=0x43911002 chip=0x43911002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 SATA Controller [AHCI mode]' class = mass storage subclass = SATA This works flawlessly. C) Intel SC5400BRP with 7.3/i386: atapci2@pci0:0:31:2:class=0x01018f card=0x34768086 chip=0x26808086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Serial ATA Storage Controller' class = mass storage subclass = ATA No way this will work: using two disk gives gobs of errors, until the whole box crashes. With only one disk it appears to work for a while, but will eventually panic over a few day. This same controller used to work with a single Hitachi drive. With two Seagates drives, I get READ_DMA48/WRITE_DMA48 timeouts, the disks will hang for minutes, but then they will start again; this does not happen as soon as I start using them, but will happen every some minutes after a few hours of usage. D) Intel SC5600BRP with 7.3/amd64: atapci0@pci0:0:31:2:class=0x01018f card=0x34dc8086 chip=0x3a208086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'SATA2(4Port2) (ICH10 Family)' class = mass storage subclass = ATA atapci1@pci0:0:31:5:class=0x010185 card=0x34dc8086 chip=0x3a268086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'SATA2(2Port2) (ICH10 Family)' class = mass storage subclass = ATA This works flawlessly, with every HD I could try (one or two). E) Promise PCI controller with 7.3/i386 and /amd64: atapci0@pci0:7:2:0: class=0x018000 card=0x3d17105a chip=0x3d17105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'SATA 300 TX4 Controller (PDC40718-GP)' class = mass storage This will give few errors if not none at all; however the box will sometimes reboot or just hang (phisical reset required). This happens on two different box with both WD Green and Seagate drives. So: altough a bit flaky, WD drives are not the main problem. I'll still appreciate some help WRT the third box (Intel SC5400BRP with 7.3/i386). Different BIOS settings did not help with WD drives, but I still have to test them with Seagate's. Possibly an OS upgrade would help? 8.x also has an AHCI driver that 7.3 is missing. I don't care that much for top of the chart performance, I just want this thing to work decently. bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: ATA trouble again
Hello. This is a follow-up of a previous thread, which can be found here: http://lists.freebsd.org/pipermail/freebsd-questions/2011-July/232257. html I finally have two working WD Green drives: they have run severel times for more than a few days continuosly and I've run their full diags a few times over a span of some weeks, so I think I can be sure of that. Still I experience lot of troubles; however, trying different boxes, I found out that these depend heavily on the controller I use. Hi Andrea, I don’t know if this will help you or not, but it may lead you to another possibility. I had a similar problem on my box (I was running 9.0-Current and Now 10.0-Current). I was also running under ZFS and would get TONS of Errors across my SATA drives. The errors would be anything from time-outs to physical locking of the drive (I would have to pull the drive to let the PHY on the controller reset and then plug the drive back in before it would communicate with the machine again). In particular this would happen when I was doing large writes to the drives. Read performance also suffered. I then created a single drive pool and did a large transfer to the drive (about 800Gb) and the controller timed out again. I moved the drive to various ports on the machine and also various controllers in the machine. Some seemed to exabate the problem quicker but no port or drive was safe from this. I later found out that the drives I was using were using 4096 Bytes per sector. When I recreated the zpool using 4096 byte sectors All the timeout errors disappeared and my data-rate has climbed Dramatically. Are you using ZFS or do you know if the drives are using 4096 bytes Per sector? Ta Peg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ATA trouble again
On 11/16/11 12:23, Pegasus Mc Cleaft wrote: Are you using ZFS? No. I'm using gstripe. or do you know if the drives are using 4096 bytes Per sector? How do I find out without physical access to the box? bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ATA trouble again
On Wed, 16 Nov 2011, Andrea Venturoli wrote: On 11/16/11 12:23, Pegasus Mc Cleaft wrote: Are you using ZFS? No. I'm using gstripe. or do you know if the drives are using 4096 bytes Per sector? How do I find out without physical access to the box? diskinfo -v /dev/ada0 Although it may lie about true sector size. Otherwise, get the model number from dmesg and search on it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
