write dma udma icrc error
hi, can anyone tell me what this message is related to? WRITE_DMA UDMA ICRC error (retrying request) LBA=62939519 drive/hardware failing? i am seeing a lot of it lately on a particular disk where i have tried a few different installs and do not always get this problem. i have seen it disappear after some painstaking before an install to it, like wiping the whole disk clean before install, checking geometry is right, but maybe coincidence? it is a sata300, 7.2 beta1 amd64 and i am thinking there is problem with the disk, but the error varied a bit with different installs (i.e. whether i see the error or not) ___ 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
WARNING - READ_DMA UDMA ICRC error
Yesterday I upgraded my hardware from a Pentium2 400mhz setup (running freebsd 5.4) to a Sempron 2.8ghz and installed freebsd 6.1 on it (the 32bit version). There are 4 harddisks attached to the IDE-controllers: ad0: 6150MB Seagate ST36421A 6.01 at ata0-master UDMA66 ad1: 38166MB Seagate ST340823A 3.39 at ata0-slave UDMA100 ad2: 78167MB Maxtor 6Y080L0 YAR41BW0 at ata1-master UDMA133 ad3: 38166MB Seagate ST340823A 3.39 at ata1-slave UDMA100 ad1 and ad3 are the same and both contain important data. After the installation of freebsd I noticed a lot of UDMA-errors: ad1: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63 ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=63 ad3: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=63 After decreasing the speed of UDMA (on ad1 and ad3) in the BIOS-Setup, ad1 worked fine, without any errors, but ad3 still produces the same error-messages and is not mountable: (14:51) root (/home/septi) %mount /dev/ad3s1 /test mount: /dev/ad3s1: Input/output error Here the dmesg output: ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=12063 ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=12063 ad3: FAILURE - READ_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=12063 g_vfs_done():ad3s1[READ(offset=6144000, length=4096)]error = 5 ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63 ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63 ad3: FAILURE - READ_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=63 I also replaced the IDE-cable but it changed nothing... Does anybody have an idea? -- everyone's pink on the inside - http://www.nuffinsirius.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
nForce4 IDE channel UDMA woes
This is a problem on a home-built computer using an nVidia nForce4 motherboard. IDE 1 and 2 each have two devices. IDE 1 master: a Maxtor hard drive (jumpered to master) IDE 1 slave: a CDRW (jumpered to slave) IDE 2 master: CDRW (jumpered to master) IDE 2 slave: CDRW (jumpered to slave) So, when I do something intense - like build a new kernel or buildworld - I start getting the following in stdout: snip ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006527 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006527 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006655 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006655 g_vfs_done():ad0s1f[WRITE(offset=253247242240, length=131072)]error = 5 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006527 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006527 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006655 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006655 g_vfs_done():ad0s1f[WRITE(offset=253247242240, length=131072)]error = 5 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006527 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006655 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006655 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006527 g_vfs_done():ad0s1f[WRITE(offset=253247242240, length=131072)]error = 5 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006527 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006527 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006655 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006655 g_vfs_done():ad0s1f[WRITE(offset=253247242240, length=131072)]error = 5 snip Now, interestingly, if I unplug the CDRW that uses IDE 1 slave, everything works fine. But for my needs, I need three CDRWs. Questions: I have noticed a lot of Internet chatter about this kind of thing happening with similar configurations on WinXP. Using the generic XP IDE driver seems to fix it. Could this be a problem with FreeBSD? Do you think it would be a dumb idea to try to run either the hard drive or one of the CDRWs from one of the available SATAs? == Now I, Nebuchadnezzar, praise and extol and honor the King of heaven, for all his works are truth, and his ways are justice; and he is able to bring low those who walk in pride. Daniel 4:37 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nForce4 IDE channel UDMA woes
On Wednesday 12 July 2006 17:47, Neil Short wrote: This is a problem on a home-built computer using an nVidia nForce4 motherboard. IDE 1 and 2 each have two devices. IDE 1 master: a Maxtor hard drive (jumpered to master) IDE 1 slave: a CDRW (jumpered to slave) IDE 2 master: CDRW (jumpered to master) IDE 2 slave: CDRW (jumpered to slave) So, when I do something intense - like build a new kernel or buildworld - I start getting the following in stdout: snip ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006527 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006527 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006655 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006655 g_vfs_done():ad0s1f[WRITE(offset=253247242240, length=131072)]error = 5 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006527 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006527 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006655 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006655 g_vfs_done():ad0s1f[WRITE(offset=253247242240, length=131072)]error = 5 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006527 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006655 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006655 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006527 g_vfs_done():ad0s1f[WRITE(offset=253247242240, length=131072)]error = 5 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006527 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006527 ad0: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=505006655 ad0: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=505006655 g_vfs_done():ad0s1f[WRITE(offset=253247242240, length=131072)]error = 5 snip Now, interestingly, if I unplug the CDRW that uses IDE 1 slave, everything works fine. But for my needs, I need three CDRWs. Questions: I have noticed a lot of Internet chatter about this kind of thing happening with similar configurations on WinXP. Using the generic XP IDE driver seems to fix it. Could this be a problem with FreeBSD? Do you think it would be a dumb idea to try to run either the hard drive or one of the CDRWs from one of the available SATAs? == Now I, Nebuchadnezzar, praise and extol and honor the King of heaven, for all his works are truth, and his ways are justice; and he is able to bring low those who walk in pride. Daniel 4:37 if you have access to one of those converter dealies, that you can put an ide drive on an sata channel, then i would give that a shot. my system is on an sata drive (FreeBSD 6.1-STABLE) and performance is quite satisfactory. even if it performs with the same speed as any other IDE drive... at least you will have seperated your cdroms from your disk's data path. hth, jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
WARNING - WRITE_DMA UDMA ICRC error
hello list! I´m having a trouble with a hard disk, I´m getting this warning: kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=38059135 I read that it could be a IDE cable problem, that the cable does not support UDMA speed = 66 If it wasn´t the cable where the problem is, how can I set the drive UDMA speed to UDMA66 at boot time to make it permanent? I have a FreeBSD 6.1 system and ExcelStor j880 hard disk. Could you help me, please? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WARNING - WRITE_DMA UDMA ICRC error
hello list! I´m having a trouble with a hard disk, I´m getting this warning: kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=38059135 I read that it could be a IDE cable problem, that the cable does not support UDMA speed = 66 If it wasn´t the cable where the problem is, how can I set the drive UDMA speed to UDMA66 at boot time to make it permanent? I have a FreeBSD 6.1 system and ExcelStor j880 hard disk. Cool i'm not alone!!! Could you help me, please? I had this problem during installation from a CDROM. The FAQ says the kernel should switch to another mode ( PIO ) in order to configure the hard drive ( as NetBSD does for example ... ). Unfortunatly it doesn't... Someone for confirmation? ___ Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Rendez-vous sur http://fr.yahoo.com/set ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
WRITE_DMA UDMA CRC error on Nimble v5
Dear colleagues, I would really appreciate some help here. I've tried every option I was able to think of, to no avail. My server is built on Nimble v5 (http://www.nimblev5.com/product/specification.htm). This is a wonderful little box built on VIA C3 Eden 733MHz, quiet and consuming very little electricity (meaning longer UPS runtimes). I'm running FreeBSD 5.3 on it, and everything was fine until I tried to upgrade. Originally, the box sports 2.5 Fujitsu MHT2030AT hard drive. FreeBSD reports it as UDMA-100, and it works like a charm. I'm trying to replace in with Toshiba MK6025GAS 60Gb 2.5 laptop hard drive, and try to install FreeBSD 5.4 on it. However, no matter how hard I try, I always run into the same problem: ad0: WARNING - WRITE_DMA UDMA ICRC (retrying request) LBA=63 ad0: WARNING - WRITE_DMA UDMA ICRC (retrying request) LBA=63 ad0: WARNING - WRITE_DMA UDMA ICRC (retrying request) LBA=63 ad0: FAILURE - status=51READY,DSC,ERROR error=84CRC,ABORTED LBA=63 This error repeats many times. Here's the steps that I've tried to make: 1) Googled that UltraDMA (80-pin) cable should be used to avoid these errors. This doesn't help -- to my knowledge, there's no 80-pin ribbon cables for 2.5 hard drives, at least nobody sells any. And after all, the original 20Gb drive has no problems with the existing cable, though it's UDMA100 as well. 2) This box is pretty limited in choice of external storage devices I can use -- basicly, all I can connect to it is USB stuff. I googled a suggestion that that error might show up on VIA chipsets when installing from USB CD-ROM. Tried installing from USB floppy and over the network -- same thing. 3) Upgraded BIOS to the latest one. No effect. 4) Tried different Nimble box (I've got 2). Same thing. 5) Thought it might be the Toshiba drive. Tried with 2.5 100Gb Seagate. Same thing. 6) Tried 6.0RC1. Same thing. Tried 5.3 (the one that works OK on the original 20Gb drive), same thing. 7) Put the 60Gb drive into a USB enclosure and installed onto it. Worked fine, but when I get the drive out of the enclosure and into the box, the error happens again. Here's the table of what I tried: --- Freebsd Installation TargetTargetResult version medium drive interface 5.3 USB-FDD Fujitsu 20GB IDE OK 5.3 USB-CD --- --- Install disk boot stalls -- image corrupt 5.4 USB-FDD Toshiba 60GB IDE ICRC error 5.4 USB-CD Toshiba 60GB IDE ICRC error 5.4 USB-CD Seagate 100GB IDE ICRC error 6.0RC1 USB-FDD Toshiba 60GB IDE ICRC error 5.4 USB-FDD Toshiba 60GB USB OK 5.4 USB-CD Toshiba 60GB USB OK 5.4 any Toshiba 60GB USB-IDE OK, then ICRC error on boot --- Any sugggestions? -- Best regards, Wesha mailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do these warning messages mean (READ_DMA UDMA ICRC error)?
bob self [EMAIL PROTECTED] writes: I rearanged my hard drives / dvd burner and am now seeing these messages. The system SEEMS to run ok though. ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267359 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267359 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=119267359 g_vfs_done():ad0s1f[READ(offset=44958728192, length=45056)]error = 5 vnode_pager_getpages: I/O read error vm_fault: pager read error, pid 808 (firefox-bin) ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267359 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267359 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267519 If it's the same blocks all the time, you may have coincidentally developed a hard disk problem at the same time. Much more likely, though, you've got a problem with the ATA cable for that drive. Maybe it has gotten pinched or bent too sharply? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What do these warning messages mean (READ_DMA UDMA ICRC error)?
Lowell Gilbert wrote: bob self [EMAIL PROTECTED] writes: I rearanged my hard drives / dvd burner and am now seeing these messages. The system SEEMS to run ok though. ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267359 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267359 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=119267359 g_vfs_done():ad0s1f[READ(offset=44958728192, length=45056)]error = 5 vnode_pager_getpages: I/O read error vm_fault: pager read error, pid 808 (firefox-bin) ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267359 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267359 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267519 If it's the same blocks all the time, you may have coincidentally developed a hard disk problem at the same time. Much more likely, though, you've got a problem with the ATA cable for that drive. Maybe it has gotten pinched or bent too sharply? I re-seated the cables yet again and havent seen the problem since then. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
What do these warning messages mean (READ_DMA UDMA ICRC error)?
I rearanged my hard drives / dvd burner and am now seeing these messages. The system SEEMS to run ok though. ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267359 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267359 ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=119267359 g_vfs_done():ad0s1f[READ(offset=44958728192, length=45056)]error = 5 vnode_pager_getpages: I/O read error vm_fault: pager read error, pid 808 (firefox-bin) ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267359 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267359 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=119267519 thanks, Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRCerror (retrying request)
OK. Now I really am at a loss for words. I experienced my first FAILURE message this morning when trying to fdisk my last newly formatted 160GB drive. The second fdisk would start to write, my screen would fill with WRITE_DMA WARNINGS and FAILURES. That was with another drive on the same controller. I removed that drive, and everything works fine. I just got another brand new 200GB drive within the last hour. Even it on the same channel as anything else causes errors upon mount, and FAILUREs as well. Then I cannot shut down properly because the errors continue even to the shutdown sequence. Then on the next boot I get messages about things not being properly dismounted. (First time happening). I don't know if it's hardware or FreeBSD anymore. I read this thread on freebsd-stable earlier today, and then all of a sudden I start getting all the failures that I never got before: http://lists.freebsd.org/pipermail/freebsd-stable/2005-August/017636.html So please, anybody...Is this a controller incompatibility with my other hardware (drives) or a FreeBSD problem? Up until now I was 98% certain it was hardware in some way, but now I'm not sure. I have the opportunity to get an Asus board to test, but I'm not going to shell out money for something if it isn't even a hardware problem. Thanks very much. -Mark Mark Kane wrote: Well, it's a week later and I've been trying some things. I don't want to get in to too much complicated detail, but I've now got the following disk setup: Primary Master - 200GB 7200RPM Secondary Master - TDK VeloCD CD Burner Secondary Slave - Sony DRU500A RAID0 Master - 160GB 7200RPM RAID0 Slave - 160GB 7200RPM I don't have the two 80GB's or 60GB's in there now since I was just testing with this setup. I thought keeping the OS drive on primary master and the rest on RAID would do the trick, but it didn't. Bottom line is, I'm still getting the same errors with several different configurations of the drives. Now in the last couple of days I'm also getting READ DMA errors when reading from one of the 160GB drives as well. Before it was all just WRITE, but now some READs are thrown in there as well. I should note that I have never seen a FAILURE message, only the WARNING messages. Also, if I downgrade the speed to UDMA100, it seems to work just fine as it does in UDMA66 mode. I'm wondering if anyone else has any ideas? Personally I'm out, and if nobody else knows (including Maxtor, Giga-Byte, and my parts distributor) then I'm going to have to see what I can do to get another brand/model motherboard. I'm to the point where I think it's something with their controller and how it handles Maxtor drives. Now that I remember, I used to see similar results when running Windows on the previous board before sending it in (same model). However Windows would automatically take it down to 100 so I didn't see any errors. Anyone think its something other than the board and it's controllers, or is that a pretty good estimate? Thanks in advance. -Mark Mark Kane wrote: Okay well I tried another test. I left the 160GB on the primary IDE channel, took out both optical drives, and put the 60GB on the secondary IDE channel by itself. I copied the data over again. No errors this time. I checksummed the data, and everything is OK. Chuck Swiger wrote: Without another known-working mainboard to test, you can't really be sure, but it's a hardware problem of some sort, perhaps due to poor cabling, perhaps a marginal or failing mainboard. The cables are new, and the other drive on the same channel works in UDMA133 with no errors. The motherboard is new as well, fresh from the factory (unless it's defective). If you use BIOS or atacontrol to slow down to UDMA 33 speeds, does everything work OK? I tried slowing it down to UDMA66 speeds via atacontrol, and the errors went away on the 80GB. I haven't tried the 60GB drive yet. -Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRCerror (retrying request)
Well, it's a week later and I've been trying some things. I don't want to get in to too much complicated detail, but I've now got the following disk setup: Primary Master - 200GB 7200RPM Secondary Master - TDK VeloCD CD Burner Secondary Slave - Sony DRU500A RAID0 Master - 160GB 7200RPM RAID0 Slave - 160GB 7200RPM I don't have the two 80GB's or 60GB's in there now since I was just testing with this setup. I thought keeping the OS drive on primary master and the rest on RAID would do the trick, but it didn't. Bottom line is, I'm still getting the same errors with several different configurations of the drives. Now in the last couple of days I'm also getting READ DMA errors when reading from one of the 160GB drives as well. Before it was all just WRITE, but now some READs are thrown in there as well. I should note that I have never seen a FAILURE message, only the WARNING messages. Also, if I downgrade the speed to UDMA100, it seems to work just fine as it does in UDMA66 mode. I'm wondering if anyone else has any ideas? Personally I'm out, and if nobody else knows (including Maxtor, Giga-Byte, and my parts distributor) then I'm going to have to see what I can do to get another brand/model motherboard. I'm to the point where I think it's something with their controller and how it handles Maxtor drives. Now that I remember, I used to see similar results when running Windows on the previous board before sending it in (same model). However Windows would automatically take it down to 100 so I didn't see any errors. Anyone think its something other than the board and it's controllers, or is that a pretty good estimate? Thanks in advance. -Mark Mark Kane wrote: Okay well I tried another test. I left the 160GB on the primary IDE channel, took out both optical drives, and put the 60GB on the secondary IDE channel by itself. I copied the data over again. No errors this time. I checksummed the data, and everything is OK. Chuck Swiger wrote: Without another known-working mainboard to test, you can't really be sure, but it's a hardware problem of some sort, perhaps due to poor cabling, perhaps a marginal or failing mainboard. The cables are new, and the other drive on the same channel works in UDMA133 with no errors. The motherboard is new as well, fresh from the factory (unless it's defective). If you use BIOS or atacontrol to slow down to UDMA 33 speeds, does everything work OK? I tried slowing it down to UDMA66 speeds via atacontrol, and the errors went away on the 80GB. I haven't tried the 60GB drive yet. -Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Joel Rees wrote: I have two which reliably fail if you put TWO disks on them in a gmirror config within minutes of starting a make buildworld. Pardon the interruption, but is this two drives on one channel? Two drives can not be on one channel on SATA controller. Also try Sii3112 Windows trouble on any search site and you'll find many links to problem reports. SII3112 IS NOT Server (even small-server) chipset. It does not work well with semi-heavy load. Of course, you can install and use FreeBSD, Linux, Windows on it, just dont put load on it with 2 disks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said: There are Maxtor MaXLine II and III, and perhaps several other models, that are supposed to work 24/7. Right, i have a dead 250GB Maxline Plus II drive on my desk, only after about 1.5 years. At least its still on warranty. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
It's sad isn't it, Mike..I don't know what the hd manufacturers are doing to the HD drives..ok, the systems get faster, there's usually bad cooling unless you build your own system...but even if you get enough cooling that won't change a thing some hds are prone to die an early death such as the Maxtors..I used to love Maxtor and hated Seagate now it's the other way around but my #1 HD still is Western Digital...I have an old Maxtor drive here 6 gb that's still running perfectly, just like 3 40gb Seagate Barracuda and Western Digital Caviar...I had a 120gb Hitachi that died after 1 yr of use... Mike Jakubik wrote: On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said: There are Maxtor MaXLine II and III, and perhaps several other models, that are supposed to work 24/7. Right, i have a dead 250GB Maxline Plus II drive on my desk, only after about 1.5 years. At least its still on warranty. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Mike Jakubik wrote: On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said: There are Maxtor MaXLine II and III, and perhaps several other models, that are supposed to work 24/7. Right, i have a dead 250GB Maxline Plus II drive on my desk, only after about 1.5 years. At least its still on warranty. On the other hand: In the department for physics of the athmosphere, where I built six years ago a server for meteorological data, a RAID-5 with 4 older IBM U160 SCSI discs still works - 24/7. Never had a problem! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
O. Hartmann wrote: Mike Jakubik wrote: On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said: There are Maxtor MaXLine II and III, and perhaps several other models, that are supposed to work 24/7. Right, i have a dead 250GB Maxline Plus II drive on my desk, only after about 1.5 years. At least its still on warranty. On the other hand: In the department for physics of the athmosphere, where I built six years ago a server for meteorological data, a RAID-5 with 4 older IBM U160 SCSI discs still works - 24/7. Never had a problem! I still own old 1-2 GB old SCSI disks and these are still working, I also had an old 500mb SCSI disk that was in an old Mac that also worked but I trashed it since it was that old and no longer of use... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Am Mittwoch, 10. August 2005 19:48 CEST schrieb Unix: O. Hartmann wrote: Mike Jakubik wrote: On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said: There are Maxtor MaXLine II and III, and perhaps several other models, that are supposed to work 24/7. Right, i have a dead 250GB Maxline Plus II drive on my desk, only after about 1.5 years. At least its still on warranty. On the other hand: In the department for physics of the athmosphere, where I built six years ago a server for meteorological data, a RAID-5 with 4 older IBM U160 SCSI discs still works - 24/7. Never had a problem! I still own old 1-2 GB old SCSI disks and these are still working, I also had an old 500mb SCSI disk that was in an old Mac that also worked but I trashed it since it was that old and no longer of use... I have an old 700 MB WD IDE drive that still works fine and has about 6 years 24/7 survived. And I also had a 2000$ 73G SCSI IBM drive that lasted for about 5 monthas and was that damadged that Convar sent it back without one byte recovered! And I don't want to remember the 80GB WD drive that lasted for 2 months.. Please, don't discuss about SCSI/ATA reliability, there are bad designed/produced drives and there are good ones. You can't tell before, only experience counts. I can say only good things about Seagates Barracuda 7200.8 drives for example. Some dozends are running for two years without _any_ single drive failed. Also the Samsung (p)ATA drives are still running without any single failure. And WDs once were perfect drices, but they also produced crap. So you can't even be sure by vendor! -Harry P.S.: I'm planning to bring up a FreeBSD site which reflects hardware compatibility experiences as well as long term experiences. I'll be back if I have more... pgpKca9tdzt07.pgp Description: PGP signature
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Chuck Swiger wrote: O. Hartmann wrote: [ ... ] One of my SATA disks, the SAMSUNG SP2004C seems to show errors during operation (and also showd under 5.4-RELEASE-p3). Sometimes I get this error: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 while the machine still keeps working. Other days the box crashes completely. Is this a operating system bug or is this message an evidence of defective hardware? You can also run a dd if=/dev/ad10 of=/dev/null bs=8192 to do a full read test under FreeBSD, and see how many CRC errors show up. I did so and I ran into a crash of the system ... I changed the cabling, did it again and until now nothing happend ... hope it was only a cabling issue. The first time I use ATA/SATA and now these experiences ... When is SCSI back for desktops? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
On 平成 17/08/10, at 7:36, O. Hartmann wrote: [...] When is SCSI back for desktops? I vote for that. In my opinion, ATA is primarily for home media systems, if that. Joel Rees [EMAIL PROTECTED] digitcom, inc. 株式会社デジコム Kobe, Japan +81-78-672-8800 ** http://www.ddcom.co.jp ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Joel Rees wrote: On 平成 17/08/10, at 7:36, O. Hartmann wrote: [...] When is SCSI back for desktops? I vote for that. In my opinion, ATA is primarily for home media systems, if that. Joel Rees [EMAIL PROTECTED] digitcom, inc. 株式会社デジコム Kobe, Japan +81-78-672-8800 ** http://www.ddcom.co.jp ** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] I thought the WD Raptors were supposed to replace the SCSI for that purpose. I used to run one in a Powermac and performance wise it behaved very well, unfortunately I haven't had the chance to test the 30 or 70 GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 or server use anyway, they die after a while, in my case, two 80gb seagate drives after 1.5 yrs with proper cooling...thing is that SCSI drives are not affordable to the regular home server user...if they were, I bet more people would use them so that's why the current alternatives are ATA and SATA and SATA Raptors. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
On 8/10/05, Unix [EMAIL PROTECTED] wrote: ... I thought the WD Raptors were supposed to replace the SCSI for that purpose. I used to run one in a Powermac and performance wise it behaved very well, unfortunately I haven't had the chance to test the 30 or 70 GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 or server use anyway ... There are Maxtor MaXLine II and III, and perhaps several other models, that are supposed to work 24/7. -- Dmitry Mityugov, St. Petersburg, Russia I ignore all messages with confidentiality statements We live less by imagination than despite it - Rockwell Kent, N by E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Dmitry Mityugov wrote: On 8/10/05, Unix [EMAIL PROTECTED] wrote: ... I thought the WD Raptors were supposed to replace the SCSI for that purpose. I used to run one in a Powermac and performance wise it behaved very well, unfortunately I haven't had the chance to test the 30 or 70 GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 or server use anyway ... There are Maxtor MaXLine II and III, and perhaps several other models, that are supposed to work 24/7. Yes, but I don't like Maxtor drives, the ones I've used always failed after a year or less than a year... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
On 8/10/05, Unix [EMAIL PROTECTED] wrote: Dmitry Mityugov wrote: On 8/10/05, Unix [EMAIL PROTECTED] wrote: ... I thought the WD Raptors were supposed to replace the SCSI for that purpose. I used to run one in a Powermac and performance wise it behaved very well, unfortunately I haven't had the chance to test the 30 or 70 GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 or server use anyway ... There are Maxtor MaXLine II and III, and perhaps several other models, that are supposed to work 24/7. Yes, but I don't like Maxtor drives, the ones I've used always failed after a year or less than a year... Western Digital produces similar drives as well - from http://store.westerndigital.com/product.asp?sku=2700729: ...24x7 100% duty cycle–the highest available reliability rating on high capacity drives... -- Dmitry Mityugov, St. Petersburg, Russia I ignore all messages with confidentiality statements We live less by imagination than despite it - Rockwell Kent, N by E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Dmitry Mityugov wrote: On 8/10/05, Unix [EMAIL PROTECTED] wrote: Dmitry Mityugov wrote: On 8/10/05, Unix [EMAIL PROTECTED] wrote: ... I thought the WD Raptors were supposed to replace the SCSI for that purpose. I used to run one in a Powermac and performance wise it behaved very well, unfortunately I haven't had the chance to test the 30 or 70 GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 or server use anyway ... There are Maxtor MaXLine II and III, and perhaps several other models, that are supposed to work 24/7. Yes, but I don't like Maxtor drives, the ones I've used always failed after a year or less than a year... Western Digital produces similar drives as well - from http://store.westerndigital.com/product.asp?sku=2700729: ...24x7 100% duty cycle–the highest available reliability rating on high capacity drives... thanks, I need to get some new drives anyway...and WD was on my list... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request)LBA=11441599
On 8/10/05, Unix [EMAIL PROTECTED] wrote: I thought the WD Raptors were supposed to replace the SCSI for that purpose. I used to run one in a Powermac and performance wise it behaved very well, unfortunately I haven't had the chance to test the 30 or 70 GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 or server use anyway I have a FreeBSD 6.0-BETA2 machine that's using a WD Raptor 36 GB using the on-board controller (VIA 8237) of the Asus A7V880 motherboard and it works perfectly. The most taxing thing it runs is the occasional buildworld or (re)build of KDE3 though... Cheers, Mathijs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Mike Tancsa wrote: At 08:25 PM 08/08/2005, O. Hartmann wrote: Hello. My box is a FreeBSD 6.0-BETA2 driven ASUS A8N-SLI Deluxe based AMD64 boxed (see dmesg). One of my SATA disks, the SAMSUNG SP2004C seems to show errors during operation (and also showd under 5.4-RELEASE-p3). Sometimes I get this error: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 while the machine still keeps working. Other days the box crashes completely. Is this a operating system bug or is this message an evidence of defective hardware? You can probably confirm a hardware issue with the smartmon tools. (/usr/ports/sysutils/smartmontools). It was quite handy the other day for us to narrow down a problem between a drive tray and the actual drive. We started to see Aug 3 02:02:49 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=391423 Aug 3 02:03:00 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2304319 Aug 3 02:03:10 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2312927 Aug 3 02:03:17 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2308639 Aug 3 02:03:26 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2309855 Aug 3 02:03:37 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2348359 Aug 4 12:12:37 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=1528639 Aug 4 12:13:04 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=1530031 Aug 4 12:13:04 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=1528639 Aug 4 12:13:04 verify1 kernel: ad0: FAILURE - READ_DMA timed out Aug 4 12:13:04 verify1 kernel: spec_getpages:(ad0s1a) I/O read failure: (error=5) bp 0xd630b4fc vp 0xc2640d68 Yet when we read the actual error info off the drive via smartctl -a ad0, it was clean. So it pointed to the drive tray which we swapped and all was well. In other situations however, the smart info will often tell you if the drive is starting to fail. Its not 100% reliable, but since we started using it, it generally gave us some sort of heads up as to whether or not a drive is in trouble. ---Mike Dear Mike. Thanks a lot for this info. I will use this tool and try to report what I found out. I also use trays for my drives (like I did with SCSI and SCA2 on our servers at the lab). Maybe this could be an issue. Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
O. Hartmann wrote: [ ... ] One of my SATA disks, the SAMSUNG SP2004C seems to show errors during operation (and also showd under 5.4-RELEASE-p3). Sometimes I get this error: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 while the machine still keeps working. Other days the box crashes completely. Is this a operating system bug or is this message an evidence of defective hardware? Back up any data you care about now. Use the smartmontools port or hunt down a utility from Samsung which'll do a surface test (read only, nondestructive). You can also run a dd if=/dev/ad10 of=/dev/null bs=8192 to do a full read test under FreeBSD, and see how many CRC errors show up. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRCerror (retrying request)
Wesley Will wrote: I can try to pull the data off one of my other drives, maybe the 60GB, then format that and try to dump backjust to see if that one copies back OK with no DMA errors. Very good idea. This is an excellent plan, especially if you already have the hardware. Okay, well I finally got a 60GB drive copied to the 160GB, and am now copying the data back after I formatted it and created partitions in UFS. I didn't notice any DMA errors when I was starting like before. When I did the 80GB drive before, the screen was full of them. However, I typed dmesg after 10 minutes or so of copying, and saw this: ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=93353919 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=79306399 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=74453535 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=85548799 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=4249471 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=10253311 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=61090751 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=61585151 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=107013535 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=87075327 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=98752223 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=52787103 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=53049919 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=58052959 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=26957151 Note that this is a clean boot, so it's not the errors from before. It just finished, but while it was copying, the errors would increase by one or two every few minutesmeaning the errors are still occurring, just not as many or as frequent. It's done copying the 39GB of data now, and ended with 18 errors in total. To Gary: My drives are like this PRIMARY IDE: Master - 160GB Slave - 60GB SECONDARY IDE: Master: TDK VeloCD CD Burner Slave: Sony DRU500A DVD Burner I never put optical drives on the same channel as hard drives. I was going to give Maxtor a call on the 80GB when I thought the 60GB was fine, but that was before I found the errors on the 60GB as well. Could something be bad on the board, or is this a FreeBSD problem, or other hardware? Thanks again for all your replies. -Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRCerror (retrying request)
Mark Kane wrote: [ ... ] My drives are like this PRIMARY IDE: Master - 160GB Slave - 60GB SECONDARY IDE: Master: TDK VeloCD CD Burner Slave: Sony DRU500A DVD Burner I never put optical drives on the same channel as hard drives. I was going to give Maxtor a call on the 80GB when I thought the 60GB was fine, but that was before I found the errors on the 60GB as well. Could something be bad on the board, or is this a FreeBSD problem, or other hardware? Without another known-working mainboard to test, you can't really be sure, but it's a hardware problem of some sort, perhaps due to poor cabling, perhaps a marginal or failing mainboard. If you use BIOS or atacontrol to slow down to UDMA 33 speeds, does everything work OK? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRCerror (retrying request)
Okay well I tried another test. I left the 160GB on the primary IDE channel, took out both optical drives, and put the 60GB on the secondary IDE channel by itself. I copied the data over again. No errors this time. I checksummed the data, and everything is OK. Chuck Swiger wrote: Without another known-working mainboard to test, you can't really be sure, but it's a hardware problem of some sort, perhaps due to poor cabling, perhaps a marginal or failing mainboard. The cables are new, and the other drive on the same channel works in UDMA133 with no errors. The motherboard is new as well, fresh from the factory (unless it's defective). If you use BIOS or atacontrol to slow down to UDMA 33 speeds, does everything work OK? I tried slowing it down to UDMA66 speeds via atacontrol, and the errors went away on the 80GB. I haven't tried the 60GB drive yet. -Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
Hello. My box is a FreeBSD 6.0-BETA2 driven ASUS A8N-SLI Deluxe based AMD64 boxed (see dmesg). One of my SATA disks, the SAMSUNG SP2004C seems to show errors during operation (and also showd under 5.4-RELEASE-p3). Sometimes I get this error: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 while the machine still keeps working. Other days the box crashes completely. Is this a operating system bug or is this message an evidence of defective hardware? By the way, DMA support is enabled: hw.ata.ata_dma: 1 hw.ata.atapi_dma: 1 Thanks in advance,\ Oliver Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-BETA2 #23: Sun Aug 7 23:32:03 UTC 2005 [EMAIL PROTECTED]:/usr/backup/obj/usr/src/sys/THOR Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3500+ (2211.34-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x10ff0 Stepping = 0 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 AMD Features=0xe2500800SYSCALL,NX,MMX+,b25,LM,3DNow+,3DNow real memory = 2147418112 (2047 MB) avail memory = 2064375808 (1968 MB) ACPI APIC Table: Nvidia AWRDACPI ioapic0 Version 1.1 irqs 0-23 on motherboard netsmb_dev: loaded acpi0: Nvidia AWRDACPI on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR pci_link0: ACPI PCI Link LNK1 irq 10 on acpi0 pci_link1: ACPI PCI Link LNK2 on acpi0 pci_link2: ACPI PCI Link LNK3 irq 5 on acpi0 pci_link3: ACPI PCI Link LNK4 on acpi0 pci_link4: ACPI PCI Link LNK5 on acpi0 pci_link5: ACPI PCI Link LUBA irq 5 on acpi0 pci_link6: ACPI PCI Link LUBB on acpi0 pci_link7: ACPI PCI Link LMAC irq 11 on acpi0 pci_link8: ACPI PCI Link LACI irq 3 on acpi0 pci_link9: ACPI PCI Link LMCI on acpi0 pci_link10: ACPI PCI Link LSMB irq 11 on acpi0 pci_link11: ACPI PCI Link LUB2 irq 3 on acpi0 pci_link12: ACPI PCI Link LIDE on acpi0 pci_link13: ACPI PCI Link LSID irq 11 on acpi0 pci_link14: ACPI PCI Link LFID irq 10 on acpi0 pci_link15: ACPI PCI Link LPCA on acpi0 pci_link16: ACPI PCI Link APC1 irq 0 on acpi0 pci_link17: ACPI PCI Link APC2 irq 0 on acpi0 pci_link18: ACPI PCI Link APC3 irq 0 on acpi0 pci_link19: ACPI PCI Link APC4 irq 0 on acpi0 pci_link20: ACPI PCI Link APC5 irq 16 on acpi0 pci_link21: ACPI PCI Link APCF irq 0 on acpi0 pci_link22: ACPI PCI Link APCG irq 0 on acpi0 pci_link23: ACPI PCI Link APCH irq 0 on acpi0 pci_link24: ACPI PCI Link APCJ irq 0 on acpi0 pci_link25: ACPI PCI Link APCK irq 0 on acpi0 pci_link26: ACPI PCI Link APCS irq 0 on acpi0 pci_link27: ACPI PCI Link APCL irq 0 on acpi0 pci_link28: ACPI PCI Link APCZ irq 0 on acpi0 pci_link29: ACPI PCI Link APSI irq 0 on acpi0 pci_link30: ACPI PCI Link APSJ irq 0 on acpi0 pci_link31: ACPI PCI Link APCP irq 0 on acpi0 Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci_link26: BIOS IRQ 11 for -2145766612.1.INTA is invalid pci_link21: BIOS IRQ 5 for -2145766612.2.INTA is invalid pci_link27: BIOS IRQ 3 for -2145766612.2.INTB is invalid pci_link23: BIOS IRQ 11 for -2145766612.10.INTA is invalid pci_link24: BIOS IRQ 3 for -2145766612.4.INTA is invalid pci_link29: BIOS IRQ 11 for -2145766612.7.INTA is invalid pci_link30: BIOS IRQ 10 for -2145766612.8.INTA is invalid pci0: ACPI PCI bus on pcib0 pci_link26: Unable to choose an IRQ pci_link21: Unable to choose an IRQ pci_link27: Unable to choose an IRQ pci_link24: Unable to choose an IRQ pci_link29: Unable to choose an IRQ pci_link30: Unable to choose an IRQ pci_link23: Unable to choose an IRQ pci0: memory at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 ichsmb0: SMBus controller port 0xe400-0xe41f,0x4c00-0x4c3f,0x4c40-0x4c7f irq 20 at device 1.1 on pci0 ichsmb0: [GIANT-LOCKED] smbus0: System Management Bus on ichsmb0 smb0: SMBus generic I/O on smbus0 ohci0: OHCI (generic) USB controller mem 0xd8104000-0xd8104fff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0: EHCI (generic) USB 2.0 controller mem 0xfeb0-0xfeb000ff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: EHCI (generic) USB 2.0 controller on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 10
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
At 08:25 PM 08/08/2005, O. Hartmann wrote: Hello. My box is a FreeBSD 6.0-BETA2 driven ASUS A8N-SLI Deluxe based AMD64 boxed (see dmesg). One of my SATA disks, the SAMSUNG SP2004C seems to show errors during operation (and also showd under 5.4-RELEASE-p3). Sometimes I get this error: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 while the machine still keeps working. Other days the box crashes completely. Is this a operating system bug or is this message an evidence of defective hardware? You can probably confirm a hardware issue with the smartmon tools. (/usr/ports/sysutils/smartmontools). It was quite handy the other day for us to narrow down a problem between a drive tray and the actual drive. We started to see Aug 3 02:02:49 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=391423 Aug 3 02:03:00 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2304319 Aug 3 02:03:10 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2312927 Aug 3 02:03:17 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2308639 Aug 3 02:03:26 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2309855 Aug 3 02:03:37 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2348359 Aug 4 12:12:37 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=1528639 Aug 4 12:13:04 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=1530031 Aug 4 12:13:04 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=1528639 Aug 4 12:13:04 verify1 kernel: ad0: FAILURE - READ_DMA timed out Aug 4 12:13:04 verify1 kernel: spec_getpages:(ad0s1a) I/O read failure: (error=5) bp 0xd630b4fc vp 0xc2640d68 Yet when we read the actual error info off the drive via smartctl -a ad0, it was clean. So it pointed to the drive tray which we swapped and all was well. In other situations however, the smart info will often tell you if the drive is starting to fail. Its not 100% reliable, but since we started using it, it generally gave us some sort of heads up as to whether or not a drive is in trouble. ---Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRCerror (retrying request)
Mark Kane [EMAIL PROTECTED] writes: This is a brand new motherboard. Giga-Byte GA-K8NS Pro. FreeBSD 5.4-RELEASE (amd64). I was also doing some searching around and found a list post about FreeBSD 5 and DMA write problems: I've got a GA-K8NSC-939 running 5.4-R (i386) with two 80GB using UDMA100 that I've run pretty hard occasionally with dump/restore, diff -r kind of operations, with no problems. I ran 5.4-R (amd64) lightly for a few days without noticing disk problems. You said one of your disks was a slave. I've read rumors that that's a bad thing if its master is a CDROM, but I'd think it should just run slower than it's capable of. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRCerror (retrying request)
I had a disk that was giving the same errors so at the time I just disabled DMA (in loader.conf, hw.ata.ata_dma=0) but I still wanted to fix it.. so yesterday.. the drive was set as primary (ad2) but I switched it to slave (ad3). it seems fine now. clayton On 8/7/05, Gary W. Swearingen [EMAIL PROTECTED] wrote: Mark Kane [EMAIL PROTECTED] writes: This is a brand new motherboard. Giga-Byte GA-K8NS Pro. FreeBSD 5.4-RELEASE (amd64). I was also doing some searching around and found a list post about FreeBSD 5 and DMA write problems: I've got a GA-K8NSC-939 running 5.4-R (i386) with two 80GB using UDMA100 that I've run pretty hard occasionally with dump/restore, diff -r kind of operations, with no problems. I ran 5.4-R (amd64) lightly for a few days without noticing disk problems. You said one of your disks was a slave. I've read rumors that that's a bad thing if its master is a CDROM, but I'd think it should just run slower than it's capable of. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRC error (retrying request)
Hi everyone. I have searched the lists and Google about this, but none of the things I find seem to be my exact problem. I have an 80GB Maxtor IDE hard drive that was in NTFS yesterday. Last night, I copied all 75GB of data off that drive to another drive in the system. It took a while, but didn't give any errors. Today, I go to use sysinstall to fdisk and disklabel the drive to make it UFS for use with FreeBSD. That goes OK and it's now mounted fine. I go to copy the data back from the backups I made last night, and immediately I get tons of warnings like this: ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=3205439 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=3206591 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=3208767 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=3210047 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=3214655 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=3215167 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=4163583 ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=4164479 Most of the things I see from searching online point to faulty IDE cables, but I swapped the cables a month or so ago. Also, the drive that I copied all this data to last night (a 160GB Maxtor) is on the same IDE cable as this one with no errors. I have 3 more drives to backup and convert from NTFS to UFS after this, so if anyone has any ideas to help me get on my way, that would be excellent. ad1: 76344MB MAXTOR 6L080J4/A93.0500 [155112/16/63] at ata0-slave UDMA133 Thanks very much in advance! -Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRC error (retrying request)
ad1: 76344MB MAXTOR 6L080J4/A93.0500 [155112/16/63] at ata0-slave UDMA133 Do the errors go away if you switch the disk (in BIOS, and what are the BIOS settings for this drive right now?) to PIO mode? -- wes will ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRC error (retrying request)
Hello Wesley, Saturday, August 6, 2005, 8:51:19 PM, you typed: ad1: 76344MB MAXTOR 6L080J4/A93.0500 [155112/16/63] at ata0-slave UDMA133 Do the errors go away if you switch the disk (in BIOS, and what are the BIOS settings for this drive right now?) to PIO mode? or try to decrease it's speed with atacontrol to, let's say, UDMA66. -- Best Regards, DanGer, ICQ: 261701668 | e-mail protecting at: http://www.2pu.net/ http://danger.rulez.sk | proxy list at:http://www.proxy-web.com/ | FreeBSD - The Power to Serve! [ Famous last words: Hiyah, Captain BALDY! ]
Re: After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRC error (retrying request)
Daniel Gerzo wrote: Hello Wesley, Saturday, August 6, 2005, 8:51:19 PM, you typed: ad1: 76344MB MAXTOR 6L080J4/A93.0500 [155112/16/63] at ata0-slave UDMA133 Do the errors go away if you switch the disk (in BIOS, and what are the BIOS settings for this drive right now?) to PIO mode? or try to decrease it's speed with atacontrol to, let's say, UDMA66. Thanks for the replies. After decreasing to UDMA66, the errors went away (at least from what I saw). I didn't let it run all the way through obviously, but when it was in UDMA133 mode the errors came on the second I started. I haven't tried PIO yet since UDMA66 worked. Wesley, I'm not sure what info you wanted from the BIOS. It's the primary IDE channel slave (the 80GB). What could this mean? -Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: After Partitioning a Drive: WARNING - WRITE_DMA UDMA ICRCerror (retrying request)
Wesley Will wrote: It almost assuredly means that the drive electronics are failing. The mag bubble is likely still intact but the controller isn't capable of keeping up with that data rate any longer. It could (easily) be an overheating issue causing the degradation of performance. These drives and every Maxtor I've ever had the bad luck to run across ran as hot as a firecracker. It could also be a cable issue, but it isn't the most likely of causes. I'd not count on that drive under any circumstances for any data of importance. I was thinking of drive failure earlier as well, so I started to run the PowerMax utility. The quick 90 second test came up Passed. The advanced test just got done running, and it passed that as well. This drive has been in a 5 1/4 hard drive cooler, and to the touch after operation it's not very warm at all compared to Maxtor drives that I run without coolers. The thing I find odd is that when copying the data from the drive while it was NTFS last night, there were no errors. I'm not sure if this kind of problem would only happen with writing, but I didn't see it until I tried to copy the data back to the drive after formatting to UFS. It seemed to be working fine when it was the machine was running Windows. I didn't think it was the cable since the other drive on the same cable runs at 133 fine now. The only other thing I could think of hardware would be that the master is at the end of the cable (jumper set to master) and this drive (slave) is in the middlebut I wouldn't think that would cause this. This is a brand new motherboard. Giga-Byte GA-K8NS Pro. FreeBSD 5.4-RELEASE (amd64). I was also doing some searching around and found a list post about FreeBSD 5 and DMA write problems: http://lists.freebsd.org/pipermail/freebsd-stable/2005-August/017610.html I was hoping this wasn't it since I didn't want to wait for 6 to become stable, but if we're leaning more towards the drive, then maybe I can get a new one. I'd just like to know for sure before I buy another drive, since I just bought a new 160GB for the FreeBSD install drive. I can try to pull the data off one of my other drives, maybe the 60GB, then format that and try to dump backjust to see if that one copies back OK with no DMA errors. -Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Big directory and the UDMA ICRC error writing fsbn message
Hello Recently, a server of mine running FreeBSD 4.6.2-RELEASE started getting UDMA ICRC errors and put it's disk communication into PIO mode. I'm just wondering if this could have been caused by one very big and growing directory under /var, where one new file was being created every 15 minutes. It had reached about 100,000 files in the one directory. Is this possible? Or is something more prozaic at play here, eg a dodgy cable or a disk on the way out? There are two identical disks on this box that are mirrored with a hardware raid chip. Here are the messages anyhow: Apr 2 01:13:45 eagle /kernel: ad5: UDMA ICRC error writing fsbn 119103807 of 0-255 (ad5 bn 119103807; cn 118158 tn 8 sn 39) retrying Apr 2 01:14:01 eagle /kernel: ad5: UDMA ICRC error writing fsbn 79975487 of 0-23 (ad5 bn 79975487; cn 79340 tn 12 sn 11) retrying Apr 2 01:14:02 eagle last message repeated 2 times Apr 2 01:14:02 eagle /kernel: ad5: UDMA ICRC error writing fsbn 79975487 of 0-23 (ad5 bn 79975487; cn 79340 tn 12 sn 11) falling back to PIO m ode I'm also getting some other errors about time, eg: Apr 15 03:17:13 eagle named[78]: gettimeofday returned bad tv_usec: corrected Apr 18 15:16:54 eagle /kernel: microuptime() went backwards (44815198.498490 - 44815198.-695597409) about the disks and filesystems: # df -k Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ar0s1a 103214263190 886382 7%/ /dev/ar0s1g 107383706 94043514 474949695%/large /dev/ar0s1f 4129310 1432826 236614038%/usr /dev/ar0s1e 4129310 649442 314952417%/var procfs 44 0 100%/proc # atacontrol status ar0 ar0: ATA RAID1 subdisks: ad4 ad5 status: READY Thanks very much Jesse ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA ICRC error
Rob wrote: --- Ramiro Aceves [EMAIL PROTECTED] wrote: Rob wrote: Ramiro Aceves wrote: I have read that others had this problem before. I just write this report for you to know. When I installed FreeBSD 5.3 R, I get some errors like this, but I could end the install: ad0: WARNING -READ_DMA UDMA ICRC error (retrying request) LBA=5313599 ad0: FAILURE -READ_DMA status=51READY,DSC,ERROR error=84 ICRC,ABORTED spec_getpages:(ad0s1a) I/O read failure: (error=5) I have solved the problem disabling DMA: hw.ata.ata_dma=0 It's indeed a serious problem, but too few people running 5.3 seem to suffer from this. Have you tried with 4.11? I bet that would not generate these problems. Thanks, I see that we are not alone! I have not got a 4.11 CDROM here. I could test it on 4.10 if you think it is important, I have a 4.10 CDROM here. My internet is too slow to dowload a full CDROM at home. I can download 4.11 install CDROM on the computers at University if it worths the effort. No, no need for that. It's already confirmed that 4.X does not have this problem. However, recently there's a 'ATA mkIII' patch around, which seems to also solve this problem. Follow the discussion on -stable mailinglist for further details. I'm not yet sure whether you have to upgrade first to 5-STABLE before applying this patch. Rob. Thanks Rob! __ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
UDMA ICRC error
Hello FreeBSD friends. I have read that others had this problem before. I just write this report for you to know. I received yesterday two old computers retired from a school and finally I was able to build a decent machine mixing the best parts of each one. The machine is an AMD K6 400 MHz with 64 MB RAM, AGP i740 video. Hard disk is Seagate ST34321A/3.05 master on ide0 bus. On ide1 bus there is a CD-R as master, and a CD-RW as slave. Disk controller is VIA 82C586B UDMA33. When I installed FreeBSD 5.3 R, I get some errors like this, but I could end the install: ad0: WARNING -READ_DMA UDMA ICRC error (retrying request) LBA=5313599 ad0: FAILURE -READ_DMA status=51READY,DSC,ERROR error=84 ICRC,ABORTED spec_getpages:(ad0s1a) I/O read failure: (error=5) I have solved the problem disabling DMA: hw.ata.ata_dma=0 (I previously tried disabling ACPI with no success, and playing with BIOS LBA, LARGE, NORMAL settings at the BIOS with no success). Now ad0: works in PIO4 mode and everything is fine, previously , it was UDMA33. Now there are no errors. Should I investigate it further, or this is the only possible solution? Should I expect a great performance decreasing in I/O disk access? Thanks in advance. Ramiro. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA ICRC error
Ramiro Aceves wrote: I have read that others had this problem before. I just write this report for you to know. When I installed FreeBSD 5.3 R, I get some errors like this, but I could end the install: ad0: WARNING -READ_DMA UDMA ICRC error (retrying request) LBA=5313599 ad0: FAILURE -READ_DMA status=51READY,DSC,ERROR error=84 ICRC,ABORTED spec_getpages:(ad0s1a) I/O read failure: (error=5) I have solved the problem disabling DMA: hw.ata.ata_dma=0 (I previously tried disabling ACPI with no success, and playing with BIOS LBA, LARGE, NORMAL settings at the BIOS with no success). Now ad0: works in PIO4 mode and everything is fine, previously , it was UDMA33. Now there are no errors. There's you and me now. I have this problem with two of my PCs. I don't know yet of anybody else who has these problems. It's indeed a serious problem, but too few people running 5.3 seem to suffer from this. Have you tried with 4.11? I bet that would not generate these problems. Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA ICRC error
On Wed, 2005-02-16 at 06:31 -0800, Rob wrote: Ramiro Aceves wrote: I have read that others had this problem before. I just write this report for you to know. When I installed FreeBSD 5.3 R, I get some errors like this, but I could end the install: ad0: WARNING -READ_DMA UDMA ICRC error (retrying request) LBA=5313599 ad0: FAILURE -READ_DMA status=51READY,DSC,ERROR error=84 ICRC,ABORTED spec_getpages:(ad0s1a) I/O read failure: (error=5) I have solved the problem disabling DMA: hw.ata.ata_dma=0 (I previously tried disabling ACPI with no success, and playing with BIOS LBA, LARGE, NORMAL settings at the BIOS with no success). Now ad0: works in PIO4 mode and everything is fine, previously , it was UDMA33. Now there are no errors. There's you and me now. I have this problem with two of my PCs. I don't know yet of anybody else who has these problems. It's indeed a serious problem, but too few people running 5.3 seem to suffer from this. No, it's a known problem and I filed a pr about it a while back. So far as I know, there's been no action on the pr and disabling dma is the only workaround. Have you tried with 4.11? I bet that would not generate these problems. Agreed. Peter. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA ICRC error
Rob wrote: Ramiro Aceves wrote: I have read that others had this problem before. I just write this report for you to know. When I installed FreeBSD 5.3 R, I get some errors like this, but I could end the install: ad0: WARNING -READ_DMA UDMA ICRC error (retrying request) LBA=5313599 ad0: FAILURE -READ_DMA status=51READY,DSC,ERROR error=84 ICRC,ABORTED spec_getpages:(ad0s1a) I/O read failure: (error=5) I have solved the problem disabling DMA: hw.ata.ata_dma=0 (I previously tried disabling ACPI with no success, and playing with BIOS LBA, LARGE, NORMAL settings at the BIOS with no success). Now ad0: works in PIO4 mode and everything is fine, previously , it was UDMA33. Now there are no errors. There's you and me now. I have this problem with two of my PCs. I don't know yet of anybody else who has these problems. It's indeed a serious problem, but too few people running 5.3 seem to suffer from this. Have you tried with 4.11? I bet that would not generate these problems. Thanks, I see that we are not alone! I have not got a 4.11 CDROM here. I could test it on 4.10 if you think it is important, I have a 4.10 CDROM here. My internet is too slow to dowload a full CDROM at home. I can download 4.11 install CDROM on the computers at University if it worths the effort. Please let me know. Ramiro. Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA ICRC error
Peter Risdon wrote: On Wed, 2005-02-16 at 06:31 -0800, Rob wrote: Ramiro Aceves wrote: I have read that others had this problem before. I just write this report for you to know. When I installed FreeBSD 5.3 R, I get some errors like this, but I could end the install: ad0: WARNING -READ_DMA UDMA ICRC error (retrying request) LBA=5313599 ad0: FAILURE -READ_DMA status=51READY,DSC,ERROR error=84 ICRC,ABORTED spec_getpages:(ad0s1a) I/O read failure: (error=5) I have solved the problem disabling DMA: hw.ata.ata_dma=0 (I previously tried disabling ACPI with no success, and playing with BIOS LBA, LARGE, NORMAL settings at the BIOS with no success). Now ad0: works in PIO4 mode and everything is fine, previously , it was UDMA33. Now there are no errors. There's you and me now. I have this problem with two of my PCs. I don't know yet of anybody else who has these problems. It's indeed a serious problem, but too few people running 5.3 seem to suffer from this. No, it's a known problem and I filed a pr about it a while back. So far as I know, there's been no action on the pr and disabling dma is the only workaround. Have you tried with 4.11? I bet that would not generate these problems. Agreed. Peter. Hi Peter! Thank you very much for the usefull information. We will keep in touch for any news. Ramiro. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA ICRC error
--- Ramiro Aceves [EMAIL PROTECTED] wrote: Rob wrote: Ramiro Aceves wrote: I have read that others had this problem before. I just write this report for you to know. When I installed FreeBSD 5.3 R, I get some errors like this, but I could end the install: ad0: WARNING -READ_DMA UDMA ICRC error (retrying request) LBA=5313599 ad0: FAILURE -READ_DMA status=51READY,DSC,ERROR error=84 ICRC,ABORTED spec_getpages:(ad0s1a) I/O read failure: (error=5) I have solved the problem disabling DMA: hw.ata.ata_dma=0 It's indeed a serious problem, but too few people running 5.3 seem to suffer from this. Have you tried with 4.11? I bet that would not generate these problems. Thanks, I see that we are not alone! I have not got a 4.11 CDROM here. I could test it on 4.10 if you think it is important, I have a 4.10 CDROM here. My internet is too slow to dowload a full CDROM at home. I can download 4.11 install CDROM on the computers at University if it worths the effort. No, no need for that. It's already confirmed that 4.X does not have this problem. However, recently there's a 'ATA mkIII' patch around, which seems to also solve this problem. Follow the discussion on -stable mailinglist for further details. I'm not yet sure whether you have to upgrade first to 5-STABLE before applying this patch. Rob. __ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
WRITE_DMA UDMA ICRC ERROR
A few days ago I started to get some errors which seemed like a HD was about to fail. Changed the drive and put a brand new drive. Since changing the drive I am getting even more errors. Jan 30 12:52:24 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=52551839 Jan 30 13:08:36 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=88194655 Jan 30 13:12:01 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Jan 30 13:12:01 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Jan 30 13:12:01 zoraida kernel: ad2: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=106009983 Jan 30 13:12:04 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Jan 30 13:12:04 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Jan 30 13:12:05 zoraida kernel: ad2: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=106009983 Jan 30 13:12:21 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Jan 30 13:12:21 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Jan 30 13:12:22 zoraida kernel: ad2: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=106009983 Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WRITE_DMA UDMA ICRC ERROR
check if yours new hd is connected through a 80 pin ide cable ( for UDMA speed = 66 ). I had the same troble and it disappeared as soon as i replaced the cable. hope this will help, regards On Mon, Jan 31, 2005 at 08:18:33PM -0500, Francisco Reyes wrote: A few days ago I started to get some errors which seemed like a HD was about to fail. Changed the drive and put a brand new drive. Since changing the drive I am getting even more errors. Jan 30 12:52:24 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=52551839 Jan 30 13:08:36 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=88194655 Jan 30 13:12:01 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Jan 30 13:12:01 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Jan 30 13:12:01 zoraida kernel: ad2: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=106009983 Jan 30 13:12:04 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Jan 30 13:12:04 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Jan 30 13:12:05 zoraida kernel: ad2: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=106009983 Jan 30 13:12:21 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Jan 30 13:12:21 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Jan 30 13:12:22 zoraida kernel: ad2: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=106009983 Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WRITE_DMA UDMA ICRC ERROR
On Tue, 1 Feb 2005, Santo Natale wrote: check if yours new hd is connected through a 80 pin ide cable ( for UDMA speed = 66 ). I had the same troble and it disappeared as soon as i replaced the cable. hope this will help, regards (retrying request) LBA=106009983 Jan 30 13:12:05 zoraida kernel: ad2: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=106009983 Jan 30 13:12:21 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=106009983 Thanks. Will check the cable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WRITE_DMA UDMA ICRC ERROR
On Tue, 1 Feb 2005, Santo Natale wrote: check if yours new hd is connected through a 80 pin ide cable ( for UDMA speed = 66 ). Jan 30 12:52:24 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=52551839 Jan 30 13:08:36 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=88194655 In the mean time how could I decrease the UDMA setting so it operates at a lower speed? It probably will be a few days before I get to stop by the computer store. Most lines are simply warnings, but there area a few errors. This is just a backup drive (ie every X number of hours backup some data from my primary drive) so it's not too much of a problem to slow it down temporarily. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WRITE_DMA UDMA ICRC ERROR
Francisco Reyes wrote: On Tue, 1 Feb 2005, Santo Natale wrote: check if yours new hd is connected through a 80 pin ide cable ( for UDMA speed = 66 ). Jan 30 12:52:24 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=52551839 Jan 30 13:08:36 zoraida kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=88194655 In the mean time how could I decrease the UDMA setting so it operates at a lower speed? Use atacontrol(8): # atacontrol mode 0 Master = UDMA66 Slave = BIOSPIO # atacontrol mode 0 udma33 biospio # atacontrol mode 0 Master = UDMA33 Slave = BIOSPIO It probably will be a few days before I get to stop by the computer store. Most lines are simply warnings, but there area a few errors. This is just a backup drive (ie every X number of hours backup some data from my primary drive) so it's not too much of a problem to slow it down temporarily. They are warnings, but a UDMA speed mismatch can bite you when you least expect it :) Cheers, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WRITE_DMA UDMA ICRC ERROR
On Tue, 1 Feb 2005, cpghost wrote: In the mean time how could I decrease the UDMA setting so it operates at a lower speed? Use atacontrol(8): Thanks. That was easy enough. :-) They are warnings, but a UDMA speed mismatch can bite you when you least expect it :) The drive is UDMA100. Set it to UDMA66 for now. Till I have time to check the cable. How would one set it at boot time, if I needed, to make this permanent? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA - UDMA ICRC Error
Can anyone help with this please? --- Rishi Chopra [EMAIL PROTECTED] wrote: Date: Sun, 19 Sep 2004 23:29:01 -0700 (PDT) From: Rishi Chopra [EMAIL PROTECTED] Subject: ATA - UDMA ICRC Error To: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] I noticed the posting at: http://groups.google.com/groups?hl=enlr=ie=UTF-8threadm=20040120192745.GA1209%40uriel.mcgoldrick.orgrnum=29prev=/groups%3Fq%3Dfreebsd%2Bstatus%253D51%2Berror%253D84%2BICRC%26hl%3Den%26lr%3D%26ie%3DUTF-8%26start%3D20%26sa%3DN and was curious if a solution had been found for this problem (kernel: ad4: FAILURE - READ_DMA status=51READ, DSC, ERROR error=84ICRC, ABORTED). I have the same problem with a PCI promise Ultra100 TX2 controller card and 200GB Western Digital 2000JB drive on startup. I've double-checked that the cable, controller, and drive are all working by plugging them by accessing them through DOS and Windows 2000; the drive shows up just fine and produces flawless I/O. My drive is jumpered as single/master, set to ATA100, and the cable works just fine. I've noticed other postings with a similar error, but the only suggestion given was either controller failure or cable failure. In my case I'm certain that neither is the cause of the problem. Any ideas? = Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com = Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ATA - UDMA ICRC Error
I noticed the posting at: http://groups.google.com/groups?hl=enlr=ie=UTF-8threadm=20040120192745.GA1209%40uriel.mcgoldrick.orgrnum=29prev=/groups%3Fq%3Dfreebsd%2Bstatus%253D51%2Berror%253D84%2BICRC%26hl%3Den%26lr%3D%26ie%3DUTF-8%26start%3D20%26sa%3DN and was curious if a solution had been found for this problem (kernel: ad4: FAILURE - READ_DMA status=51READ, DSC, ERROR error=84ICRC, ABORTED). I have the same problem with a PCI promise Ultra100 TX2 controller card and 200GB Western Digital 2000JB drive on startup. I've double-checked that the cable, controller, and drive are all working by plugging them by accessing them through DOS and Windows 2000; the drive shows up just fine and produces flawless I/O. My drive is jumpered as single/master, set to ATA100, and the cable works just fine. I've noticed other postings with a similar error, but the only suggestion given was either controller failure or cable failure. In my case I'm certain that neither is the cause of the problem. Any ideas? = Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
More ata/UDMA disk write questions
Hey again everyone. I had a problem recently with TIMEOUT - WRITE_DMA errors, often followed by a complete lockup and data loss, sometimes enough to require a complete reinstall. There were a number of recommendations, some of which, however well intentioned, and definitely appreciated nonetheless, caused more trouble and not less. One thing that wasn't suggested was simply turning off write caching in the ata(4) driver itself. This is done by setting hw.ata.wc=0 in /boot/loader.conf. Well, I've read through the ata(4) manpage and the atacontrol(8) manpage a little more thoroughly, and looked at the /var/run/dmesg.boot log a lot more. I've noticed a couple things: * The ICH5 SATA 150 controller is correctly recognized as such by the kernel. * The Intel ICH5 controller is listed as supported in ata(4), and in the 4.10 hardware list (http://www.freebsd.org/releases/4.10R/hardware-i386.html#AEN34), but not in the 5.2.1 hardware list (http://www.freebsd.org/releases/5.2.1R/hardware-i386.html#AEN65). That's still a little confusing to me. And, the ICH5 SATA 150 controller is supposed to be capable of a 150M/sec transfer rate, but the atacontrol(8) manpage only mentions UDMA2 (aka UDMA33), UDMA4 (aka UDMA66), UDMA5 (aka UDMA100) and UDMA6 (aka UDMA133), which, if I understand these names right, don't provide the full 150M/s transfer rate. The atacontrol utility indicates the drive controller in question is currently using UDMA100. I'm not really familiar with these protocols/standards, so if anyone knows where a 25 cent tour of these can be found, I'd appreciate the pointer. Assuming I am correct about the meaning of the 33/66/100/133 values, does anyone on this list know if (or when) the ata driver will support the full 150M/s transfer rate? Is it possible that the ata(4) write caching could be incompatible with the disks hardware caching mechanisms? I've turned off hw.ata.wc, rebooted, and am currently executing a full port rebuild/reinstall (portupgrade -afR) which should be done some time next year (well, maybe tomorrow). So far so good. I'm going to guess that the disk activity incurred in this would be likely to indicate that the problem is either still around or has been fixed by turning off write caching. I have put the drive through a bios level diagnostic built into newer Dell MoBos (CTRL-ALT-D at the Dell startup logo) and it passed just fine. There is a WDC diagnostic tool I have downloaded and will find a way to use if this happens again, but I think the drive must be fine. Any thoughts, pointers, etc. on ata, atacontrol, UDMA150 support, etc. would be appreciated. Thanks Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ share, n.: To give in, endure humiliation. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to disable UDMA for HDD?
On Thursday 12 August 2004 19:11, Chuck Swiger wrote: Stevan Tiefert wrote: [ ... ] you did not understood what I wanted. I needed a suggestion how to install FreeBSD without UDMA-support. Your suggestion is only useful if the system is running, but that was not the case! What happens if you configure the BIOS of the system not to use UDMA modes for that device? Most BIOSes will let you control individual devices, so set whatever it is to PIO4; otherwise, disable UDMA for everything long enough to complete the install, and then tweak things from there. Hello Chuck, it is right, if you say that BIOSes provide switching between PIO0 to PIO4, but there is no way to control UDMA in a BIOS. Anyway, it doesn't matter, because every Operating System (without DOS) is taking control after the bootstrap over the hardware and even FreeBSD. If the kernel is taking control, switches have to take in the kernel described in the e-mail from Nathan at the loader prompt: set hw.ata.ata_dma=0 Bye Stevan Tiefert -- deltree /y c:\windows My suggestion to solve all your problems! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to disable UDMA for HDD?
Stevan Tiefert wrote: [ ... ] you did not understood what I wanted. I needed a suggestion how to install FreeBSD without UDMA-support. Your suggestion is only useful if the system is running, but that was not the case! What happens if you configure the BIOS of the system not to use UDMA modes for that device? Most BIOSes will let you control individual devices, so set whatever it is to PIO4; otherwise, disable UDMA for everything long enough to complete the install, and then tweak things from there. -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to disable UDMA for HDD?
On Tue, 10 Aug 2004 09:08:29 +0200, Stevan Tiefert [EMAIL PROTECTED] wrote: SNIP set hw.ata.ata_dma=0 Now it is possible to install FreeBSD! Thanks very much! Mr. Stevan Tiefert Is there a way to disable DMA for a single hard drive, instead of all IDE devices? -- Matt H [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to disable UDMA for HDD?
Matt H wrote: On Tue, 10 Aug 2004 09:08:29 +0200, Stevan Tiefert [EMAIL PROTECTED] wrote: SNIP set hw.ata.ata_dma=0 Now it is possible to install FreeBSD! Thanks very much! Mr. Stevan Tiefert Is there a way to disable DMA for a single hard drive, instead of all IDE devices? How about this: /sbin/atacontrol mode 0 PIO4 XXX? (if you want UDMA disabled on the master at channel 0). - Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to disable UDMA for HDD?
On Wednesday 11 August 2004 16:46, Matt H wrote: On Tue, 10 Aug 2004 09:08:29 +0200, Stevan Tiefert [EMAIL PROTECTED] wrote: SNIP set hw.ata.ata_dma=0 Now it is possible to install FreeBSD! Thanks very much! Mr. Stevan Tiefert Is there a way to disable DMA for a single hard drive, instead of all IDE devices? Hello, I don't know it. Bye Stevan Tiefert -- deltree /y c:\windows My suggestion to solve all your problems! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to disable UDMA for HDD?
On Wednesday 11 August 2004 16:55, Mark wrote: Matt H wrote: On Tue, 10 Aug 2004 09:08:29 +0200, Stevan Tiefert [EMAIL PROTECTED] wrote: SNIP set hw.ata.ata_dma=0 Now it is possible to install FreeBSD! Thanks very much! Mr. Stevan Tiefert Is there a way to disable DMA for a single hard drive, instead of all IDE devices? How about this: /sbin/atacontrol mode 0 PIO4 XXX? (if you want UDMA disabled on the master at channel 0). - Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hello Mark, you did not understood what I wanted. I needed a suggestion how to install FreeBSD without UDMA-support. Your suggestion is only useful if the system is running, but that was not the case! Thanks to Nathan! Bye Stevan Tiefert -- deltree /y c:\windows My suggestion to solve all your problems! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to disable UDMA for HDD?
Hello, when I try to install FreeBSD 5.2.1 on my computer with HDD on ata0-master and CD-ROM on ata0-slave I got five interessting messages during the boot-process: ... ad0: 4124MB SAMSUNG VA34323A [8938/15/63] at ata0-master UDMA33 ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=8446347 ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=0 ad0: WARNING - READ_DMA interrupt was seen but timeout fired LBA=8446347 ad0: WARNING - READ_DMA interrupt was seen but taskqueue stalled LBA=8446347 then the computer stops and he resists in this state till now... OpenBSD downgrades this DMA-thing automaticly and the CD-ROM seems not supporting UDMA and I assume to set at bootphase 3 a device.hint but I don't know which one? With regards Mr. Stevan Tiefert -- deltree /y c:\windows My suggestion to solve all your problems! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to disable UDMA for HDD?
On Mon, Aug 09, 2004 at 11:10:40AM +0200, Stevan Tiefert wrote: Hello, when I try to install FreeBSD 5.2.1 on my computer with HDD on ata0-master and CD-ROM on ata0-slave I got five interessting messages during the boot-process: ... ad0: 4124MB SAMSUNG VA34323A [8938/15/63] at ata0-master UDMA33 ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=8446347 ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=0 ad0: WARNING - READ_DMA interrupt was seen but timeout fired LBA=8446347 ad0: WARNING - READ_DMA interrupt was seen but taskqueue stalled LBA=8446347 then the computer stops and he resists in this state till now... OpenBSD downgrades this DMA-thing automaticly and the CD-ROM seems not supporting UDMA and I assume to set at bootphase 3 a device.hint but I don't know which one? With regards Mr. Stevan Tiefert Here are the two pertinent sysctl variables for your ATA hard disk and CDROM, respectively: hw.ata.ata_dma: 1 hw.ata.atapi_dma: 0 These variables are read only once the kernel has been booted, so if you want to try setting them manually you'll have to put them into /boot/loader.conf as something like: hw.ata.ata_dma=0 Nathan -- PGP Public Key: pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD8527E49 pgpYhBXqPCvyD.pgp Description: PGP signature
Re: Problems with UDMA harddisks
On Fri, 2 Jul 2004, Jud wrote: On Fri, 2 Jul 2004 08:28:12 +0200 (CEST), Peter Ulrich Kruppa [EMAIL PROTECTED] said: Hi! I hope somebody on this list has another good idea, I haven't thought of yet: I have a machine that came with two Excel Stor 40 GB (Ganymede) UDMA/100 harddisks. To install FreeBSD 4.10 I had to disable UDMA in the BIOS, otherwise they wouldn't have booted (some complaint about ata0). Of course I wish to get UDMA working, since this is said to improve perfomance significantly. I checked if the UDMA cable is plugged into the correct places for mainboard, master and slave - this is o.k. . Are there any other things (bios settings, kernel modules, magic chants,...) I could try? I've been using DragonFly so I am not absolutely certain 4.10 still uses /boot/loader.conf, but if it does, then inserting the following line in that file may help: hw.ata.ata_dma=1 No, it still doesn't work. But thanks anyway. Uli. Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] +---+ |Peter Ulrich Kruppa| | Wuppertal | | Germany | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with UDMA harddisks
Hi! I hope somebody on this list has another good idea, I haven't thought of yet: I have a machine that came with two Excel Stor 40 GB (Ganymede) UDMA/100 harddisks. To install FreeBSD 4.10 I had to disable UDMA in the BIOS, otherwise they wouldn't have booted (some complaint about ata0). Of course I wish to get UDMA working, since this is said to improve perfomance significantly. I checked if the UDMA cable is plugged into the correct places for mainboard, master and slave - this is o.k. . Are there any other things (bios settings, kernel modules, magic chants,...) I could try? Thanks, Uli. +---+ |Peter Ulrich Kruppa| | Wuppertal | | Germany | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with UDMA harddisks
On Fri, 2 Jul 2004 08:28:12 +0200 (CEST), Peter Ulrich Kruppa [EMAIL PROTECTED] said: Hi! I hope somebody on this list has another good idea, I haven't thought of yet: I have a machine that came with two Excel Stor 40 GB (Ganymede) UDMA/100 harddisks. To install FreeBSD 4.10 I had to disable UDMA in the BIOS, otherwise they wouldn't have booted (some complaint about ata0). Of course I wish to get UDMA working, since this is said to improve perfomance significantly. I checked if the UDMA cable is plugged into the correct places for mainboard, master and slave - this is o.k. . Are there any other things (bios settings, kernel modules, magic chants,...) I could try? I've been using DragonFly so I am not absolutely certain 4.10 still uses /boot/loader.conf, but if it does, then inserting the following line in that file may help: hw.ata.ata_dma=1 Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
WRITE_DMA UDMA ICRC errors with my ata drive(s)/controller
Greetings. I recently upgraded my server from 4.9-RELEASE to 5.2.1-RELEASE and immediately started to get the following error logged whenever there is significant disk activity: ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=137690696 ad0: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=137690696 [there are slight, insignificant variations, of course] Anyhow, the first thing I did was to install and run smartctl (part of the smartmontools package) since both my drives are S.M.A.R.T. enabled. Aside from having the same write dma errors in their internal logs, the drives appear to be fine (all values are well above their threshold). Also, all disk activity that sparked said errors always succeeded as all copied files were uncorrupted. So, I did a little searching online and found that besides the misc. person having this problem and being told to check their drives or cables or ide controllers, I came across the following two threads: http://groups.google.com/groups?hl=enlr=ie=UTF-8threadm=20040409042611.GA68595_binary.net%40ns.sol.netrnum=1prev=/groups%3Fq%3Dfreebsd%2Bwrite_dma%2Budma%2Bicrc%2Berror%26hl%3Den%26lr%3D%26ie%3DUTF-8%26selm%3D20040409042611.GA68595_binary.net%2540ns.sol.net%26rnum%3D1 http://groups.google.com/groups?hl=enlr=ie=UTF-8threadm=20040414024308.GA6468%40binary.netrnum=4prev=/groups%3Fq%3Dfreebsd%2Bwrite_dma%2Budma%2Bicrc%2Berror%26hl%3Den%26lr%3D%26ie%3DUTF-8%26selm%3D20040414024308.GA6468%2540binary.net%26rnum%3D4 The first thing I noted was that I am also using a board with the VIA 8235: [dmesg] atapci0: VIA 8235 UDMA133 controller port 0xdc00-0xdc0f at device 17.1 on pci0 And I also have fairly large drives, two Maxtor 120GB drives: [dmesg] ad0: 117246MB Maxtor 6Y120P0 [238216/16/63] at ata0-master UDMA133 acd0: CDRW LITE-ON LTR-48246S at ata0-slave BIOSPIO ad2: 117246MB Maxtor 6Y120P0 [238216/16/63] at ata1-master UDMA133 Also of note is that these two drives worked just fine in UDMA133 mode in my 4.9-RELEASE system. Due to this and the newness of the two drives, the motherboard, and the ATA133 round cables as well as having everything check out in my S.M.A.R.T. test, and the fact that despite these errors, the disk I/O transactions always seem to succeed (as far as I've been able to test) and the system otherwise functions normally even with both drives in UDMA133 mode, I wonder if there is possibly either some hardware bug with the VIA 8235 or some incompatibility between the ata driver in 5.2.1-RELEASE and the VIA 8235 or if someone, after reading my message and the two threads I linked to, has yet another idea? P.S. - Just as was described in the threads above, if I also put my problem drive in PIO mode, I get no more UDMA ICRC errors. P.P.S. - While, for reasons I've describe above, I suspect my hardware is not at fault, I know that I certainly can't guarantee that this is the case since I don't have the resources (a.k.a. extra hardware and time) to swap parts around to verify, for sure, it isn't at fault. -- Kendall Gifford WEB: http://kendall.jedis.com/ EMAIL: REPLY TO LIST ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Harddisk UDMA ICRC error... from kernel at bootup. What does it mean?
Hi, A friend of mine switched from Windows XP to FreeBSD, because I garanteed that FreeBSD would be faster. I also want to optimize performance as much as possible. I'm therefore worried about the following messages from the kernel at bootup: [...snip...] ad0: 16448MB WDC WD172AA [33420/16/63] at ata0-master UDMA66 ad1: 76319MB WDC WD800JB-00CRA1 [155061/16/63] at ata0-slave UDMA66 acd0: CD-RW HL-DT-ST RW/DVD GCC-4320B at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a ad1s5c: UDMA ICRC error reading fsbn 93787664 of 46885768-46885895 (ad1s5 bn 93787664; cn 5838 tn 3 sn 5) retrying ad1s5c: UDMA ICRC error reading fsbn 93787664 of 46885768-46885895 (ad1s5 bn 93787664; cn 5838 tn 3 sn 5) retrying ad1s5c: UDMA ICRC error reading fsbn 93787664 of 46885768-46885895 (ad1s5 bn 93787664; cn 5838 tn 3 sn 5) retrying ad1s5c: UDMA ICRC error reading fsbn 93787664 of 46885768-46885895 (ad1s5 bn 93787664; cn 5838 tn 3 sn 5) falling back to PIO mode --- Both harddisks are on the same IDE 40-pin cable as master and slave. ad0 is the FreeBSD formatted harddisk; one slice and several FreeBSD partitions. ad1 is from a former Windows XP installation, with two partitions: ad1s5 (ntfs) and ad1s6 (msdos). I don't understand much of the lines above. The last line says it falls back to PIO mode due to errors with ad1s5c. What does that mean? Will it use the slow 16.6 MB/s data exchange from disk to host? Does this then also imply that both disks use PIO/slow data exchange speed? (remember: both disks are on the same cable to the motherboard). What can I do to get things better and faster? And also: is this UDMA ICRC error because it's a Windows/DOS partition? Would formatting to FreeBSD filesystem solve the problem? Thanks, Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Harddisk UDMA ICRC error... from kernel at bootup. What does it mean?
Rob [EMAIL PROTECTED] wrote: Hi, A friend of mine switched from Windows XP to FreeBSD, because I garanteed that FreeBSD would be faster. I also want to optimize performance as much as possible. I'm therefore worried about the following messages from the kernel at bootup: [...snip...] ad0: 16448MB WDC WD172AA [33420/16/63] at ata0-master UDMA66 ad1: 76319MB WDC WD800JB-00CRA1 [155061/16/63] at ata0-slave UDMA66 acd0: CD-RW HL-DT-ST RW/DVD GCC-4320B at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a ad1s5c: UDMA ICRC error reading fsbn 93787664 of 46885768-46885895 (ad1s5 bn 93787664; cn 5838 tn 3 sn 5) retrying ad1s5c: UDMA ICRC error reading fsbn 93787664 of 46885768-46885895 (ad1s5 bn 93787664; cn 5838 tn 3 sn 5) retrying ad1s5c: UDMA ICRC error reading fsbn 93787664 of 46885768-46885895 (ad1s5 bn 93787664; cn 5838 tn 3 sn 5) retrying ad1s5c: UDMA ICRC error reading fsbn 93787664 of 46885768-46885895 (ad1s5 bn 93787664; cn 5838 tn 3 sn 5) falling back to PIO mode --- Both harddisks are on the same IDE 40-pin cable as master and slave. ad0 is the FreeBSD formatted harddisk; one slice and several FreeBSD partitions. ad1 is from a former Windows XP installation, with two partitions: ad1s5 (ntfs) and ad1s6 (msdos). I don't understand much of the lines above. Super-simplified: it's telling you it gets checksum erros when it tries to talk to the drives at ATA66 speed, so it slows down and is then successful. The last line says it falls back to PIO mode due to errors with ad1s5c. What does that mean? Will it use the slow 16.6 MB/s data exchange from disk to host? Yes. Windows is probably already running at this speed, but it just doesn't bother to inform you. Does this then also imply that both disks use PIO/slow data exchange speed? (remember: both disks are on the same cable to the motherboard). Yes. What can I do to get things better and faster? Get an 80 conductor cable (probably). And also: is this UDMA ICRC error because it's a Windows/DOS partition? Would formatting to FreeBSD filesystem solve the problem? No, it's more likely because of the 40 pin cable. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Harddisk UDMA ICRC error... from kernel at bootup. What does it mean?
- Original Message - From: Bill Moran [EMAIL PROTECTED] To: Rob [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, June 16, 2004 12:26 PM Subject: Re: Harddisk UDMA ICRC error... from kernel at bootup. What does it mean? | Rob [EMAIL PROTECTED] wrote: | Hi, | | A friend of mine switched from Windows XP to FreeBSD, because I garanteed that FreeBSD | would be faster. I also want to optimize performance as much as possible. I'm therefore | worried about the following messages from the kernel at bootup: | | [...snip...] | ad0: 16448MB WDC WD172AA [33420/16/63] at ata0-master UDMA66 | ad1: 76319MB WDC WD800JB-00CRA1 [155061/16/63] at ata0-slave UDMA66 | acd0: CD-RW HL-DT-ST RW/DVD GCC-4320B at ata1-master PIO4 | Mounting root from ufs:/dev/ad0s1a | ad1s5c: UDMA ICRC error reading fsbn 93787664 of 46885768-46885895 (ad1s5 bn 93787664; cn 5838 tn 3 sn 5) retrying | ad1s5c: UDMA ICRC error reading fsbn 93787664 of 46885768-46885895 (ad1s5 bn 93787664; cn 5838 tn 3 sn 5) retrying | ad1s5c: UDMA ICRC error reading fsbn 93787664 of 46885768-46885895 (ad1s5 bn 93787664; cn 5838 tn 3 sn 5) retrying | ad1s5c: UDMA ICRC error reading fsbn 93787664 of 46885768-46885895 (ad1s5 bn 93787664; cn 5838 tn 3 sn 5) falling back to PIO mode | | --- | | Both harddisks are on the same IDE 40-pin cable as master and slave. | ad0 is the FreeBSD formatted harddisk; one slice and several FreeBSD partitions. | ad1 is from a former Windows XP installation, with two partitions: ad1s5 (ntfs) and ad1s6 (msdos). | | I don't understand much of the lines above. | | Super-simplified: it's telling you it gets checksum erros when it tries to | talk to the drives at ATA66 speed, so it slows down and is then successful. | | The last line says it falls back to PIO mode due to errors with ad1s5c. | What does that mean? Will it use the slow 16.6 MB/s data exchange from disk to host? | | Yes. Windows is probably already running at this speed, but it just doesn't | bother to inform you. | | Does this then also imply that both disks use PIO/slow data exchange speed? | (remember: both disks are on the same cable to the motherboard). | | Yes. | | What can I do to get things better and faster? | | Get an 80 conductor cable (probably). Shouldn't they be able to use ATA33 on a 40 pin cable atleast? Try atacontrol? | | And also: is this UDMA ICRC error because it's a Windows/DOS partition? | Would formatting to FreeBSD filesystem solve the problem? | | No, it's more likely because of the 40 pin cable. | | -- | Bill Moran | Potential Technologies | http://www.potentialtech.com | ___ | [EMAIL PROTECTED] mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-questions | To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
HDD-UDMA-100 support at setup
Hello, I want to install a Freebsd 4.9 System with a 40GB UDMA-100 HDD. After the CD has booted i got an error while the IDE-Bus is scanning. Has anybody solved this Problem? On other Systems it is possible to solve this problems with deactivating this function in the bios, but this bios hasn't such a switchbutton. Any idea? Volker ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
UDMA ICRC error
i keep getting this in my securty run mailings and in my logs what dose this mean ? my HD going bad or what ... ad0s1b: UDMA ICRC error writing fsbn 1418815 of 197376-197503 (ad0s1 bn 1418815; cn 88 tn 80 sn 55) retrying ohh ond its different every time aswell vampextream# uname -a FreeBSD vampextream.com 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 and thx inadvance for any help on this .. David D. _ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA ICRC error
I got this on several hds. was told once it was cuz the hd was like ata 100 and the cable or controller didnt't match . however sometime later (months) the drives died. tyring to redo a machine that had these errors that the drive died in. MD - Original Message - From: white vamp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, May 29, 2004 3:53 PM Subject: UDMA ICRC error i keep getting this in my securty run mailings and in my logs what dose this mean ? my HD going bad or what ... ad0s1b: UDMA ICRC error writing fsbn 1418815 of 197376-197503 (ad0s1 bn 1418815; cn 88 tn 80 sn 55) retrying ohh ond its different every time aswell vampextream# uname -a FreeBSD vampextream.com 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 and thx inadvance for any help on this .. David D. _ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA ICRC error
I occasionally get those errors as well. When I'd boot, the drive would try and do ATA-100, fail, and revert to PIO-4. (I blame the cheap PCI IDE card, it came free with a hard drive, and I have to use it, since the nforce2 chipset on my mobo won't see anything but primary master and secondary master under FBSD.) I can make it work by setting the drive to ATA-33, though. (The command, for me, is # atacontrol mode 2 UDMA33 xxx but check the manpage to see what options you should use.) I've been using the hard drive for about 7 months now, and it works fine. I don't put anything I care about much on it, though. -- Marshall Pierce Harvey Mudd College '06 [EMAIL PROTECTED] On May 29, 2004, at 1:13 PM, SWIT wrote: I got this on several hds. was told once it was cuz the hd was like ata 100 and the cable or controller didnt't match . however sometime later (months) the drives died. tyring to redo a machine that had these errors that the drive died in. MD - Original Message - From: white vamp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, May 29, 2004 3:53 PM Subject: UDMA ICRC error i keep getting this in my securty run mailings and in my logs what dose this mean ? my HD going bad or what ... ad0s1b: UDMA ICRC error writing fsbn 1418815 of 197376-197503 (ad0s1 bn 1418815; cn 88 tn 80 sn 55) retrying ohh ond its different every time aswell vampextream# uname -a FreeBSD vampextream.com 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 and thx inadvance for any help on this .. David D. _ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
UDMA error
I run FreeBSD 4.9 and keep getting this message in my dmesg both the cable and the drive are cable of UDMA 100 at least and the board is a newer Intel 865 chip set. Do i have to configure something in my kernel or what?? ad0: DMA limited to UDMA33, non-ATA66 cable or device ad0: 38204MB SAMSUNG SP0411N [77622/16/63] at ata0-master UDMA33 acd0: CD-RW HL-DT-ST GCE-8525B at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA error
RYAN vAN GINNEKEN wrote: I run FreeBSD 4.9 and keep getting this message in my dmesg both the cable and the drive are cable of UDMA 100 at least and the board is a newer Intel 865 chip set. Do i have to configure something in my kernel or what?? ad0: DMA limited to UDMA33, non-ATA66 cable or device ad0: 38204MB SAMSUNG SP0411N [77622/16/63] at ata0-master UDMA33 acd0: CD-RW HL-DT-ST GCE-8525B at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a We were talking about this very thing not too long ago on this list. Some have claimed this can happen if you: a] Plug the cable in backwards - ie., the end with the single plug should go into the motherboard and the end that has the two plugs closer together should go into the drives. b] Plug the wrong one of the two that are closer together into the driver. So I'd say try pulling out the cable and plugging it back in in a different way. Another thing to be sure of is that you have the UDMA 100 cable; ie, one end should have a blue connector and that end should go into the motherboard. -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) Daemon Dancing in the Dark, a FreeBSD weblog: http://freebsd.amazingdev.com/blog/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-RELEASE - UDMA ICRC error - falling back to PIO mode
Rajamani, Rajarajan (Rajarajan) [EMAIL PROTECTED] writes: I am running 5.1-RELEASE on a DELL GX150 with 512MB RAM on which I installed a new WD-1600JB IDE along with the promise UDMA100 controller which came along with the drive. The drive can be accessed but the access speed is very slow and I noticed that dmesg shows the following ad4: UDMA ICRC error cmd=read fsbn 0 of 0-3 retrying This repeats and is followed by ad4: UDMA ICRC error cmd=read fsbn 0 of 0-3 falling back to PIO mode I have changed the PCI slot on which the card is seated, changed cables and even hooked the drive directly to the mother board but the problem persists. The disc+controller however works ok on a wintel machine. Could it be some type of hard disc error ? Possible, but not terribly likely. [Unless it's actually running in PIO mode on Windows also.] Does the same occur on FreeBSD 5.2 or 4.9? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5.1-RELEASE - UDMA ICRC error - falling back to PIO mode
I am running 5.1-RELEASE on a DELL GX150 with 512MB RAM on which I installed a new WD-1600JB IDE along with the promise UDMA100 controller which came along with the drive. The drive can be accessed but the access speed is very slow and I noticed that dmesg shows the following ad4: UDMA ICRC error cmd=read fsbn 0 of 0-3 retrying This repeats and is followed by ad4: UDMA ICRC error cmd=read fsbn 0 of 0-3 falling back to PIO mode I have changed the PCI slot on which the card is seated, changed cables and even hooked the drive directly to the mother board but the problem persists. The disc+controller however works ok on a wintel machine. Could it be some type of hard disc error ? Can anyone help, Thanks, Rajarajan --- BEGIN dmesg output Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-RELEASE #0: Thu Jun 5 02:55:42 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc06d4000. Preloaded elf module /boot/kernel/acpi.ko at 0xc06d426c. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 996769775 Hz CPU: Intel Pentium III (996.77-MHz 686-class CPU) Origin = GenuineIntel Id = 0x68a Stepping = 10 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 534802432 (510 MB) avail memory = 512077824 (488 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: DELL GX150 on motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00fbb40 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82815 (i815 GMCH) SVGA controller mem 0xff00-0xff07,0xf800-0xfbff irq 9 at device 2.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 30.0 on pci0 pci1: ACPI PCI bus on pcib1 atapci0: Promise PDC20268 UDMA100 controller port 0xecc0-0xeccf,0xecd8-0xecdb,0xece0-0xece7,0xecf0-0xecf3,0xecf8-0xecff mem 0xfdffc000-0xfdff irq 11 at device 9.0 on pci1 ata2: at 0xecf8 on atapci0 ata3: at 0xece0 on atapci0 xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xec00-0xec7f mem 0xfdffbc00-0xfdffbc7f irq 11 at device 12.0 on pci1 xl0: Ethernet address: 00:b0:d0:94:f2:67 miibus0: MII bus on xl0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci1: Intel ICH2 UDMA100 controller port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xff80-0xff9f irq 11 at device 31.2 on pci0 usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: serial bus, SMBus at device 31.3 (no driver attached) uhci1: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0xff60-0xff7f irq 11 at device 31.4 on pci0 usb1: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: multimedia, audio at device 31.5 (no driver attached) fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77f,0x378-0x37f irq 7 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 orm0: Option ROMs at iomem 0xca000-0xcbfff,0xc-0xc9fff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec ad0: 19073MB Maxtor 5T020H2 [38752/16/63] at ata0-master UDMA100 ad4: 152627MB WDC WD1600JB-00DUA3 [310101/16/63] at ata2-master UDMA100 ad4: READ command timeout tag=0 serv=0 - resetting ata2: resetting devices .. done ad4: UDMA ICRC error cmd=read fsbn 0 of 0-3 retrying ad4: UDMA ICRC error cmd=read fsbn 0 of 0-3 retrying ad4
Re: UDMA ICRC Error FreeBSD 4.9, falling back to PIO mode
I have the same messages in my `dmesg'. It's caused by your IDE cable, replace it. HTH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA ICRC Error FreeBSD 4.9, falling back to PIO mode
treeml wrote: I get a following error on boot ad1s1a: UDMA ICRC error reading fsbn 511 of 244-255 (ad1s1 bn 511; cn 0 tn 8sn 7) retrying ad1s1a: UDMA ICRC error reading fsbn 511 of 244-255 (ad1s1 bn 511; cn 0 tn 8sn 7) retrying ad1s1a: UDMA ICRC error reading fsbn 511 of 244-255 (ad1s1 bn 511; cn 0 tn 8sn 7) retrying ad1s1a: UDMA ICRC error reading fsbn 511 of 244-255 (ad1s1 bn 511; cn 0 tn 8sn 7) retrying falling back to PIO mode Sounds like your drive was physically damaged. This recently happend to a mail server of ours, and I had to reinstall the whole thing. (After long fsck sessions, only a small part of the file systems was accessible, and there was nothing of value that could be salvaged) Sorry for the Bad News (tm) :( Gilad. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
UDMA ICRC Error FreeBSD 4.9, falling back to PIO mode
I get a following error on boot ad1s1a: UDMA ICRC error reading fsbn 511 of 244-255 (ad1s1 bn 511; cn 0 tn 8sn 7) retrying ad1s1a: UDMA ICRC error reading fsbn 511 of 244-255 (ad1s1 bn 511; cn 0 tn 8sn 7) retrying ad1s1a: UDMA ICRC error reading fsbn 511 of 244-255 (ad1s1 bn 511; cn 0 tn 8sn 7) retrying ad1s1a: UDMA ICRC error reading fsbn 511 of 244-255 (ad1s1 bn 511; cn 0 tn 8sn 7) retrying falling back to PIO mode BTW, this all happened after a power failure. At first I was prompted to go into the single user mode, but then after second reboot that doesn't even happen anymore. Just the error message. I switch a IDE cable to the hard drive, and now, I don't even get the error message anymore. The system stuck at Mounting root from ufs:/dev/ad1s1a And it stuck there. I can reboot by ctr+alt+del I boot the system using the FreeBSD Fixit disk. However, I can't seem to see all the hard drive partitions in /dev. Following is my partition setup. FilesystemSize Used Avail Capacity Mounted on /dev/ad1s1a 252M46M 186M20%/ /dev/ad1s2e20G 9.0M18G 0%/backup /dev/ad1s2f20G 130M18G 1%/data /dev/ad1s2g32G 8.9G21G30%/hd2 /dev/ad1s1f 252M18K 232M 0%/tmp /dev/ad1s1g 9.8G 1.6G 7.5G17%/usr /dev/ad1s1d47G10G33G24%/usr/home /dev/ad1s1h20G 190M18G 1%/usr/local /dev/ad1s1e 1008M49M 878M 5%/var /dev/ad0s1e /space I only see /dev/ad0s1 /dev/ad1s1 What happened to /dev/ad1s1a /dev/ad1s2f /dev/ad0s1e I ran fsck Fixit# fsck /dev/ad1s1 and it seems to be fine Fixit# mount /dev/ad1s1 /mnt That seems to be the root, but I still can't find /dev/ad1s2f or any other /dev/ad1s2* partitions. Any idea? Tree ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
UDMA ICRC Error
-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default ad0: 9671MB WDC AC310100B [19650/16/63] at ata0-master UDMA33 ad6: 194481MB Maxtor 6Y200P0 [395136/16/63] at ata3-master UDMA100 ad7: 194481MB Maxtor 6Y200P0 [395136/16/63] at ata3-slave UDMA100 ad12: 114473MB WDC WD1200JB-00DUA0 [232581/16/63] at ata6-master UDMA100 ad14: UDMA ICRC error reading fsbn 234441585 of 0-3 (ad14 bn 234441585; cn 232580 tn 15 sn 0) retrying ad14: UDMA ICRC error reading fsbn 234441585 of 0-3 (ad14 bn 234441585; cn 232580 tn 15 sn 0) retrying ad14: UDMA ICRC error reading fsbn 234441585 of 0-3 (ad14 bn 234441585; cn 232580 tn 15 sn 0) retrying ad14: UDMA ICRC error reading fsbn 234441585 of 0-3 (ad14 bn 234441585; cn 232580 tn 15 sn 0) falling back to PIO mode ad14: 114473MB WDC WD1200JB-00DUA0 [232581/16/63] at ata7-master PIO4 ad15: UDMA ICRC error reading fsbn 234441585 of 0-3 (ad15 bn 234441585; cn 232580 tn 15 sn 0) retrying ad15: UDMA ICRC error reading fsbn 234441585 of 0-3 (ad15 bn 234441585; cn 232580 tn 15 sn 0) retrying ad15: UDMA ICRC error reading fsbn 234441585 of 0-3 (ad15 bn 234441585; cn 232580 tn 15 sn 0) retrying ad15: UDMA ICRC error reading fsbn 234441585 of 0-3 (ad15 bn 234441585; cn 232580 tn 15 sn 0) falling back to PIO mode ad15: 114473MB WDC WD1200JB-00DUA0 [232581/16/63] at ata7-slave PIO4 ad16: 95396MB WDC WD1000BB-60CCB0 [193821/16/63] at ata8-master UDMA66 ad17: 95396MB WDC WD1000BB-32CCB0 [193821/16/63] at ata8-slave UDMA66 ad18: 95396MB WDC WD1000BB-60CCB0 [193821/16/63] at ata9-master UDMA66 Mounting root from ufs:/dev/ad0s1a ad12: UDMA ICRC error reading fsbn 0 (ad12 bn 0; cn 0 tn 0 sn 0) retrying ad12: UDMA ICRC error reading fsbn 0 (ad12 bn 0; cn 0 tn 0 sn 0) retrying ad12: UDMA ICRC error reading fsbn 0 (ad12 bn 0; cn 0 tn 0 sn 0) retrying ad12: UDMA ICRC error reading fsbn 0 (ad12 bn 0; cn 0 tn 0 sn 0) falling back to PIO mode ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA ICRC Error
At 17:04 03.11.2003 +0100, Tomas Nyman wrote: Hi! I have a serious problem with 3 of my harddrives, the fail to enter DMA mode on boot, I can force them into udma5 using atacontrol but after a few reads I will get the same error and they will fall back into PIO4 mode. The 3 disks are in a Vinum array consisting of 6 drives, the other 3 are working fine. Sometimes when I try to boot I get this error: Fatal trap 12: page fault while in kernel mode fault code = supervisor read, page not present ... DMESG: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.9-RELEASE #1: Thu Oct 30 19:09:30 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SOPP . atapci1: Promise TX2 ATA100 controller port 0xa400-0xa40f,0xa000-0xa003,0x9c00-0x9c07,0x9800-0x9803,0x9400-0x9407 mem 0xdb00-0xdb003fff irq 7 at device 11.0 on pci0 ata2: at 0x9400 on atapci1 ata3: at 0x9c00 on atapci1 ad6: 194481MB Maxtor 6Y200P0 [395136/16/63] at ata3-master UDMA100 ad7: 194481MB Maxtor 6Y200P0 [395136/16/63] at ata3-slave UDMA100 ... Maybe this is related with http://www.freebsd.org/cgi/query-pr.cgi?pr=35461. Although I answered that the problem still exists the PR gets closed. Probably because others were not able to reproduce this or were not affected. Another disk related trap 12 problem is: http://www.freebsd.org/cgi/query-pr.cgi?pr=58391 Can you reproduce this? Does the problem still occur if you remove one of the two Promise controllers? Probably you should reopen the PR 35461. Sorry, no real answers... Alexander ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA
I have seen these errors before. It has to do with Electro Magnetic Interference (noise). Try using different ribbons (ATA33) and see if the errors disappear. - aW ad0: UDMA ICRC error cmd=read fsbn 61731938 retrying ad0: UDMA ICRC error cmd=read fsbn 61731938 retrying ad0: UDMA ICRC error cmd=read fsbn 61731938 retrying ad0: UDMA ICRC error cmd=read fsbn 61731938 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA
On Mon, Mar 31, 2003 at 09:39:40AM +0930, Wilkinson,Alex wrote: I have seen these errors before. It has to do with Electro Magnetic Interference (noise). Try using different ribbons (ATA33) and see if the errors disappear. - aW It can also have to do with dying drives and/or controllers, as well as bad cables. Josh Paetzel ad0: UDMA ICRC error cmd=read fsbn 61731938 retrying ad0: UDMA ICRC error cmd=read fsbn 61731938 retrying ad0: UDMA ICRC error cmd=read fsbn 61731938 retrying ad0: UDMA ICRC error cmd=read fsbn 61731938 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
UDMA
From dmesg I get the following: ad0: UDMA ICRC error cmd=read fsbn 61731938 retrying ad0: UDMA ICRC error cmd=read fsbn 61731938 retrying ad0: UDMA ICRC error cmd=read fsbn 61731938 retrying ad0: UDMA ICRC error cmd=read fsbn 61731938 I found in the troubleshooting faq information about this, but I have checked everything it says and i still get this during boot. The cables are fine, the drive is capable etc. I want it to use DMA and not PIO, what am I doing wrong? Anthony Carter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UDMA
What is the BIOS set to use? At 01:49 PM 3/28/2003 +0100, you wrote: From dmesg I get the following: ad0: UDMA ICRC error cmd=read fsbn 61731938 retrying ad0: UDMA ICRC error cmd=read fsbn 61731938 retrying ad0: UDMA ICRC error cmd=read fsbn 61731938 retrying ad0: UDMA ICRC error cmd=read fsbn 61731938 I found in the troubleshooting faq information about this, but I have checked everything it says and i still get this during boot. The cables are fine, the drive is capable etc. I want it to use DMA and not PIO, what am I doing wrong? Anthony Carter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Peter Elsner [EMAIL PROTECTED] Vice President Of Customer Service (And System Administrator) 1835 S. Carrier Parkway Grand Prairie, Texas 75051 (972) 263-2080 - Voice (972) 263-2082 - Fax (972) 489-4838 - Cell Phone (425) 988-8061 - eFax I worry about my child and the Internet all the time, even though she's too young to have logged on yet. Here's what I worry about. I worry that 10 or 15 years from now, she will come to me and say Daddy, where were you when they took freedom of the press away from the Internet? -- Mike Godwin Unix IS user friendly... It's just selective about who its friends are. System Administration - It's a dirty job, but somebody said I had to do it. If you receive something that says 'Send this to everyone you know, pretend you don't know me. Standard $500/message proofreading fee applies for UCE. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
UDMA ICRC error reading fsbn (Possible Fix)
ISSUE: UDMA ICRC error reading fsbn in dmesg and /var/log/messages $ dmesg ... FreeBSD 4.7-STABLE #0: Tue Feb 20 22:06:43 EST 2003 ... ICRC error reading fsbn 257696511 of 128848224-128848479 (ad1s1 bn 257696511; cn 16040 tn 220 sn 51) retrying ad1s1e: UDMA ICRC error reading fsbn 6803007 of 3401472-3401727 (ad1s1 bn 6803007; cn 423 tn 119 sn 15) retrying ... After adding a Seagate 80GB Barracuda IDE (ad1s1e) hard drive recently I began to notice the above errors in dmesg and /var/log/messages. After reading posts and researching I did some testing with transferring files using both cp and mv on: /dev/ad1s1e results were sporadic at best, sometimes producing the errors and sometimes not. Believing this to be a cabling issue, I replaced the new IDE 80wire/40pin another 80wire/40pin IDE cable only to receive even more errors of this type. After shutting down, reopening the box, and staring blank-facedly at the motherboard and cables I remembered what an old hardware guru suggested once when adding additional hard drives, Run the IDE cable to from the controller to the interim connector (master drive) to the end connector (slave drive). i.e., (diagram 1) |---IDE 80 WIRE CABLE--| ::---::-:: controller interim connector end connector MOTHERBOARDMASTER DRIVE SLAVE DRIVE (My Seagate 80GB) I figured it couldn't be that easy. I tried to find some info on this using google, of course there were differing opinions on the subject. One argument suggests that the drives will fight for bandwidth, so the logic suggested here seems correct. Before this, I had the drives reversed and in the order of: (diagram 2) |-ide cable--| controller---slave---master (Seagate 80G) repeating this with other cables gave same type of error messages. Following diagram 1 above I used the original IDE cable, this seems to have solved the problem. 5 days later still no error messages. So it seems this is a possible fix to this issue. Outside my bad diagrams, I figured this might just be worth a try to others having similar issues. All opinions and any additional information on this topic are welcome. Regards, Rob Clark To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
kernel: ad3s1e: UDMA ICRC error writing fsbn
just put a new drive in service as an Amanda dumpdisk, and I'm fetting console messages like this: kernel: ad3s1e: UDMA ICRC error writing fsbn Is the drive bad? Or the controler? -- They that would give up essential liberty for temporary safety deserve neither liberty nor safety. -- Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
UDMA on Via 686B
Found some references to a Via south bridge causing ICRC errors and dropping UDMA-PIO a while back. Is there a fix for this issue ? I'm still seeing it as of 4.7-Release Generic kernel, on known good drives, cables, and mobos. -- Josh Litherland ([EMAIL PROTECTED]) public key: temp123.org/fauxpas.pgp fingerprint: CFF3 EB2B 4451 DC3C A053 1E07 06B4 C3FC 893D 9228 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
UDMA ICRC error's
What is the best way to resolve these? ad0s1e: UDMA ICRC error reading fsbn 897759 of 144-159 (ad0s1 bn 897759; cn 55 tn 225 sn 9) retrying ad0s1a: UDMA ICRC error reading fsbn 45439 of 22688-22719 (ad0s1 bn 45439; cn 2 tn 211 sn 16) retrying ad0s1a: UDMA ICRC error reading fsbn 39391 of 19664-19695 (ad0s1 bn 39391; cn 2 tn 115 sn 16) retrying ad0s1a: UDMA ICRC error reading fsbn 39391 of 19664-19695 (ad0s1 bn 39391; cn 2 tn 115 sn 16) retrying I've tried bringing the system down to single user mode, umounting the filesystems and running fsck but it never finds anything wrong. Next I'm going to switch out the ide cable, and i'm hoping that is the problem as I'd prefer not to have my drive go out. What else can I do besides running fsck? Are there any other utilites to check the disk, maybe something from the ports tree? Thanks, Ed To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: UDMA ICRC error's
On Tue, Nov 12, 2002 at 01:23:57PM -0600, Ed McGough wrote: What is the best way to resolve these? ad0s1e: UDMA ICRC error reading fsbn 897759 of 144-159 (ad0s1 bn 897759; cn 55 tn 225 sn 9) retrying ad0s1a: UDMA ICRC error reading fsbn 45439 of 22688-22719 (ad0s1 bn 45439; cn 2 tn 211 sn 16) retrying ad0s1a: UDMA ICRC error reading fsbn 39391 of 19664-19695 (ad0s1 bn 39391; cn 2 tn 115 sn 16) retrying ad0s1a: UDMA ICRC error reading fsbn 39391 of 19664-19695 (ad0s1 bn 39391; cn 2 tn 115 sn 16) retrying What else can I do besides running fsck? Are there any other utilites to check the disk, maybe something from the ports tree? Most (all?) disk manafacturers have free diagnostic programs you can download from their websites. Take a look -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: UDMA ICRC error's
I already tried that...its a Maxtor drive and the utilites that they have only run on the Microsoft platform. The utility is too large to fit on a bootable ms-dos floppy and that won't work anyways as it says not to run it in 16 bit dos mode. -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd-questions;FreeBSD.ORG]On Behalf Of Cliff Sarginson Sent: Tuesday, November 12, 2002 2:02 PM To: [EMAIL PROTECTED] Subject: Re: UDMA ICRC error's On Tue, Nov 12, 2002 at 01:23:57PM -0600, Ed McGough wrote: What is the best way to resolve these? ad0s1e: UDMA ICRC error reading fsbn 897759 of 144-159 (ad0s1 bn 897759; cn 55 tn 225 sn 9) retrying ad0s1a: UDMA ICRC error reading fsbn 45439 of 22688-22719 (ad0s1 bn 45439; cn 2 tn 211 sn 16) retrying ad0s1a: UDMA ICRC error reading fsbn 39391 of 19664-19695 (ad0s1 bn 39391; cn 2 tn 115 sn 16) retrying ad0s1a: UDMA ICRC error reading fsbn 39391 of 19664-19695 (ad0s1 bn 39391; cn 2 tn 115 sn 16) retrying What else can I do besides running fsck? Are there any other utilites to check the disk, maybe something from the ports tree? Most (all?) disk manafacturers have free diagnostic programs you can download from their websites. Take a look -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: UDMA ICRC error's
In the last episode (Nov 12), Ed McGough said: What is the best way to resolve these? ad0s1e: UDMA ICRC error reading fsbn 897759 of 144-159 (ad0s1 bn 897759; cn 55 tn 225 sn 9) retrying ad0s1a: UDMA ICRC error reading fsbn 45439 of 22688-22719 (ad0s1 bn 45439; cn 2 tn 211 sn 16) retrying ad0s1a: UDMA ICRC error reading fsbn 39391 of 19664-19695 (ad0s1 bn 39391; cn 2 tn 115 sn 16) retrying ad0s1a: UDMA ICRC error reading fsbn 39391 of 19664-19695 (ad0s1 bn 39391; cn 2 tn 115 sn 16) retrying I've tried bringing the system down to single user mode, umounting the filesystems and running fsck but it never finds anything wrong. Next I'm going to switch out the ide cable, and i'm hoping that is the problem as I'd prefer not to have my drive go out. What else can I do besides running fsck? Are there any other utilites to check the disk, maybe something from the ports tree? An ICRC error means that the data was corrupted between the drive and the controller, and usually means cabling problems. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: UDMA ICRC error's
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What is the best way to resolve these? ad0s1e: UDMA ICRC error reading fsbn 897759 of 144-159 (ad0s1 bn 897759; cn 55 tn 225 sn 9) retrying ad0s1a: UDMA ICRC error reading fsbn 45439 of 22688-22719 (ad0s1 bn 45439; cn 2 tn 211 sn 16) retrying ad0s1a: UDMA ICRC error reading fsbn 39391 of 19664-19695 (ad0s1 bn 39391; cn 2 tn 115 sn 16) retrying ad0s1a: UDMA ICRC error reading fsbn 39391 of 19664-19695 (ad0s1 bn 39391; cn 2 tn 115 sn 16) retrying I've tried bringing the system down to single user mode, umounting the filesystems and running fsck but it never finds anything wrong. Next I'm going to switch out the ide cable, and i'm hoping that is the problem as I'd prefer not to have my drive go out. What else can I do besides running fsck? Are there any other utilites to check the disk, maybe something from the ports tree? I would suggest to run badsect (8) so u can mark the sector as bad, unreadable and thus u can continue accessing ur drive. Of course in the badsect you have to put sectors and not fsbn, and I dont know in your error message how u can find the sector number...(anyone can help on this?) perhaps the sectors for example are 144-159 ? But I dont know... Perhaps u should try to find out the 'fsdb' tool...but it will be a tricky thing.. Any help is appreciated... - --- We are being monitored..but there is a solution... Use PGP for signing and encrypting emails Download my public key at http://www.us.pgp.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE90XunGe/V3CxAyHoRArxBAKDIf32vQwNtyN6P20yLeslc/tHokwCgp9bb BN+Nr6Ezrq5ZDR+5Rgkdaec= =pf4d -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: UDMA limited to 33 - resolution
On 2002-10-23, Kevin Stevens scribbled: # However, it *is* correct that all devices on a UDMA channel must support # UDMA, so yes, the above is a problem. I don't recall if all devices must # also be the same UDMA speed (66/100/133) or not, bbelieve that is true # too. This is not a BSD issue, it is part of the UDMA spec. IIRC- The channel will run at the speed of the slowest device, meaning that if you have a drive that is capable of ATA/66 and a drive capable of ATA/33 on the same channel, then the channel will run at ATA/33. If you have a drive at ATA/100 and a drive that is only capable of PIO4, then the speed of the channel will be knocked down to either PIO4 or ATA/33 (the latter will only occur if the PIO4 drive is also capable to running at ATA/33, just without DMA). -- Linh Pham [EMAIL PROTECTED] Webmaster and FreeBSD Geekhttp://closedsrc.org closedsrc.org Every solution breeds new problems To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: UDMA limited to 33 - resolution
On 2002-10-23, lewiz scribbled: # Afaik, UDMA100 is only supported if there is just one device on the # channel. Feel free to shoot me if I am incorrect, which is quite # possible. Just double-check by asking Google or something - but I have # a gut feeling this may be the case. You should be able to run two devices at ATA/100 speeds on the same channel provided that you are using a cable within the ATA/100 specs (i.e.: 40-pin/80-conductor, the cable length is about 18 or less, etc.) and that both drives are capable and set to run at ATA/100. Of course, you run into the issue that both drives cannot send data across the channel at once... so you won't gain any performance by doing that. It's just the limitation of ATA (and the reason why Serial ATA only allows one device per host connector, and why higher-end ATA RAID controllers have so many channels and only allow one device per channel). HTH -- Linh Pham [EMAIL PROTECTED] Webmaster and FreeBSD Geekhttp://closedsrc.org closedsrc.org Every solution breeds new problems To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: UDMA limited to 33 - resolution
At 09:47 AM 10.25.2002 -0700, Linh Pham wrote: On 2002-10-23, Kevin Stevens scribbled: # However, it *is* correct that all devices on a UDMA channel must support # UDMA, so yes, the above is a problem. I don't recall if all devices must # also be the same UDMA speed (66/100/133) or not, bbelieve that is true # too. This is not a BSD issue, it is part of the UDMA spec. IIRC- The channel will run at the speed of the slowest device, meaning that if you have a drive that is capable of ATA/66 and a drive capable of ATA/33 on the same channel, then the channel will run at ATA/33. If you have a drive at ATA/100 and a drive that is only capable of PIO4, then the speed of the channel will be knocked down to either PIO4 or ATA/33 (the latter will only occur if the PIO4 drive is also capable to running at ATA/33, just without DMA). -- Linh Pham [EMAIL PROTECTED] Well, then what does the jumper settings on modern drives for Master with non-ATA compatible sleave mean in regard to the above speed limits...??? Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
