From owner-freebsd-stable@FreeBSD.ORG Sun Apr 2 20:43:02 2006 Return-Path: X-Original-To: stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70CE816A401; Sun, 2 Apr 2006 20:43:02 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id E70BE43D45; Sun, 2 Apr 2006 20:43:01 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from [194.192.25.142] (spider.deepcore.dk [194.192.25.142]) by spider.deepcore.dk (8.13.4/8.13.4) with ESMTP id k32Kgh7s085655; Sun, 2 Apr 2006 22:42:44 +0200 (CEST) (envelope-from sos@deepcore.dk) Message-ID: <44303743.3030205@deepcore.dk> Date: Sun, 02 Apr 2006 22:42:43 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 1.5 (X11/20060213) MIME-Version: 1.0 To: Mikhail Teterin References: <200604021132.10482@aldan> In-Reply-To: <200604021132.10482@aldan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.16 Cc: stable@FreeBSD.ORG, hardware@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: problems with an SATA drive on nVidia3 controller X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Apr 2006 20:43:02 -0000 Mikhail Teterin wrote: > Hello! > > We have an amd64 machine with an nVidia3 SATA controller on motherboard. > > The drive just came from the manufacturer and the self-tests initiated > via smartctl show no problems: > > atapci1: port 0xcc00-0xcc07,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc0f,0xb800-0xb87f irq 22 at device 10.0 > on pci0 > ata2: on atapci1 > ata3: on atapci1 > ad6: 238475MB at ata3-master SATA150 > > > Yet even newfs-ing it leads to DMA errors and the drive is unusable: > > % newfs -f 8192 -b 65536 /dev/ad6 > /dev/ad6: 238475.2MB (488397168 sectors) block size 65536, fragment size 8192 > using 81 cylinder groups of 2969.06MB, 47505 blks, 95232 inodes. > super-block backups (for fsck -b #) at: > 256, 6080896, 12161536, 18242176, 24322816, 30403456, 36484096, 42564736, > 48645376, 54726016, 60806656, 66887296, 72967936, 79048576, 85129216, > 91209856, 97290496, 103371136, 109451776, 115532416, 121613056, 127693696, > 133774336, 139854976, 145935616, 152016256, 158096896, 164177536, 170258176, > 176338816, 182419456, 188500096, 194580736, 200661376, 206742016, 212822656, > 218903296, 224983936, 231064576, 237145216, 243225856, 249306496, 255387136, > 261467776, 267548416,newfs: wtfs: 262144 bytes at sector 273629056: Input/output error > > % atacontrol reinit ata3 > Master: ad6 Serial ATA v1.0 > Slave: no device present > > % newfs -f 8192 -b 65536 /dev/ad6 > /dev/ad6: 238475.2MB (488397168 sectors) block size 65536, fragment size 8192 > using 81 cylinder groups of 2969.06MB, 47505 blks, 95232 inodes. > super-block backups (for fsck -b #) at: > 256, 6080896, 12161536, 18242176, 24322816, 30403456, 36484096, 42564736, > 48645376, 54726016, 60806656, 66887296, 72967936, 79048576, 85129216, > 91209856, 97290496, 103371136, 109451776, 115532416, 121613056, 127693696, > 133774336, 139854976, 145935616, 152016256, 158096896, 164177536, 170258176, > 176338816, 182419456, 188500096, 194580736, 200661376, 206742016, 212822656, > 218903296, 224983936, 231064576, 237145216, 243225856, 249306496, 255387136, > 261467776, 267548416,newfs: wtfs: 262144 bytes at sector 273629056: Input/output error > > After each such attempt, the kernel complains loudly: > [...] > ad6: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=249306496 > ad6: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=261467776 > ad6: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=273629312 > ad6: FAILURE - WRITE_DMA48 status=51 error=10 LBA=273629312 > > Is this controller working for others? We connected the disk to it in > preference to the Silicon Image connectors, which are also present > on-board, because SI has poor reputation :-( > > Is this controller supposed to work? Thanks! What freebsd version are we talking about here ? (dmesg would have been nice). Have you tried another cable ? -Søren