Delayed Write Error - Revisited, but different this time...

I have a NDAS device called a Ximeta 250GB Network Storage. It has a
8-port ethernet switch that allows multiple connections to the device.

Recently, we had gotten delayed write errors, so after some research
we decided to replace the drive. From WD to Seagate, easy enough...
Only problem is, we're getting the errors again. I work for a company
that employs 10 of these Ximeta drives, and they're all starting to
have it, not 6 months after having the drives replaced.

After more research, finding the numerous possible solutions,
including disabling write caching, verifying device driver versions
and manufacturer drivers, we're at a loss as to why this continues to
happen.

Disabling write caching does not produce errors, only more hang-ups.

So is it a trade-off? Or does someone have any advice or a suggestion
I can try?

RedForeman

"RedForeman" <RedForeman@gmail.com> wrote in message news:1179948868.899510.282140@k79g2000hse.googlegr oups.com
> I have a NDAS device called a Ximeta 250GB Network Storage. It has a
> 8-port ethernet switch that allows multiple connections to the device.
>
> Recently, we had gotten delayed write errors, so after some research
> we decided to replace the drive. From WD to Seagate, easy enough...
> Only problem is, we're getting the errors again. I work for a company
> that employs 10 of these Ximeta drives, and they're all starting to
> have it, not 6 months after having the drives replaced.
>
> After more research, finding the numerous possible solutions,
> including disabling write caching, verifying device driver versions
> and manufacturer drivers, we're at a loss as to why this continues to
> happen.
>
> Disabling write caching does not produce errors, only more hang-ups.

> So is it a trade-off? Or does someone have any advice or a suggestion
> I can try?

Return as unfit for their purpose.

>
> RedForeman

On 23 May 2007 12:34:28 -0700, RedForeman <RedForeman@gmail.com>
wrote:

>So is it a trade-off? Or does someone have any advice or a suggestion
>I can try?

Unless Microsoft has something I don't know yet, not much you can do
about it. Last I checked, no one knows exactly why this happens but
it seems to be caused by large file chink size (something like 512k
chunk) that is causing the problem. I've had write delayed error on
IDE (PCI not onboard), firewire, and USB. USB 2.0 gets em a lot.

Plan 1: If you can dig up an older 10base hub, you could put that
between your network drive and the rest of the network. Yes it'd be
much slower but forcing the data to go slow seems to reduce the
problem.

Plan 2: build or buy an older PC that has 100base network, run Linux
or older Windows, and install up to 4 hard drives. I almost never see
write delayed error from onboard IDE. Set the drives to be shared so
everyone can use it.

Plan 3: replace the IDE cable in your drive with older 40 conductor
cable and see if that'd force the drive to operate at a slower ATA
protocol.

On May 23, 5:30 pm, Impmon <imp...@digi.mon> wrote:
> On 23 May 2007 12:34:28 -0700, RedForeman <RedFore...@gmail.com>
> wrote:
>
> >So is it a trade-off? Or does someone have any advice or a suggestion
> >I can try?
>
> Unless Microsoft has something I don't know yet, not much you can do
> about it. Last I checked, no one knows exactly why this happens but
> it seems to be caused by large file chink size (something like 512k
> chunk) that is causing the problem. I've had write delayed error on
> IDE (PCI not onboard), firewire, and USB. USB 2.0 gets em a lot.
>
> Plan 1: If you can dig up an older 10base hub, you could put that
> between your network drive and the rest of the network. Yes it'd be
> much slower but forcing the data to go slow seems to reduce the
> problem.
>
> Plan 2: build or buy an older PC that has 100base network, run Linux
> or older Windows, and install up to 4 hard drives. I almost never see
> write delayed error from onboard IDE. Set the drives to be shared so
> everyone can use it.
>
> Plan 3: replace the IDE cable in your drive with older 40 conductor
> cable and see if that'd force the drive to operate at a slower ATA
> protocol.

Good points...

