Drive errors on boot

[Bryan Curl]

On 4/10/06, David J Brooks <daeg at houston.rr.com> wrote:
>
> On Monday 10 April 2006 09:26, Bryan Curl wrote:
> > --- Lowell Gilbert
> >
> > <freebsd-questions-local at be-well.ilk.org> wrote:
> > > Bryan Curl <bc3910 at yahoo.com> writes:
> > > > My apologies if this is a repost. It seems either
> > >
> > > I
> > >
> > > > had a gmail problem or list never posted the
> > >
> > > question.
> > >
> > > > I have subscribed with another address to monitor
> > > > problem.
> > > >
> > > > Anyway, here is my question again.
> > > >
> > > > I get the following errors from dmesg on one of my
> > >
> > > ide
> > >
> > > > drives on boot.
> > > > Other similar drives dont error and are setup the
> > >
> > > same
> > >
> > > > in bios (except cylinder & block config of course)
> > > > System and this drive seem to work fine otherwise.
> > >
> > > I
> > >
> > > > re-fdisk this one but it still does this error.
> > > >
> > > > FreeBSD 6.0-RELEASE-p6 #0: Tue Apr  4 09:43:53 MDT
> > > > 2006
> > > >
> > > > ad1: 1916MB <Maxtor 72004 AP 2A3C0B31> at
> > >
> > > ata0-slave
> > >
> > > > WDMA2
> > > > ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
> > > > error=10<NID_NOT_FOUND> LBA=3924359
> > > > ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
> > > > error=10<NID_NOT_FOUND> LBA=3924343
> > > > ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
> > > > error=10<NID_NOT_FOUND> LBA=3924356
> > > > ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
> > > > error=10<NID_NOT_FOUND> LBA=3924359
> > >
> > > This is probably a hardware problem.  My first guess
> > > would be
> > > cabling.  Try swapping the cable.  And make sure
> > > there is a master on
> > > the bus if this one is probing as a slave.
> >
> > This is the primary slave drive. Primary master is the
> > boot drive where OS lives. The master is cabled on the
> > end connector and the slave is connected to the middle
> > connector on the cable.
> >
> > The supplied documentation on the drive jumpers is
> > vague at best. It only makes mention of one jumper
> > (master or slave positions) There are 3 other jumpers
> > on the drive that are not mentioned.
> >
> > Looks to me like DMA feature isn't working but I dont
> > know if this is activated by a jumper or by firmware
> > somehow.
> >
> > > > I  dont know what causes these errors either.
> > > >
> > > > dc0: failed to force tx and rx to idle state
> > > > dc0: failed to force tx and rx to idle state
> > >
> > > The driver tried to force the transmitter and
> > > receiver to be "idle"
> > > temporarily, and failed.  There are a number of
> > > different cases where
> > > the driver tries to do this, so it's hard to guess
> > > exactly what's
> > > happening this time.  Some of the relevant variables
> > > are: whether this
> > > happens at boot time, whether it happens after an
> > > underrun or overrun,
> > > and which real controller chip you have.
> >
> > I have seen this error on every FreeBSD installation I
> > have ever had. To my knowledge, it never seemed to
> > bother anything. I just hate watching errors scroll by.
>
> I solved this same error on my machine by adding
> sysctl hw.ata.ata_dma=0
> to /boot/loader.conf
>
> That slows down drive access something fierce, but it worked for me. Once
> the
> machine has booted you may be able to turn DMA access back on with
> atacontrol(8).
>
> The problem was ultimately solved for me by upgrading to 6.1-PRERELEASE.
>
> HTH,
> David
> --
> Sure God created the world in only six days,
> but He didn't have an established user-base.
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at freebsd.org"
>

Writing a file to the drive the other day it coredumped.
So I pulled the drive and booted to an old WIn98 foppy and partitioned and
formatted the drive just to start from scratch, no problems indicated in
that process.
Then I CVSUPed to RELENG_6_1. No problems upgrading at all.
I reinstalled the drive with a different cable and put it on the secondary
slave position, and fdisk and labeled per sysinstall, full use, no MBR
changes.
I tried different bios settings like auto recognition, user defined, with
LBA, Normal and Large Modes. No change.

fsck /dev/ad3s1d looks good this time but same dmesg errors exists on boot.
This an older Maxtor 72004 AP 2Gig

Could be time for trashcan to take ownership.
Any more ideas?


--
--
Bryan
bc3910 'at' gmail 'dot' com