Re: problems with an SATA drive on nVidia3 controller
On Sunday 02 April 2006 04:42 pm, Søren Schmidt wrote: = What freebsd version are we talking about here ? (dmesg would have been = nice). 6.1 as of Sunday. dmesg.boot attached. = Have you tried another cable ? Not yet -- I was not there on weekend. I vaguely remember nVidia controllers being special, so I thought, I'll ask... Unlike in Volker's situation, though, the drive does not disappear, though. Thanks! -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
problems with an SATA drive on nVidia3 controller
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: nVidia nForce3 Pro SATA150 controller port 0xcc00-0xcc07,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc0f,0xb800-0xb87f irq 22 at device 10.0 on pci0 ata2: ATA channel 0 on atapci1 ata3: ATA channel 1 on atapci1 ad6: 238475MB WDC WD2500SD-01KCC0 08.02D08 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 WDC WD2500SD-01KCC0/08.02D08 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=51READY,DSC,ERROR error=10NID_NOT_FOUND 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! -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with an SATA drive on nVidia3 controller
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: nVidia nForce3 Pro SATA150 controller port 0xcc00-0xcc07,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc0f,0xb800-0xb87f irq 22 at device 10.0 on pci0 ata2: ATA channel 0 on atapci1 ata3: ATA channel 1 on atapci1 ad6: 238475MB WDC WD2500SD-01KCC0 08.02D08 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 WDC WD2500SD-01KCC0/08.02D08 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=51READY,DSC,ERROR error=10NID_NOT_FOUND 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
{Spam?} Re: problems with an SATA drive on nVidia3 controller
Hello! We have an amd64 machine with an nVidia3 SATA controller on motherboard. [...] 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=51READY,DSC,ERROR error=10NID_NOT_FOUND 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! -mi Mikhail, I've had a similar problem (or probably still have). Someone answered to my post this might be a SATA-cable problem and this seems to be true. As far as I'm aware of the ICRC error message might be a hint to an interface problem. The system(s) I was seeing this kind of problem are providing SATA on board (VIA 6420). Whenever the problem occurs, the drive isn't being seen by the OS anymore until a reboot (atacontrol list doesn't show the failed drive anymore) and SMART shows DMA error and ICRC error messages. I really guess it's a cable problem. On the other side I've seen this problem only on RELENG_6_0 systems (but this does not say it's a FreeBSD problem). AsRock (the mainboard manufacturer) also asked me to change the SATA cable and they told me to change the disks jumper settings of the failed drive to run on SATA150 (if it's a SATA300 disk). Because my troubled box is remote, I've been unable to check those both suggestions. Probably you may check that first if it solves your problem. Greetings, Volker ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
