Re: Need some insight on error messages that I am getting.
snip Is there a way to put the proper atacontrol command in somewhere so that it will slow the first hdd (ad0) down to UDMA33? Perhaps a script in /usr/local/etc/rc.d... but before it is run, ad0 will be UDMA66. Wherever you put an atacontrol command, ad0 will be UDMA66 before that (outside of modifying the kernel), which might cause some trouble. A solution might be to first set all drives into PIO (by adding hw.ata.ata_dma=0 in the loader config) and `atacontrol' them in rc.d to their speeds (both to UDMA33). This may cause the boot to be somewhat slower. Thanks! I will look into this. I appreciate the help in this matter! Marshall ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need some insight on error messages that I am getting.
snip Try tweaking it up to, say, WDMA2, etc. and see what happens... OK I changed it to WDMA2 and it seems to behave! Well I went a little further and changed it back to UDMA33 and slowed the ad0 drive to UDMA33. It was previously set at UDMA66. Did the copy operation again, it did not show me any errors. I am assuming here that FreeBSD does not like drives with different speeds on the same bus??? Is my assumption correct?? From what little bit of fooling around that I did seems to support this. When putting everything back to the defaults, I start seeing the messages again. Interesting huh? One of the drives ad0 is capable of ATA100 though my motherboard is not capable of that. It uses UDMA66 and this transfer mode works well in other OS's. The drive that is driving me nuts the ad1 is only capable of UDMA33. This info may/maynot help but it might get one to thinking what could be causing this. Thanks for the help so far! Marshall ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need some insight on error messages that I am getting.
snip \From ata(4) manpage: man The use of UDMA4(66MHz) and higher together with non-UDMA4 devices on the man same ATA channel is not recommended, unless they are run at the non-UDMA4 man device's lower speed. The driver has been designed to handle that kind man of setup but lots of older devices do not like this. This definitely would explain it. Shows how new I am to FreeBSD. Thanks! Is there a way to put the proper atacontrol command in somewhere so that it will slow the first hdd (ad0) down to UDMA33? Thank you! Marshall ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need some insight on error messages that I am getting.
(And now the messages) ad1: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices -- done It really really looks like a hardware fault. This is what I suspected but below in my post, I checked the drive with a diagnostic utility from the manufacturer and the drive tested OK. snip ad1: removed from configuration done handle_workitem_freeblocks: block count Oh yeah, so it removes its boot disk from the configuration because it thinks it faulty and you think it may proceed without it? No I didn't. Well I can see that this is going to be a barrel of laughs. I don't quite understand FreeBSD and this is why I came here for help. Sorry that I asked my question. Judging by the error messages, the system is telling me that there is a problem with the drive. Well I shutdown the system and looked again at the jumpers on the drives. They are set correctly. Next I go out to the net and get a diagnostic utility for the hard drive and run it on the drive. It passed with flying colors. I even reinstalled FreeBSD and even installed the 5.1 to see if the same thing occurs and it does. Here is where I stated that I tested the drive. And I also checked to see if the jumpers were correctly set. You could try setting PIO mode to see if the problem persists: # atacontrol mode 0 XXX PIO0 I will try this and let you know what happens. Does the same thing happen to ad0? In the email, ad0 has windows and Linux on it. I did not try and mount the windows slice and see if this drive exhibits the same behavior. I did not have any issues with the drive using it as storage for Windows and Linux. It seemed to start when I put FreeBSD on the drive. You can change it back to LBA in the BIOS, can't you? I did and it doesn't seem to help. Funny thing is though is when I wipe out the drive, BIOS sees the drive as a LBA but after installation and the subsequent reboot, which causes the computer to hang and I have to to a hard reboot, then the drive shows up as a CHS so I do not know. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need some insight on error messages that I am getting.
On Wed, 2003-10-22 at 09:51, M.D. DeWar wrote: I get these all the time. I was told that it was possibly in the cable or motherboard controller. The point was the drive was like ata 100 and the cable was ata 33 or the mb did not support the ata mode of the drive. I never confirmed it cuz when I put in a maxtor ata controller I lost all my slices and had to go back to the mb controller. I think that the person that sent me that was off this list so it might be in the archives. Thanks, I used atacontrol to change the mode in which the drive was working and the errors went away. I changed it from UDMA66 to PIO0 and no more messages. My motherboard controller will handle the UDMA66 mode so I do not know what the deal is. My drives are on a ATA100 cable. I will look a little deeper so see what else is causing this. I would much rather operate the drive in UDMA66 mode than PIO0. I will take a look in the archives to see what I can dig up. Marshall ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