On May 23, 4:44 pm, "Folkert Rienstra" <see_reply...@myweb.nl> wrote:
> "RedForeman" <RedFore...@gmail.com> wrote in messagenews:1179948868.899510.282140@k79g2000hse.g ooglegroups.com
> > I have a NDAS device called a Ximeta 250GB Network Storage. It has a
> > 8-port ethernet switch that allows multiple connections to the device.
>
> > Recently, we had gotten delayed write errors, so after some research
> > we decided to replace the drive. From WD to Seagate, easy enough...
> > Only problem is, we're getting the errors again. I work for a company
> > that employs 10 of these Ximeta drives, and they're all starting to
> > have it, not 6 months after having the drives replaced.
>
> > After more research, finding the numerous possible solutions,
> > including disabling write caching, verifying device driver versions
> > and manufacturer drivers, we're at a loss as to why this continues to
> > happen.
>
> > Disabling write caching does not produce errors, only more hang-ups.
> > So is it a trade-off? Or does someone have any advice or a suggestion
> > I can try?
>
> Return as unfit for their purpose.
>
>
>
>
>
> > RedForeman- Hide quoted text -
>
> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

They are actually "made" for this purpose...

It's the OS that has surpassed the drive technology. Trying to run
NDAS via external enclosures... It works, but has become less
reliable as the laptops and OS'es get faster, the externals don't/
can't...

"RedForeman" <RedForeman@gmail.com> wrote in message news:1180112709.268067.252370@q75g2000hsh.googlegr oups.com
> On May 23, 4:44 pm, "Folkert Rienstra" <see_reply...@myweb.nl> wrote:
> > "RedForeman" <RedFore...@gmail.com> wrote in messagenews:1179948868.899510.282140@k79g2000hse.g ooglegroups.com
> > > I have a NDAS device called a Ximeta 250GB Network Storage. It has a
> > > 8-port ethernet switch that allows multiple connections to the device.
> >
> > > Recently, we had gotten delayed write errors, so after some research
> > > we decided to replace the drive. From WD to Seagate, easy enough...
> > > Only problem is, we're getting the errors again. I work for a company
> > > that employs 10 of these Ximeta drives, and they're all starting to
> > > have it, not 6 months after having the drives replaced.
> >
> > > After more research, finding the numerous possible solutions,
> > > including disabling write caching, verifying device driver versions
> > > and manufacturer drivers, we're at a loss as to why this continues to
> > > happen.
> >
> > > Disabling write caching does not produce errors, only more hang-ups.
> > > So is it a trade-off? Or does someone have any advice or a suggestion
> > > I can try?
> >
> > Return as unfit for their purpose.
> >

> They are actually "made" for this purpose...

But obviously not fit for it.

>
> It's the OS that has surpassed the drive technology.

If so, it would show immediately, not after 6 months.

> Trying to run NDAS via external enclosures...
> It works, but has become less reliable as the laptops and OS'es get
> faster, the externals don't/ can't...

On May 25, 4:53 pm, "Folkert Rienstra" <see_reply...@myweb.nl> wrote:
> "RedForeman" <RedFore...@gmail.com> wrote in messagenews:1180112709.268067.252370@q75g2000hsh.g ooglegroups.com
> > On May 23, 4:44 pm, "Folkert Rienstra" <see_reply...@myweb.nl> wrote:
> > > "RedForeman" <RedFore...@gmail.com> wrote in messagenews:1179948868.899510.282140@k79g2000hse.g ooglegroups.com
> > > > I have a NDAS device called a Ximeta 250GB Network Storage. It has a
> > > > 8-port ethernet switch that allows multiple connections to the device.
>
> > > > Recently, we had gotten delayed write errors, so after some research
> > > > we decided to replace the drive. From WD to Seagate, easy enough...
> > > > Only problem is, we're getting the errors again. I work for a company
> > > > that employs 10 of these Ximeta drives, and they're all starting to
> > > > have it, not 6 months after having the drives replaced.
>
> > > > After more research, finding the numerous possible solutions,
> > > > including disabling write caching, verifying device driver versions
> > > > and manufacturer drivers, we're at a loss as to why this continues to
> > > > happen.
>
> > > > Disabling write caching does not produce errors, only more hang-ups.
> > > > So is it a trade-off? Or does someone have any advice or a suggestion
> > > > I can try?
>
> > > Return as unfit for their purpose.
>
> > They are actually "made" for this purpose...
>
> But obviously not fit for it.
>
>
>
> > It's the OS that has surpassed the drive technology.
>
> If so, it would show immediately, not after 6 months.
>
>
>
> > Trying to run NDAS via external enclosures...
> > It works, but has become less reliable as the laptops and OS'es get
> > faster, the externals don't/ can't...- Hide quoted text -
>
> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

Ok, thanks anyway... you're obviously right... duh?