Munish Chopra wrote:
>
> On Wed, May 30, 2001 at 02:45:16PM -0400, Jason Andresen wrote:
> > One interesting theory on there was that the drives were overheating and
> > somehow damanging themselves. Although this doesn't seem too likely,
> > I wonder if it isn't a catalyst.
> >
> > Truthfully,
On Wed, May 30, 2001 at 02:45:16PM -0400, Jason Andresen wrote:
> Munish Chopra wrote:
> > I just finished reading this:
> >
> > http://www.storagereview.com/jive/sr/thread.jsp?forum=1&thread=13134
> >
> > ...it's a message board at a pretty decent storage site. There aren't
> > too many great p
Munish Chopra wrote:
> I just finished reading this:
>
> http://www.storagereview.com/jive/sr/thread.jsp?forum=1&thread=13134
>
> ...it's a message board at a pretty decent storage site. There aren't
> too many great posts, but what seems to be pretty consistent is that the
> problems arise (in
On Wed, May 30, 2001 at 11:08:28AM -0400, Brian Reichert wrote:
> On Tue, May 29, 2001 at 11:46:04PM -0700, Peter Wemm wrote:
> > Mike Silbersack wrote:
> > > Unfortunately, it sounds like you're not alone. If you check out various
> > > hardware message boards, there are people hopping mad about
I went through some of those messages myself. I didn't read any IBM
technical reps, only marketing dweebs who told people that it was
the controller, which is bullshit. PC motherboard controllers do not
cause hard read errors on disks.
In my case it was a hard-read error on
On Wed, 30 May 2001, Brian Reichert wrote:
> On Tue, May 29, 2001 at 11:46:04PM -0700, Peter Wemm wrote:
> > Sounds like the DTLA series drives.. The biggest piles of junk I've seen!in
> > quite a while.
>
> Could someone give me a pointer to a current discussions concerning
> these drives? I'v
On Tue, May 29, 2001 at 11:46:04PM -0700, Peter Wemm wrote:
> Mike Silbersack wrote:
> > Unfortunately, it sounds like you're not alone. If you check out various
> > hardware message boards, there are people hopping mad about recent IBM
> > drives having a high failure rate. :|
> >
> > But they
Mike Silbersack wrote:
>
> On Mon, 28 May 2001, Matt Dillon wrote:
>
> > Yah, I figured that out... I hadn't even considered it could happen wit
h
> > a brand new IBM drive! Ah well... back to the
> > tried-and-true-but-run-slightly-hot seacrates.
> >
> >
On Mon, 28 May 2001, Matt Dillon wrote:
> Yah, I figured that out... I hadn't even considered it could happen with
> a brand new IBM drive! Ah well... back to the
> tried-and-true-but-run-slightly-hot seacrates.
>
> -Matt
Unfortunately,
:> SetAttrs ports/emulators/sim6811/pkg-comment,v
:> SetAttrs ports/emulators/sim6811/pkg-descr,v
:> SetAttrs ports/emulators/sim6811/pkg-plist,v
:> TreeList failed: Read failure from "/usr/sup/ports-all/checkouts.cvs": Input/output
:error
:
:This is an I/O error happening on your own system w
In article <[EMAIL PROTECTED]>,
Matt Dillon <[EMAIL PROTECTED]> wrote:
> Not sure who to notify here... I tried twice, this looks like a
> real error.
>
> -Matt
>
> /usr/local/bin/cvsup -g -r 20 -L 2 -h cvsup.freebsd.org
>/usr/share/examples/cvsup/cvs-sup
Oops. The I/O error is on my machine , not cvsup :-)
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Not sure who to notify here... I tried twice, this looks like a
real error.
-Matt
/usr/local/bin/cvsup -g -r 20 -L 2 -h cvsup.freebsd.org
/usr/share/examples/cvsup/cvs-supfile
SetAttrs ports/emulators/sim6811/distinfo,v
SetAttrs ports/emulators/sim681
13 matches
Mail list logo
