Date: Tue, 15 Jun 2010 08:06:36 -0700 (PDT) From: Casey Scott <casey@phantombsd.org> To: freebsd-questions@freebsd.org Subject: Re: SATA time outs Message-ID: <1246163718.463.1276614396590.JavaMail.root@spitfire.phantombsd.org> In-Reply-To: <1609626746.429.1276527962347.JavaMail.root@spitfire.phantombsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I'd appreciate it if someone could lend some assistance with this issue. The machine in question is pretty much unusable atm! Regards, Casey ----- "Casey Scott" <casey@phantombsd.org> wrote: > Since upgrading to 8.0 RELEASE, I continually get these errors: > > ... > Jun 11 15:24:08 xxxx kernel: ad6: 953869MB <Seagate ST31000340AS SD1A> > at ata3-master SATA150 > Jun 11 15:24:08 xxxx kernel: (probe6:ahc0:0:6:0): TEST UNIT READY. > CDB: 0 0 0 0 0 0 > Jun 11 15:24:08 xxxx kernel: (probe6:ahc0:0:6:0): CAM Status: SCSI > Status Error > Jun 11 15:24:08 xxxx kernel: (probe6:ahc0:0:6:0): SCSI Status: Check > Condition > Jun 11 15:24:08 xxxx kernel: (probe6:ahc0:0:6:0): UNIT ATTENTION > asc:29,2 > Jun 11 15:24:08 xxxx kernel: (probe6:ahc0:0:6:0): SCSI bus reset > occurred > Jun 11 15:24:08 xxxx kernel: (probe6:ahc0:0:6:0): Retrying Command > (per Sense Data) > ... > > > I've tried 3 different drives w/ 2 different disk controllers. > Anything I use as the second drive generates this message on boot, and > will eventually fail with timeout errors after a couple hours. The > other drive on the system, ad4, never displays these symptoms. This > isn't new hardware, and worked flawlessly until now. > > Any suggestions? Has a bug been introduced into the ata driver? > > Regards, > Casey > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1246163718.463.1276614396590.JavaMail.root>