RE: ata1: resetting devices ...
These messages say you have a UDMA66 hard drive on the master ribbon connector of IDE1 controller and a UDMA33 hard drive on the master ribbon connector of IDE2 controller and both ribbons are ATA66 ribbons. This will not hurt anything or cause any performance slow down. You can get rid of this problem by replacing the ATA66 ribbon on IDE2 with a ATA33 ribbon. -Original Message- From: samy lancher [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 28, 2004 2:36 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: ata1: resetting devices ... These are the messages from "dmesg" ad0: 76345MB [155114/16/63] at ata0-master UDMA66 ad2: DMA limited to UDMA33, non-ATA66 cable or device ad2: 38166MB [77545/16/63] at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s1a ad2: READ command timeout tag=0 serv=0 - resetting ata1: resetting devices .. ad2: DMA limited to UDMA33, non-ATA66 cable or device Thanks, Naveen. JJB <[EMAIL PROTECTED]> wrote: These means that you have a mismatch between the devices and the ribbon connecting them to your motherboard. Most common cause is a UDMA66 hard drive plugged into the master connector on the ribbon and a UDMA33 CDROM. The messages is telling you the IDE hard drive controller is defaulting the ribbon read/write speed to the slower speed of the CDROM. Now this is not harmful to your hardware, but does deny your server the ability to utilize the full speed potential of your hard drive. This is easily fixed by moving the CDROM drive from the slave connector on the primary IDE controller to the master commenter on the secondary IDE controller on your motherboard. This also can occur if you have two hard drives on the primary IDE controller of different speeds. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of samy lancher Sent: Wednesday, July 28, 2004 12:48 PM To: [EMAIL PROTECTED] Subject: ata1: resetting devices ... Hello All, This morning I have seen the following log message on my FreeBSD 4.7 server. ad2: READ command timeout tag=0 serv=0 - resetting ata1: resetting devices .. ad2: DMA limited to UDMA33, non-ATA66 cable or device done. I would really appreciate if someone could tell me the cause for this message and is there something to worry about the server?. Thanks in advance. Thanks, Naveen. - Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" _ Do you Yahoo!? Yahoo! Mail Address AutoComplete <http://us.rd.yahoo.com/mail_us/taglines/aac/*http://promotions.yahoo.com/ne w_mail/static/ease.html> - You start. We finish. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ata1: resetting devices ...
These messages say you have a UDMA66 hard drive on the master ribbon connector of IDE1 and a UDMA33 hard drive on the master ribbon connector of IDE2 and both ribbons are ATA66 ribbons. This will not hurt anything or cause any performance slow down. You can get rid of this problem by replacing the ATA66 ribbon on IDE2 with a ATA33 ribbon. -Original Message- From: samy lancher [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 28, 2004 2:36 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: ata1: resetting devices ... These are the messages from "dmesg" ad0: 76345MB [155114/16/63] at ata0-master UDMA66 ad2: DMA limited to UDMA33, non-ATA66 cable or device ad2: 38166MB [77545/16/63] at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s1a ad2: READ command timeout tag=0 serv=0 - resetting ata1: resetting devices .. ad2: DMA limited to UDMA33, non-ATA66 cable or device Thanks, Naveen. JJB <[EMAIL PROTECTED]> wrote: These means that you have a mismatch between the devices and the ribbon connecting them to your motherboard. Most common cause is a UDMA66 hard drive plugged into the master connector on the ribbon and a UDMA33 CDROM. The messages is telling you the IDE hard drive controller is defaulting the ribbon read/write speed to the slower speed of the CDROM. Now this is not harmful to your hardware, but does deny your server the ability to utilize the full speed potential of your hard drive. This is easily fixed by moving the CDROM drive from the slave connector on the primary IDE controller to the master commenter on the secondary IDE controller on your motherboard. This also can occur if you have two hard drives on the primary IDE controller of different speeds. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of samy lancher Sent: Wednesday, July 28, 2004 12:48 PM To: [EMAIL PROTECTED] Subject: ata1: resetting devices ... Hello All, This morning I have seen the following log message on my FreeBSD 4.7 server. ad2: READ command timeout tag=0 serv=0 - resetting ata1: resetting devices .. ad2: DMA limited to UDMA33, non-ATA66 cable or device done. I would really appreciate if someone could tell me the cause for this message and is there something to worry about the server?. Thanks in advance. Thanks, Naveen. - Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" _ Do you Yahoo!? Yahoo! Mail Address AutoComplete <http://us.rd.yahoo.com/mail_us/taglines/aac/*http://promotions.yahoo.com/ne w_mail/static/ease.html> - You start. We finish. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ata1: resetting devices ...
On Wed, 28 Jul 2004 09:48:02 -0700 (PDT) samy lancher <[EMAIL PROTECTED]> wrote: > Hello All, > > This morning I have seen the following log message on my FreeBSD 4.7 > server. > > ad2: READ command timeout tag=0 serv=0 - resetting > ata1: resetting devices .. ad2: DMA limited to UDMA33, non-ATA66 > cable or device > > done. > > I would really appreciate if someone could tell me the cause for > this message and is there something to worry about the server?. Bad drive or cable most likely. I've seen it three times. Fist it was bad cable. The other two it was bad drives. Try a new cable first and if that does not fix it, it is the drive most likely. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ata1: resetting devices ...
Same solution, move IDE1 slave to IDE2 master. Check dmesg.boot file for boot messages about hard drives and their speeds. ATA66 should be your fastest drive and the one that you want FreeBSD on, and it should be the master on IDE1. -Original Message- From: samy lancher [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 28, 2004 2:13 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: ata1: resetting devices ... Hi, Thanks for the reply. Yes, i do have two hard drives in my server. I am not sure about their speeds. Could you please give me the solution if the problem is from having two hard drives. Thanks, Naveen. JJB <[EMAIL PROTECTED]> wrote: These means that you have a mismatch between the devices and the ribbon connecting them to your motherboard. Most common cause is a UDMA66 hard drive plugged into the master connector on the ribbon and a UDMA33 CDROM. The messages is telling you the IDE hard drive controller is defaulting the ribbon read/write speed to the slower speed of the CDROM. Now this is not harmful to your hardware, but does deny your server the ability to utilize the full speed potential of your hard drive. This is easily fixed by moving the CDROM drive from the slave connector on the primary IDE controller to the master commenter on the secondary IDE controller on your motherboard. This also can occur if you have two hard drives on the primary IDE controller of different speeds. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of samy lancher Sent: Wednesday, July 28, 2004 12:48 PM To: [EMAIL PROTECTED] Subject: ata1: resetting devices ... Hello All, This morning I have seen the following log message on my FreeBSD 4.7 server. ad2: READ command timeout tag=0 serv=0 - resetting ata1: resetting devices .. ad2: DMA limited to UDMA33, non-ATA66 cable or device done. I would really appreciate if someone could tell me the cause for this message and is there something to worry about the server?. Thanks in advance. Thanks, Naveen. - Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" _ Do you Yahoo!? Yahoo! Mail Address AutoComplete <http://us.rd.yahoo.com/mail_us/taglines/aac/*http://promotions.yahoo.com/ne w_mail/static/ease.html> - You start. We finish. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ata1: resetting devices ...
These are the messages from "dmesg" ad0: 76345MB [155114/16/63] at ata0-master UDMA66 ad2: DMA limited to UDMA33, non-ATA66 cable or device ad2: 38166MB [77545/16/63] at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s1a ad2: READ command timeout tag=0 serv=0 - resetting ata1: resetting devices .. ad2: DMA limited to UDMA33, non-ATA66 cable or device Thanks, Naveen. JJB <[EMAIL PROTECTED]> wrote: These means that you have a mismatch between the devices and the ribbon connecting them to your motherboard. Most common cause is a UDMA66 hard drive plugged into the master connector on the ribbon and a UDMA33 CDROM. The messages is telling you the IDE hard drive controller is defaulting the ribbon read/write speed to the slower speed of the CDROM. Now this is not harmful to your hardware, but does deny your server the ability to utilize the full speed potential of your hard drive. This is easily fixed by moving the CDROM drive from the slave connector on the primary IDE controller to the master commenter on the secondary IDE controller on your motherboard. This also can occur if you have two hard drives on the primary IDE controller of different speeds. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of samy lancher Sent: Wednesday, July 28, 2004 12:48 PM To: [EMAIL PROTECTED] Subject: ata1: resetting devices ... Hello All, This morning I have seen the following log message on my FreeBSD 4.7 server. ad2: READ command timeout tag=0 serv=0 - resetting ata1: resetting devices .. ad2: DMA limited to UDMA33, non-ATA66 cable or device done. I would really appreciate if someone could tell me the cause for this message and is there something to worry about the server?. Thanks in advance. Thanks, Naveen. - Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" - Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ata1: resetting devices ...
Hi, Thanks for the reply. Yes, i do have two hard drives in my server. I am not sure about their speeds. Could you please give me the solution if the problem is from having two hard drives. Thanks, Naveen. JJB <[EMAIL PROTECTED]> wrote: These means that you have a mismatch between the devices and the ribbon connecting them to your motherboard. Most common cause is a UDMA66 hard drive plugged into the master connector on the ribbon and a UDMA33 CDROM. The messages is telling you the IDE hard drive controller is defaulting the ribbon read/write speed to the slower speed of the CDROM. Now this is not harmful to your hardware, but does deny your server the ability to utilize the full speed potential of your hard drive. This is easily fixed by moving the CDROM drive from the slave connector on the primary IDE controller to the master commenter on the secondary IDE controller on your motherboard. This also can occur if you have two hard drives on the primary IDE controller of different speeds. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of samy lancher Sent: Wednesday, July 28, 2004 12:48 PM To: [EMAIL PROTECTED] Subject: ata1: resetting devices ... Hello All, This morning I have seen the following log message on my FreeBSD 4.7 server. ad2: READ command timeout tag=0 serv=0 - resetting ata1: resetting devices .. ad2: DMA limited to UDMA33, non-ATA66 cable or device done. I would really appreciate if someone could tell me the cause for this message and is there something to worry about the server?. Thanks in advance. Thanks, Naveen. - Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" - Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ata1: resetting devices ...
These means that you have a mismatch between the devices and the ribbon connecting them to your motherboard. Most common cause is a UDMA66 hard drive plugged into the master connector on the ribbon and a UDMA33 CDROM. The messages is telling you the IDE hard drive controller is defaulting the ribbon read/write speed to the slower speed of the CDROM. Now this is not harmful to your hardware, but does deny your server the ability to utilize the full speed potential of your hard drive. This is easily fixed by moving the CDROM drive from the slave connector on the primary IDE controller to the master commenter on the secondary IDE controller on your motherboard. This also can occur if you have two hard drives on the primary IDE controller of different speeds. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of samy lancher Sent: Wednesday, July 28, 2004 12:48 PM To: [EMAIL PROTECTED] Subject: ata1: resetting devices ... Hello All, This morning I have seen the following log message on my FreeBSD 4.7 server. ad2: READ command timeout tag=0 serv=0 - resetting ata1: resetting devices .. ad2: DMA limited to UDMA33, non-ATA66 cable or device done. I would really appreciate if someone could tell me the cause for this message and is there something to worry about the server?. Thanks in advance. Thanks, Naveen. - Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! ___ [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: ata1 resetting
On Wed, Jan 22, 2003 at 04:49:40PM +0100, Marc Schneiders wrote: > On Wed, 22 Jan 2003, at 07:31 [=GMT-0800], Nathan Kinkade wrote: > > On Wed, Jan 22, 2003 at 07:58:31AM +0100, Marc Schneiders wrote: > > [...] > > > Jan 21 19:47:39 pan /kernel: ata1: resetting devices .. ata1-slave: > > > ATA identify retries exceeded > > > Jan 21 19:47:39 pan /kernel: done > > > Jan 21 22:06:39 pan /kernel: ad0: WRITE command timeout tag=0 serv=0 - > > > resetting > > > > > > Do you have DMA enabled on those drives when possibly they don't support > > it? > > sysctl reports: hw.ata.ata_dma: 1 > > > What type of ribbon cable are you using - a 40 or 80 conductor? > > 40, it is a rather old motherboard, as I mentioned. > > > Try setting the sysctl(8) value "hw.ata.ata_dmai" to 0 and see what results > > you get. The errors you are getting look similar to ones I've seen > > where the kernel is trying to use DMA on a drive that doesn't support > > it, or on a drive that supports DMA that is using an improper 40 > > conductor cable instead of the correct 80 conductor cable. You can use > > the atacontrol(8) utilitly to find out more about the capabilities of > > your devices. For example, `atacontrol cap 0 0` should give you all > > manner of info about your primary master ATA device. > > This is what it says: > > ATA channel 0, Master, device ad0: > > ATA/ATAPI revision4 > device model ST34312A > serial number [secret] > firmware revision 3.09 > cylinders 8354 > heads 16 > sectors/track 63 > lba supported 8420832 sectors > lba48 not supported > dma supported > overlap not supported > > Feature Support EnableValue Vendor > write cacheyes yes > read ahead yes yes > dma queued no no 0/00 > SMART yes no > microcode download yes yes > security yes no > power management yes yes > advanced power management no no 0/00 > automatic acoustic management no no 0/000/00 > > So it can do DMA, but doesn't use it?? > > I have another machine with the same hardware, except for video and > ethernet cards, that does _not_ have the error messages (and the > problem). It also has just one harrdisk, and the problem machine two, > on two channels. Can that be it? What does the command `grep "ad[0-9]" /var/run/dmesg.boot` return. Specifically, look at the end of the line which defines each of your disks and you should see how the device was detected (PIO, UDMA, etc). Regarding the ribbon cable, the 80 conductor cable is really on required for UDMA mode 3 and above, although maybe recommended for all UDMA modes. In any case, as far as I know, FreeBSD should auto-detect the presence, or absence, of an 80 conductor cable and set dma modes accordingly. I'm not sure that dma/udma is causing your issues at all, but it certainly couldn't hurt to turn off dma and see if the problems go away. Nathan -- GPG Public Key ID: 0x4250A04C gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc msg16345/pgp0.pgp Description: PGP signature
Re: ata1 resetting
On Wed, 22 Jan 2003, at 07:31 [=GMT-0800], Nathan Kinkade wrote: > On Wed, Jan 22, 2003 at 07:58:31AM +0100, Marc Schneiders wrote: [...] > > Jan 21 19:47:39 pan /kernel: ata1: resetting devices .. ata1-slave: > > ATA identify retries exceeded > > Jan 21 19:47:39 pan /kernel: done > > Jan 21 22:06:39 pan /kernel: ad0: WRITE command timeout tag=0 serv=0 - > > resetting > > > Do you have DMA enabled on those drives when possibly they don't support > it? sysctl reports: hw.ata.ata_dma: 1 > What type of ribbon cable are you using - a 40 or 80 conductor? 40, it is a rather old motherboard, as I mentioned. > Try setting the sysctl(8) value "hw.ata.ata_dmai" to 0 and see what results > you get. The errors you are getting look similar to ones I've seen > where the kernel is trying to use DMA on a drive that doesn't support > it, or on a drive that supports DMA that is using an improper 40 > conductor cable instead of the correct 80 conductor cable. You can use > the atacontrol(8) utilitly to find out more about the capabilities of > your devices. For example, `atacontrol cap 0 0` should give you all > manner of info about your primary master ATA device. This is what it says: ATA channel 0, Master, device ad0: ATA/ATAPI revision4 device model ST34312A serial number [secret] firmware revision 3.09 cylinders 8354 heads 16 sectors/track 63 lba supported 8420832 sectors lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes dma queued no no 0/00 SMART yes no microcode download yes yes security yes no power management yes yes advanced power management no no 0/00 automatic acoustic management no no 0/000/00 So it can do DMA, but doesn't use it?? I have another machine with the same hardware, except for video and ethernet cards, that does _not_ have the error messages (and the problem). It also has just one harrdisk, and the problem machine two, on two channels. Can that be it? [...] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: ata1 resetting
On Wed, Jan 22, 2003 at 07:58:31AM +0100, Marc Schneiders wrote: > Does someone see some sort of pattern in the times (from > /var/log/messages) below? I do but know not what. > > And what could explain it? > > Please, note that it occurs on both harddisks and on both controllers. > > Something cron related? Something swap related, since there is swap > space on both disks? I think, however, that swap is hardly used: > > Device 1K-blocks UsedAvail Capacity Type > /dev/ad0s1b524160 16 524144 0%Interleaved > /dev/rad2b 5241600 524160 0%Interleaved > Total 1048320 16 1048304 0% > > > Jan 21 18:49:40 pan /kernel: ad2: WRITE command timeout tag=0 serv=0 - > resetting > Jan 21 18:49:40 pan /kernel: ata1: resetting devices .. ata1-slave: > ATA identify retries exceeded > Jan 21 18:49:40 pan /kernel: done > Jan 21 19:47:39 pan /kernel: ad2: WRITE command timeout tag=0 serv=0 - > resetting > Jan 21 19:47:39 pan /kernel: ata1: resetting devices .. ata1-slave: > ATA identify retries exceeded > Jan 21 19:47:39 pan /kernel: done > Jan 21 22:06:39 pan /kernel: ad0: WRITE command timeout tag=0 serv=0 - > resetting Do you have DMA enabled on those drives when possibly they don't support it? What type of ribbon cable are you using - a 40 or 80 conductor? Try setting the sysctl(8) value "hw.ata.ata_dmai" to 0 and see what results you get. The errors you are getting look similar to ones I've seen where the kernel is trying to use DMA on a drive that doesn't support it, or on a drive that supports DMA that is using an improper 40 conductor cable instead of the correct 80 conductor cable. You can use the atacontrol(8) utilitly to find out more about the capabilities of your devices. For example, `atacontrol cap 0 0` should give you all manner of info about your primary master ATA device. If you want to set the value of "hw.ata.ata_dma" on boot, you will have to put the command in the file /boot/loader.conf as a line with the text "hw.ata.ata_dma=0". It needs to go here rather /etc/sysctl.conf because by the time /etc/sysctl.conf is processes the disk subsystems have already been activated. Nathan -- GPG Public Key ID: 0x4250A04C gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc msg16310/pgp0.pgp Description: PGP signature
