one more load-cycle-count problem

[Daniel O'Connor]

On Wed, 10 Feb 2010, Freddie Cash wrote:
> > /d sets it (for me) to 6300 milliseconds (6.3 seconds). I took this
> > as a special value that disabled it entirely (no idea why they
> > didn't use 0 or 255..)
> >
> > I've seen reports of the same on various hardware forums.  Not sure
> > if it's
>
> due to different firmware, or different drive models.
>
> You should still be able to list the timeout value explicitly
> (instead of using /d).  According to the help output, you can use
> either 25.5 seconds or 3000-something seconds as the max value
> (depends on the drive).

Yes I know, I used /d and haven't had any issues since.

As the original timeout was 8 seconds I am pretty confident it treats 63 
as special otherwise the problem would still be happening for me.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100210/70f8c074/attachment.pgp