Date: Tue, 6 Jan 2004 04:18:41 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> Cc: current@freebsd.org Subject: Re: slow probe for ata channel with only an atapi master on it Message-ID: <20040106041140.A6673@gamplex.bde.org> In-Reply-To: <20040106030133.U6241@gamplex.bde.org> References: <200401050914.i059EYfW036079@spider.deepcore.dk> <20040106030133.U6241@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[Private reply] [I wrote] > The other drive is undead. It seems to fail to spin up sometimes, but > works perfectly if its probe succeeds and I start accessing it immediately, > but tends to fail if I don't access it for a while. It now always fails > overnight. I'm wondering if it spins down and then the spin up doesn't > work, and plan to try putting it in sleep modes intentionally. The I tried your "atacontrol sleep" command. It broke the drive in much the same way as not using it overnight, except the BIOS was able to wake it up correctly :-). "atacontrol standby" doesn't break it. > driver handles its failure poorly. The failure is usually hard (takes > several power cycles to recover from), to it gets "removed from > configuration" after several seconds or minutes of the system being > unusable because it is blocked on Giant. Then removal usually causes > a null pointer panic. "atacontrol detach" also puts the drive too sleep, and it works much better than shooting an active drive. It also works to help wake up the drive: the drive works right after "atacontrol sleep; atacontrol detach; atacontrol attach", except it takes about 5 seconds to wake up after the first i/o command (attach apparently doesn't wake it up). Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040106041140.A6673>