RE: Re: Windows Home Server - jesus!

[Jonathan Twyford <ukha@xxxxxxxxxxxxxxxxx>]

One problem I have found with on board hard drive controllers is if you
install the manufactures drivers it can cause a problem for whs to get some
of the information from the drives (i.e. Temperature, transfer speed, disk
failure). I had a problem with one of my drives (750MB) that could not be
added until I uninstalled the manufactures drivers and let whs use its own
drivers.

I don't know if this is of any help.

Jon.

-----Original Message-----
From: Phil Harris <phil@xxxxxxx>
Sent: 16 December 2008 13:43
To: ukha_d@xxxxxxx
Subject: RE: [ukha_d] Re: Windows Home Server - jesus!

Basically the Mac Mini solution was getting unwieldy ... too many noisy
external drive boxes, too many cables looping in and out of too many
bridgeboards and given that I'd had to sell the house (one of the few
downsides of shedding the missus) I just didn't have the room for that
solution any more. I also wanted to go gigabit (the old Mac Mini didn't
have
Gigabit) and I also wanted to go for SATA / eSATA rather than firewire.

I *HAVE* however been considering whether it's possible to get the old Mac
Mini based solution up and running again as it did work so damn well ...

I think I've found what's caused the problem with WHS though ... I'm
guessing it's a bug but I can add 1Tb drives to the nForce SATA controller
that's built into my motherboard with no problems but as soon as I add more
than one 1Tb drive to the Marvel controller that's built into the
motherboard (and remember all these 1Tb drives are the same make and model)
then WHS thinks that the previous 1Tb drive has failed and marks it as
unavailable. :-(

*sigh*

Phil



[The entire original message is not included]

------------------------------------

********************************************
Limited Time Offer - Free iPhone VAT Calculator
http://berble.com/index.php/component/content/article/109
********************************************