The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Compaq Proliant 2500R power supply blown up!



I have a Compaq proliant server sat in my node 0. (brought it from Geriant
via this list and it has behaved impeccably since then.)

It runs the mp3 database for my collection of Rio's. The homevision software
and a email mailing list for a small coldwar historical society. I've been
doing a lot of work on the list and the backup copy of a month old is too
out of date for the other machine that acts as a standby. (Must automate my
backups! <g>)

Last night I lost power to the house and the power supply didn't survive the
switch on. (it's via a ups)

This morning took the machine apart, replaced the fuse inside the
powersupply hooked it back upto the mains and enjoyed a brief November 5th
fireworks display!

Does anyone have a spare power supply avaible for sale? Even a spare 2500R
(it needs to be the rack mountable version)

The part number of the supply is 270236-001 or the replacement number is:
270241-001

Otherwise I guess I will be fedexing a psu over from the US late on
Monday.....

The data is stored on a Scsi Raid 5 array, I hope and would believe that it
survived the first blow up, I had disconnected the array's data and psu
cables before I played with the psu.

Open to any ideas! <g>

Regards

Richard


http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx
List of UKHA Groups here - http://groups.yahoo.com/group/UKHA_Grouplists/


Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.