Re: Beginning to think about VMware and SCO 5.0.5
- From: "Steve M. Fabac, Jr." <smfabac@xxxxxxx>
- Date: Fri, 27 Jun 2008 01:33:10 -0500
Bob Bailin wrote:
"Steve M. Fabac, Jr." <smfabac@xxxxxxx> wrote in message news:4862CF7E.7030205@xxxxxxxxxxBob Bailin wrote:Steve,By smaller, are you referring to 2.5" drives?
A newer RAID supporting SCO and switching over to
RAID10 using smaller, faster 15K drives will provide
an additional boost, along with a Quantum DDS5 tape
No, just 36 or 72GB 15K drives instead of 200GB drives.
Raid-10 is total overkill for this application. The systems
are running with RAID1 on two 36G drives with 14G remaining
un-assigned drive space.
Besides, I am now gun shy of SCSI RAID: On 6/12 I was called at 19:50
when they had been down for 4 hours after losing building
power. They tell me that the servers had all been shutdown
before the UPS batteries ran down.
I don't believe it, unless they shutdown the system without actually
powering it off manually. When was the last time this server was
powered down before this?
May 27 22:23:36 xxxreal syslogd: restart
May 27 22:23:36 xxxreal SCO OpenServer(TM) Release 5
May 27 22:23:36 xxxreal
May 27 22:23:36 xxxreal (C) 1976-1998 The Santa Cruz Operation
, Inc.
[snip the details]On 6/19, I added three new Seagate 15K 146G disks to the
mix by removing Fujitsu disk ID0 from the primary system and
installing one of the 15K disks and allowed the controller rebuild from
the 36G disk at ID1. I installed a 15K disk in the backup system
at ID1, shutdown and created a RAID1 out of the 36G 10K Seagate
at ID0 and the new 15K disk at ID1. Both RAID's completed the
rebuild and went "optimal."
During the night of 6/19 they lost power again after the night
shift had left. The UPS(s) battery ran down. The next morning, None
of the disks would come up. All showed "no media" for the block size
in the RAID controller setup screen. All drives connected to
the Adaptec 29160 controller POST'ed as "Failed Start Unit Request."
So, in two weeks we lost four of the original six 10k 36G Seagate drives,
Two new Fujitsu 10K 36G drives, the remaining two original 10K 36 Seagate
drives, and three new 15K 146G Seagate drives. All these drives
report "Failed Start Unit Request."
How the hell can all the disks in two servers go bad in less then
two weeks? So I'm a little shell shocked and gun shy concerning
RAID10 at this time.
I would be more concerned with how your UPS handles a power loss
situation after the batteries have run down. It should cut the output
power cleanly, swiftly and permanently when the battery charge
reaches a certain level. It shouldn't power on automatically when
the power resumes. And it shouldn't try to extend the battery life
by outputting a lower voltage. Consider testing the backup system
by cutting the power to its UPS at the breaker (not by pulling
the plug) and monitoring the results until complete power down.
You didn't mention whether the SCA cages were internal or
external. If external, were they plugged into the same UPS?
SuperMicro SC742S-400 (400W PS) 6 internal SCA hot_swap cages
In either case, are the drives configured to spin up with a delay
or on receipt of a Start Unit command from the hba? This is one
way to get around an inadequate power supply that can't handle
the initial startup currents all at once, killing the drives by rapidly
cycling the power.
Bob
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
.
- References:
- Re: Beginning to think about VMware and SCO 5.0.5
- From: Steve M. Fabac, Jr.
- Re: Beginning to think about VMware and SCO 5.0.5
- From: Bob Bailin
- Re: Beginning to think about VMware and SCO 5.0.5
- Prev by Date: Re: rusty at shell functions
- Next by Date: Re: OSR 6.0.0 MP3 installation errors
- Previous by thread: Re: Beginning to think about VMware and SCO 5.0.5
- Next by thread: rusty at shell functions
- Index(es):
Relevant Pages
|
