Re: [cobalt-users] Qube3 Disk Failure

["E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>]

MM> Date: Wed, 24 Apr 2002 11:04:11 +1000
MM> From: Malcolm McLeary <mmcleary@xxxxxxx>


MM> I replace the drive with a new one ... it did its RAID thing and all seemed
MM> well.  There were some problems with FileMaker Server serving databases, but
MM> it may not have been happy with the RAID process copying open files.  I
MM> guess I should have stopped FileMaker Server during the mirroring process.

RAID 1 does not work at the file level.  It does not copy files.
It creates a pseudodevice that looks and feels like a normal hard
drive.


MM> Anyway I've just copied some large files to the Qube3 (it is running OS
MM> Update 6.4) and it has once again reported a drive failure ... same drive
MM> letter ... but a new disk!  This is too much of a coincidence.

Odd.  Unless it's a low-quality hard drive line.  I had a client
who purchased a 20GB Quantum 7200RPM drive... flaky on arrival.
Confirmed bad with Maxtor disk test software.  Replacement drive
worked great, testing clean with diagnostic software, until I
delivered their machine.  It then failed to even boot.  (Note to
self: Machine failure at 2300 results in severe lack of sleep
while rebuilding overnight.)

YMMV, of course, but it can happen.


MM> Is it possible that its not the drive which is failing, but its the RAID
MM> software ... or OS Update 6.4?

I'd suspect the drive cable or controller.

Have you another Qube3?  Can you move the known-good drive to it,
then try mirroring with a "bad" drive?


--
Eddy

Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.

These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.