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
>
>
On Mon, Feb 8, 2010 at 6:01 PM, Daniel O'Connor wrote:
> On Tue, 9 Feb 2010, Freddie Cash wrote:
> > I just did this to 8 of the 1.5 TB Caviar Green disks, without ZFS
> > complaining in any way.
> >
> > I did test it on a spare drive before doing it to the 7 live drives.
> > And I did replace the
On Tue, Feb 09, 2010 at 02:42:10AM -0800, per...@pluto.rain.com wrote:
> Jeremy Chadwick wrote:
> > The DOS utilities submit custom ATA CMDs or data to all WD disks
> > to toggle or adjust these features. If someone could figure out
> > what the command(s) were, the feature(s) could be implemente
Jeremy Chadwick wrote:
> The DOS utilities submit custom ATA CMDs or data to all WD disks
> to toggle or adjust these features. If someone could figure out
> what the command(s) were, the feature(s) could be implemented into
> atacontrol(8). Of course, that would require reverse-engineering
> of
On Tue, 9 Feb 2010, Freddie Cash wrote:
> > I just did this to 8 of the 1.5 TB Caviar Green disks, without ZFS
>
> complaining in any way.
>
> I did test it on a spare drive before doing it to the 7 live drives.
> And I did replace them while the server was turned off, just to be
> safe (and to pr
On Mon, Feb 8, 2010 at 4:29 PM, Daniel O'Connor wrote:
> On Tue, 9 Feb 2010, Dan Naumov wrote:
> > which essentially solves the problem. Note that going this route will
> > probably involve rebuilding your entire array from scratch, because
> > applying WDIDLE3 to the disk is likely to very slight
On Tue, 9 Feb 2010, Gerrit Kühn wrote:
> :-)))
>
> I would really prefer to be able to set this stuff via camcontrol or
> atacontrol. Alone having to boot DOS with this machine (no floppy, no
> cdrom) will be a real pain. And most probably the DOS tool will not
> be able to see the disks sitting be
On Tue, 9 Feb 2010, Dan Naumov wrote:
> which essentially solves the problem. Note that going this route will
> probably involve rebuilding your entire array from scratch, because
> applying WDIDLE3 to the disk is likely to very slightly affect disk
> geometry, but just enough for hardware raid or
On Mon, 8 Feb 2010 06:22:59 -0800 Jeremy Chadwick
wrote about Re: one more load-cycle-count
problem:
JC> The DOS utilities submit custom ATA CMDs or data to all WD disks to
JC> toggle or adjust these features. If someone could figure out what the
JC> command(s) were, the feature(s)
On Mon, 8 Feb 2010 15:56:35 +0200 Dan Naumov wrote:
> WDIDLE3 changes the drive firmware. This is also how WD can detect
> you've used it on your disk and void your warranty accordingly :)
I've upgraded the firmware at five WD1000FYPS disks. One of them
still kept on running load cycles. Then I u
On Mon, Feb 08, 2010 at 03:56:35PM +0200, Dan Naumov wrote:
> 2010/2/8 Gerrit Kühn :
> > On Mon, 8 Feb 2010 15:43:46 +0200 Dan Naumov wrote
> > about RE: one more load-cycle-count problem:
> >
> > DN> >Any further ideas how to get rid of this "feature"?
2010/2/8 Gerrit Kühn :
> On Mon, 8 Feb 2010 15:43:46 +0200 Dan Naumov wrote
> about RE: one more load-cycle-count problem:
>
> DN> >Any further ideas how to get rid of this "feature"?
>
> DN> 1) The most "clean" solution is probably using the
On Mon, 8 Feb 2010 15:43:46 +0200 Dan Naumov wrote
about RE: one more load-cycle-count problem:
DN> >Any further ideas how to get rid of this "feature"?
DN> 1) The most "clean" solution is probably using the WDIDLE3 utility on
DN> your drives to disable automat
>Any further ideas how to get rid of this "feature"?
You have several options.
1) The most "clean" solution is probably using the WDIDLE3 utility on
your drives to disable automatic parking or in cases where its not
possible to complete disable it, you can adjust it to 5 minutes, which
essentiall
Hi all,
After being disturbed by the firmware issues of the wd drives causing
exceeding load cycles (see thread "immense delayed write to file system
(ZFS and UFS2), performance issues" in January), I have found some more
problematic drives in the following setup:
4 x 2.5" WDC WD4000BEVT-00ZAT0 i
15 matches
Mail list logo
